I went through most of the projects and updated their Maven coordinates. wildfly-swarm needs more attention but may be not related to this. Also updated couple references in the document in in the archtypes section.

I did not see any reason to modify the JBoss modules names, the main aim was with frameworks that are using the maven directly like spring-boot and wildfly-swarm. If there is an issue when we check the wildfly-swarm stuff we will reconsider this, as this will touch lot more in terms of documents and scripts etc.

I did find that 10.0.0.Alpha2 version did not build the jdbc and admin jar, I corrected it now.

If there are no more issues I ready to resolve this.

Do you want to similarly update our other projects?

Also you want to keep the jboss module names using the old convention correct?

With these updates it looks like I've been successful with the build.

Ok, for now I've just updated the release plugin to use the final-release profile so that I can get out Alpha2. We may want to rename release to local-release to clarify it's purpose. It does also look though that we'll need to update the jenkins build - http://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/Teiid-WeeklyBuild/323/

The maven central is making gpg signing mandatory, so I was not sure how a ci/cd system can provide one. I couldn't find any references, so I did a different profile. May be there is way

Is there a reason to use a separate profile? Since this overrides the distribution management, it affects maven deploy run in the release profile as well - which has caused the weekly build not to run. Also the release plugin only knows to use the release profile (which can of course be changed).

A new profile called "final-release" has been added to the Teiid pom.xml, this profile needs to uses the PGP signing and Javadoc requirements by Maven Central. Before this profile can be run, please set up a PGP key for yourself using directions here [1], then add following code snippet in your private settings.xml file

<servers>
      <server>
        <id>oss.sonatype.org</id>
        <username>{sona-type-user-name}</username>
        <password>{sona-type-password}</password>
      </server>
   </servers>

  <profiles>
    <profile>
      <id>teiid</id> 
      <properties>
        <gpg.homedir>/home/rareddy/.gnupg</gpg.homedir>
        <gpg.keyname>{pgp-key-name-generated}</gpg.keyname>
        <gpg.passphrase>{key-password}</gpg.passphrase>
	<gpg.executable>gpg</gpg.executable>
      </properties>
    </profile>
</profiles>
  <activeProfiles>
    <activeProfile>teiid</activeProfile>
  </activeProfiles>

[1] http://central.sonatype.org/pages/working-with-pgp-signatures.html

I logged https://issues.sonatype.org/browse/OSSRH-33284 and given access to maven central using following coordinates

Configuration has been prepared, now you can:
Deploy snapshot artifacts into repository https://oss.sonatype.org/content/repositories/snapshots
Deploy release artifacts into the staging repository https://oss.sonatype.org/service/local/staging/deploy/maven2
Promote staged artifacts into repository 'Releases'
Download snapshot and release artifacts from group https://oss.sonatype.org/content/groups/public
Download snapshot, release and staged artifacts from staging group https://oss.sonatype.org/content/groups/staging

As part of this, the maven groupId of all the projects in Teiid will also be modified and loosing the "jboss" in them. For example "org.jboss.teiid" will become "org.teiid"

Try contacting jboss.org for greater nexus rights.