inaddition to Wayne's suggestion, take a looks at build-helper-maven-plugin's source, it does some thing similar
On Mon, Oct 13, 2008 at 12:32 PM, Wayne Fay <[EMAIL PROTECTED]> wrote: > You can add a property via MavenProject, see the Mojo Developer Cookbook here: > http://docs.codehaus.org/display/MAVENUSER/Mojo+Developer+Cookbook > > Wayne > > On Mon, Oct 13, 2008 at 9:04 AM, stug23 <[EMAIL PROTECTED]> wrote: >> >> Is there a standard way to access a property that was set/established within >> a mojo in other, different plugin executions in the same POM? >> >> My use case is one where a mojo determines the value for a property that was >> not set/input to the mojo. This property needs to be available to other >> plugins for execution within the same lifecycle in later phases. I was able >> to stuff the property into System.setProperty("key",value) however I was >> wondering if there is a better way to do this? >> >> Or is the only way to make this work via filtering and writing to files? >> >> TIA >> >> -- >> View this message in context: >> http://www.nabble.com/Using-a-property-from-a-mojo-in-subsequent-plugin-executions-tp19957750p19957750.html >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
