public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Thomas Zander <zander@kde.org>
To: Steven Schwarz <schwarz@solekai.com>
Cc: mauve-discuss@sources.redhat.com, classpath@gnu.org
Subject: Re: can Mauve help me test a PersonalJava implementation?
Date: Fri, 29 Apr 2005 16:45:00 -0000	[thread overview]
Message-ID: <200504291840.02274.zander@kde.org> (raw)
In-Reply-To: <XFMail.20050429081640.schwarz@solekai.com>

[-- Attachment #1: Type: text/plain, Size: 754 bytes --]

On Friday 29 April 2005 17:16, Steven Schwarz wrote:
> If I compile with a JDK 1.4.2 or 1.5.0 I end up with class files with
> major.minor version 46.0.  If I attempt to run them with a
> PersonalJava or JDK 1.1.8 VM, I run up against the limitation that
> those VMs are only empowered to accept classes whose versions are in
> the range 45.0 .. 45.65535, i.e. strictly before version 46.0.  JDKs
> 1.2.2 and 1.3.1 will produce class files with versions before 46.0,
> but unfortunately, cannot compile Mauve, as I explained in my previous
> posting.


Good point.
Please do an cvs update on the build.xml in mauve and try again:
JAVA_HOME=/usr/lib/j2sdk1.5.0 ant jars

Oh; don't forget an ant clean first, naturally.
-- 
Thomas Zander

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-04-29 16:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-28 22:52 Steven Schwarz
2005-04-29  9:36 ` Thomas Zander
2005-04-29 15:17   ` Steven Schwarz
2005-04-29 15:31     ` Dalibor Topic
2005-04-29 15:33     ` Archie Cobbs
2005-04-29 16:39       ` Steven Schwarz
2005-04-29 16:46       ` Steven Schwarz
2005-05-09 16:19         ` Tom Tromey
2005-04-29 16:45     ` Thomas Zander [this message]
2005-04-30 23:28 ` Tom Tromey
2005-05-02 16:44   ` Steven Schwarz
2005-05-02 17:03     ` Thomas Zander

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200504291840.02274.zander@kde.org \
    --to=zander@kde.org \
    --cc=classpath@gnu.org \
    --cc=mauve-discuss@sources.redhat.com \
    --cc=schwarz@solekai.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).