On Mon, 2007-07-23 at 02:30 +0200, Dennis Lundberg wrote:
> Dennis Lundberg wrote:
> > My plan is to create a 1.1.1 release with Maven 2. However, Maven 2 runs
> > on a 1.4 JVM so we can't be 100% sure that the tests really pass on a
> > 1.2 JVM. The idea is that the RM will run a separate Ant script that
> > uses the binaries that M2 created (both main and test jars) and run it
> > on an earlier JVM, for verification.

Sounds good to me. I was initally thinking that Maven could use "run in
external jvm" to execute tests under 1.2/1.3 JVMs, but an Ant script
also sounds ok to me.

> >> JCL source will not compile for me on a 1.2.2 JVM (IIRC some 1.2 JVM had
> >> compilers bugs)
> >
> > Compiler bugs are of no concern to me at the moment. As explained above
> > the goal is to build with Maven 2 on a 1.4 JVM.

+1

> However, I'm seeing
> > runtime bugs in the JVM, which is disturbing.
>
> OK, I turned to old friend Google with the JIT error messages. After
> some digging it turns out that Ant doesn't like to run on an old JVM
> with the JIT turned on, so it has to be turned off. I've added
> instructions for this in build-testing.xml.

Well spotted :-)

>
> >> the tests will not compile for me on 1.3.1 JVM: MockSecurityManager uses
> >> Exception.getStackTrace() which was introduced with 1.4
> >
> > Aah, brilliant! I looked and looked at the two tests that use the damned
> > thing and couldn't find anything wrong with them. Thanks for the extra
> > pair of eyes!
>
> I've excluded the security tests from the Ant testing script, because I
> couldn't find a way to rewrite the MockSecurityManager so that it could
> run on earlier JVMs.

Fine with me.

Cheers,

Simon


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jaka...
For additional commands, e-mail: commons-dev-help@jaka...