# This file describes the projects that are/were in the Attic. # # Fields : # tracker : (JIRA|Bugzilla) tag --- name: Abdera project: abdera retired: March 2017 mailnames: - dev - commits - user tracker: JIRA ABDERA scm: svn wiki: https://cwiki.apache.org/confluence/display/abdera/ description: |- Apache Abdera was a project to build a functionally-complete, high-performance implementation of the IETF Atom Syndication Format (RFC 4287) and Atom Publishing Protocol (RFC 5023) specifications. postlude: |- Some related projects to Abdera are: --- name: ACE project: ace retired: December 2017 mailnames: - dev - commits - users tracker: JIRA ACE scm: svn wiki: https://cwiki.apache.org/confluence/display/ace/ description: |- Apache ACE was a software distribution framework that allows you to centrally manage and distribute software components, configuration data and other artifacts to target systems. It is built using OSGi and can be deployed in different topologies. The target systems are usually also OSGi based, but don't have to be. --- name: Avalon project: avalon retired: June 2004 mailnames: - dev tracker: JIRA AVALON scm: svn wiki: http://wiki.apache.org/avalon/ description: |- Apache Avalon was closed long before the creation of the Apache Attic. It's mentioned here for completeness. --- name: AxKit project: xml subproject: axkit retired: August 2009 mailnames: [] website: http://axkit.org description: |- Apache AxKit was an XML Application Server for Apache. It provided on-the-fly conversion from XML to any format, such as HTML, WAP or text using either W3C standard techniques, or flexible custom code. --- name: Axis Sandesha2/C project: axis subproject: axis2/c/sandesha dist: ws/sandesha2/c stem: axis-sandesha-c retired: September 2014 mailnames: [] tracker: JIRA SANDESHA2C scm: svn description: |- Sandesha2/C was a C implementation of the WS-ReliableMessaging specification. Sandesha2/C was built on top of Apache Axis2/C Web services engine, as a module. Therefore by using Sandesha2/C you could add reliable messaging capability to Web services hosted using Axis2/C. Sandesha2/C could also be used with Axis2/C client to interact with an already hosted Web services in a reliable manner. --- name: Axis Savan/C project: axis subproject: axis2/c/savan dist: ws/savan/c retired: September 2014 mailnames: [] tracker: JIRA AXIS2C scm: svn description: |- Savan/C was a C implementation of WS-Eventing specification. Savan/C was built on top of Axis2/C. Therefore by using Savan/C you could add WS-Eventing capability to Web services hosted using Axis2/C. Savan/C was designed as a general publisher/subscriber tool. The arcitecture was designed to abstract the general publisher/subscriber features so that people could support more than one publisher/subscriber mechanisms within the same infrastructure. --- name: Axis Savan/Java project: axis subproject: axis2/java/savan dist: '' retired: September 2014 mailnames: [] tracker: JIRA SAVAN description: |- Savan/Java was a Java implementation of WS-Eventing specification. Savan/Java was built on top of Axis2/Java. Therefore by using Savan/Java you could add WS-Eventing capability to Web services hosted using Axis2/Java. Savan/Java was designed as a general publisher/subscriber tool. The arcitecture was designed to abstract the general publisher/subscriber features so that people could support more than one publisher/subscriber mechanisms within the same infrastructure. --- name: Beehive project: beehive retired: January 2010 mailnames: - dev - commits - user tracker: JIRA BEEHIVE scm: svn wiki: https://wiki.apache.org/beehive description: |- Apache Beehive was a simple object model built on J2EE and Struts that used annotations to reduce the amount of required code. postlude: |-

If you are looking for a project to use in place of Beehive, the following have been suggested for its components:

--- name: Click project: click retired: May 2014 mailnames: - dev - commits - user tracker: JIRA CLK scm: svn wiki: https://cwiki.apache.org/confluence/display/click/ description: |- Apache Click was a JEE web application framework, providing a natural rich client style programming model. --- name: Crimson project: xml subproject: crimson dist: '' retired: August 2010 mailnames: [] description: |- Apache Crimson was a Java XML parser which supports XML 1.0 via various APIs. postlude: |-

Apache Xerces replaced Crimson.

