The Apache Archiva team is pleased to announce the release of Archiva 1.0.2

Archiva is a build artifact repository manager for use with build tools such
as Maven, Continuum and Ant.

It has features like repository search and browse, securing repositories,
identifying unknown artifacts and reporting of repository problems.

Aside from these, it can also act as a nearby (proxy) cache of popular
global repositories.


The latest release is now available here:

http://maven.apache.org/archiva/download.html

If you have any questions, please consult:

 - the web site: http://maven.apache.org/archiva/
 - the archiva-user mailing list: 
http://maven.apache.org/archiva/mail-lists.html


New in Archiva 1.0.2
================

* Configurable Proxy Error Handling

Two new options have been added to the proxy connector configuration page:

- On remote error - gives control over whether to stop immediately, continue to try for a successful proxy, or ignore an error - Return error when - gives control over whether to return an existing artifact if present or fail regardless if a remote error occurs when updating an artifact


Change Log for Archiva 1.0.2
=======================

* [MRM-159] - should not respond with a 404 if proxying a file results in a remote error * [MRM-532] - Unable to specify the location of the index files through the web ui * [MRM-598] - Validation error on new repository creation and other fields under certain conditions * [MRM-608] - Unable to find project model for [...] if the initial import of the POM failed * [MRM-617] - Reporting does not work due to bug in client-side JavaScript validation
  * [MRM-618] - PLEXUS_BASE does not work for local databases
* [MRM-622] - database not being updated with project model information * [MRM-626] - ClassCastException when saving proxy connector with property defined * [MRM-627] - Archiva doesn't download SNAPSHOTs for proxied repositories.
  * [MRM-642] - archiva-common tests rely on relative paths
* [MRM-655] - The logs are duplicated in the archiva.log and wrapper.log file. * [MRM-659] - archiva cannot serve ejb artifacts from a maven1 repository
  * [MRM-661] - remote repository removals are not saved after restart
* [MRM-664] - Cannot download a strut-module artifact in a Legacy repository
  * [MRM-674] - LayoutException when downloading SNAPSHOT test-sources
  * [MRM-683] - Archiva version missing from pages and logs
* [MRM-687] - Project model cannot be added to database if it inherits groupId and/or version from parent POM
  * [MRM-689] - Incorrect war name in example for tomcat
  * [MRM-690] - using undefined appserver.base
* [MRM-691] - Can't get any of the consumers to work without through a NPE * [MRM-701] - Buggy documentation on "separating the base from the installation" * [MRM-703] - Artifacts with extensions longer than fours characters breaks repository scanning.
  * [MRM-713] - extensionPattern in FilenameParser is incorrect
* [MRM-715] - error adding artifacts to Lucene under some circumstances
  * [MRM-719] - NPE during repository scan
  * [MRM-725] - /archiva/browse URL does not work on WebSphere
  * [MRM-727] - Archiva does not download plugin artifacts in Geronimo
* [MRM-734] - Unable to update metadata - No versions found for reference * [MRM-746] - unable to include *.xml in artifacts list as it picks up maven-metadata.xml
  * [MRM-750] - Adding a network proxy doesn't require an identifier
* [MRM-755] - No content type for .pom files denoted in file "archiva-mime-types.txt" - workaround included * [MRM-758] - unable to schedule cron expressions that contain a comma * [MRM-761] - Exception when trying to retrieve a Maven 1 artifact of type zip * [MRM-762] - Footer doesn't stretch across repositoryScanning and database pages
  * [MRM-763] - Default cron expression for database update is invalid
* [MRM-764] - default policies are not selected in the add proxy connector page * [MRM-504] - Find Artifact page needs more onscreen information/ instructions
  * [MRM-656] - Admin guide for installing WAR needs updating
* [MRM-666] - Edit Managed Repository page should indicate the repo id being edited * [MRM-700] - Review the documentation on deploying to Archiva for inconsistent repository ids
  * [MRM-720] - Upgrade Lucene from 2.0 to 2.3.1

Thanks,
The Apache Archiva team

Reply via email to