Hi Wayne
Yes, you have right. It certainly the best solution and it will be simpler.
I also think that it better to use profile just for some cases.
I was looking for this feature. As it doesn't exist yet, I used profiles
instead.
Rémy
2007/2/17, Wayne Fay [EMAIL PROTECTED]:
Would it perhaps
Hi Kennedy,
Just trying to think of some ways to implement this feature request...
I think this is the only feasible option right now.
Yes, and it's better to use the Wayne's proposal.
'site' is not a phase, it's a lifecycle. It may be possible
to add a profile activator based on
Wayne Fay wrote:
Would it perhaps be sufficient to add a skip configuration to all
plugins, such that you could declare the plugin the parent, and then
add a skiptrue in the plugin definition in the children which would
cause that plugin to be skipped for that specific child/module?
Just
Would it perhaps be sufficient to add a skip configuration to all
plugins, such that you could declare the plugin the parent, and then
add a skiptrue in the plugin definition in the children which would
cause that plugin to be skipped for that specific child/module?
Just trying to think of some
I would like to propose a new profile activation.
As described in
http://www.nabble.com/Execute-only-in-the-parent-POM-and-some-sub-modules---tf3201453s177.html#a8889223
, I need to execute a plugin only for some sub-modules from the parent pom.
For instance to generate the project web site.
I
