Hi,
if possible, I suggest to update Maven 2.1 to use the latest version of
Classworlds instead of 1.2-alpha-12. The recent Hudson package is still
failing for an encoding like UTF-16, among others due to PLX-367 which
prevents Maven from booting.
In this context: Brian has once setup some ITs to run Maven with
file.encoding=UTF-16. Since Maven 2.0.x is to my knowledge locked to an
old Classworlds version (i.e. there is no chance for the ITs to ever
pass), it might be best to focus on the future and upgrade these ITs to
run for Maven 2.1 instead.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail:
dev-unsubscribe@...
For additional commands, e-mail:
dev-help@...
