You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ben Caradoc-Davies (JIRA)" <ji...@codehaus.org> on 2009/04/14 09:19:52 UTC
[jira] Issue Comment Edited: (MECLIPSE-548) MECLIPSE-442 should be
reverted. Classpath container entries should come before 3rd party jars in
.classpath
[ http://jira.codehaus.org/browse/MECLIPSE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=172863#action_172863 ]
Ben Caradoc-Davies edited comment on MECLIPSE-548 at 4/14/09 2:17 AM:
----------------------------------------------------------------------
I second the rating of this bug as critical. This bug breaks Eclipse integration for GeoTools, because maven-eclipse-plugin does not honour exclusions of transitive dependencies, and GeoTools Eclipse integration relies on xml-apis provided by the JRE being compatible with xerces 2.7 and being earlier on the classpath. Yes, this sucks, but it works.
To reproduce with Maven 2.0.10 (use a Java 5 JDK):
(1) svn co -r32785 http://svn.osgeo.org/geotools/trunk geotools-trunk
(2) cd geotools-trunk
(3) mvn -Dmaven.test.skip install eclipse:eclipse
(4) import into Eclipse, and see modules fail to compile
was (Author: bencaradocdavies):
I second the rating of this bug as critical. This bug breaks Eclipse integration for GeoTools, because maven-eclipse-plugin does not honour exclusions of transitive dependencies, and GeoTools Eclipse integration relies on xml-apis provided by the JRE being compatible with xerces 2.7 and being earlier on the classpath. Yes, this sucks, but it works.
To reproduce with Maven 2.0.10 (use a Java 5 JDK):
(1) svn co http://svn.osgeo.org/geotools/trunk geotools-trunk
(2) cd geotools-trunk
(3) mvn -Dmaven.test.skip install eclipse:eclipse
(4) import into Eclipse, and see modules fail to compile
> 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