<rss version="2.0">
  <channel>
    <title>Apache Software Foundation Project Releases</title>
    <link>http://projects.apache.org/</link>
    <generator>Projects Site Generator</generator>
    <language>en-us</language>
    <description>All projects managed by the Apache Software Foundation release software. This feed shows the latest releases.</description>
    <copyright>The Apache Software Foundation</copyright>
    <webMaster>site-dev@apache.org</webMaster>
    <pubDate>Wed, 10 Feb 2010 03:30:22 GMT</pubDate>
    <image>
      <title>Apache Software Foundation Project Releases</title>
      <url>http://projects.apache.org/images/feather_a.gif</url>
      <link>http://projects.apache.org/</link>
      <width>40</width>
      <height>40</height>
    </image>
    <item>
      <title>Release of Apache Ant, version 1.8.0</title>
      <description>
        <p>
          <a href="/projects/ant.html">Apache Ant</a>
        </p>
        <p>Apache Ant is a Java-based build tool.</p>
      </description>
      <guid isPermaLink="false">Apache_Ant_id286531025</guid>
      <link>http://ant.apache.org/bindownload.cgi</link>
      <pubDate>Mon, 8 Feb 2010 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache HTTP Server, version 1.3.42</title>
      <description>
        <p>
          <a href="/projects/http_server.html">Apache HTTP Server</a>
        </p>
        <p>
The Apache HTTP Server is an open-source HTTP server for modern
operating systems including UNIX, MS-Windows, Macintosh and Netware.
The goal of this project is to provide a secure, efficient and
extensible server that provides HTTP services in sync with the current
HTTP standards. Apache has been the most popular web server on the
Internet since April of 1996.
    </p>
      </description>
      <guid isPermaLink="false">Apache_HTTP_Server_id286548484</guid>
      <link>http://httpd.apache.org/download.cgi</link>
      <pubDate>Tue, 2 Feb 2010 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache Xerces C++ XML Parser, version 3.1.0</title>
      <description>
        <p>
          <a href="/projects/xerces_c++_xml_parser.html">Apache Xerces C++ XML Parser</a>
        </p>
        <p>
     Xerces-C++ is a validating XML parser written in a portable subset of C++. Xerces-C++ makes it easy to give your application the ability to read and write XML data. A shared library is provided for parsing, generating, manipulating, and validating XML documents.
     Xerces-C++ is faithful to the XML 1.0 and 1.1 recommendations and many associated standards.
     The parser provides high performance, modularity, and scalability. Source code, samples and API documentation are provided with the parser. For portability, care has been taken to make minimal use of templates, no RTTI, and minimal use of #ifdefs.
    </p>
      </description>
      <guid isPermaLink="false">Apache_Xerces_C++_XML_Parser_id286560954</guid>
      <link>http://xml.apache.org/xerces-c/download.cgi</link>
      <pubDate>Mon, 1 Feb 2010 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache Lenya, version 2.0.3</title>
      <description>
        <p>
          <a href="/projects/lenya.html">Apache Lenya</a>
        </p>
        <p>Apache Lenya is an Open Source Java/XML Content Management Framework and comes with revision control, site management, scheduling, search, WYSIWYG editors, and workflow.</p>
      </description>
      <guid isPermaLink="false">Apache_Lenya_id286552232</guid>
      <link>http://lenya.apache.org/docs/2_0_x/installation/index.html</link>
      <pubDate>Wed, 20 Jan 2010 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache Cayenne, version 3.0M6</title>
      <description>
        <p>
          <a href="/projects/cayenne.html">Apache Cayenne</a>
        </p>
        <p>Cayenne is a powerful, full-featured, opensource framework created for developers working with relational databases. it seamlessly maps any relational database to Java objects, reducing development time and adding considerable functionality to any application which requires a database. Developers using Cayenne will be able to concentrate on the core business requirements and the data model instead of the SQL details. The application can then be easily moved to any JDBC-capable database. In addition to management of persistent Java objects mapped to relational databases, Cayenne provides a plethora of features including single method call queries and updates (including atomic updates of all modified objects), seamless integration of multiple databases into a single virtual data source, three tier persistence with caching on the remote client, paging of results, record locking, and many more features. JPA compliance is in progress.</p>
      </description>
      <guid isPermaLink="false">Apache_Cayenne_id286532631</guid>
      <link>http://cayenne.apache.org/download.html</link>
      <pubDate> GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache Velocity, version 1.6.3</title>
      <description>
        <p>
          <a href="/projects/velocity.html">Apache Velocity</a>
        </p>
        <p>Velocity is a Java-based template engine. It permits anyone to use a simple yet powerful template language to reference objects defined in Java code.

