Sorry Mark, should have mentioned that I usually use the following config
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>jetty-maven-plugin</artifactId>
<configuration>
<contextPath>${build.finalName}</contextPath>
<scanIntervalSeconds>10</scanIntervalSeconds>
</configuration>
</plugin>
;)
And thanks to bring up the feature with the artifactId.
(I'm not sure if the groupId-artifactId-version behaviour I have in mind is
from either a very old jetty plugin or from the tomcat or cargo plugin i've
worked with. Anyway, it's good to know that this works now.)
LieGrue,
strub
--- Mark Hobson <[EMAIL PROTECTED]> schrieb am Fr, 24.10.2008:
> Von: Mark Hobson <[EMAIL PROTECTED]>
> Betreff: Re: What is the purpose of <finalName>? really?
> An: "Maven Users List" <[email protected]>
> Datum: Freitag, 24. Oktober 2008, 9:41
> 2008/10/24 Mark Struberg <[EMAIL PROTECTED]>:
> > To give Kent an example:
> >
> > Consider a pom for building a WAR.
> > If you set
> >
> > <finalName>mycontextpath</finalName>
> >
> > and use e.g. the jetty plugin to start your webserver
> in 1 go:
> >
> > $> mvn package jetty:run
> >
> > Then your finalName is being used for
> 'deployment' and you may access your webapp via
> >
> > http://localhost:8080/mycontextpath/
>
> BTW, the Jetty plugin uses the project's artifact id
> for its context path :)
>
> > which may then automatically be regression tested via
> Canoo, etc without having to type
> http://localhost:8080/mygroup_id.myartifact_id-2.5.3-SNAPSHOT/
> and change the version every time.
>
> Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
