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.

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.

Cheer

On Mon, Jun 15, 2015 at 2:10 AM, Paul Merlin <[email protected]> wrote:

> Niclas Hedhman a écrit :
> > I suggest org.apache.zest
> Yeah, maybe it would be simpler to register org.apache.zest at
> repositories.apache.org. WDYT?
>
> But, looking at actual artifacts "hierarchy" and our build system
> organization it seems we should use org.apache.zest.qi4j for Qi4j
> artifacts.
>
> groupIds:
>
> org.apache.zest.qi4j.core
> org.apache.zest.qi4j.libraries
> org.apache.zest.qi4j.extensions
>
> artifactIds:
>
> org.apache.zest.qi4j.core.api
> org.apache.zest.qi4j.core.runtime
> org.apache.zest.qi4j.library.something
> org.apache.zest.qi4j.extension.whatever
> ...
>
> Yes, they are quite long as we pay the Apache > Zest > Qi4j umbrellas
> chain. Group & Artifact IDs should reflect our organization, that is
> Qi4j is a subproject of Zest. It will also pave the way for future
> subprojects like Qi4cs.
>
> Would that be ok for you guys? Or you do have a shorter suggestion?
>
> Cheers
>
> /org.apache.zest.qi4j.Paul :)
>
>
>


-- 
Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java

Reply via email to