| Summary: | Incompatible Classpath on a Maven Multiproject (M2E) and WTP | ||
|---|---|---|---|
| Product: | [WebTools] WTP Java EE Tools | Reporter: | Robert Einsle <robert> |
| Component: | wst.web | Assignee: | wst.web <wst.web-inbox> |
| Status: | NEW --- | QA Contact: | Chuck Bridgham <cbridgha> |
| Severity: | normal | ||
| Priority: | P3 | CC: | alberto.da |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
I had the same problem a few hours ago. I discovered that if you add "Utility Project" facet to the failing child projects (data and services), the problem disappears and jar files are now deployed. I think it's a bug, but using this workaround worked for me. Have a nice day! Alberto |
Build Identifier: M20110909-1335 Hi *, i've creating a Maven Multiproject-Site of this style: parent ----- data |-- services |-- web Services has a (maven-)dependencie to data, web to services. After creating this Project-Layout in Eclipse with New -> Maven -> Maven Project and Maven Module i must configure Properties / Deployment Assembly and add the Maven Dependencies. After that i got the Errors: --- cut --- Description Resource Path Location Type Invalid classpath publish/export dependency /data. Project entries not supported. web P/web Classpath Dependency Validator Message Invalid classpath publish/export dependency /service. Project entries not supported. web P/web Classpath Dependency Validator Message --- cut --- Here i think WTP cannot assing the both projekts data and services but i whould expect i now have the Dependencies only to the Libraries of Maven-Dependencies, and not to the Projects in Workspace. How can i handle this? Thanks a lot. Robert Reproducible: Always