Jakarta Project

From Wikipedia, the free encyclopedia

The Jakarta Project creates and maintains open source software for the Java platform. It operates as an umbrella project under the auspices of the Apache Software Foundation, and all of Jakarta products are released under the Apache License.

[edit] Subprojects

Major contributions by the Jakarta Project include tools, libraries and frameworks such as:

BCEL - a Java byte code manipulation library
BSF - a scripting framework
Cactus - a unit testing framework for server-side Java classes
Commons - a collection of useful classes intended to complement Java's standard library.
ECS - The Element Construction Set is a Java API for generating elements for various markup languages.
HttpComponents- The Hyper-Text Transfer Protocol.
JCS - JCS is a distributed caching system written in java.
JMeter - a load- and stress-testing tool.
ORO - Java classes that provide Perl5 compatible regular expressions.
POI - a pure Java port of Microsoft's popular file formats.
Regexp - Pure Java Regular Expression package.
Slide - a content repository primarily using WebDAV.
Taglibs - Repository for JSP custom tag libraries.
Turbine - a rapid development web application framework.
Velocity - a template engine.

Following projects were formerly part of Jakarta:

Ant - a build tool
Maven - a project build and management tool
Struts - a web application development framework
Tomcat - a JSP/Servlet container
Tapestry - A component object model based on JavaBeans properties and strong specifications.
HiveMind - a services and configuration microkernel

[edit] Project History

A frequent question in discussions related to Jakarta regards the origin of the name. Jakarta is not directly named after the capital city of Indonesia (which happens to be located on the Java island), nor after the Jakarta blue butterfly species. Instead, it is named after the conference room at Sun Microsystems where the majority of discussions leading to the project's creation took place. For more of Jakarta's history, please see the JavaWorld article from June 1999.