When Velocity is used for web development, Web designers can work in parallel with Java programmers to develop web sites according to the Model-View-Controller (MVC) model, meaning that web page designers can focus solely on creating a site that looks good, and programmers can focus solely on writing top-notch code. Velocity separates Java code from the web pages, making the web site more maintainable over its lifespan and providing a viable alternative to Java Server Pages (JSPs) or PHP. </p>
      </description>
      <guid isPermaLink="false">Apache_Velocity_id286559810</guid>
      <link>http://velocity.apache.org/download.cgi</link>
      <pubDate>Wed, 16 Dec 2009 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache XML Commons External, version 1.4.01</title>
      <description>
        <p>
          <a href="/projects/xml_commons_external.html">Apache XML Commons External</a>
        </p>
        <p>The External components portion of Apache XML Commons contains interfaces that are defined by external standards organizations. For DOM, that's the W3C; for SAX it's David Megginson (http://www.saxproject.org); for JAXP it's Sun. While we could send users to each of the primary sources for these deliverables, keeping our own versions of these in the XML Commons repository gives us a number of advantages: 1) Simplicity of downloads; users get the whole product from one place, 2) Better version control; we can only take fixes we want and add Apache-specific changes, 3) Better overview documentation of how these interfaces fit into the XML processing world, 4) More chance for cross-project community building within Apache projects.</p>
      </description>
      <guid isPermaLink="false">Apache_XML_Commons_External_id286564621</guid>
      <link>http://xerces.apache.org/mirrors.cgi</link>
      <pubDate>Tue, 15 Dec 2009 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache XML Commons External, version 1.3.05</title>
      <description>
        <p>
          <a href="/projects/xml_commons_external.html">Apache XML Commons External</a>
        </p>
        <p>The External components portion of Apache XML Commons contains interfaces that are defined by external standards organizations. For DOM, that's the W3C; for SAX it's David Megginson (http://www.saxproject.org); for JAXP it's Sun. While we could send users to each of the primary sources for these deliverables, keeping our own versions of these in the XML Commons repository gives us a number of advantages: 1) Simplicity of downloads; users get the whole product from one place, 2) Better version control; we can only take fixes we want and add Apache-specific changes, 3) Better overview documentation of how these interfaces fit into the XML processing world, 4) More chance for cross-project community building within Apache projects.</p>
      </description>
      <guid isPermaLink="false">Apache_XML_Commons_External_id286564637</guid>
      <link>http://xerces.apache.org/mirrors.cgi</link>
      <pubDate>Tue, 15 Dec 2009 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache XML Commons External, version 1.2.06</title>
      <description>
        <p>
          <a href="/projects/xml_commons_external.html">Apache XML Commons External</a>
        </p>
        <p>The External components portion of Apache XML Commons contains interfaces that are defined by external standards organizations. For DOM, that's the W3C; for SAX it's David Megginson (http://www.saxproject.org); for JAXP it's Sun. While we could send users to each of the primary sources for these deliverables, keeping our own versions of these in the XML Commons repository gives us a number of advantages: 1) Simplicity of downloads; users get the whole product from one place, 2) Better version control; we can only take fixes we want and add Apache-specific changes, 3) Better overview documentation of how these interfaces fit into the XML processing world, 4) More chance for cross-project community building within Apache projects.</p>
      </description>
      <guid isPermaLink="false">Apache_XML_Commons_External_id286564670</guid>
      <link>http://xerces.apache.org/mirrors.cgi</link>
      <pubDate>Tue, 15 Dec 2009 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache XML Commons External, version 1.4.01</title>
      <description>
        <p>
          <a href="/projects/xml_commons_external.html">Apache XML Commons External</a>
        </p>
        <p>The External components portion of Apache XML Commons contains interfaces that are defined by external standards organizations. For DOM, that's the W3C; for SAX it's David Megginson (http://www.saxproject.org); for JAXP it's Sun. While we could send users to each of the primary sources for these deliverables, keeping our own versions of these in the XML Commons repository gives us a number of advantages: 1) Simplicity of downloads; users get the whole product from one place, 2) Better version control; we can only take fixes we want and add Apache-specific changes, 3) Better overview documentation of how these interfaces fit into the XML processing world, 4) More chance for cross-project community building within Apache projects.</p>
      </description>
      <guid isPermaLink="false">Apache_XML_Commons_External_id286564621</guid>
      <link>http://xerces.apache.org/mirrors.cgi</link>
      <pubDate>Tue, 15 Dec 2009 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache XML Commons External, version 1.3.05</title>
      <description>
        <p>
          <a href="/projects/xml_commons_external.html">Apache XML Commons External</a>
        </p>
        <p>The External components portion of Apache XML Commons contains interfaces that are defined by external standards organizations. For DOM, that's the W3C; for SAX it's David Megginson (http://www.saxproject.org); for JAXP it's Sun. While we could send users to each of the primary sources for these deliverables, keeping our own versions of these in the XML Commons repository gives us a number of advantages: 1) Simplicity of downloads; users get the whole product from one place, 2) Better version control; we can only take fixes we want and add Apache-specific changes, 3) Better overview documentation of how these interfaces fit into the XML processing world, 4) More chance for cross-project community building within Apache projects.</p>
      </description>
      <guid isPermaLink="false">Apache_XML_Commons_External_id286564637</guid>
      <link>http://xerces.apache.org/mirrors.cgi</link>
      <pubDate>Tue, 15 Dec 2009 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache XML Commons External, version 1.2.06</title>
      <description>
        <p>
          <a href="/projects/xml_commons_external.html">Apache XML Commons External</a>
        </p>
        <p>The External components portion of Apache XML Commons contains interfaces that are defined by external standards organizations. For DOM, that's the W3C; for SAX it's David Megginson (http://www.saxproject.org); for JAXP it's Sun. While we could send users to each of the primary sources for these deliverables, keeping our own versions of these in the XML Commons repository gives us a number of advantages: 1) Simplicity of downloads; users get the whole product from one place, 2) Better version control; we can only take fixes we want and add Apache-specific changes, 3) Better overview documentation of how these interfaces fit into the XML processing world, 4) More chance for cross-project community building within Apache projects.</p>
      </description>
      <guid isPermaLink="false">Apache_XML_Commons_External_id286564670</guid>
      <link>http://xerces.apache.org/mirrors.cgi</link>
      <pubDate>Tue, 15 Dec 2009 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache XML Commons External, version 1.4.01</title>
      <description>
        <p>
          <a href="/projects/xml_commons_external.html">Apache XML Commons External</a>
        </p>
        <p>The External components portion of Apache XML Commons contains interfaces that are defined by external standards organizations. For DOM, that's the W3C; for SAX it's David Megginson (http://www.saxproject.org); for JAXP it's Sun. While we could send users to each of the primary sources for these deliverables, keeping our own versions of these in the XML Commons repository gives us a number of advantages: 1) Simplicity of downloads; users get the whole product from one place, 2) Better version control; we can only take fixes we want and add Apache-specific changes, 3) Better overview documentation of how these interfaces fit into the XML processing world, 4) More chance for cross-project community building within Apache projects.</p>
      </description>
      <guid isPermaLink="false">Apache_XML_Commons_External_id286564621</guid>
      <link>http://xerces.apache.org/mirrors.cgi</link>
      <pubDate>Tue, 15 Dec 2009 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache XML Commons External, version 1.3.05</title>
      <description>
        <p>
          <a href="/projects/xml_commons_external.html">Apache XML Commons External</a>
        </p>
        <p>The External components portion of Apache XML Commons contains interfaces that are defined by external standards organizations. For DOM, that's the W3C; for SAX it's David Megginson (http://www.saxproject.org); for JAXP it's Sun. While we could send users to each of the primary sources for these deliverables, keeping our own versions of these in the XML Commons repository gives us a number of advantages: 1) Simplicity of downloads; users get the whole product from one place, 2) Better version control; we can only take fixes we want and add Apache-specific changes, 3) Better overview documentation of how these interfaces fit into the XML processing world, 4) More chance for cross-project community building within Apache projects.</p>
      </description>
      <guid isPermaLink="false">Apache_XML_Commons_External_id286564637</guid>
      <link>http://xerces.apache.org/mirrors.cgi</link>
      <pubDate>Tue, 15 Dec 2009 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache XML Commons External, version 1.2.06</title>
      <description>
        <p>
          <a href="/projects/xml_commons_external.html">Apache XML Commons External</a>
        </p>
        <p>The External components portion of Apache XML Commons contains interfaces that are defined by external standards organizations. For DOM, that's the W3C; for SAX it's David Megginson (http://www.saxproject.org); for JAXP it's Sun. While we could send users to each of the primary sources for these deliverables, keeping our own versions of these in the XML Commons repository gives us a number of advantages: 1) Simplicity of downloads; users get the whole product from one place, 2) Better version control; we can only take fixes we want and add Apache-specific changes, 3) Better overview documentation of how these interfaces fit into the XML processing world, 4) More chance for cross-project community building within Apache projects.</p>
      </description>
      <guid isPermaLink="false">Apache_XML_Commons_External_id286564670</guid>
      <link>http://xerces.apache.org/mirrors.cgi</link>
      <pubDate>Tue, 15 Dec 2009 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache HttpComponents Client, version 4.0.1</title>
      <description>
        <p>
          <a href="/projects/httpcomponents_client.html">Apache HttpComponents Client</a>
        </p>
        <p>
HttpClient is a library for client-side HTTP communication built on HttpCore.
It provides connection management, cookie management, and authentication.
This is the successor to the widely used Jakarta Commons HttpClient 3.1.
    </p>
      </description>
      <guid isPermaLink="false">Apache_HttpComponents_Client_id286547034</guid>
      <link>http://httpcomponents.apache.org/downloads.cgi</link>
      <pubDate>Fri, 11 Dec 2009 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache HttpComponents Client, version 4.1-alpha1</title>
      <description>
        <p>
          <a href="/projects/httpcomponents_client.html">Apache HttpComponents Client</a>
        </p>
        <p>
HttpClient is a library for client-side HTTP communication built on HttpCore.
It provides connection management, cookie management, and authentication.
This is the successor to the widely used Jakarta Commons HttpClient 3.1.
    </p>
      </description>
      <guid isPermaLink="false">Apache_HttpComponents_Client_id286545614</guid>
      <link>http://httpcomponents.apache.org/downloads.cgi</link>
      <pubDate>Fri, 11 Dec 2009 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache Commons Pool, version 1.5.4</title>
      <description>
        <p>
          <a href="/projects/commons_pool.html">Apache Commons Pool</a>
        </p>
        <p>Commons Object Pooling Library</p>
      </description>
      <guid isPermaLink="false">Apache_Commons_Pool_id286541075</guid>
      <link>http://jakarta.apache.org/site/downloads/downloads_commons-pool.cgi</link>
      <pubDate>Fri, 20 Nov 2009 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache Solr, version 1.4.0</title>
      <description>
        <p>
          <a href="/projects/solr.html">Apache Solr</a>
        </p>
        <p>Solr is an open source enterprise search server based on the Lucene Java search library, with XML/HTTP and JSON, Ruby, and Python APIs, hit highlighting, faceted search, caching, replication, and a web administration interface.
    </p>
      </description>
      <guid isPermaLink="false">Apache_Solr_id286552728</guid>
      <link>http://www.apache.org/dyn/closer.cgi/lucene/solr/</link>
      <pubDate>Tue, 10 Nov 2009 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache Cayenne, version 3.0b1</title>
      <description>
        <p>
          <a href="/projects/cayenne.html">Apache Cayenne</a>
        </p>
        <p>Cayenne is a powerful, full-featured, opensource framework created for developers working with relational databases. it seamlessly maps any relational database to Java objects, reducing development time and adding considerable functionality to any application which requires a database. Developers using Cayenne will be able to concentrate on the core business requirements and the data model instead of the SQL details. The application can then be easily moved to any JDBC-capable database. In addition to management of persistent Java objects mapped to relational databases, Cayenne provides a plethora of features including single method call queries and updates (including atomic updates of all modified objects), seamless integration of multiple databases into a single virtual data source, three tier persistence with caching on the remote client, paging of results, record locking, and many more features. JPA compliance is in progress.</p>
      </description>
      <guid isPermaLink="false">Apache_Cayenne_id286532647</guid>
      <link>http://cayenne.apache.org/download.html</link>
      <pubDate>Tue, 10 Nov 2009 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache Lucene Java, version 2.9.1</title>
      <description>
        <p>
          <a href="/projects/lucene_java.html">Apache Lucene Java</a>
        </p>
        <p>Apache Lucene is a high-performance, full-featured text search engine library written entirely in Java. It is a technology suitable for nearly any application that requires full-text search, especially cross-platform.</p>
      </description>
      <guid isPermaLink="false">Apache_Lucene_Java_id286528272</guid>
      <link>http://www.apache.org/dyn/closer.cgi/lucene/java/</link>
      <pubDate>Fri, 6 Nov 2009 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache HTTP Server, version 2.2.14</title>
      <description>
        <p>
          <a href="/projects/http_server.html">Apache HTTP Server</a>
        </p>
        <p>
The Apache HTTP Server is an open-source HTTP server for modern
operating systems including UNIX, MS-Windows, Macintosh and Netware.
The goal of this project is to provide a secure, efficient and
extensible server that provides HTTP services in sync with the current
HTTP standards. Apache has been the most popular web server on the
Internet since April of 1996.
    </p>
      </description>
      <guid isPermaLink="false">Apache_HTTP_Server_id286548212</guid>
      <link>http://httpd.apache.org/download.cgi</link>
      <pubDate>Mon, 5 Oct 2009 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache POI, version 3.5</title>
      <description>
        <p>
          <a href="/projects/poi.html">Apache POI</a>
        </p>
        <p>APIs for manipulating various file formats based upon Open Office XML (ECMA-376) and Microsoft's OLE 2 Compound Document formats using pure Java. Apache POI is your Java Excel, Word and PowerPoint solution. We have a complete API for porting other OOXML and OLE 2 Compound Document formats and welcome others to participate.</p>
      </description>
      <guid isPermaLink="false">Apache_POI_id286555691</guid>
      <link>http://www.apache.org/dyn/closer.cgi/poi/</link>
      <pubDate>Mon, 28 Sep 2009 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache Commons Pool, version 1.5.3</title>
      <description>
        <p>
          <a href="/projects/commons_pool.html">Apache Commons Pool</a>
        </p>
        <p>Commons Object Pooling Library</p>
      </description>
      <guid isPermaLink="false">Apache_Commons_Pool_id286541088</guid>
      <link>http://jakarta.apache.org/site/downloads/downloads_commons-pool.cgi</link>
      <pubDate>Wed, 23 Sep 2009 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache Lucene Java, version 2.9.0</title>
      <description>
        <p>
          <a href="/projects/lucene_java.html">Apache Lucene Java</a>
        </p>
        <p>Apache Lucene is a high-performance, full-featured text search engine library written entirely in Java. It is a technology suitable for nearly any application that requires full-text search, especially cross-platform.</p>
      </description>
      <guid isPermaLink="false">Apache_Lucene_Java_id286528284</guid>
      <link>http://www.apache.org/dyn/closer.cgi/lucene/java/</link>
      <pubDate>Wed, 23 Sep 2009 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache Commons Exec, version 1.0.1</title>
      <description>
        <p>
          <a href="/projects/commons_exec.html">Apache Commons Exec</a>
        </p>
        <p>
      A library to reliably execute external processes from within the JVM    
    </p>
      </description>
      <guid isPermaLink="false">Apache_Commons_Exec_id286537576</guid>
      <link>http://commons.apache.org/downloads/download_exec.cgi</link>
      <pubDate>Wed, 23 Sep 2009 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Release of Apache Websh, version 3.6.0b5</title>
      <description>
        <p>
          <a href="/projects/websh.html">Apache Websh</a>
        </p>
        <p>Websh is a rapid development environment for building powerful, fast, and reliable web applications in Tcl. Websh is versatile and handles everything from HTML generation to data-base driven one-to-one page customization. Websh can be run CGI environments and as Apache module.
</p>
      </description>
      <guid isPermaLink="false">Apache_Websh_id286557879</guid>
      <link>http://tcl.apache.org/websh/download.ws3</link>
      <pubDate>Mon, 14 Sep 2009 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>