I do something similar in one of my projects, except that instead of trying to get to the property directory, I create a property file (filtered), and then just read it in from the classpath (since at that point it's packaged in the plugin JAR like everything else).
On 9/17/07, Wayne Fay <[EMAIL PROTECTED]> wrote: > > Oh good point. I missed that in the original mail, I think. ;-) > > I have no idea about that, unfortunately. > > Wayne > > On 9/17/07, Manos Batsis <[EMAIL PROTECTED]> wrote: > > Wayne Fay wrote: > > > You should generally be able to get that kind of property from > > > MavenProject.getProperties(). > > > > > > If I understand correctly, this would be a reference to the MavenProject > > the mojo is used at runtime and not it's *own* POM, correct? > > > > Thanks, > > > > Manos > > > > --------------------------------------------------------------------- > > 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] > >
