Re: newer jikes may never get to testing (and thus stable)

2003-09-05 Thread Grzegorz B. Prokopski
On Sat, 2003-09-06 at 00:36, Matt Zimmerman wrote: > On Fri, Sep 05, 2003 at 10:16:53PM -0400, Grzegorz B. Prokopski wrote: > > > Package: jikes > > Version: 1.18-6 > > Severity: wishlist > > Please don't CC other addresses when mailing [EMAIL PROTECTED] Read the BTS > documentation about the X-

Re: newer jikes may never get to testing (and thus stable)

2003-09-05 Thread Matt Zimmerman
On Fri, Sep 05, 2003 at 10:16:53PM -0400, Grzegorz B. Prokopski wrote: > Package: jikes > Version: 1.18-6 > Severity: wishlist Please don't CC other addresses when mailing [EMAIL PROTECTED] Read the BTS documentation about the X-Debbugs-CC header. -- - mdz

Re: newer jikes may never get to testing (and thus stable)

2003-09-05 Thread Grzegorz B. Prokopski
On Sat, 2003-09-06 at 00:36, Matt Zimmerman wrote: > On Fri, Sep 05, 2003 at 10:16:53PM -0400, Grzegorz B. Prokopski wrote: > > > Package: jikes > > Version: 1.18-6 > > Severity: wishlist > > Please don't CC other addresses when mailing [EMAIL PROTECTED] Read the BTS > documentation about the X-

Re: newer jikes may never get to testing (and thus stable)

2003-09-05 Thread Matt Zimmerman
On Fri, Sep 05, 2003 at 10:16:53PM -0400, Grzegorz B. Prokopski wrote: > Package: jikes > Version: 1.18-6 > Severity: wishlist Please don't CC other addresses when mailing [EMAIL PROTECTED] Read the BTS documentation about the X-Debbugs-CC header. -- - mdz -- To UNSUBSCRIBE, email to [EMAI

newer jikes may never get to testing (and thus stable)

2003-09-05 Thread Grzegorz B. Prokopski
Package: jikes Version: 1.18-6 Severity: wishlist Hi all! I used to be very busy/without net during last months but I am back. And attacking ;-) The problem is that currently jikes (in the sense of source package, which is important from testing migration scripts POV) depends of a whole pile of

Re: JAVA_HOME and ant (was: [PROPOSAL] New Virtual Packages and way to handle Classpath)

2003-09-05 Thread Ben Burton
> >Then why push for $JAVA_HOME, which suffers from the same problem? > > Because I think there are a lot of programs, which rely on the > 'java.home' property to be set. Here is for example the result on > going thru the ant tasks. ant is IMO one of the important packages, > which should be made

newer jikes may never get to testing (and thus stable)

2003-09-05 Thread Grzegorz B. Prokopski
Package: jikes Version: 1.18-6 Severity: wishlist Hi all! I used to be very busy/without net during last months but I am back. And attacking ;-) The problem is that currently jikes (in the sense of source package, which is important from testing migration scripts POV) depends of a whole pile of

[PROPOSAL] 3. RfD on new debian java policy

2003-09-05 Thread Jan Schulz
Hallo, This is a significant rewrite of my previous proposal. To make discussion alittle easier, I've broken the subject line to tell, that this is the third request for discussion. The changes to the second try are * unfree interfaces are now 'additional to' the normal (free) debian packages,

Re: JAVA_HOME and ant (was: [PROPOSAL] New Virtual Packages and way to handle Classpath)

2003-09-05 Thread Ben Burton
> >Then why push for $JAVA_HOME, which suffers from the same problem? > > Because I think there are a lot of programs, which rely on the > 'java.home' property to be set. Here is for example the result on > going thru the ant tasks. ant is IMO one of the important packages, > which should be made

[PROPOSAL] 3. RfD on new debian java policy

2003-09-05 Thread Jan Schulz
Hallo, This is a significant rewrite of my previous proposal. To make discussion alittle easier, I've broken the subject line to tell, that this is the third request for discussion. The changes to the second try are * unfree interfaces are now 'additional to' the normal (free) debian packages,

JAVA_HOME and ant (was: [PROPOSAL] New Virtual Packages and way to handle Classpath)

2003-09-05 Thread Jan Schulz
Hallo Ben, * Ben Burton wrote: >I'm really not sure what you mean here. At the moment, using $CLASSPATH >is somewhat *more* portable across different JVMs than using -classpath. >In particular, it doesn't suffer from the ever-changing command-line >syntax, nor does it override the bootstrap class

JAVA_HOME and ant (was: [PROPOSAL] New Virtual Packages and way to handle Classpath)

2003-09-05 Thread Jan Schulz
Hallo Ben, * Ben Burton wrote: >I'm really not sure what you mean here. At the moment, using $CLASSPATH >is somewhat *more* portable across different JVMs than using -classpath. >In particular, it doesn't suffer from the ever-changing command-line >syntax, nor does it override the bootstrap class

Running native eclipse on Debian (unstable/x86)

2003-09-05 Thread Mark Wielaard
Hi, Someone asked how I got native eclipse running on my Debian box and how to get the JDT (Java Development Tools) and api documentation/code completion tooltips work out of the box. The following only explains how to get the needed binaries installed. For compiling from source you will need a l

Running native eclipse on Debian (unstable/x86)

2003-09-05 Thread Mark Wielaard
Hi, Someone asked how I got native eclipse running on my Debian box and how to get the JDT (Java Development Tools) and api documentation/code completion tooltips work out of the box. The following only explains how to get the needed binaries installed. For compiling from source you will need a l

Norton AntiVirus failed to scan an attachment in a message you sent.

2003-09-05 Thread NAVMSE-MAILSRV1
Recipient of the attachment: MAILSRV1, First Storage Group\Private Information Store (MAILSRV1), Mail Admin/Inbox Subject of the message: Re: That movie No action was taken on the attachment. Attachment application.pif was Logged Only for the following reasons: Scan Engine Failure (0x8

Norton AntiVirus failed to scan an attachment in a message you sent.

2003-09-05 Thread NAVMSE-MAILSRV1
Recipient of the attachment: MAILSRV1, First Storage Group\Private Information Store (MAILSRV1), Mail Admin/Inbox Subject of the message: Re: That movie No action was taken on the attachment. Attachment application.pif was Logged Only for the following reasons: Scan Engine Failure (0x8