You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Stefano Mazzocchi <st...@apache.org> on 2003/07/12 00:04:29 UTC

Do we still have JVM compilation dependencies?

The build script says

+--------------------| W A R N I N G |----------------------+
   This build is targeted for use with JVM 1.3
 Using this build on a virtual machine other than the one
   it is targeted for may result in runtime errors.
+-----------------------------------------------------------+

do we still need that now that the database connection thing doesn't
need any specific JVM version?

-- 
Stefano.




Re: Do we still have JVM compilation dependencies?

Posted by Vadim Gritsenko <va...@verizon.net>.
Stefano Mazzocchi wrote:

>The build script says
>
>+--------------------| W A R N I N G |----------------------+
>   This build is targeted for use with JVM 1.3
> Using this build on a virtual machine other than the one
>   it is targeted for may result in runtime errors.
>+-----------------------------------------------------------+
>
>do we still need that now that the database connection thing doesn't
>need any specific JVM version?
>

We may need this warning for 1.4 -- it's not (always) compatible down to 
1.3 (example - new method in StringBuffer)


Vadim


RE: Do we still have JVM compilation dependencies?

Posted by Reinhard Pötz <re...@gmx.net>.

> -----Original Message-----
> From: Stefano Mazzocchi [mailto:stefano@apache.org] 
> Sent: Saturday, July 12, 2003 12:04 AM
> To: Apache Cocoon
> Subject: Do we still have JVM compilation dependencies?
> 
> 
> The build script says
> 
> +--------------------| W A R N I N G |----------------------+
>    This build is targeted for use with JVM 1.3
>  Using this build on a virtual machine other than the one
>    it is targeted for may result in runtime errors.
> +-----------------------------------------------------------+
> 
> do we still need that now that the database connection thing 
> doesn't need any specific JVM version?

Yes. I ran into big troubles as I built Cocoon using 1.4.2 and wanted 
to run it with a 1.3.1 JVM - this led to "Unsupported major.minor
version 48.0"

Reinhard