On Mon, Feb 28, 2011 at 2:45 AM, Peter Niederwieser <[email protected]> wrote:
> Dependency entries in the POM seem to be constructed from their corresponding
> org.gradle.api.Project objects. So the only solution I can see at the moment
> is to change the projects' names to match the desired artifact IDs. Probably
> worth an issue.
Possibly. However, I took the bull by the horn, worked out a new
naming convention and convinced the community it is worth while.
So, in settings.gradle I build up the project names by prepending the
parent's name (plus a bit mangling), then in build.gradle.allprojects
I set the project.group to name.substring(0,name.lastIndexOf('.'))
(can probably be expressed more elegantly). This gives me good enough
names in the Maven space;
groupId=org.qi4j.libraries
artifactId=org.qi4j.library.constraints
The 'downside' is more expressive project() dependencies within the project;
compile project( ":libraries:constraints" )
became
compile project( ":org.qi4j.libraries:org.qi4j.library.constraints" )
but good enough compromise for now.
Cheers
--
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java
I live here; http://tinyurl.com/3xugrbk
I work here; http://tinyurl.com/24svnvk
I relax here; http://tinyurl.com/2cgsug
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
