I have no strong opinion about it. I just note that it is "should" and not "must", and compatibility is always a reasonable excuse.
Are you suggesting that only the GroupId will be changed, and that the artfacts are still called org.qi4j.core.api-2.1.jar ? Niclas On Mon, Jun 15, 2015 at 3:56 PM, Paul Merlin <[email protected]> wrote: > Niclas Hedhman a écrit : > > Second thought... Let's do like this; Keep the existing groupId for 2.x > > releases, and we can re-open this discussion for 3.0. > It seems we can't use org.qi4j as a groupId. > > http://www.apache.org/dev/publishing-maven-artifacts.html > > Maven Group Ids: a list of the groupIds for this project. > > They should all be subgroups of org.apache > > > The qi4j.org domain name is being transferred to ASF at the moment > (note to > > self; need to check the hold up), on the grounds that we will be able to > > keep compatibility as long as we want. > What we're talking about here is the maven coordinates of the Apache > Zest Qi4j artifacts. For 2.1 we could use new ones but keep the java > packages as is to keep compatibility. It would means that developpers > using 2.0 and wanting to update to 2.1 will only have to change maven > coordinates, not imports in source code. > > Question is still open. > > Cheers > > /Paul > > -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java
