nope, not correct

both JBoss Nexus and Sonatype do have "org.jboss.aerogear"

However, for recently created projects (e.g. the kafka-cdi xtension) we did pick "org.aerogear".

If you wanna deploy to OSSRH, than you need to do some overrides (e.g. distributionManagement) and also not 100% sure the parent works.

That said, there is no need to do any change on the groupIds 

On Thu, Sep 28, 2017 at 9:59 AM, Ali Ok <aliok@redhat.com> wrote:
Hello,

In order to make things compatible with https://oss.sonatype.org Nexus, we need to change the group id from "org.jboss.aerogear" to "org.aerogear" for various components.

I will only touch AeroGear Digger related things, not everything.

Just a heads up!

Cheers,
Ali

On Wed, Sep 27, 2017 at 10:57 AM, Matthias Wessendorf <matzew@apache.org> wrote:
+1 

no issues here

On Wed, Sep 27, 2017 at 9:47 AM, Ali Ok <aliok@redhat.com> wrote:
Hi,

I am currently working on setting up a proper release procedure for Digger Java client [1].

While at it, I would like to rename the Git repo from "digger-java" "digger-java-client".

Any objections?


Cheers,
Ali

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf