Hi, When releasing the Maven archetypes I was reminded that we build all the Maven stuff with the main reactor POM.
IMO the tooling part is not part of the Sling product like the bundles / tests / launchpads. They participate in building the product, but they are not needed in the same reactor. Also, we can't consume SNASPHOT Maven plugins as part of the same reactor. So I would suggest that we move the tooling/maven out of the main reactor, with the following changes: 1. Remove all tooling/maven stuff out of the main reactor 2. Create a reactor pom for tooling/maven which builds the plugins 3. Create a reactor pom for tooling/maven/archetypes which builds the archetypes 4. Include tooling/maven/archetypes as a module of tooling/maven 5. Create a separate sling-tooling-trunk-1.7 build on Jekins Advantages: 1. Slightly faster builds ( have not really measured ) 2. The main reactor does not break when the tooling/maven one breaks ( like I did earlier :-) ) Thoughts? Robert
