public inbox for gentoo-java@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thufir <hawat.thufir@gmail.com>
To: gentoo-java@lists.gentoo.org
Subject: [gentoo-java]  gcj, maven, the GPL and ebuild
Date: Sat, 9 Sep 2006 22:56:51 +0100	[thread overview]
Message-ID: <Pine.LNX.4.64.0609092245160.3522@neenxvf.ubzryvahk.bet> (raw)

I've been sifting through the archives on these topics and would like a 
status report on java.  stat ;)

The best thing would be for gcj to catch-up to Java 5, but that won't be 
for a while.  There are several threads about ebuilds auto-magically 
fetching a Sun JRE or JDK, displaying a license and then installing.  That 
also would be nice in a more perfect world, but fetching a binary via the 
web browser every now and then isn't the greatest inconvenience in the 
world.

However, even were the Sun JDK easily installed as described above, it'd 
still be masked, as I understand, due to some source files in Gentoo not 
working with Java 5 due to problems with reserved words.

Then there's the philosophical problem with distributing compiled classes 
instead of building a java app from source.

Finally, I was amazed to read that maven is, apparently, windows-centric. 
Very disappointing.

The bottom line appears to be that java for Linux sucked, got better, but 
still sucks and will continue to suck for the foreseeable future.  Yes?


-Thufir

-- 
gentoo-java@gentoo.org mailing list



             reply	other threads:[~2006-09-09 21:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-09 21:56 Thufir [this message]
2006-09-09 22:05 ` [gentoo-java] gcj, maven, the GPL and ebuild Krzysiek Pawlik
2006-09-09 23:19   ` [gentoo-java] " Thufir
2006-09-10 14:10     ` [gentoo-java] " Alistair Bush
2006-09-10 14:47       ` Thufir
2006-09-10  5:52 ` [gentoo-java] " Joshua Nichols

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=Pine.LNX.4.64.0609092245160.3522@neenxvf.ubzryvahk.bet \
    --to=hawat.thufir@gmail.com \
    --cc=gentoo-java@lists.gentoo.org \
    /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