[Sculptor 3] Group ID of all Maven artifacts (plugin, archetypes and dependencies) renamed to "org.sculptorgenerator"

19 views
Skip to first unread message

Torsten Juergeleit

unread,
Sep 29, 2013, 4:45:26 PM9/29/13
to fornax-...@googlegroups.com
Due to the artifact coordinate requirements for publishing to Maven Central the group id of Sculptors Maven artifacts (plugin, archetypes and dependencies) was renamed to "org.sculptorgenerator" (issue #26). The renamed artifacts are deployed to the snapshot Maven repository on GitHub.

Now we have to fulfill all the other requirements (information in POMs, signed jars, attached source / javadoc, ...). I started to work on the corresponding issue #60.

@Pavel, Ron, please add you preferred email within your <developer/> tag in parent POM. To publish signed jars to Maven Central for this email a GPG public key must be publicly available as described here, e.g. mine can be found here.

/Torsten

Pavel Tavoda

unread,
Sep 30, 2013, 4:24:10 AM9/30/13
to fornax-...@googlegroups.com
On Sunday, September 29, 2013 10:45:26 PM UTC+2, Torsten Juergeleit wrote:
@Pavel, Ron, please add you preferred email within your <developer/> tag in parent POM. To publish signed jars to Maven Central for this email a GPG public key must be publicly available as described here, e.g. mine can be found here.

Till I will rely with deployment on you, I don't need this, am I right?
Can we somehow manage that travis will do it for us?

Torsten Juergeleit

unread,
Sep 30, 2013, 8:53:07 AM9/30/13
to fornax-...@googlegroups.com
Till I will rely with deployment on you, I don't need this, am I right?

Regarding the publicly available GPG public key - yes. Regarding adding your prefered email to the parent POM - no (this is validated by Sonatypes publish process within Nexus).



Can we somehow manage that travis will do it for us?

Nope, publishing artifacts should be a manual process triggered by someone who has its private GPG available for signing the JARs.

/Torsten

Pavel Tavoda

unread,
Oct 2, 2013, 9:59:47 AM10/2/13
to fornax-...@googlegroups.com
Are you going to automatize signing with maven plugin?

Torsten Juergeleit

unread,
Oct 2, 2013, 12:04:44 PM10/2/13
to fornax-...@googlegroups.com
Are you going to automatize signing with maven plugin?

Sure, as part of the command line execution of the release build process the passphrase of the GPG key is retrieved from settings.xml.

/Torsten
Reply all
Reply to author
Forward
0 new messages