Hi John,
Am 14.09.11 22:53, schrieb John E. Vincent: I was hoping
someone could help me with a couple of issues in a multi-project
build. I'm attempting to convert this from Maven2. I'm also not in a
position to radically change the directory structure and artifact
names. Also I'm not a java developer (just ruby and python) so please
consider that ;) For reference:
https://gist.github.com/3f71c7e8ea55c35168af Above is a pretty
standard build with subprojects. Everything is working perfectly with one
exception which leads to my first question: How to I stop
generating an empty jar file in 'common/dao/build/libs'? On the
first sight, I don't why this empty jar is created. Can you provide
the output of "gradle tasks --all" of your multiproject build.
The common-dao I WANT is in 'common/dao/common/build/libs'
and dao is obviously just a containing folder)? I've seen
the references to the gradle project's build.gradle and 'def
groovyProjects()' but I'm just not up to my groovy and
gradle skills yet to parse that myself. The second
question is more of a shortcut one: What's the best way to
DRY up the dao:* subproject specific settings. There's
obviously a pattern there that I can address
programatically. I'm guessing some sort of array and
iterator would be involved but again, my groovy isn't there
yet. Thanks again. I've only been working on converting
this for a day now. I think that speaks volumes about the
approachability and friendliness of Gradle. -- View this
message in context:
http://gradle.1045684.n5.nabble.com/Help-with-two-issues-tp4804406p4804406.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
-- ----------------------- regards René rene groeschke
http://www.breskeby.com @breskeby
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
