Project

General

Profile

Bug #5068

Investigate jars (why they are necessary) and upgrade whenever possible.

Added by David Welker almost 9 years ago. Updated almost 9 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
general
Target version:
Start date:
06/30/2010
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5068

Description

(4) Investigate jars (why they are necessary) and upgrade whenever possible.

It is better for us to make the latest jars available, so that Kepler developers can easily use the latest functionality. The assumption is that later versions are usually better than older versions. Also, we should have a better understanding of the interrelationship between jars and code.


Related issues

Blocked by Kepler - Bug #5064: Kepler 2.1 Tracking BugNew06/30/2010

History

#1 Updated by Christopher Brooks almost 9 years ago

Updating the 3rd part jars is a laudable goal and a good practice, but
quite a bit of work. I'm not sure if we have the resources to go
through each jar file and update it. Having more tests that exercise
the old and new behaviour would help.

#2 Updated by Christopher Brooks almost 9 years ago

As per Kepler leadership discussion, moving this to 2.X.Y. Note that
we will have Kepler devel telcon to discuss 2.1, so I'm leaving this as
blocking 5064.

#3 Updated by Redmine Admin about 6 years ago

Original Bugzilla ID was 5068

Also available in: Atom PDF