--- name: Continuum project: continuum retired: May 2016 mailnames: - dev - users - commits - issues - notifications tracker: JIRA CONTINUUM scm: svn wiki: https://cwiki.apache.org/confluence/display/continuum/ description: |- Continuum was an enterprise-ready continuous integration server with features such as automated builds, release management, role-based security, and integration with popular build tools and source control management systems. --- name: Deltacloud project: deltacloud retired: July 2015 mailnames: - dev - commits - user tracker: JIRA DTACLOUD scm: git-wip description: |- Deltacloud provided the API server and drivers necessary for connecting to cloud providers via a cloud abstraction API. --- name: DeviceMap project: devicemap retired: December 2016 mailnames: - dev - commits tracker: JIRA DMAP scm: svn wiki: http://wiki.apache.org/devicemap/ description: |- Apache DeviceMap was a project to create a data repository containing device information, images and other relevant information for all sorts of mobile devices. postlude: |-

Some related projects to DeviceMap are:

--- name: DirectMemory project: directmemory retired: July 2015 mailnames: - dev - commits - user tracker: JIRA DIRECTMEMORY scm: svn wiki: https://cwiki.apache.org/confluence/display/directmemory/ description: |- DirectMemory was an off-heap cache for the Java Virtual Machine. --- name: ESME project: esme retired: July 2013 mailnames: - dev - commits tracker: JIRA ESME scm: svn wiki: https://cwiki.apache.org/confluence/display/esme/ description: |- Apache ESME (Enterprise Social Messaging Environment) was a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information. --- name: Etch project: etch retired: June 2016 mailnames: - dev - user - commits tracker: JIRA ETCH scm: svn description: |- Etch was a cross-platform, language- and transport-independent framework for building and consuming network services. --- name: Excalibur project: excalibur retired: December 2010 mailnames: - dev - scm - user tracker: JIRA EXLBR scm: svn wiki: https://wiki.apache.org/excalibur description: |- Apache Excalibur was a Java Inversion of Control container. --- name: Harmony project: harmony retired: November 2011 mailnames: - dev - alerts - commits tracker: JIRA HARMONY scm: svn wiki: http://wiki.apache.org/harmony/ description: |- Harmony software was a modular Java runtime with class libraries and associated tools. --- name: HiveMind project: hivemind retired: April 2009 mailnames: - dev - commits - user tracker: JIRA HIVEMIND scm: svn wiki: http://wiki.apache.org/hivemind/ description: |- Apache HiveMind was a services and configuration microkernel. Its features are also referred to as Inversion of Control (IoC) Container or Lightweight Container. Closely linked to Tapestry 4, it lost activity when Tapestry 5 moved to a new IoC container. postlude: |-

Discussion on the mailing list indicated that Tapestry IoC was the natural successor to HiveMind.

One fork that has been created is Gaderian at http://gaderian.ops4j.org/.

--- name: iBATIS project: ibatis retired: June 2010 mailnames: - dev - commits - user-cs - user-java scm: svn description: |- iBATIS was a data mapper framework that made it easier to use a relational database with object-oriented applications. There were both Java and .Net implementations. postlude: |-

One fork that has been created is MyBatis at http://www.mybatis.org/.

--- name: Jakarta project: jakarta retired: December 2011 mailnames: - dev - announcements - general - site-cvs - notifications scm: svn nokeys: true description: |- Jakarta Project housed a diverse set of popular open source Java solutions. --- name: Jakarta Cactus project: jakarta subproject: cactus retired: August 2011 mailnames: - dev - user tracker: JIRA CACTUS scm: svn description: |- Jakarta previously hosted Cactus, a simple test framework for unit testing server-side java code. --- name: Jakarta ECS project: jakarta subproject: ecs retired: September 2010 mailnames: - dev - user tracker: JIRA ECS scm: svn description: |- Jakarta previously hosted ECS (Element Construction Set), a Java API for generating elements for any of a variety of markup languages (examples included HTML 4.0 and XML). --- name: Jakarta ORO project: jakarta subproject: oro retired: September 2010 mailnames: - dev - user tracker: Bugzilla oro scm: svn description: |- Jakarta previously hosted ORO, a set of text-processing Java classes that provide Perl5 compatible regular expressions, AWK-like regular expressions, glob expressions, and utility classes for performing substitutions, splits, filtering filenames, etc. postlude: |-

Jakarta ORO users are encouraged to use similar features in newer Java versions, such as java.util.regexp

--- name: Jakarta Regexp project: jakarta subproject: regexp retired: April 2011 mailnames: - dev - user tracker: Bugzilla regexp scm: svn description: |- Jakarta previously hosted Regexp, a 100% Pure Java Regular Expression package. postlude: |-

Jakarta Regexp users are encouraged to use similar features in newer Java versions, such as java.util.regexp

--- name: Jakarta Slide project: jakarta subproject: slide retired: November 2007 mailnames: - dev - user tracker: Bugzilla slide scm: svn wiki: https://wiki.apache.org/jakarta-slide description: |- Jakarta previously hosted Slide, a content repository which could serve as a basis for a content management system as well as other purposes. Among its features was full WebDAV support. postlude: |-

