14.07.2013 Views

Contents - Cultural View

Contents - Cultural View

Contents - Cultural View

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Apache Harmony 24<br />

Apache Harmony<br />

Developer(s) Apache Software Foundation<br />

Stable release 5.0M14<br />

6.0M2 / June 7, 2010<br />

Development status Active<br />

Written in C++ and Java<br />

Operating system Windows and Linux<br />

Type Java Virtual Machine and Java Library<br />

License Apache License 2.0<br />

Website http:/ / harmony. apache. org<br />

Apache Harmony is an open source / free Java implementation from the Apache Software Foundation, starting with<br />

Java SE 5 and 6. It will be licensed under the Apache License, Version 2. It was announced in early May 2005 and<br />

on October 25, 2006, the Board of Directors voted to make Apache Harmony a top-level project.<br />

History<br />

Initiation<br />

The Harmony project was initially conceived as an effort to unite all developers of the Free Java implementations.<br />

Many developers expected that it would be the project above the GNU, Apache and other communities. GNU<br />

developers were invited into and participated during the initial, preparatory planning. Later it was decided not to use<br />

the code from GNU Classpath, and that Harmony would use an incompatible license; therefore blocking the sharing<br />

of code between Harmony and existing free Java projects. Apache developers would then write the needed classes<br />

from scratch and expect necessary large code donations from software companies.<br />

Reasons for rewriting from scratch<br />

The main reason for disagreements between the GNU Classpath and Apache projects is due to differences between<br />

the GNU General Public License (GNU Classpath's license also contains the linking exception) and Apache License.<br />

These disagreements are inspired by various organizations and individuals [1] that prefer the Apache License, which<br />

allows for closed source derived works. GNU Classpath can also be linked [2] with proprietary code, but it is legally<br />

difficult to make a closed source derivative of GNU Classpath itself. However, many free software developers think<br />

that the licenses and philosophy of these communities are not different enough to split the efforts, and the inability to<br />

find compromises is frequently estimated negatively. The occasionally appearing suggestion to view these projects<br />

as opposing forces does not find wide support. Enthusiasts of the free software tend to break the discussion with the<br />

simple words that "more free software is not a problem". [3]<br />

Difficulties to obtain a TCK license from Sun<br />

The Apache Software Foundation sent a letter to Sun Microsystems CEO, Jonathan Schwartz, on April 10, 2007,<br />

regarding their inability to acquire an acceptable license for the Java SE 5 Technology Compatibility Kit (TCK), a<br />

test kit needed by the project to demonstrate compatibility with the Java SE 5 specification, as required by the Sun<br />

specification license for Java SE 5. [4] What makes the license unacceptable for ASF is the fact that it imposes rights<br />

restrictions through limits on the "field of use" available to users of Harmony, not compliant with the Java<br />

Community Process rules. [5]

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!