Re: [Cooker] Java packages now built using icedtea by default

Anssi Hannula wrote:
> Java packages are now built using icedtea by default on ix86 and x86_64,
> via new java-rpmbuild virtual jdk package.
If we can build all java packages through icedtead, do we really need to
keep 3 different jdk in the distribution, especially proprietary ones ?

And even if we keep them, can we drop this ugly and fragile system of
alternative-setup based setup, and adopt the standard setup of all other
languages in the distribution, where we have a default version, and
eventually non-default ones if really needed (such as python vs
python2.4) ? I know you guys don't want to deviate from one single inch
from jpackage practices, but it may be time to realize those practices
date back from old times, and doesn't match current needs ? This one, in
particular, was made to be able to build some packages with the only
free jdk available at this moment, instead of hardcoding the use of
proprietary sun jdk. This is just not true anymore.

I'd like to have a java packaging in the distribution suiting the needs
of average users (the one needing to run java applications), not suiting
the needs of java developpers needing to test their own applications
against all different flavours of available jvms. Current situation is
just overkill.
--
Guillaume Rousse
Moyens Informatiques - INRIA Futurs
Tel: 01 69 35 69 62