Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 1.2-M4
-
Fix Version/s: 1.2-RC1
-
Component/s: None
-
Labels:None
Description
When using a local resolver mavenLocal() and/or pom resolver, any dependencies that are stored in the local maven repository ~/.m2 are resolved, but their transitive dependencies are not.
This is very crucial I think, especially when working in an environment when local modules are used. For example in many projects, you'll have a few components build using maven and they are installed locally during install phase. Maven resolves those correctly, along with their transitive dependencies. Grails/Ivy seems to not. At least the local file resolver and pom resolver seem to ignore transitive deps for any local packages.
I added the mavenLocal() support back a few releases ago and I'd look into this issue, but I'm not sure if I'll have time. I think this is an ivy issue. Seems like file resolver doesn't enforce transitive dependencies. I'm wondering if we should use a different resolver? Maybe dual? I can't seem to find ivy documentation about this, so wondering if someone knows a bit more about how these resolvers work.
Thanks.
Ilya
This thread might help: http://markmail.org/message/wkhaubkqhkdf4hbu#query:ivy%20maven%20local%20resolver+page:1+mid:blvoe7aqja5ngwx5+state:results