I have submitted a new feature which allows a configuration to return
the dependency files only for a subset of the dependencies belonging
to this configuration.
configuration.files(someSpec) or with lazy resolving:
configuration.fileCollection(someSpec) // I could not come up with a
better name than fileCollection. I'm very happy to hear about a better
name.
This is a pretty important feature. The way we have solved this so far
is to use a copy of the configuration. But in case of version
conflicts between dependencies of the subset and dependencies not
contained in the subset, the resolve result of a copy versus the new
methods is different. As part of this I have changed the way we
extract the dependency files from ivy. Of course all tests are running
but I'm keen to get feedback if this has changed the behavior in any
way.
Currently there is one limitation. Let's say we have the following
dependencies:
A->B(exclude C)->C
X->C
configuration.files(A) returns: A,C It should be: A
This is because C is part of the configuration. I haven't figured out
a good way yet to get the right information from Ivy via its public
API to return the right result.
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
