There has never been such native Maven support (i.e. in Maven core). /Anders
On Tue, Sep 20, 2011 at 14:57, Maven User <maven.2.u...@gmail.com> 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 <and...@hammar.net> 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 <maven.2.u...@gmail.com> 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: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
