Hi tinca,
I think the easiest way to get the groovy-all-1.6-RC-1.jar resolved in
your setup, is to add a second pattern like this:
http://our.www.server/librepo/[organisation]/[revision]/[module]-[revision].[ext]
this adds the revision to the jar file name.
now you should be able to resolve groovy via groovy:groovy-all:1.6-RC-1
This adds the revision to the jar file name. Now you should be able to
resolve groovy via groovy:groovy-all:1.6-RC-1
cheers,
René
tinca wrote:
...
Now, most of my dependencies gets resolved except the groovy one which
gives:
http://our.www.server/librepo/groovy/1.6-RC-1/groovy.jar
The jar should contain the revision however: groovy-all-1.6-RC-1.jar
Is it possible at all to mix client module transitive dependencies where
some may contain revision in the artifact name and some are not? If I
remember well, in an other type of dependency gradle makes efforts to find
artifact with both versioned and unversioned forms.
If not possible, then the only way to go repo has to contain revisioned
jars, right?
..
This is just to show the details of the resolving process:
module not found: groovy#groovy;1.6-RC-1
==== clientModule: tried
==== internal-repository: tried
/project/path/.gradle/internal-repository/groovy/groovy/ivy-1.6-RC-1.xml
-- artifact groovy#groovy;1.6-RC-1!groovy.jar:
/project/path/.gradle/internal-repository/groovy/groovy/jars/groovy-1.6-RC-1.jar
==== ourRepo: tried
http://our.www.server/librepo/groovy/1.6-RC-1/groovy.xml
-- artifact groovy#groovy;1.6-RC-1!groovy.jar:
http://our.www.server/librepo/groovy/1.6-RC-1/groovy.jar
ourRepo contains no descriptors.
Zsolt
--
------------------------------------
Rene Groeschke
[email protected]
http://www.breskeby.com
------------------------------------
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
