Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 361713 - If a module is named 'schema' it does not appear in the classpath of modules depending on it
Summary: If a module is named 'schema' it does not appear in the classpath of modules ...
Status: CLOSED WORKSFORME
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-21 17:22 EDT by Altin Papa CLA
Modified: 2021-04-19 13:22 EDT (History)
1 user (show)

See Also:

Attachments
working example (4.29 KB, application/zip)
2011-10-21 17:34 EDT, Igor Fedorenko CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Altin Papa CLA 2011-10-21 17:22:26 EDT 
Build Identifier: STS 2.7.1.201107091000-RELEASE - Eclipse Core Runtime 3.7.0.v20110110

'schema' seems to be a reserved name in some sense. We have a module named 'container' which depends on another named 'schema'. Module schema, with jar packaging, contains just XSD resources.

Tests within 'container' fail and their classpath printed out at runtime does not contain the 'schema' module.

Simply renaming 'schema' to anything else, say 'myschema', resolves the issue.

Reproducible: Always

Steps to Reproduce:
1. create a multi-module project, with two jar modules: 'container' depending on 'schema'
2. Print or otherwise examine the classpath of 'container'. 'schema' is missing.
3. Rename 'schema' and retry. Problem resolved.
Comment 1 Igor Fedorenko CLA 2011-10-21 17:34:59 EDT 
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.
Comment 2 Altin Papa CLA 2011-10-21 17:36:53 EDT 
thanks for the prompt response! I will take a closer look at isolating the issue, as suggested.
Comment 3 Denis Roy CLA 2021-04-19 13:22:57 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/