jdom at tuis.net
Thu Feb 16 20:43:20 PST 2012
I want some input on the way that JDOM has previously shipped as both
the 'core' and 'contrib' jars. It is my feeling that 'contrib' is a
second-class citizen in the JDOM process... this is reinforced by the
fact that I have paid it very little attention in the past 6 months and
there are still functional elements in it which are new to me.
I do not feel that I am in a position to 'support' the contrib code...
if there are bugs, I am not familiar enough with the code to fix them, etc.
If anyone has any ideas of how to deal with contrib I would appreciate
The options I see are:
1. keep the code as 'sample' code, but do not create a contrib jar (my
preference, I think).
2. keep the code, build it, but document that the 'contrib' jar contains
3. move the 'valuable' contrib code in to core, 'support' that code, and
'kill' the code that is not valuable.
I am interested in hearing people's ideas on this, and I am also
interested in hearing from people who use the contrib jar, and what they
use from that jar.
More information about the jdom-interest