Hi
Perhaps we should introduce a third party dependencies freeze at M4,
encouraging transition to the latest stable version up until then, and
giving time to align or fall back as necessary.
Regards
Ed Willink
On 20/05/2010 15:05, Scott Lewis wrote:
FWIW,
Yes...as Pascal and John A indicated, ECF is using the apache
httpclient (3.1) and this dictates a dependency on commons logging
1.0.4.
We (ECF, etc) would be completely willing to move some other mutually
agreed upon version of commons logging, but there are some important
subtleties: Since it's httpclient that depends upon 1.0.4, once a
replacement version of commons logging was selected, someone would have
to look for/test for regression in httpclient 3.1 in order to do
so...since there's unfortunately no guarantee that httpclient 3.1
doesn't have a hard dependency on 1.0.4 (I'm not saying there is or
anything...just that we don't know, and discovering something like that
could be dramatically bad if the change was done
cavalierly...especially this late in the game).
All this by way of saying...I think aligning on a version would be fine
(I mean...other than the version upon which we're aligned now)...but
it's unfortunately not trivial for us to safely change this
dependency...particularly without some available resource to check/test
for possible regression.
Scott
Martin Taal wrote:
This topic (commons.logging 1.0.4 being
supplied and other projects needing 1.1) has also cost me several hours
and many builds. I would not be surprised if it also cost others a few
hours (so we talk about mandays of work).
So from my point of view it would be great if Eclipse projects can
align on the version used for such a base jar file as
commons.logging....
.
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Cell: +31 (0)6 288 48 943
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@xxxxxxxxxxxxxx - mtaal@xxxxxxxxx
Web: www.springsite.com - www.elver.org
Pascal Rapicault wrote:
This is being brought in by
org.apache.commons.httpclient which is used by p2 (through ECF)
Do you know if they are compatible with each others? Did you try
running with just the 1.1 version? Remember that at Apache, version
numbers don't necessarily have the same semantics than eclipse.
Actually worse, ppl just bump versions without really thinking.
At this point p2 ships 1.0.4 because we don't know any better. However
given all the problems we have had around transports in p2 and the time
it took us to stabilize I'm really not inclined to change that just for
source issues of a third party bundle.
On 2010-05-20, at 6:42 AM, Eike Stepper wrote:
Hi,
I noticed that many projects depend on o.a.c.logging 1.1.x+ while the
platform still includes 1.0.4. That causes duplicate bundles and some
build problems regarding the respective source bundles. Would it be
possible to agree on a common version?
Cheers
/Eike
----
http://thegordian.blogspot.com
http://twitter.com/eikestepper
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.819 / Virus Database: 271.1.1/2884 - Release Date: 05/19/10 19:26:00
|
