I don't think so unless the tomcat plugin can be configured to use it. Using a separate properties file is IMHO not a good idea, for reasons you now see. And there are even worse examples where you could effectively be distributing a non-working pom making people using your artifact lives' miserable.
Keep everything in the POM, /Anders On Mon, Sep 19, 2011 at 22:15, Maven User <maven.2.u...@gmail.com> wrote: > And there's no way to inject the property files we've loaded at that level? > > On Mon, Sep 19, 2011 at 3:59 PM, Anders Hammar <and...@hammar.net> wrote: > >> It will get properties defined in the effective POM. >> >> /Anders >> On Mon, Sep 19, 2011 at 21:48, Maven User <maven.2.u...@gmail.com> wrote: >> > Yet it gets properties from profiles/plugin configuration/etc? >> > >> > On Mon, Sep 19, 2011 at 2:35 PM, Anders Hammar <and...@hammar.net> >> wrote: >> > >> >> When you execute >> >> mvn tomcat:deploy >> >> you're NOT executing the build lifecycle but only the specify plugin >> >> goal. Thus, your plugin that loads the props is not executed. >> >> >> >> /Anders >> >> >> >> On Mon, Sep 19, 2011 at 17:35, Maven User <maven.2.u...@gmail.com> >> wrote: >> >> > Hi all - >> >> > >> >> > Quick question, I think there's some confusion on my end. >> >> > >> >> > We have a plugin that loads properties into the reactor so they're >> >> available >> >> > for things like resource processing, various other plugins, etc. >> >> > >> >> > However, when using the tomcat plugin directly on the command line >> (such >> >> as >> >> > mvn tomcat:deploy), the properties are not expanded when they've come >> >> from a >> >> > property file. >> >> > >> >> > If we use the standard plugin configuration and bind the deployment to >> a >> >> > particular lifecycle goal with an execution, the property is expanded >> >> > successfully. >> >> > >> >> > What are we doing wrong/what are we missing? >> >> > >> >> > When the tomcat goals are called on the command line, it's as if they >> >> skip >> >> > several steps but grab things from activated profiles and <properties> >> >> > blocks. >> >> > >> >> > Suggestions? >> >> > >> >> >> >> --------------------------------------------------------------------- >> >> 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 >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
