http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Lifecycle_Reference will give you all the phases that are available.
Sounds like you need to bind one to validate and the other to initialize On 2 September 2011 19:33, Kelly Davis <[email protected]> wrote: > Thanks for your reply Stephen > The property files that I am reading are pulled into the project using > the maven-remote-resources-plugin. This must happen before the > ReadPropertiesMojo executes. Currently, the remote resources plugin is bound > to the initialize phase so it runs first. Is there anyway to bind them both > to validate and guarantee that remote-resources runs before the properties > plugin? When I was originally building this out, it seemed like there was an > issue with not being able to control the order the plugins execute within a > phase. > Kelly > > On Fri, Sep 2, 2011 at 12:32 PM, Stephen Connolly > <[email protected]> wrote: >> >> binding it to the first phase, validate >> >> - Stephen >> >> --- >> Sent from my Android phone, so random spelling mistakes, random nonsense >> words and other nonsense are a direct result of using swype to type on the >> screen >> >> On 1 Sep 2011 14:12, "Kelly Davis" <[email protected]> wrote: >> > I realize this plugin hasn't been updated in a while, but I thought I >> > what >> > throw this question out there to see if anyone has any helpful thoughts. >> > >> > I am using the plugin to read in a set of properties using the >> > ReadPropertiesMojo. The mojo is bound to the generate-resources phase. >> > The >> > properties are used in the pom in a <properties/> block, to essentially >> > rename the properties. For example, in the properties file, I will have >> > a >> > property foo.jetty.port and in the properties block in the pom I have: >> > >> > <jetty.port>${foo.jetty.port}</jetty.port> >> > >> > This seems to mostly work correctly. If I turn on debug logging, I can >> > see >> > that the jetty.port property gets set to the value of foo.jetty.port in >> > the >> > properties file. Resource filtering seems to correctly resolve the value >> > of >> > jetty.port. The problem is that for configuration in some plugins >> > (maven-jetty-plugin, exec plugin), if they use the value of the >> > jetty.port >> > property, it resolves to null, as if the configuration read in the value >> > of >> > jetty.port AND resolved it before the read properties mojo was run >> > (which >> > would be ${foo.jetty.port}). Is this analysis correct? Is there any way >> > to >> > make this work? It seems like the problem is that whatever is handling >> > plugin configuration needs to resolve property values at a later time, >> > but >> > that seems like a core change. >> > >> > Any insights would be appreciated. >> > >> > Kelly > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
