Distributed external jars not current versions in acvtivemq 4.1.0 rc2

[Endre Stølsvik <Ap...@Stolsvik.com>]

Hi.

Just thought I'd point out the following regarding 4.1.0 RC2:

The log4j jar included is 1.2.12 - current is 1.2.14, which was released 
several months ago.

The xstream jar included is 1.1.2 - current is 1.2.1, released nov 11.

The mx4j jars included are 2.1.1 - current is 3.0.1, which seems to have 
been released March 1., 2005!

The JmDNS jar included is 1.0 Release Candidate 2 - current is 1.0, 
which was released Oct 23., 2005! _It is also LGPL_.

The derby jar included in 10.1.1.0 - derby are in two lines, 10.1 and 
10.2. Currents are 10.2.1.6 (released 6-oct-2006) and 10.1.3.1 (released 
5-jul-2006).

IMHO it is slightly non-optimal to not include (and thus have verified 
operation on) the newest versions of dependent projects. It is of course 
good if the stuff works on really old versions and everything up to 
current too, but at least the newest available at the time of release 
should have been tested and OKayed. IMO.

Regards,
Endre.

Re: Distributed external jars not current versions in acvtivemq 4.1.0 rc2

[Hiram Chirino <hi...@hiramchirino.com>]

On 11/20/06, Endre Stølsvik <Ap...@stolsvik.com> wrote:
> Hi.
>
> Just thought I'd point out the following regarding 4.1.0 RC2:
>
> The log4j jar included is 1.2.12 - current is 1.2.14, which was released
> several months ago.
>
> The xstream jar included is 1.1.2 - current is 1.2.1, released nov 11.
>
> The mx4j jars included are 2.1.1 - current is 3.0.1, which seems to have
> been released March 1., 2005!
>
> The JmDNS jar included is 1.0 Release Candidate 2 - current is 1.0,
> which was released Oct 23., 2005! _It is also LGPL_.

JmDNS license was changed to ASL a while back.

>
> The derby jar included in 10.1.1.0 - derby are in two lines, 10.1 and
> 10.2. Currents are 10.2.1.6 (released 6-oct-2006) and 10.1.3.1 (released
> 5-jul-2006).
>
> IMHO it is slightly non-optimal to not include (and thus have verified
> operation on) the newest versions of dependent projects. It is of course
> good if the stuff works on really old versions and everything up to
> current too, but at least the newest available at the time of release
> should have been tested and OKayed. IMO.

Please open a JIRA issues to request that versions get upgraded.
There is usually very little incentive to upgrade dependencies if the
old ones are working fine.

>
> Regards,
> Endre.
>


-- 
Regards,
Hiram

Blog: http://hiramchirino.com