On Mon, 2006-01-30 at 15:05 -0800, Anthony Green wrote:
> Fedora Core does not include "Java(tm)", but it does include a tools
> suite and execution environment based on Free Software technologies
> that is capable of building and running many useful programs written
> in the Java programming language, including the Eclipse IDE, Tomcat,
> and OpenOffice.org.
Why the term "execution environment" rather than the "runtime
environment" most Java users are familiar with from JRE?
If changed, would "capable of building and executing" then sound better?
> In addition to the Free Software stack, Fedora Core is designed to let
> you install multiple Java implementations and switch between them
> using the "alternatives" command line tool.
I think the phrase "using the "alternatives" command line tool" is
redundant at this point, given the later explanation of how to switch.
> However, every Java system you install must be packaged using
> the JPackage Project's packaging guidelines.
> No proprietary Java vendor currently ships their products in JPackage
> compatible RPMs. Do not install RPMs from vendors such as Sun
> Microsystems, IBM or BEA without first repackaging them using the
> appropriate JPackage wrapper or compatibility package. Failure to do
> so will lead to unpredictable results.
The word "must" in the first part bothers me, as I don't think it's
strictly true.
How about something like:
The Java tools and software provided by Fedora Core follow the JPackage
Project's packaging guidelines. Installing RPM or binary packages
directly from vendors such as Sun Microsystems, IBM, or BEA, without
first repackaging them using the appropriate JPackage wrapper or
compatibility package, can lead to serious installation conflicts
between implementations with unpredictable results.
> Once installed properly, however, the root user should be able to
> switch between "java" and "javac" implementations using the
> "alternatives" command ("alternatives --config java" and "alternatives
> --config javac").
>
> Instructions on repackaging proprietary Java implementations may be
> found here: http://www.fedorafaq.org/fc3/custom_java.html
I would say "If installed properly" ... rather than subconsciously push
them to other implementations :)
Anyhow, despite my nits above, my real question is if there will also be
something to the effect of:
"Please note that despite utilizing the JPackage installation
guidelines, several of the Java application software packages shipped
with Fedora have been slightly modified from those provided by JPackage,
in order to work out of the box with the included compiler and runtime
environment. Additionally, the Fedora packages also include
pre-compiled fast and optimized native binary code alongside the
original Java bytecode JAR files. As a result, if you modify your Yum
configuration and update to packages shipped directly through the
JPackage Yum repository, you will end up with an unpredictable mix of
bytecode and binary software. Users wishing to maintain a supported
environment, by using the Free Java tools shipped with Fedora, are thus
advised to only update their systems with Java packages provided through
the Fedora and Fedora Extras Yum repositories, and not directly through
JPackage unless they plan to switch to a proprietary Java runtime. The
Fedora provided application software packages should continue to work
with other Java Runtime Environments which follow JPackage guidelines,
but as stated above, there is a good chance unmodified JPackage
applications will not work with the default Runtime Environment shipped
with Fedora."
I fell victim to the above, as once I saw that FC4 was built on top of
JPackage, the first thing I did was to rush out and update to the latest
and greatest from their Yum repo. The JPackage site, being geared
toward proprietary JVM's, conveniently provided me with Yum instructions
for my FC4 distro, with no mention of the possible hazards to my shiny
new Free Java setup.
--
Chris Hubick
mailto:chris@xxxxxxxxxx
http://www.hubick.com/
