That's something different. I said Maven 2 core doesn't have support for reading properties from a file. There might be plugins, but no such support in core.
/Anders On Tue, Sep 20, 2011 at 15:20, Maven User <[email protected]> wrote: > In 2.2.1, this worked flawlessly. > > In 3.X this (known) feature no longer works. > > http://www.mailinglistarchive.com/html/[email protected]/2011-01/msg00729.html > > Ok, I'm clear now :-) > > On Tue, Sep 20, 2011 at 9:13 AM, Anders Hammar <[email protected]> wrote: > >> There has never been such native Maven support (i.e. in Maven core). >> >> /Anders >> >> On Tue, Sep 20, 2011 at 14:57, Maven User <[email protected]> wrote: >> > Heh - yeah a quick look at the docs and it says: >> > >> > >> > - Requires a Maven 2.0 project to be executed. >> > - Since version: 1.0-alpha-2. >> > - Invokes the execution of the lifecycle phase package prior to >> executing >> > itself. >> > >> > There's no mention of forking and all the documentation around this >> plugin >> > kinda stinks. >> > >> > Cargo is also a great option but one of the things we try to do is load >> > property files from a jar and put the results into the reactor. >> > >> > I think this functionality is gone in maven 3 though.... >> > >> > >> > On Tue, Sep 20, 2011 at 3:32 AM, Anders Hammar <[email protected]> >> wrote: >> > >> >> tomcat:deploy could possibly fork a new process performing a maven >> >> build with the lifecycle (the docs should tell). I haven't used that >> >> plugin as I'm a Cargo addict...:-) >> >> >> >> /Anders >> >> >> >> On Mon, Sep 19, 2011 at 22:35, Maven User <[email protected]> >> wrote: >> >> > BTW - this is totally not the behavior we're seeing with a >> >> "tomcat:deploy". >> >> > >> >> > That seems to go through all the standard build lifecycle goals, then >> NOT >> >> > pull in any dynamically loaded configuration... >> >> > >> >> >> >> --------------------------------------------------------------------- >> >> 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] >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
