| Summary: | If a module is named 'schema' it does not appear in the classpath of modules depending on it | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Altin Papa <altin.papa> | ||||
| Component: | m2e | Assignee: | Project Inbox <m2e.core-inbox> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | igor | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Altin Papa
Created attachment 205757 [details]
working example
I am not able to reproduce the problem using current m2e 1.1 and I am fairly certain the problem does not exist in m2e 1.0 either (see attached working example). If I were to guess, I'd say either STS ships with a patched m2e or one of m2e extensions included with STS messes up project dependencies.
In any case, if you believe the problem is with m2e itself, please provide a complete standalone project that we can use to reproduce the problem using eclipse distribution "for java developers" available from eclipse.org.
thanks for the prompt response! I will take a closer look at isolating the issue, as suggested. |