[MECLIPSE-548] MECLIPSE-442 should be reverted. Classpath container entries should come before 3rd party jars in .classpath

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.6
• Fix Version/s: 2.9
• Component/s: Core : Dependencies resolution and build path (.classpath)
• Environment: all
• Assignee: Fabrizio Giustina
• Reporter: Joe Freeman
• Created: 07/Apr/09 10:57
• Updated: 17/Apr/10 11:10
• Resolved: 17/Apr/10 11:10

Description

A patch was accepted into maven 2.6 as part of jira MECLIPSE-442 that configures eclipse to compile with a different order than the jre will load with. This patch moved the container classpaths to the end of the classpath in eclipse. This behavior is incorrect. The JRE's jar files should come before any 3rd party libraries on the classpath because those classes will be loaded before any of the 3rd party jars and because the JRE's classes cannot be overridden by classes in a 3rd party jar.

I understand why MECLIPSE-442 wanted to reverse the order so they could pick up the properties files. The best way to do this was to create properties files in the indvidual projects if he needed at run time or in the test/resources directory if it was only needed for unit testing. project resources come before everything in eclipse

With this patch added to maven 2.6, we have a situation where eclipse tells us we have compiler error when maven command line compilations do not.

Issue Links

• is depended upon by: MECLIPSE-605 JRE position in Eclipse generated classpath is different from the one used in Maven compiler
• relates to: MECLIPSE-581 Test source directories appear before Main source directories