This link helped me to solve my issue:
http://maven.40175.n5.nabble.com/Does-the-lt-pluginGroup-gt-in-the-setting-xml-work-td115219.html
my metadata file for org.mortbay.jetty had configured the prefix to always
call jetty-maven-plugin vs maven-jetty-plugin. Both were in the file, but
seems li
A follow up.
We have a very large and complex system that is being deployed to jetty
6.1.22, so I'd like to try to keep things a close to the same as possible
with the plugin.
One issue I am running into is that, the config isn't being honored for:
>
> org.mortbay.jetty
> maven-jetty-p
Noted...added version number.
Thanks!
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-Jetty-Plugin-won-t-honor-webAppSourceDirectory-tp4774500p4774652.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
got this fixed, thanks for the suggestion Jason.
I changed this FROM:
>
> org.mortbay.jetty
> maven-jetty-plugin
> 6.1.22
>
>
> ${basedir}/src/main/webapp2
> ${basedir}/src/main/webapp2/WEB-INF/web.xml
>
>
TO
org.mortbay.jetty
jetty-maven-plugin<--
Based on the documentation the Jetty plugin is supposed to allow you to be
able to change the default location of the webapp directory
(http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin)
when I issue a mvn jetty:run in the plugin configuration I keep seeing this:
...
[INFO] webAppSourceDi
