Hani Suleiman wrote:
>
> I have a project where dependencies are composed of a number of files (not
> just jar files) that I need unpacked and included as sub projects, and was
> wondering what the best approach for this is.
>
What do you mean by "dependencies that I need [...] included as sub
projects"?
Hani Suleiman wrote:
>
> The solution I'm pondering is declaring the dependencies in buildSrc, then
> having a task in there to unpack them all under the project's root dir
> from the gradle cache.
>
> Is this the right approach? Is there a better way of declaring
> dependencies that need to be unpacked/included in the build?
>
Doesn't sound like the right approach. Does zipTree and/or tarTree solve
your problem?
dependencies {
compile zipTree(...), tarTree(...)
}
--
Peter Niederwieser
Principal Engineer, Gradleware
http://gradleware.com
Creator, Spock Framework
http://spockframework.org
Twitter: @pniederw
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Subprojects-as-dependencies-tp4622761p4622862.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
