maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Barrie Treloar (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MECLIPSE-548) MECLIPSE-442 should be reverted. Classpath container entries should come before 3rd party jars in .classpath
Date Tue, 16 Jun 2009 06:20:42 GMT

     [ http://jira.codehaus.org/browse/MECLIPSE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Barrie Treloar updated MECLIPSE-548:
------------------------------------

    Fix Version/s: 2.8

> MECLIPSE-442 should be reverted. Classpath container entries should come before 3rd party
jars in .classpath
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: MECLIPSE-548
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-548
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>          Components: Core : Dependencies resolution and build path (.classpath)
>    Affects Versions: 2.6
>         Environment: all
>            Reporter: Joe Freeman
>            Priority: Critical
>             Fix For: 2.8
>
>
> 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.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message