Date: Mon, 26 Aug 2002 21:07:37 -0400 (EDT) From: Mikhail Kruk <meshko@mail.cs.brandeis.edu> To: Archie Cobbs <archie@dellroad.org> Cc: freebsd-java@FreeBSD.ORG Subject: Re: Jikes problems Message-ID: <Pine.LNX.4.44.0208262105480.5435-100000@orestes.cs.brandeis.edu> In-Reply-To: <200208270029.g7R0TeN36903@arch20m.dellroad.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I think the combination of #2 and #3 is optimal. That is all the problems on FreeBSD should always be reported to developers. One suggestion though: if 1.16 is that bad, maybe it's better to rename 1.16 to jikes-dev and keep jikes at 1.15? > Jikes 1.16 has several bugs. It core dumps, sometimes generates invalid > classfiles, and other bad stuff. Some of this I've seen and other things > only heard about. > > As maintainer of the port, I'm wondering what we should do about it... > > Option #0: Do nothing and live with it. > Option #1: Revert jikes port back to 1.15 > Option #2: Add a new port "jikes-stable" that builds version 1.15 > Option #3: Try to prod the jikes development team to fix the bugs > so jikes is more stable and then put out a new release. > > I'm thinking Option #2 might be best.. what do other people think? > > Thanks, > -Archie > > __________________________________________________________________________ > Archie Cobbs * Packet Design * http://www.packetdesign.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-java" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.44.0208262105480.5435-100000>