The jettyEnvXml should be a File parameter or prefixed with basedir to work in a context where current working directory is not where pom.xml is

If I have

<configuration>
  ..
  <jettyEnvXml>src/test/jetty-env.xml</jettyEnvXml>
</configuration>

and run Maven like this:

mvn -f myapp-web/pom.xml jetty:run

it tries to load "src/test/jetty-env.xml" instead of "myapp-web/src/test/jetty-env.xml".

Technically all that the plugin has to do it to change the jettyEnvXml field to be a File or prefix with ${basedir}

Ascending order - Click to sort in descending order

Hide

Permalink

Leopoldo Agdeppa III added a comment - 09/Aug/07 12:55 AM

Trygve Laugstol

jettyEnvXml should be a file, ill make the fix for this

thanks
bong

Show

Leopoldo Agdeppa III added a comment - 09/Aug/07 12:55 AM Trygve Laugstol jettyEnvXml should be a file, ill make the fix for this thanks bong

Hide

Permalink

Jan Bartel added a comment - 21/Oct/07 11:09 PM

David,

Can you also check and fix webXml and other parameters that denote files?

thanks,
Jan

Show

Jan Bartel added a comment - 21/Oct/07 11:09 PM David, Can you also check and fix webXml and other parameters that denote files? thanks, Jan

Hide

Permalink

David Yu added a comment - 22/Oct/07 3:23 AM

Attached the fix for this issue.
Tested with webXml, jettyEnvXml and jettyConfig.

Show

David Yu added a comment - 22/Oct/07 3:23 AM Attached the fix for this issue. Tested with webXml, jettyEnvXml and jettyConfig.

Hide

Permalink

David Yu added a comment - 03/Jan/08 6:26 AM

plugin-config-resources.patch attached.
File/Classpath resource params:

Show

David Yu added a comment - 03/Jan/08 6:26 AM plugin-config-resources.patch attached. File/Classpath resource params:

Vote (0)

Watch (0)