The Apache Software Foundation

History

The Apache Server started as a fork (an independent development stream)
of the NCSA httpd, a Web server created by Rob McCool at the National Center for Supercomputing Applications.  Further development to the server ceased after McCool's departure from NCSA in 1994, so an online community of individuals was formed to support and enhance its software via email collaboration. The founding members of that community (the Apache Group) included Brian Behlendorf, Roy Fielding, Rob Hartill, David Robinson, Cliff Skolnick, Randy Terbush, Robert Thau, and Andrew Wilson.

Within less than a year of the Apache Group's formation, the Apache server surpassed NCSA httpd as the #1 server on the Internet.

In March 1999, members of the Apache Group formed The Apache Software Foundation to provide organizational, legal, and financial support for the Apache HTTP Server. An additional goal for the Foundation was to serve as a neutral, trusted platform for the development of community-driven software.

Growth, the "Apache Way"

Beyond the Apache HTTP Server, dozens of ASF projects – from build tools to Web services to cloud computing and more – lead the way in Open Source technology.

At the ASF, community plays a vital role in the collaborative development of consensus-driven, enterprise-grade solutions. The number of projects led by the Apache community has grown from the singular Apache HTTP Server at the ASF's inception in 1999 to nearly 140 projects today.

The ASF's commitment to fostering a collaborative approach to development has long served as a model for producing consistently high quality software and helping advance the future of open development. Through its leadership, robust community, and meritocratic process known as the "Apache Way", the ASF continues to gain recognition as one of the most successful influencers in Open Source.

Through the Apache Way, the ASF is able to spearhead new projects that meet the demands of the marketplace and help users achieve their business goals. With the Apache Incubator mentoring more projects than ever before, the ASF continues to meet the growing demand for quality Open Source products.

"Community Over Code": among the Foundation's core tenets is open collaboration through respectful, honest, technically-focused interaction. The ASF's success is testament to its outstanding community efforts that serve as best practices widely embraced by organizations and individuals alike.

"If it didn't happen on-list, it didn't happen": building upon the transparency-oriented culture of the Apache Group, whose collaboration took place on email lists, millions of messages are archived on Apache publicly-accessible mailing lists, documenting the ASF's achievements over the past decade.

"Meritocracy in Action": the ASF's tagline reflects an average of 10,000 code contributions (commits) made each month. The ASF is responsible for millions of lines of code by more than 2,000 ASF Committers and countless contributors across the Open Source landscape. Nearly 500 community-driven modules have been developed to extend functionality of the Apache HTTP Server alone.

Milestones

February 23, 1994: Individual patch authors around the world are invited to join the "new-httpd" mailing list to discuss enhancements and future releases of NCSA httpd. The Apache name was chosen for this new effort within the first few days of discussion, along with basic rules for email-based collaboration and a mission to replace the existing server with a standards-based, open source, and extensible software system.

March 15, 1994: Apache-style voting created (+1, 0, -1; with '-1' meaning 'no', '0' meaning 'neutral', and '+1' meaning 'yes.')

March 18, 1994: First Apache Group release (Apache 0.2)

Apache server v.1.0 was released in December 1995. Four years later, Apache HTTP Server v.1.3.0 was released, and rapidly becoming the most popular Web server on the planet.

Apache HTTP Server v.2.0 alpha was released in March 2000, with the first general availability release two years later. V.2.0 remained best-of-breed sever until the release of v.2.2.0 in December 2005, and is widely deployed across the Internet.

In February 2009, the Apache HTTP Server became the first Web server software in history to surpass the 100 million Website milestone.

The most current, best-of-breed, stable version of the Apache HTTP Server is v.2.2.14, released September 2009. Developers seeking to test new features and preview what will become stable Version 2.4 are able to do so today with the development of v.2.3.5.

Earlier this month, after ten years and more than forty revisions, the Apache HTTP Server v.1.3.x officially reached end of life status with the release of v.1.3.42. Future patches to v.1.3.x will be for critical security updates only.

The Apache HTTP Server remains the world's most beloved Web server, forming the backbone of nearly 70% of all sites on the Internet.

Availability

The Apache HTTP Server is available for a variety of operating systems, including Unix, Linux, GNU, FreeBSD, Netware, Solaris, Windows, Mac OS X, OS/2, TPF, and eCS. In addition, the Apache HTTP Server is redistributed through many proprietary software packages such as WebSphere, Oracle RDBMS, Kylix, NetWare, and Delphi, as well as numerous Linux distributions.

All ASF projects, including the Apache HTTP Server, are available free of charge under the Apache Software License v.2.0. To download, or for more information, visit http://httpd.apache.org/

About The Apache Software Foundation (ASF)

