On Wed, Sep 5, 2012 at 5:01 PM, Kristian Rosenvold <kristian.rosenv...@gmail.com> wrote: [del] > Which makes me think we should consider such a switch an opportunity > to re-think some of our tooling > around multi-module projects. What the 99% others want (who're not > setting up a CI) is a checkout algorithm that builds the *vertical* > stack for a given plugin, not the horizontal top-level stack for all > the plugins (which is what we have currently). So if I checkout > "maven-ear-plugin", I would basically want something like this: > root-dir\ > maven-ear-plugin\ > maven-archiver\ > maven-filtering\ > plexus-archiver\ > plexus-utils > .. maybe more.. (probably configurable somewhere)
I've lost count of the times I've been bug hunting starting at the plugin where the problem occurs and had to pull in dependencies until I have found the problem. Even if the repository doesn't allow this, tooling to help checkout as you describe would be great. Especially when things live in shared, plexus, plugins etc its a manual PITA looking at poms for scm sections and then checking them out. At least a re-think of the structure would help in understanding/explaining why things live where. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
