Wayne Fay wrote: > > properties-m-p is a bit of a hack. The Maven team is pretty clear > about where properties should go -- in pom.xml, profiles.xml, or > settings.xml files ONLY. > That's good to know.
Wayne Fay wrote: > > Is there a good reason for not simply putting the port directly in the > pom? Or even in a profile? > That's certainly what I would prefer, but I'm working with a legacy "profile" system that was built in Ant and which everyone is used to working a particular way. I was hoping I could just reuse the system and have Maven load its properties from it. It's all based on properties files, so it would be extremely convenient if it would just work. If I have to convert the whole thing into Maven profiles, it would take many hours of work and probably change the way things work enough that people would complain. It seems to work fine for everything so far except this one use case, so I suspect it has something to do with the executePhase setting of the goal. -- View this message in context: http://old.nabble.com/Property-loaded-by-plugin-not-available-to-gwt%3Arun-tp27227122p27263433.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]
