No exceptions. As I mentioned in my follow up message. The problem was
solved by moving the java plugin declaration from allprojects{} to
subprojects{} .-leo On Wed, Mar 16, 2011 at 11:03 PM, Adam Murdoch <[email protected]>wrote: > > On 17/03/2011, at 5:11 AM, leo wrote: > > I am porting an open source project (http://s4.io) from Maven to Gradle. > When > I ran the install task I couldn't get the subprojects to install jars in > the > local maven repo. > > > Do you have some more details? For example, was there an exception > reported? > > > By chance I discovered that if I inject archivesBaseName = > project.name to the subprojects, the jar gets installed as expected. Just > curious if I am doing something wrong here. Shouldn't the Java Plugin make > all jars part of the archives configuration by default. > > The build script is here: > https://github.com/s4/s4 > > Thanks! > -leo > > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Maven-install-problem-in-multi-level-Java-build-tp3791548p3791548.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 > > > > > -- > Adam Murdoch > Gradle Developer > http://www.gradle.org > Co-Founder and VP of Engineering, Gradleware Inc. - Gradle Training, > Support, Consulting > http://www.gradleware.com > > -- -leo
