|Line 95:||Line 95:|
== JBoss AS ==
== JBoss AS ==
The [[SIGs/Java|Java SIG]] is working on packaging [http://jboss.org/as7 JBoss AS 7], along with a minimal set of required JARs, to provide this Open Source Java EE application server as a service in Fedora. You can learn more about the effort and the current progress on the [[JBossAS7|JBoss AS 7 on Fedora]] page.
The [[SIGs/Java|Java SIG]] is working on packaging [http://jboss.org/as7 JBoss AS 7], along with a minimal set of required JARs, to provide this Open Source Java EE application server as a service in Fedora.
You can learn more about the effort and the current progress on the [[JBossAS7|JBoss AS 7 on Fedora]] page.
= Teaching and Learning Java =
= Teaching and Learning Java =
Revision as of 07:29, 16 January 2012
- 1 Java on Fedora
- 2 Terminology
- 3 Java Runtime Environments (JRE)
- 4 Java Develoment Tools (SDK)
- 5 Java Server Side Environments
- 6 Teaching and Learning Java
- 7 Open Issues with Java packages
- 8 Communicate
- 9 See Also
- 10 References
Java on Fedora
Fedora uses a Free software stack that consists of OpenJDK, GNU Compiler for Java, GNU Classpath and the Eclipse Java compiler to provide Java support. See our Java/FAQ for more information on that. Note that AOT compilation using GCJ has been deprecated (made optional) and new or updated packages will be built using OpenJDK to produce regular Java bytecode.
Software mentioned on this page may come in different packaging formats. Fedora's own packages (RPM) are easy to install (with Yum) and installation instructions can be found from Docs/Drafts/SoftwareManagementGuide. Third party packages may be in archive formats (.zip, tar) for which case-specific instructions should be provided.
In Java context, terms may be a bit confusing for newcomers. JRE (Java Runtime Environment) stands for virtual machine, which is able to run Java programs.
JDK (Java Development Kit) or SDK (Software Developmenet Kit) is needed to develop Java programs. Many SDK packages these days also ship JRE, or to confuse more, no separate JRE is provided and thus terminal installations are supposed to include the development environment.
Terms AOT (Ahead of Time]), SE, J2EE need some more explanation.
Java Runtime Environments (JRE)
Java's history is well known to consist different JRE implementations and wide variety of combinations which work together. Different implementations can be installed simultaneously to Fedora and activated one at the time. Activation is done using the Alternatives system (also used to change some other subsystems). Java's subsystem name is surprisingly java and typical commands include:
# alternatives --display java
# alternatives --config java
See alternative's own documentation for more information for usage and parts involved.
Should be noted that JRE implementations installed outside Fedora distribution, may not support alternatives and thus not be visible there. Then the symbolic links under directory /etc/alternatives must be manually fixed.
OpenJDK and project IcedTea
Fedora has shipped OpenJDK as default JRE implementation since Fedora release 9. It's based on Sun Microsystem's JavaOne open source release and complemented by Red Hat's IcedTea project that implements the missing third party components that Sun could not release under free License.
OpenJDK's java.library.path, shared librarary paths for i386 are:
and for x86_64:
OpenJDK package name on Fedora is java-1.6.0-openjdk.
GNU GCJ+GIJ for Java
GCJ JRE package on Fedora is java-1.5.0-gcj.
Oracle's Java SE
Original Oracle's Java SE (Standard Edition) can be downloaded directly from http://www.java.com/en/download/ and installed manually.
You're, however, encouraged to try out the OpenJDK runtime first.
Please add your knowledge about Harmony and Fedora.
Fedora's JRE in browser environment can be tested using the following test pages:
If these don't work, proceed with Java/Troubleshooting page.
Java Develoment Tools (SDK)
The following SDKs are listed in alphabetic order.
See our Eclipse page for an integrated development environment platform that itself is written in Java and has plugin support for many programming languages.
IntelliJ IDEA is considered by many the ultimate Java development environment. A commercial project for many years, IntelliJ IDEA became open-source in 2009 by releasing the IntelliJ IDEA Community Edition. It's part of the Fedora packages and can easily the installed with yum. IntelliJ is written in Java, features a portable Swing UI and is extensible via plugins.
Fedora includes a somewhat customized version of Maven in the distribution. The customization is purely to make Maven work well in offline mode with the rest of the system. Details on how packagers can use this customized Maven are located at Java/JPPMavenReadme . We are in the process of upgrading from maven2 2.0.4 to maven2 2.0.8 (ETA = F12). Once that is achieved we will proceed immediately to maven2 2.0.9 and then to 2.0.10. The reason for going by steps is that it is easier to bootstrap a maven2 release from the previous one. Also related to maven2, a feasibility study is being performed to change the installation of Java packages to become a valid maven2 repository. We will no longer have to modify maven2 (not even with our small patch), and it wil be easier to support parallel installation of either "legacy" or "progressive" versions of Java packages. Once some positive results are obtained, it will be discussed on the fedora-devel-java-list.
The "reference" Java IDE, developed for many years by Sun(now Oracle). NetBeans is written in Java, features a portable Swing UI, out of the box support for many Java tools and frameworks and it's extensible via plugins.
Java Server Side Environments
Fedora ships Apache Tomcat as part of standard distribution.
Apache Tomcat package name on Fedora is tomcat6.
You can learn more about the effort and the current progress on the JBoss AS 7 on Fedora page.
Teaching and Learning Java
As part of planning and implementing new 100% FLOSS Java components into Fedora, this draft document has been opened to give developers a place to teach each other about best practices, patterns, etc.
Open Issues with Java packages