Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 365287 - Incompatible Classpath on a Maven Multiproject (M2E) and WTP
Summary: Incompatible Classpath on a Maven Multiproject (M2E) and WTP
Status: NEW
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: wst.web (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: wst.web CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-01 04:48 EST by Robert Einsle CLA
Modified: 2012-01-14 19:16 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Einsle CLA 2011-12-01 04:48:03 EST
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
Comment 1 Alberto Díaz CLA 2012-01-14 19:16:23 EST
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