[jira] Commented: (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=216926#action_216926 ] Ben Caradoc-Davies commented on MECLIPSE-548: - Fabrizio, that sounds like a good solution. Documentation for the optional property should include a warning about JRE behaviour, as noted in this issue (JRE classes always loaded before 3rd party jars). Fixing this issue would be much appreciated. Kind regards, Ben. > 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 >Assignee: fabrizio giustina >Priority: Critical > Fix For: 2.9 > > > A patch was accepted into maven 2.6 as part of jiraMECLIPSE-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
[jira] Commented: (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=211667#action_211667 ] Robert Watkins commented on MECLIPSE-548: - Still not fixed for Version 2.8, I see... > 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.9 > > > A patch was accepted into maven 2.6 as part of jiraMECLIPSE-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
[jira] Commented: (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=180415#action_180415 ] Ben Caradoc-Davies commented on MECLIPSE-548: - Thanks, Barrie. > 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 jiraMECLIPSE-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
[jira] Commented: (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=180396#action_180396 ] Ben Caradoc-Davies commented on MECLIPSE-548: - I suspect that we need to get this assigned to someone. I will email the project lead. GeoTools is still pinned to 2.5, and so it will remain until this bug is fixed. > 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 jiraMECLIPSE-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
[jira] Commented: (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=180352#action_180352 ] Joe Freeman commented on MECLIPSE-548: -- How many votes does this have to have before it makes a release. Version 2.7 just came out and it still has the same incorrect classpath ordering for the JDK/JRE :-( > 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 jiraMECLIPSE-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
[jira] Commented: (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=177437#action_177437 ] Rustam Abdullaev commented on MECLIPSE-548: --- I would suggest to make this configurable. Most application servers can be configured to place their classes before or after application classes. But I agree that JRE classes must come first in any case. > 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 jiraMECLIPSE-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
[jira] Commented: (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=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 jiraMECLIPSE-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
[jira] Commented: (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=172915#action_172915 ] Robert Newson commented on MECLIPSE-548: this also broke my project. I have a dependency on mx4j (it's transitive and shouldn't appear on here, but that's a different bug). It took a few frustrating hours to track down why I could not compile in Eclipse but could in Maven. Please revert this change. I have pinned to 2.5.1 for now. > 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 jiraMECLIPSE-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
[jira] Commented: (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=172868#action_172868 ] Ben Caradoc-Davies commented on MECLIPSE-548: - See Nabble discussion: http://n2.nabble.com/Eclipse-integration-broken--td2631438.html > 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 jiraMECLIPSE-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
[jira] Commented: (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=172867#action_172867
]
Ben Caradoc-Davies commented on MECLIPSE-548:
-
Workaround for this bug is to pin your project to version 2.5:
{code}
org.apache.maven.plugins
maven-eclipse-plugin
2.5
...
{code}
> 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 jiraMECLIPSE-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
[jira] Commented: (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 commented on MECLIPSE-548: - 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 jiraMECLIPSE-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
[jira] Commented: (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=172323#action_172323 ] Arnaud Heritier commented on MECLIPSE-548: -- A simple testcase to help us to see if this time we don't do another error could be a good thing... thx. > 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 jiraMECLIPSE-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
