Simon Kitching wrote on Tuesday, June 14, 2005 9:13 AM: > On Tue, 2005-06-14 at 15:24 +1000, Brett Porter wrote: >> Firstly, I still believe if you've got sufficient testing, this isn't >> really necessary, and this discussion is getting a little carried >> away. > > The problem is that testing is supposed to be done by the > unit tests. But the unit tests won't pick this up, even when > testers download the source onto a machine with jdk1.3 and > run "maven test". > > The only way this would be picked up is if someone downloads > a RC jar file pre-built and then runs it in an application > that uses the class that has the problem. And that can't be > relied upon for commons projects with fairly small user bases.
It seems we need a new Maven plugin "jdktest". You configure the SDKs to be tested and the plugin uses those for the test code only. This might automatically ensure compatibility also with non-Sun JDKs. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
