Hi Jason, Examples: 1) In our current m2 build we have a specialized "rpm build" which lays out 4 separate plugins that play into 4 different phases of the build. Together they form a system. Each of these plugins is parametrized, such that using artifactId, etc, they have enough information to do their job. This set of plugins is general enough to apply to a wide range of projects. I don't want to repeat the plugin definitions in each project. Of course, this system is being fleshed out, which is why I'm writing this ;-)
2) In m1 I have a build system which builds Java web services. It slips many extra goals into the standard maven Java build sequence (e.g. WSDL2Java, copy extra test resources, company specific stuff, etc.) I collect these goals into a single maven build file which is imported (using jelly:core import) into a project's vanilla maven.xml. This way I control the build process for my many "clients" -- who ultimately just want to type "maven" and don't really care what or how it gets built -- as long as it builds correctly. When I port this to m2, I need something similar -- a composite representing a complete, reusable build solution. Does this make sense?? Thanks, -- Chris On 10/18/05, Brill Pappin <[EMAIL PROTECTED]> wrote: > > I've got one for you... I used to have a m1 goal that called several other > goals while preparing for a release... the idea was to make a repetitive > task (executing several goals) simple by executing one goal. > > Since I no longer have the maven.xml. I'd love to be able to set up a > "composit" plugin where I could define a set of goals to execute. > > - Brill Pappin > > On 10/19/05, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > > > On Tue, 2005-10-18 at 22:00 -0500, Chris Berry wrote: > > > Greetings, > > > Is it possible to write a "plugin of plugins"?? I.e. a plugin that is > > simply > > > a composite of other plugins. > > > > > > To make this concrete, imagine that you have a common set of plugins > > that > > > are used across many projects -- together forming a common build > system. > > For > > > example, in project A you have > > > > > > <plugins. > > > <plugin/> ..... plugin X at phase 1 > > > <plugin/> ..... plugin Y at phase 5 > > > <plugin/> ..... plugin Z at phase 7 > > > <plugins> > > > > Do you have a concrete example which may help me understand what you're > > trying to do before I respond. Looks like you're trying to provide > > solution before we know what you're really trying to do. > > > > -- > > jvz. > > > > Jason van Zyl > > jason at maven.org <http://maven.org> <http://maven.org> > > http://maven.apache.org > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
