Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: 
 <17218486.1239718252623.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Date: Tue, 14 Apr 2009 09:10:52 -0500 (CDT)
From: "Arnaud Heritier (JIRA)" <jira@codehaus.org>
To: issues@maven.apache.org
Subject: [jira] Commented: (MECLIPSE-548) MECLIPSE-442 should be reverted.
 Classpath container entries should come before 3rd party jars in .classpath
In-Reply-To: 
 <14295993.1239119953056.JavaMail.haus-jira@codehaus01.managed.contegix.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


    [ http://jira.codehaus.org/browse/MECLIPSE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=172916#action_172916 ] 

Arnaud Heritier commented on MECLIPSE-548:
------------------------------------------

Do not hesitate to vote for the issue. I always try to check them (http://www.sonatype.org/~j2ee-hudson/reports/plugin-votes.html#Maven%202.x%20Eclipse%20Plugin). For this issue, isn't there a different case for a jre container (which should be at the beginning) and others containers (which should be at the end to be able to override them  MECLIPSE-442)

> 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
>
> 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