Apache Commons abandoned ?

J

Joerg Meier

Hello,

looking for a proper solution to deal with Windows style INI files, I was
linked to the Apache Commons Configurations library. While it looks like
what I want, I was surprised and dismayed to notice that a lot of the
Apache Common libraries seem to have been completely abandoned. Many have
not have had any updates since 2008 or 2010, and some even are specifically
designed to still run on Java 1.2!

Are those libraries so incredibly polished that no further updates are
necessary, or have they simply been abandoned ? Looking in from the
outside, it seems like no maintenance or anything has been done, and I'm a
bit worried about adding something that is explicitly 1.2-compatible to my
build path.

Anyone familiar with the communities surrounding these libraries ? Hard to
tell from the outside.

Liebe Gruesse,
Joerg
 
A

Arne Vajhøj

looking for a proper solution to deal with Windows style INI files, I was
linked to the Apache Commons Configurations library. While it looks like
what I want, I was surprised and dismayed to notice that a lot of the
Apache Common libraries seem to have been completely abandoned. Many have
not have had any updates since 2008 or 2010, and some even are specifically
designed to still run on Java 1.2!

Are those libraries so incredibly polished that no further updates are
necessary, or have they simply been abandoned ? Looking in from the
outside, it seems like no maintenance or anything has been done, and I'm a
bit worried about adding something that is explicitly 1.2-compatible to my
build path.

Anyone familiar with the communities surrounding these libraries ? Hard to
tell from the outside.

If Apache stops a project then they state that very explicit. No such
statement means that it is still active.

Some projects is not updated frequently. Maybe because there is
no need. Maybe because no committer has time to do it.

I do not see running on Java 1.2 as a problem. It was probably started
when 1.2 was relevant and why break the capability if not needed.

Apache Commons Configurations do have recent updates:

Version Date Description
2.0 in SVN TBD
1.9 2012-08-22 Minor bug fixes and improvements
1.8 2012-02-04 Support for Java 1.5
1.7 2011-09-07 Many bugfixes, some new features.
1.6 2008-12-25 Another set of smaller bug fixes
1.5 2007-11-24 Many smaller bugfixes
1.4 2007-04-08 Improved interpolation, configuration for INI files,
reloading strategy triggered with JMX, bug fixes.
1.3 2006-09-24

Arne
 
M

markspace

I was surprised and dismayed to notice that a lot of the
Apache Common libraries seem to have been completely abandoned. Many have
not have had any updates since 2008 or 2010, and some even are specifically
designed to still run on Java 1.2!

Are those libraries so incredibly polished that no further updates are
necessary, or have they simply been abandoned ?


Software does eventually have to be abandoned. Sometimes it is
superseded by something better. Sometimes the need for it just goes away.

For Apache.org, check out the Apache Attic to see if a project is
officially retired.

<http://attic.apache.org/>
 
J

Joerg Meier

I do not see running on Java 1.2 as a problem. It was probably started
when 1.2 was relevant and why break the capability if not needed.

Running on Java of course is not a problem in and of itself, but software
being specifically tailored to run on 1.2 kind of seems like it's pretty
ancient.
Apache Commons Configurations do have recent updates:

Yeah, in this case I was referring to it's dependencies (lang 2.6, which is
the 1.2 version, instead of lang 3.1, last updated in January 2011,
collections, last updated in April 2008, and logging, last updated in 2007,
almost 5 years ago).

Liebe Gruesse,
Joerg
 
A

Arne Vajhøj

Running on Java of course is not a problem in and of itself, but software
being specifically tailored to run on 1.2 kind of seems like it's pretty
ancient.

If you have some software that was started 10 years ago and back then
it was decided to support 1.2, then it makes sense to keep that support
if there are no significant gain by dropping it.

Being backwards compatible unless very good reasons exists for not
being it is not ancient.
Yeah, in this case I was referring to it's dependencies (lang 2.6, which is
the 1.2 version, instead of lang 3.1, last updated in January 2011,
collections, last updated in April 2008, and logging, last updated in 2007,
almost 5 years ago).

Are there any inventions in collections or logging since 2008/2007 that
you miss?

Arne
 
L

Lew

"Seems" is such a weasel word. Who does the "seeming"? It *seems* like
you're trying to avoid responsibility for your judgment.

And it *seems* like you ignored that the library was updated for Java 5
compatibility, undercutting your very assumption.
If you have some software that was started 10 years ago and back then
it was decided to support 1.2, then it makes sense to keep that support
if there are no significant gain by dropping it.

Being backwards compatible unless very good reasons exists for not
being it is not ancient.
Apache Commons Configurations do have recent updates:

Yeah, in this case I was referring to it's [sic] dependencies (lang 2.6,which is
the 1.2 version, instead of lang 3.1, last updated in January 2011,
collections, last updated in April 2008, and logging, last updated in 2007,
almost 5 years ago).

Why are you so scared of something not updated in a while?

Rapid updates are not a bellwether of good quality.
Are there any inventions in collections or logging since 2008/2007 that
you miss?

Is there anything preventing you from using the packages under Java 7 with
the latest Collections library?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,744
Messages
2,569,484
Members
44,906
Latest member
SkinfixSkintag

Latest Threads

Top