Can we upgrade to xmlunit 1.3? It is only used for testing. This is AFAIK the latest stable, and is already used in GeoTools. It fixes a few bugs.
I propose to upgrade the top level pom dependency management (and one of my modules currently pinned to 1.1). There are a couple of other modules pinned to 1.1: istyler and a maven plugin. I will not touch these.
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
Ben Caradoc-Davies wrote:
Can we upgrade to xmlunit 1.3? It is only used for testing. This is AFAIK the latest stable, and is already used in GeoTools. It fixes a few bugs.
I propose to upgrade the top level pom dependency management (and one of my modules currently pinned to 1.1). There are a couple of other modules pinned to 1.1: istyler and a maven plugin. I will not touch these.
+1 from me, I actually tried the upgrade some time ago trying to chase
a bug (which was in my xpath expression, not in the library) and it
worked fine
Cheers
Andrea
On 09/06/10 18:16, Andrea Aime wrote:
+1 from me, I actually tried the upgrade some time ago trying to chase
a bug (which was in my xpath expression, not in the library) and it
worked fine
Thanks. That was my motivation as well: I wrote "//element[2]" when I meant "(//element)[2]", and no amount of xmlunit upgrading would make it do what I meant, not what I wrote. 
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre