My only concern would be one of support. Whilst fine for the moment, if we
remain at a fixed level forever,
we might find an upgrade forced upon us should we hit a bug in 2.8.1 some
time in the future.
Having said that we are now running with a proven Xerces-J version which
meets our needs.
Is 2.8.1 a pure maintenance release or does it introduce new features
and/or dependencies?
In general, I'd prefer to only upgrade jars when the need arises.
My 2c.
Kind Regards,
Graham.
_____________________________________________
Graham C Turrell CEng, MBCS
Chartered IT Practitioner
WebSphere ESB Foundation Technologies
DE3F16 / MP 211
IBM Labs
Hursley Park
Winchester, Hampshire
England. SO21 2JN
Tel +44-(0)1962-815018
email: [EMAIL PROTECTED]
"No army can withstand the force of an idea whose time
has come.". -Victor Hugo
"Jeremy Hughes"
<[EMAIL PROTECTED]
rg> To
Sent by: [email protected]
[EMAIL PROTECTED] cc
om
Subject
Xerces-J 2.8.1
15/09/2006 20:05
Please respond to
[EMAIL PROTECTED]
he.org
Hi, Xerces-J just released 2.8.1. Our ant build is set to require
2.8.0. It's easy enough to move up to 2.8.1 but should we? Should we
be moving up to the latest and greatest Xerces when an older one would
be sufficient. We don't require the latest JRE.
I'd be +1 to using the oldest Xerces that we can use and still pass
our unit tests. This then puts a lesser requirement on our users.
What do you all think?
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
