On Thu, Jan 21, 2010 at 2:46 PM, Ryan Stewart <[email protected]> wrote:
> > > 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. > According to http://maven.apache.org/developers/mojo-api-specification.html, @execute phase="compile", Maven will "...first invoke a parallel lifecycle, ending at the given phase. ... The execution of [the lifecycle] will not affect the current project, but instead make available the ${executedProject} expression if required." (emphasis on the last sentence) So, what you are seeing appears to be the expected behavior. There should be a way to workaround this, but it will require some code changes. Justin
