On Thu, Apr 9, 2009 at 7:32 AM, Dan Tran <[email protected]> wrote: > I may be wrong, but i think finalName is constructed early in the > cycle and therefor buildNumber var is not propagate properly, does > maven 2.1.0 help?
No, the problem is that since Nodje is executing jetty plugin directly rather than a lifecycle phase, the buildNumber obviously doesn't get evaluated. Would it work if you execute both of them explicitly, i.e. mvn buildnumber:create jetty:run-exploded? Kalle > > On Wed, Apr 8, 2009 at 11:40 PM, nodje <[email protected]> wrote: > > > > Hi, > > > > I've just setup config with buildnumber-maven-plugin using > > > > > <finalName>${project.artifactId}-${project.version}-r${buildNumber}</finalName> > > > > as name for my artifacts. > > > > But now when I try to run 'mvn jetty:run-exploded', I get a message from > Jetty stating it can't find > > appname-1.1-rnull. > > > > So it seems Jetty isn't aware of the ${buildNumber} variable when it > check the name of the war it has to deploy. > > > > Did anyone successfully use both plugin together? > > > > cheers > > -nodje > > -- > > View this message in context: > http://n2.nabble.com/Using-buildnumber-maven-plugin-together-with-jetty-plugin-tp2609616p2609616.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] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
