Eclipse 3.0 already requires Java 1.4 so i have no problem with this.
The only problem i can see will come from the other jakarta libraries we
are using (commons-lang and regexp). They may require commons-logging
(i haven't checked on this though). It may even be possible to use the
1.4 regexp stuff to replace jakarta-regexp.
I don't understand why people would be putting commons-logging into
their lib/ext directory. It is only supposed to be for 'standards' jars
(like LDAP, JAXP, etc). Adding arbitrary stuff is asking for trouble.
Mark Phippard wrote:
>The svnClientAdapter module, which is the core of Subclipse and svnAnt,
>curently has a requirement on commons-logging. There are literally just a
>handful of places in the code that use it and I am pretty sure it has no
>real use at all in Subclipse. Anyway, with Subclipse we have run into a
>handful of users that have a newer copy of commons-logging.jar in their
>global lib/ext folder. This causes a startup conflict with Subclipse and
>our plugin fails to load. Kind of bad considering that we do not really
>need or use it anyway.
>I propose that we just change svnClientAdapter to use the Java 1.4 logging
>framework so that this will not be an issue. This would impose a Java 1.4
>requirement on our code. I think we sort of have one already, but am not
>This would not apply to the old Subclipse line for Eclipse 2.x (which can
>use Java 1.3 in the IBM versions of that IDE).
>Does anyone have any thoughts or concerns to raise?
>I have no intention of doing anything other than converting the currently
>limited use of commons-logging over to Java 1.4.
>Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
>To unsubscribe, e-mail: firstname.lastname@example.org
>For additional commands, e-mail: email@example.com
Received on Sat Jun 11 08:53:03 2005