If you are looking for a WebDAV client or a server-side Content Repository, please consider the Apache Jackrabbit project as an alternative.

--- name: Jakarta Taglibs project: jakarta subproject: taglibs retired: June 2008 mailnames: - dev tracker: Bugzilla taglibs scm: svn website: '' description: |- Jakarta hosted the Jakarta Taglibs project, a large collection of JSP Tag Libraries. They ranged from simple utility libraries and UI libraries, to Dreamweaver extensions and an implementation of the JSP Standard Tag Library (JSTL) specification. postlude: |-

In 2008 and 2009, the majority of these libraries were deprecated and have now been retired. The remaining work has moved over to the Tomcat Taglibs project - namely the following taglibs:

In 2014 the RDC Taglib was retired from the Tomcat Taglibs project.

NameJSP versionObtain
RDC2.0+svn

A list of the original retired taglibs follows:

NameJSP versionObtain
Mailer 22.0+svn
Cache1.2+svn
Data Grid1.2+svn
Application1.1+svn
Benchmark1.1+svn
BSF1.1+svn
DateTime1.1+svn
DBTags1.1+svn
I18N1.1+svn
Image1.1+svn
Input1.1+svn
IO1.1+svn
Iterators1.2+svn
JNDI1.1+svn
JMS1.1+svn
Log1.1+svn
Mailer1.1+svn
Page1.1+svn
Random1.1+svn
Regexp1.1+svn
Request1.1+svn
Response1.1+svn
Scrape1.1+svn
Session1.1+svn
String1.1+svn
UltraDev 4.0 Tool Extension1.1+svn
Unstandard1.2+svn
Utility1.1+svn
XSL1.1+svn
XTags1.1+svn
--- name: Lenya project: lenya retired: April 2015 mailnames: - dev - commits - user scm: svn description: |- Lenya was an Open Source Java/XML Content Management System that came with revision control, multi-site management, scheduling, search, WYSIWYG editors, and workflow. --- name: Lucy project: lucy retired: June 2018 mailnames: - dev - commits - issues - user scm: svn tracker: JIRA LUCY wiki: http://wiki.apache.org/lucy/ description: |- The Apache Lucy search engine library provides full-text search for dynamic programming languages. It is a "loose C" port of the Apache Lucene search engine library for Java. --- name: MRUnit project: mrunit retired: April 2016 mailnames: - dev - user - commits tracker: JIRA MRUNIT scm: svn wiki: https://cwiki.apache.org/confluence/display/MRUNIT description: |- Apache MRUnit was a Java library that helped developers unit test Apache Hadoop map reduce jobs. --- name: ObJectRelationalBridge (OJB) project: db subproject: ojb stem: ojb retired: January 2011 mailnames: - dev - user tracker: JIRA OJB scm: svn wiki: https://wiki.apache.org/db-ojb description: |- Apache OJB was an Object/Relational mapping tool that allowed transparent persistence for Java Objects against relational databases. postlude: |-

If you are looking for a project to use in place of OJB, implementations of the standards Java Data Objects (JDO) and Java Persistence API (JPA) may be good starting points. The Apache Software Foundation hosts the following alternatives:

--- name: Oltu project: oltu retired: April 2018 mailnames: - dev - user - commits tracker: JIRA OLTU scm: svn wiki: https://cwiki.apache.org/confluence/display/oltu/ description: |- Apache Oltu was an OAuth protocol implementation in Java. It also covers others OAuth family related implementations such as JWT, JWS and OpenID Connect --- name: Onami project: onami retired: January 2016 mailnames: - dev - user - commits tracker: JIRA ONAMI scm: svn description: |- Apache Onami was a project focused on the development and maintenance of a set of Google Guice extensions not provided out of the box by the library itself. --- name: Quetzalcoatl project: quetzalcoatl dist: '' retired: June 2010 mailnames: [] scm: svn website: '' description: |- Quetzalcoatl, or Quetz as it was more commonly known, was a project charged with the creation and maintenance of open-source software related to mod_python and the Python programming language. Mainly formed around the mod_python subproject, it didn't have activity in the mod_python community to drive the larger project along. postlude: |-

The mod_python website and downloads remain open. See the website at http://www.modpython.org for more information on mod_python. Quetz itself never had a website.

