Hi, Bertrand Delacretaz schrieb: > Hi, > > The full Sling build currently fails (in the launchpad/app module) if > the org.apache.sling.extensions.threaddump bundle is not present in > one's local Maven repository, instead of building that threaddump > module first. Maven tries to build launchpad/app before > extensions/threaddump, that's wrong. > > In launchpad/app/pom.xml, the org.apache.sling.extensions.threaddump > is only listed in the maven-dependency-plugin config, so it does not > appear when running mvn dependency:resolve for example - which > explains why the Maven reactor doesn't see the dependency. > > Listing org.apache.sling.extensions.threaddump as an explicit > <dependency> in that pom would fix things, but is there a simpler way?
I have created https://issues.apache.org/jira/browse/SLING-815 to track this. I also have tested it on my (linux) box: * removed all sling artifacts from my local m2 repository * run mvn clean in the root folder --> reactor seems clean extensions/threaddump before launchpad * run mvn clean install in the root folder --> reactor seems to build threaddump before launchpad So it seems, that if the module is registered in the root pom (as I have done in Rev. 732275 and no further dependency registration is thus required. For now, I add these observations to the issue and we may follow-up if more informations becomes available. Thanks. Regards Felix
