Hi,
A freshly starting build (.gradle removed, gradle clean called) downloads
some of a client module dependencies, but does not others (not even
resolving is attempted). The compile step then fails not founding classes.
If after this, all dependencies are uncommented except the missing one, this
missing one is downloaded, too (of course the compilation fails, because now
the others are not on the classpath).
Enabling all the dependencies restores the original state: the jar that was
missing is absent again from the classpath, compilation fails.
A custom repo is used with no descriptors.
This is the problematic definition couple, that is part of a client module
dependency definition:
dependency(':apache-river:2.1.1') {
artifact { name='jsk-platform' ; type='jar' }
}
dependency(':apache-river:2.1.1') {
artifact { name='jsk-lib' ; type='jar'
}
I observed that the last one is ignored (changing their order clearly shows
it).
I would consider it a bug. I see no easy workaround, putting all the jars
into different dirs tedious (there are many jars under this package).
Any other idea would be welcome!
Zsolt
Ps. Perhaps I should use a repo structure which more of Maven-like, because
the current layout is somewhat ad-hoc: [module]/[revision]/artifacts...?
--
View this message in context:
http://old.nabble.com/partially-handled-client-module-dependencies-tp27335632p27335632.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