--- name: Rave project: rave retired: January 2016 mailnames: - dev - users - commits tracker: JIRA RAVE scm: svn wiki: http://wiki.apache.org/rave/ description: |- Apache Rave was a web and social mashup engine that aggregated and served web widgets. It was targeted as an engine for internet and intranet portals. --- name: Shale project: shale retired: May 2009 mailnames: - dev - user - commits tracker: JIRA SHALE scm: svn wiki: http://wiki.apache.org/shale/ description: |- Shale was a web application framework, fundamentally based on JavaServer Faces. This blog entry from Kito Mann is an excellent discussion of Shale's retirement: http://blogs.jsfcentral.com/editorsdesk/entry/shale_in_the_attic. postlude: |-

Discussion on the mailing list indicated that Seam and MyFaces were the natural successors to Shale.

The Shale Test code has been forked into the MyFaces project - http://svn.apache.org/viewvc/myfaces/test/trunk/.

--- name: Shindig project: shindig retired: November 2015 mailnames: - dev - users - commits tracker: JIRA SHINDIG scm: svn wiki: https://cwiki.apache.org/confluence/display/shindig/ description: |- Apache Shindig was an OpenSocial container to help you to start hosting OpenSocial apps quickly. --- name: Standard C++ Library (STDCXX) project: stdcxx stem: stdcxx retired: July 2013 mailnames: - dev - commits - user tracker: JIRA STDCXX scm: svn wiki: http://wiki.apache.org/stdcxx/ board: Cxx_Standard_Library description: |- The Apache C++ Standard Library project was a collection of algorithms, containers, iterators, and other fundamental components of every piece of software, implemented as C++ classes, templates, and functions essential for writing C++ programs. --- name: Stratos project: stratos retired: January 2017 mailnames: - dev - commits tracker: JIRA STRATOS scm: git-wip wiki: https://cwiki.apache.org/confluence/display/stratos/ description: |- Stratos was a highly-extensible Platform-as-a-Service (PaaS) framework that helped run Apache Tomcat, PHP, and MySQL applications, and could be extended to support many more environments on all major cloud infrastructures. --- name: Tuscany project: tuscany retired: May 2016 mailnames: - dev - user - commits tracker: JIRA TUSCANY scm: svn wiki: https://cwiki.apache.org/confluence/display/tuscany/ description: |- Tuscany simplified the task of developing service-oriented architectured solutions by providing a comprehensive infrastructure for development and management, based on the Service Component Architecture standard. --- name: Whirr project: whirr retired: March 2015 mailnames: - dev - user - commits tracker: JIRA WHIRR scm: svn wiki: https://cwiki.apache.org/confluence/display/whirr/ description: |- Apache Whirr was a set of libraries for running cloud services and deploying clusters. postlude: |-

Note that instructions on how to obtain and build the source are found on the wiki and not the website: https://cwiki.apache.org/confluence/display/WHIRR/How+To+Contribute.

--- name: Wink project: wink retired: April 2017 mailnames: - dev - commits - user tracker: JIRA WINK scm: svn wiki: https://cwiki.apache.org/confluence/display/wink/ description: |- Apache Wink was a simple yet solid framework for building RESTful Web services. It is comprised of a Server module and a Client module for developing and consuming RESTful Web services. --- name: Wookie project: wookie retired: April 2016 mailnames: - dev - user - commits tracker: JIRA WOOKIE scm: svn wiki: https://cwiki.apache.org/confluence/display/wookie/ description: |- Wookie was a Java server application that allowed you to upload and deploy W3C/OpenSocial/Google Wave widgets to your applications. --- name: WS Muse project: ws subproject: muse stem: muse retired: January 2013 mailnames: - dev - user - commits website: '' description: |- Muse was a Java-based implementation of the WS-ResourceFramework (WSRF), WS-BaseNotification (WSN), and WS-DistributedManagement (WSDM) specifications. postlude: |-

One fork that has been created is amused, available at http://52north.org/communities/sensorweb/amused.

--- name: Xang project: xml subproject: xang dist: '' retired: December 2009 mailnames: - dev - cvs scm: svn description: |- Apache Xang was an XML Web Framework that aggregated multiple data sources, made that data URL addressable and defined custom methods to access that data. --- name: Xindice project: xml subproject: xindice retired: August 2011 mailnames: - dev - users tracker: Bugzilla Xindice scm: svn wiki: http://wiki.apache.org/xindice description: |- Apache Xindice was a native XML database. --- name: XMLBeans project: xmlbeans retired: July 2013 revived: June 2018 description: |- Apache XMLBeans is a technology for accessing XML by binding it to Java types. postlude: |- Apache XMLBeans is now a project of Apache Poi. --- name: XML project: xml retired: April 2012 mailnames: - bugs - announcements - general - general-cvs scm: svn nokeys: true description: |- the Apache XML Project housed a diverse set of popular open source XML solutions.