Release Notes for Archiva 2.2.1

The Apache Archiva team is pleased to announce the release of Archiva 2.2.1. Archiva is available for download from the web site.

Archiva is an application for managing one or more remote repositories, including administration, artifact handling, browsing and searching.

If you have any questions, please consult:

New in Archiva 2.2.1

Apache Archiva 2.2.1 is a bugs fix release:

  • NOTE: jdk 1.7 is now prerequisite with Apache Archiva 2.2.1

Compatibility Changes

  • If using the Cassandra backend, the metadatafacet column 'key' has been renamed to 'facetKey' in 2.2.0 so you should copy the data to the new column manually.
  • If upgrading from earlier versions of Archiva, the list of libraries in wrapper.conf has changed. If you have customized your copy of wrapper.conf, please update it for compatibility with the version distributed with the current release.
  • As the database storage has been removed, you can remove the JNDI entry for jdbc/archiva.

    Refer to the Upgrading Archiva guide for more information.

Release Notes

The Archiva 2.2.1 features set can be seen in the feature tour.

Changes in Archiva 2.2.1

Released: ???

Improvement

  • [MRM-1201] - Artifact upload success message should mention the classifier
  • [MRM-1906] - Allowing filtering of LDAP groups

Bug

  • [MRM-1873] - archiva doesn't recognise ldap-group to ldap-users mapping
  • [MRM-1877] - Checksum files always recreated
  • [MRM-1879] - Bug in create-missing-checksum consumer
  • [MRM-1886] - View Artifact Content Action does not Work
  • [MRM-1887] - Syntax error in DOAP file release section; wrong bug- database URL
  • [MRM-1892] - Only One Page of Proxy Connector Rules Shown
  • [MRM-1893] - Please delete old releases from mirroring system
  • [MRM-1896] - Invalid link to license
  • [MRM-1914] - Maven cannot find dependency

History

Archiva was started in November 2005, building a simple framework on top of some existing repository conversion tools within the Maven project. Initial development focused on repository conversion, error reporting, and indexing. From January 2006 a web application was started to visualise the information and to start incorporating functionality from the unmaintained maven-proxy project.

Development continued through many stops and starts. Initial versions of Archiva were built from source by contributors, and the first alpha version was not released until April 2007. Some significant changes were made to improve performance and functionality in June 2007 and over the next 6 months and a series of alpha and beta releases, a concerted effort was made to release the 1.0 version.

Archiva became an Apache "top level project" in March 2008.