Details
-
Type:
Improvement
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 6.1.17
-
Fix Version/s: 6.1.19
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
jetty:run plugin should check for the web.xml from the overlays if not found in src/main/webapp/WEB-INF/
From a comment in JETTY-241
David,
I'm using Jetty 7.0.0.pre5 and try to setup an overlay between 2 war maven projects. The project A has the web.xml file. Project B does not. Project B has a Project's A dependency in its pom file. When I try to run project B with jetty:run the overlay works but I'm getting:
[ERROR]
The following mojo encountered an error while executing:
Group-Id: org.mortbay.jetty
Artifact-Id: jetty-maven-plugin
Version: 7.0.0.pre5
Mojo: run
brought in via: Direct invocation
While building project:
Group-Id: com.test1
Artifact-Id: TestC
Version: 0.0.1-SNAPSHOT
From file: /Users/mpk35/workspace/ProjectB/pom.xml
Reason: web.xml does not exist at location /Users/mpk35/workspace/ProjectB/src/main/webapp/WEB-INF/web.xml
I'm wondering if there is anything which could be done to fix it. I would like to avoid coping the web.xml to Project B
thanks!
[ Show » ]
Michal Kuklis added a comment - 12/Dec/08 06:09 AM David, I'm using Jetty 7.0.0.pre5 and try to setup an overlay between 2 war maven projects. The project A has the web.xml file. Project B does not. Project B has a Project's A dependency in its pom file. When I try to run project B with jetty:run the overlay works but I'm getting: [ERROR] The following mojo encountered an error while executing: Group-Id: org.mortbay.jetty Artifact-Id: jetty-maven-plugin Version: 7.0.0.pre5 Mojo: run brought in via: Direct invocation While building project: Group-Id: com.test1 Artifact-Id: TestC Version: 0.0.1-SNAPSHOT From file: /Users/mpk35/workspace/ProjectB/pom.xml Reason: web.xml does not exist at location /Users/mpk35/workspace/ProjectB/src/main/webapp/WEB-INF/web.xml I'm wondering if there is anything which could be done to fix it. I would like to avoid coping the web.xml to Project B thanks!
fixed in jetty6 branch
jetty7 already handles this scenario