RE: Plugins within plugins: best practices
It can cause problems when you have another plugin artifact listed as your dependency so this probably won't work. -Original Message- From: Kallin Nagelberg [mailto:[EMAIL PROTECTED] Sent: Sunday, December 30, 2007 3:37 PM To: Maven Users List Subject: Re: Plugins within plugins: best practices What about creating a mojo instance manually from within another plugin.. Has anyone tried this? On Dec 29, 2007 11:37 PM, Kallin Nagelberg [EMAIL PROTECTED] wrote: I need to run the unpack and copy goals repeatedly, with given group:artifact:version and different target directories for each one. On Dec 29, 2007 4:23 PM, Brian E. Fox [EMAIL PROTECTED] wrote: Which part is it that you need to use in the dependency plugin? The actual copying and unpacking is mostly delegated to the maven-archiver component. -Original Message- From: Kallin Nagelberg [mailto: [EMAIL PROTECTED] Sent: Saturday, December 29, 2007 4:03 PM To: Maven Users List Subject: Plugins within plugins: best practices Hello everyone, I've created a standalone plugin in which I'm doing some unpacking/copying of artifacts in addition to a few other things. I would like to defer the unpacking/copying operations to the maven dependency plugin for obvious reasons. Has anyone tried creating and configuring a plugin instance within another plugin and calling the execute method directly? I'm tempted to try this, but am worried about potential side effects. I figure I can try to build the plugin instance with what components I've already got within my plugin and pass them along. Is there a better way to use this, perhaps some sort of core maven plugin builder? Any help would be greatly appreciated. Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Plugins within plugins: best practices
What about creating a mojo instance manually from within another plugin.. Has anyone tried this? On Dec 29, 2007 11:37 PM, Kallin Nagelberg [EMAIL PROTECTED] wrote: I need to run the unpack and copy goals repeatedly, with given group:artifact:version and different target directories for each one. On Dec 29, 2007 4:23 PM, Brian E. Fox [EMAIL PROTECTED] wrote: Which part is it that you need to use in the dependency plugin? The actual copying and unpacking is mostly delegated to the maven-archiver component. -Original Message- From: Kallin Nagelberg [mailto: [EMAIL PROTECTED] Sent: Saturday, December 29, 2007 4:03 PM To: Maven Users List Subject: Plugins within plugins: best practices Hello everyone, I've created a standalone plugin in which I'm doing some unpacking/copying of artifacts in addition to a few other things. I would like to defer the unpacking/copying operations to the maven dependency plugin for obvious reasons. Has anyone tried creating and configuring a plugin instance within another plugin and calling the execute method directly? I'm tempted to try this, but am worried about potential side effects. I figure I can try to build the plugin instance with what components I've already got within my plugin and pass them along. Is there a better way to use this, perhaps some sort of core maven plugin builder? Any help would be greatly appreciated. Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Plugins within plugins: best practices
Which part is it that you need to use in the dependency plugin? The actual copying and unpacking is mostly delegated to the maven-archiver component. -Original Message- From: Kallin Nagelberg [mailto:[EMAIL PROTECTED] Sent: Saturday, December 29, 2007 4:03 PM To: Maven Users List Subject: Plugins within plugins: best practices Hello everyone, I've created a standalone plugin in which I'm doing some unpacking/copying of artifacts in addition to a few other things. I would like to defer the unpacking/copying operations to the maven dependency plugin for obvious reasons. Has anyone tried creating and configuring a plugin instance within another plugin and calling the execute method directly? I'm tempted to try this, but am worried about potential side effects. I figure I can try to build the plugin instance with what components I've already got within my plugin and pass them along. Is there a better way to use this, perhaps some sort of core maven plugin builder? Any help would be greatly appreciated. Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Plugins within plugins: best practices
I need to run the unpack and copy goals repeatedly, with given group:artifact:version and different target directories for each one. On Dec 29, 2007 4:23 PM, Brian E. Fox [EMAIL PROTECTED] wrote: Which part is it that you need to use in the dependency plugin? The actual copying and unpacking is mostly delegated to the maven-archiver component. -Original Message- From: Kallin Nagelberg [mailto:[EMAIL PROTECTED] Sent: Saturday, December 29, 2007 4:03 PM To: Maven Users List Subject: Plugins within plugins: best practices Hello everyone, I've created a standalone plugin in which I'm doing some unpacking/copying of artifacts in addition to a few other things. I would like to defer the unpacking/copying operations to the maven dependency plugin for obvious reasons. Has anyone tried creating and configuring a plugin instance within another plugin and calling the execute method directly? I'm tempted to try this, but am worried about potential side effects. I figure I can try to build the plugin instance with what components I've already got within my plugin and pass them along. Is there a better way to use this, perhaps some sort of core maven plugin builder? Any help would be greatly appreciated. Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Plugins of plugins
Would it be possible to extend the POM inheritance model currently used for merging parent POMs to allow for merging arbitrary POMs? This would allow the plugin configuration to be stored in a single place (possibly retrieved by URL rather than file reference) and allow multiple project trees to reuse it. -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 19, 2005 00:12 To: Maven Users List Subject: Re: Plugins of plugins On Wed, 2005-10-19 at 00:00 -0400, Brill Pappin 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. Fair enough, that's a good use case I think. Essentially what we're talking about here is a way make altering the life cycle very flexible. Exactly what Chris is talking about where you might graft a bunch of mojos/goals into the life cycle. You may want to execute some goals that are not part of the life cycle and some that are. So maybe a plugin with a configuration that allowed you to do this would be the solution. I don't think this would be hard to do but would be good to get a couple more concrete use cases first. - 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.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Plugins of plugins
I can think of another use case. I would like to be able to fire off assembly multiple times from a single command to assemble multiple zips (source, jars, ibiblio bundle). -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 19, 2005 12:12 AM To: Maven Users List Subject: Re: Plugins of plugins On Wed, 2005-10-19 at 00:00 -0400, Brill Pappin 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. Fair enough, that's a good use case I think. Essentially what we're talking about here is a way make altering the life cycle very flexible. Exactly what Chris is talking about where you might graft a bunch of mojos/goals into the life cycle. You may want to execute some goals that are not part of the life cycle and some that are. So maybe a plugin with a configuration that allowed you to do this would be the solution. I don't think this would be hard to do but would be good to get a couple more concrete use cases first. - 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.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Plugins of plugins
So it seems that m2, in it's cutrrent state, has not addressed this use case, right?? So for the time being one must use POM inheritance (i.e. Parent POMs) to share a common build system. BTW: a good way to think about this is aggregation versus inheritance Cheers, -- Chris On 10/19/05, Brian E. Fox [EMAIL PROTECTED] wrote: I can think of another use case. I would like to be able to fire off assembly multiple times from a single command to assemble multiple zips (source, jars, ibiblio bundle). -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 19, 2005 12:12 AM To: Maven Users List Subject: Re: Plugins of plugins On Wed, 2005-10-19 at 00:00 -0400, Brill Pappin 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. Fair enough, that's a good use case I think. Essentially what we're talking about here is a way make altering the life cycle very flexible. Exactly what Chris is talking about where you might graft a bunch of mojos/goals into the life cycle. You may want to execute some goals that are not part of the life cycle and some that are. So maybe a plugin with a configuration that allowed you to do this would be the solution. I don't think this would be hard to do but would be good to get a couple more concrete use cases first. - 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] -- jvz. Jason van Zyl jason at maven.org http://maven.org http://maven.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Plugins of plugins
On Wed, 2005-10-19 at 09:57 -0400, Brian E. Fox wrote: I can think of another use case. I would like to be able to fire off assembly multiple times from a single command to assemble multiple zips (source, jars, ibiblio bundle). We actually discussed changing the assembly plugin to handle creating multiple assemblies with one command. -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 19, 2005 12:12 AM To: Maven Users List Subject: Re: Plugins of plugins On Wed, 2005-10-19 at 00:00 -0400, Brill Pappin 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. Fair enough, that's a good use case I think. Essentially what we're talking about here is a way make altering the life cycle very flexible. Exactly what Chris is talking about where you might graft a bunch of mojos/goals into the life cycle. You may want to execute some goals that are not part of the life cycle and some that are. So maybe a plugin with a configuration that allowed you to do this would be the solution. I don't think this would be hard to do but would be good to get a couple more concrete use cases first. - 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.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Plugins of plugins
On Wed, 2005-10-19 at 09:45 -0500, Chris Berry wrote: So it seems that m2, in it's cutrrent state, has not addressed this use case, right?? So for the time being one must use POM inheritance (i.e. Parent POMs) to share a common build system. Correct, but if we nail down the desired usage I think a plug-in to deal with this could be made in pretty short order. I'll try to write something up later today for people to peruse. BTW: a good way to think about this is aggregation versus inheritance Cheers, -- Chris On 10/19/05, Brian E. Fox [EMAIL PROTECTED] wrote: I can think of another use case. I would like to be able to fire off assembly multiple times from a single command to assemble multiple zips (source, jars, ibiblio bundle). -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 19, 2005 12:12 AM To: Maven Users List Subject: Re: Plugins of plugins On Wed, 2005-10-19 at 00:00 -0400, Brill Pappin 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. Fair enough, that's a good use case I think. Essentially what we're talking about here is a way make altering the life cycle very flexible. Exactly what Chris is talking about where you might graft a bunch of mojos/goals into the life cycle. You may want to execute some goals that are not part of the life cycle and some that are. So maybe a plugin with a configuration that allowed you to do this would be the solution. I don't think this would be hard to do but would be good to get a couple more concrete use cases first. - 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] -- jvz. Jason van Zyl jason at maven.org http://maven.org http://maven.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Plugins of plugins
I think the Composite Pattern would fit nicely here... CompositePlugin implements Plugin AbstractPlugin implements Plugin And CompositePlugin contains an array of Plugins Cheers, -- Chris On 10/19/05, Jason van Zyl [EMAIL PROTECTED] wrote: On Wed, 2005-10-19 at 09:45 -0500, Chris Berry wrote: So it seems that m2, in it's cutrrent state, has not addressed this use case, right?? So for the time being one must use POM inheritance (i.e. Parent POMs) to share a common build system. Correct, but if we nail down the desired usage I think a plug-in to deal with this could be made in pretty short order. I'll try to write something up later today for people to peruse. BTW: a good way to think about this is aggregation versus inheritance Cheers, -- Chris On 10/19/05, Brian E. Fox [EMAIL PROTECTED] wrote: I can think of another use case. I would like to be able to fire off assembly multiple times from a single command to assemble multiple zips (source, jars, ibiblio bundle). -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 19, 2005 12:12 AM To: Maven Users List Subject: Re: Plugins of plugins On Wed, 2005-10-19 at 00:00 -0400, Brill Pappin 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. Fair enough, that's a good use case I think. Essentially what we're talking about here is a way make altering the life cycle very flexible. Exactly what Chris is talking about where you might graft a bunch of mojos/goals into the life cycle. You may want to execute some goals that are not part of the life cycle and some that are. So maybe a plugin with a configuration that allowed you to do this would be the solution. I don't think this would be hard to do but would be good to get a couple more concrete use cases first. - 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.org http://maven.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl jason at maven.org http://maven.org http://maven.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Plugins of plugins
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.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Plugins of plugins
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.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Plugins of plugins
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]
Re: Plugins of plugins
On Wed, 2005-10-19 at 00:00 -0400, Brill Pappin 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. Fair enough, that's a good use case I think. Essentially what we're talking about here is a way make altering the life cycle very flexible. Exactly what Chris is talking about where you might graft a bunch of mojos/goals into the life cycle. You may want to execute some goals that are not part of the life cycle and some that are. So maybe a plugin with a configuration that allowed you to do this would be the solution. I don't think this would be hard to do but would be good to get a couple more concrete use cases first. - 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.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