Established in 1999, the all-volunteer Foundation oversees more than seventy leading Open Source projects, including Apache HTTP Server — the world's most popular Web server software. Through The ASF's meritocratic process known as "The Apache Way," more than 300 individual Members and 2,000 Committers successfully collaborate to develop freely available enterprise-grade software, benefiting millions of users worldwide: thousands of software solutions are distributed under the Apache License; and the community actively participates in ASF mailing lists, mentoring initiatives, and ApacheCon, the Foundation's official user conference, trainings, and expo. The ASF is funded by individual donations and corporate sponsors including Facebook, Google, HP, Microsoft, Progress Software, SpringSource, and Yahoo! For more information, visit http://www.apache.org/.

Bug

  * [MYFACES-2480] - @ResourceDependencies does not work on custom behaviors
  * [MYFACES-2500] - ResponseWriter clone should not include itself
  * [MYFACES-2507] - onClick on commandLink does not trigger loading of required jsf.js
  * [MYFACES-2516] - Allow any child for f:event in the case of a PreRenderViewEvent
  * [MYFACES-2517] - Problem with flash and GET
  * [MYFACES-2520] - UnsupportedOperationException when launching Trinidad 2 w/ MyFaces2 in Jetty
  * [MYFACES-2522] - f:event wrong attribute name
  * [MYFACES-2525] - Split javax.faces package in OSGi
  * [MYFACES-2526] - javax.faces.view.facelets.ResourceResolver support
  * [MYFACES-2527] - Support for decorator design pattern: RenderKit(s)
  * [MYFACES-2530] - ActionSourceRule does not deal with jsf 1.1 ActionSouce instances
  * [MYFACES-2532] - getClientId() should not be called from listener registering tree changes on DefaultFaceletsStateManagementStrategy and PostAddToViewEvent
  * [MYFACES-2533] - FaceletViewDeclarationLanguage call StateManager.saveView() before write document
  * [MYFACES-2534] - ComponentSupport.addFacet adds a panel when there is only one component as a child
  * [MYFACES-2535] - view-param on navigation case redirects not being handled properly
  * [MYFACES-2537] - FacesConfigurator.sortRelativeOrderingList() algorithm is broken trying to resolve some examples
  * [MYFACES-2540] - Facelets server state saving does not work
  * [MYFACES-2541] - Support for actionlistener method without ActionEvent parameter
  * [MYFACES-2544] - UIViewRoot skips uncorrectly encodeBegin
  * [MYFACES-2547] - FacesConfigurator absolute ordering does not handle files with no name correctly
  * [MYFACES-2551] - Set charset=iso-8859-1 using <f:view> in facelets page makes current page not being rendered
  * [MYFACES-2553] - Handle MethodExpressions on <composite:attribute> correctly
  * [MYFACES-2556] - FaceletViewDeclarationLanguage should use javax.faces.event.ActionEvent instead of java.awt.event.ActionEvent
  * [MYFACES-2557] - AbortProcessingExceptions must be handled by the ExceptionHandler
  * [MYFACES-2558] - composite:attributes action, actionListener, validator and valueChangeListener don't need the attribute method-signature

Improvement

  * [MYFACES-2510] - Remove RendererUtils.NOTHING
  * [MYFACES-2545] - ProjectStage can be set via System Property and ProjectStage!=Production should create a log entry
  * [MYFACES-2548] - META-INF resource lookup in OSGi environment
  * [MYFACES-2549] - Support for valueChangeListener method without ValueChangeEvent parameter

New Feature

  * [MYFACES-2531] - Support for name/library attributes with h:commandButton
  * [MYFACES-2542] - Don't throw exception if no SelectItems found

Task

  * [MYFACES-2483] - Find a way to allow c:if work with partial state saving enabled
  * [MYFACES-2502] - Component state is lost for composite component childs of facets relocated by composite:insertChildren or composite:insertFacet
  * [MYFACES-2503] - f:event should support no arg method on listener attribute
  * [MYFACES-2511] - Handle javax.faces.validator.DISABLE_DEFAULT_BEAN_VALIDATOR correctly
  * [MYFACES-2512] - Ensure invocation of nextHandler.apply() in ValidatorTagHandlerDelegate when in wrapping-mode
  * [MYFACES-2514] - An empty <default-validators> in faces-config should disable default validators
  * [MYFACES-2518] - BeanValidator should not be installed if bean validation is not available
  * [MYFACES-2519] - f:event could be registered twice if it is child of UIViewRoot
  * [MYFACES-2524] - Change ExternalSpecifications to enable using it in automated tests
  * [MYFACES-2538] - Remove resourceVersion and libraryVersion from resource identifiers