public inbox for gentoo-java@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java]  Re: Re: Deprecating JDK 1.4
Date: Sat, 19 Jul 2008 20:06:27 +0300	[thread overview]
Message-ID: <48821F13.1080302@gentoo.org> (raw)
In-Reply-To: <g5o7pd$9lg$1@ger.gmane.org>

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

Jörg Schaible kirjoitti:
>
>> Also like I said - more and more things require 1.5, which means that all
>> things depending on them also need to be >= 1.5. For example: new hessian
>> requires >= 1.5, which means that mx4j needs also to be switched to 1.5,
>> which means we have to switch anything depending on mx4j, and so on.
> 
> So, and where can I define then my minimum supported JDK version
> (setting -source and -target)? Can I define that my system should be JDK
> 1.3 compatible - at least for all packages that support this (e.g.
> commons-logging)? Will packages like mx4j slotted to have the last JDK 1.4
> compatible and the JDK 5 compatible version? ... No, I know. However, I
> still have to provide JDK 1.3 (or at least 1.4) compatible software. And
> this does not simply mean to compile code, it also means to run it!
> 
> This will more or less lead to the situation, where I have to drop the
> complete Gentoo Java packages (except the JDK's themselves) and install
> everything else myself using the binaries.
> 
> - Jörg
> 

There is no pressing need to start building 1.5 bytecode as long as an 
application compiles with 1.4 but if an application uses 1.5 features we 
   will not be backporting the code to work with 1.4 which would be 
required for you to be able to run applications with 1.4. If you want to 
maintain such ebuilds we can give you access to an overlay where you can 
keep 1.4 compatible ebuilds around. The Java team doesn't have that much 
man power and it's better used towards other things than keeping 1.4 
functional with our hundreds of packages.

Regards,
Petteri


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2008-07-19 17:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-13 10:01 [gentoo-java] Deprecating JDK 1.4 Krzysiek Pawlik
     [not found] ` <d61c57300807130324o5446afaah3b94e23ada11e8ce@mail.gmail.com>
2008-07-13 10:31   ` [gentoo-java] " Krzysiek Pawlik
2008-07-14 21:16 ` Jörg Schaible
2008-07-16 12:15   ` Krzysiek Pawlik
2008-07-16 17:33     ` Petteri Räty
2008-07-16 17:57       ` Krzysiek Pawlik
2008-07-17 19:50     ` [gentoo-java] " Jörg Schaible
2008-07-19 17:06       ` Petteri Räty [this message]
2008-07-16 17:38 ` [gentoo-java] " Petteri Räty
2008-07-16 17:59   ` Krzysiek Pawlik
2008-07-16 18:09     ` Petteri Räty
2009-03-26 18:41       ` Serkan Kaba
2009-03-30 18:16         ` Petteri Räty

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=48821F13.1080302@gentoo.org \
    --to=betelgeuse@gentoo.org \
    --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