Now that this bus is fixed, we may no longer have to pin maven-eclipse
plugin to 2.5.
-------- Original Message --------
Subject: [jira] Closed: (MECLIPSE-548) MECLIPSE-442 should be reverted.
Classpath container entries should come before 3rd party jars in .classpath
Date: Sun, 18 Apr 2010 00:11:12 +0800
From: fabrizio giustina (JIRA) <j...@codehaus.org>
To: Caradoc-Davies, Ben (CESRE, Kensington) <ben.caradoc-dav...@csiro.au>
[
http://jira.codehaus.org/browse/MECLIPSE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina closed MECLIPSE-548.
--------------------------------------
Resolution: Fixed
Fixed for 2.9 by reverting the behavior introduced in MECLIPSE-442 but
adding a new property that let user switch to the container-last mode if
really needed (mostly for compatibility for projects that were working
due to MECLIPSE-442).
Thanks to anybody helped by reporting the problem and voting for this to
be 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
> Assignee: fabrizio giustina
> Priority: Critical
> Fix For: 2.9
>
>
> 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
--
Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au>
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
