Well, one thing looks really nasty, and that is a project() dependency
inside qi4j would be;
compile(project(":org.qi4j.libraries:org.qi4j.library.scripting:org.qi4j.library.scripting.jruby"))
due to the multi-level project structure in scripting;
libraries/
scripting/
jruby/
Should we fix this at the same time and then make it rule not to have
multi-level in the 3 core projects?
Cheers
On Sun, Feb 27, 2011 at 3:26 PM, Niclas Hedhman <[email protected]> wrote:
> Ok,
> I would like to suggest this;
>
> The module NAME (i.e. the artifactId) will be the full qualified name, such
> as;
>
> org.qi4j.core.api
> org.qi4j.library.locking
>
> the group (i.e. groupId) will be the plural names, such as
>
> org.qi4j.libraries
>
> Inside Gradle build the project() dependencies will end up looking like;
>
> compile ":org.qi4j.libraries:org.qi4j.library.locking"
>
> and the Maven path would end up like;
>
> org/qi4j/library/org.qi4j.library.locking/1.3/org.qi4j.library.locking-1.3.jar
>
>
> (Hope I didn't make any mistake in explaining above)
>
>
> Is that reasonable??
>
>
> Note; this is still an incompatible change. But at least it is an
> algorithm without too much if() statements.
>
>
>
> 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
>
--
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
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
