From: Thomas Zander <zander@javalobby.org>
To: Andrew Haley <aph@redhat.com>
Cc: mauve-discuss@sources.redhat.com
Subject: Re: Some issues..
Date: Sat, 03 Apr 2004 13:41:00 -0000 [thread overview]
Message-ID: <200404031540.39350.zander@javalobby.org> (raw)
In-Reply-To: <16494.47358.415834.600012@cuddles.cambridge.redhat.com>
[-- Attachment #1: Type: Text/Plain, Size: 2814 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Saturday 03 April 2004 15:15, Andrew Haley wrote:
> Thomas Zander writes:
> > Next CVS does not compile with suns javac
> > (gnu/testlet/java/text/SimpleDateFormat/attribute.java)
>
> Would you please help us here by sending a patch?
It seems the author used some illegal constructs; I'm not sure what he meant
so I'll send the error messages instead.
[javac] Compiling 678 source files to /home/zander/sources/java/mauve/build
[javac] /home/zander/sources/java/mauve/gnu/testlet/java/text/SimpleDateFormat/attribute.java:160: illegal start of expression
[javac] static Format.Field[] fields = new Format.Field[] {
[javac] ^
[javac] /home/zander/sources/java/mauve/gnu/testlet/java/text/SimpleDateFormat/attribute.java:165: illegal start of expression
[javac] static int[] begin = new int[] {
[javac] ^
[javac] /home/zander/sources/java/mauve/gnu/testlet/java/text/SimpleDateFormat/attribute.java:168: illegal start of expression
[javac] static int[] end = new int[] {
I don't think these 'static' modifiers are needed in the first place; but why were
they added?
Second; I found at least one directory that contains java files without a
package; leading it to be uncompilable (due to duplicate class names)
I found:
gnu/testlet/BinaryCompatibility/altered/
Should those have package lines??
> > Please make the project seem 'less dead' to the passing eye!! If
> > Red-hat does not do anything; what about moving the project to
> > sourceforge or savannah ??
>
> How would moving the project to a different server help? Many people
> contribute to Mauve, Red Hat provide the server.
Oh; I did not want to imply mauve can't run on a RedHat server; my intent
was to let you know of the problems. And since I could not imagine being
the first to notice them I added a suggestion in case the pages on RedHat's
servers were not available to the project members.
Anyway; Please make the project seem 'less dead' to the passing eye!!
> > maybe someone here can answer my question posted on the
> > classpath list a couple of days ago (providing a patch to mauve).
> > http://mail.gnu.org/archive/html/classpath/2004-04/msg00000.html
>
> It was a very strange patch. A tarfile with one file that was a diff,
> and a new directory. However, that patch looks reasonable enough.
> However, there was no ChangeLog entry; we'll need one of those.
I noticed that the patch does not cleanly apply anymore; here is a new diff.
- --
Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAbr7TCojCW6H2z/QRAu+CAKCiC9VbH6bPq+rfQNga7ekPuLuaDACgwxI9
js0VZsiSLnzzLtIS1DitU20=
=MuJw
-----END PGP SIGNATURE-----
[-- Attachment #2: antCompat.diff --]
[-- Type: text/x-diff, Size: 1185 bytes --]
Index: gnu/testlet/SimpleTestHarness.java
===================================================================
RCS file: /cvs/mauve/mauve/gnu/testlet/SimpleTestHarness.java,v
retrieving revision 1.38
diff -u -3 -p -r1.38 SimpleTestHarness.java
--- gnu/testlet/SimpleTestHarness.java 29 Aug 2003 14:52:21 -0000 1.38
+++ gnu/testlet/SimpleTestHarness.java 3 Apr 2004 13:36:59 -0000
@@ -50,6 +50,11 @@ public class SimpleTestHarness
" (number " + (count + 1) + ")");
}
+
+ protected int getFailures() {
+ return failures;
+ }
+
public void check (boolean result)
{
if (!result)
Index: ChangeLog
===================================================================
RCS file: /cvs/mauve/mauve/ChangeLog,v
retrieving revision 1.563
diff -u -3 -p -r1.563 ChangeLog
--- ChangeLog 26 Mar 2004 13:32:23 -0000 1.563
+++ ChangeLog 3 Apr 2004 13:37:00 -0000
@@ -1,3 +1,8 @@
+2004-04-03 Thomas Zander <zander@kde.org>
+
+ * added an ant build option so the autotools are not needed if you use
+ a fully functional JVM (for example for writing tests).
+
2004-03-26 Mark Wielaard <mark@klomp.org>
* gnu/testlet/java/io/ObjectInputOutput/Compat2.java: Explicitly set
[-- Attachment #3: antMauve.tgz --]
[-- Type: application/x-tgz, Size: 2538 bytes --]
next prev parent reply other threads:[~2004-04-03 13:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-03 13:05 Thomas Zander
2004-04-03 13:16 ` Andrew Haley
2004-04-03 13:41 ` Thomas Zander [this message]
2004-04-03 15:42 ` Andrew Haley
2004-04-03 16:06 ` Thomas Zander
2004-04-15 22:22 ` Mark Wielaard
2004-04-16 9:31 ` Andrew Haley
2004-04-16 11:29 ` Mark Wielaard
2004-04-16 12:01 ` Some issues.. (batch_run and runner script documentation) Mark Wielaard
2004-04-16 12:04 ` Some issues Andrew Haley
2004-04-22 21:41 ` Mark Wielaard
2004-04-15 22:14 ` Mark Wielaard
2004-05-07 11:54 ` John Leuner
2004-05-07 13:25 ` Thomas
2004-04-23 9:12 Jeroen Frijters
2004-04-25 11:10 ` Mark Wielaard
2004-04-29 11:41 ` Andrew Haley
2004-04-29 13:16 ` Thomas
2004-04-29 15:29 ` Andrew Haley
2004-05-01 9:49 ` Thomas Zander
2004-05-02 12:27 ` Andrew Haley
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=200404031540.39350.zander@javalobby.org \
--to=zander@javalobby.org \
--cc=aph@redhat.com \
--cc=mauve-discuss@sources.redhat.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).