Hi Brett, thanks for the feedback.
On 1/26/06, Brett Porter <[EMAIL PROTECTED]> wrote: > You can already configure plugins from settings.xml using profiles. Do you mean that the property will be set as the mojo property thanks to the plexus javadoc declaration? First I find that very verbose and less intuitive. Second, there's the lifecycle limitation, and third, maybe I am wrong, but it doesn't give me a simple control over which property goes where. E.g. if I have 2 plugins in my pom <build> section, and both use the jar:sign mojo to sign using a different key, how will the correct profile be selected from settings.xml? By using a complex activation system? How come? One cannot define a <property> in a <plugin> declaration inside the <build>. So how will I activate the correct profile? The system I proposed seems to make all these limitations go away. Of course I may be wrong. And of course, if something already exists that covers most of the cases... Still! > The other alternative is to use <properties> and use expressions in the > individual poms. Properties are OK on a small scale. They are a little bit too verbose wrt to the jar sign required information (too many properties to define to my taste). But I still prefer that to the profile solution. J. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
