Hi.
I am new to XmlUnit having just stumbled across it by chance and can see me
making great use of the .Net version for a project I am working on.
I am keen to get involved in the development and noticed there are a couple of
books with coverage of XmlUnit available.
Before I start poking around the code is it worthwhile getting any of these
books, or can anyone suggest any reading that will give me a firm footing of
the capabilities as they currently stand (particularly what would be required
to bring the Java & .Net APIs up to a similair level)?
>RE: Strongly naming the assembly
Have you looked into delay signing the assembly and sharing the key amongst the
release managers?
Look forward to hearing from you.
Cheers
Colin
________________________________________
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Stefan Bodewig [EMAIL
PROTECTED]
Sent: 04 June 2008 16:21
To: xmlunit-general@lists.sourceforge.net
Subject: [Xmlunit-general] Plans
Hi all,
just so that this list finally gets something other than spam. 8-)
Short term I plan to release XMLUnit Java 1.2 and XMLUnit.NET 0.3.2.
The Java version will be the current trunk and is a way to push the
new features (in particular the JAXP 1.3 validation stuff) out into
public. The major missing piece is documentation for the new
validation stuff.
On the .NET front I only plan two things:
(1) strongly name the assembly (still need to figure out a way of
protecting the key and sharing it with prospective release
managers other than myself, though)
(2) compile against NUnit 2.4.7 since 2.4.6 had serious performance
issues. I'm on the NUnit-user list discussing with Charlie Poole
to search for a way that allows XMLUnit users switching the NUNit
version without recompiling XMLUnit.
Longer term, these are really just rough sketches:
* fresh start, develop the Java and C# versions side by side, trying
to keep the APIs similar
* focus on the library aspects of XMLUnit, i.e. create a difference
engine and a validator library without external dependencies besides
Java (1.4) and .NET (1.1) at all
* include builders that allow writing tests using a fluent interface
(but that should probably not be the only way)
* provide integration with JUnit/NUnit maybe others as separate
jars/assemblies
* provide a legacy jar that maps the XMLUnit Java 1.2 API to the new
API.
Stefan
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Xmlunit-general mailing list
Xmlunit-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xmlunit-general
Edinburgh Business School is a Charity Registered in Scotland, SC026900
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Xmlunit-general mailing list
Xmlunit-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xmlunit-general
