Le vendredi 02 mai 2008 à 14:46 -0500, Les Mikesell a écrit : > The point is that for years fedora has had a scheme of package > requirements and no standard-compliant JVM that provided them. And it > has a strange symlinked path scheme that needs to be fixed when > installing a standard JVM. ROTFL SUN couldn't even keep a stable JVM naming, let alone a standard path, or agree with the other proprietary guys on common conventions, so don't invoque a "standard-compliant JVM" when this thing never existed. An archive of all the SUN, IBM and BEA jvm releases is a baroque history of inconsistent paths and name changes no sane third-party package could ever depend on (and BTW paths that contradicted existing standards like the FHS). What ISVs depend on is a fixed version that uses SUN's conventions-of-the-day, which are anything but standard. SUN's "standard" is JSR 277. It will happen in Java 1.7. Because of market pressure (.Net, OSGi and Maven). Every Java antedating 1.7 is a huge pile of paths, names and dependencies quirks, that were used to justify the fat sums Enterprises paid SUN and its partners to smooth out Java deployment. Why do you think Java has little life outside J2EE servers? Because the J2EE server guys take care of the Java environment setup the "standard" JVM makes such a mess of. -- Nicolas Mailhot
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
