SV: More on UnitTesting

Hi Steve,

> Changes between 3.3.0 and trunk cover updates to framework 
> including the
> separation of logkit related classes from the api (resulting in api,
> impl and legacy jars), migration from excalibur/config to 
> unit/config, a
> bug fix to the util/env package, improvements to the meta task to
> support improved integration with Ant, updates to repository api and
> impl that move us towards a unified artifact protocol (which is the
> reason for the minor version bump), bugfixes in composition, 
> updates in
> activation to improve proxy handling, improvements to 
> merlin-cli (mainly
> related to build strategy), and improvements to merlin-unit to better
> handle ant driven execution.
Yep, that's a whole bunch of nice things!

> 
> Before moving to a release there's still more needed on completing the
> artifact protocol integration within the composition system and
> completing the build for a clean unix installation (not to mention
> resolution of the cygwin issue).
> 
> 
> > Maybe you could package an interim release like 3.3.1?
It is not that necessary right now, but there is the issue with
merlin/maven/magic breaking on any URI-related tests/runtime on Windows
since the default repo contains spaces (My Documents):

- RMI-adapter in the JMX-facility tries to register the URI to the class
files (file:jar:/c:/my documents)

- I found a bug related to validating XML parsing when you have e.g. the
schema shipping in a jar file, gives the same error
String temp = getClass().getResource("Schema.xsd").toString();


So maybe yes, it would be nice to have a point release since the MerlinUnit
is bound to break things if you test some special functionality. The XML bug
is really tricky to find without having the source :/

/peter

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]