Great points Stephen! I'm only using this plugin in one particular use case where we need a property in maven that's stored in a property file but as you point out it does not affect the build plan. In general though I think its best to do it the "maven way" and make Maven the definitive source and not use this plugin. But for folks that have a legacy code base use case, having this plugin available can sure make the migration path to Maven 2 easier!
-Todd Stephen Connolly-2 wrote: > > 2008/11/20 thuss2 <[EMAIL PROTECTED]> > >> >> I'm pleased to say that to solve this problem I found the >> maven-properties-plugin which has been working great for me: >> >> http://arsenalist.com/2007/02/07/maven-properties-plugin-download/ >> >> -Todd >> >> >> > Beware, that plugin suffers from a fatal flaw: > > Plugins execute after the build plan has been constructed. > > Thus it can only provide properties for things which do not affect the > build > plan. > > So, while you'll get some mileage out of that plugin.... ultimately you'll > end up frustrated when you hit one of the places where property > subsitution > takes place during determination of the build plan. > > Also, the property substitution will only take place *when* the plugin is > run, so if you invoke another plugin directly outside of a lifecycle goal, > you'll get no substitution... > > -Stephen > > -- View this message in context: http://www.nabble.com/Making-properties-accessible-in-pom.xml-tp8996414p20610367.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]
