Archiva Documentation - Apache Archiva legacy repository support configuration

Reply-To: dev@archiva.apache.org Delivered-To: mailing list commits@archiva.apache.org Received: (qmail 81346 invoked by uid 99); 2 Jun 2013 11:48:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Jun 2013 11:48:00 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Jun 2013 11:47:57 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id E8EF42388AB9; Sun, 2 Jun 2013 11:47:37 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1488677 [4/48] - in /archiva/site-content/docs/1.4.0-SNAPSHOT: ./ adminguide/ adminguide/webservices/ css/ customising/ images/ images/logos/ images/profiles/ images/tour/ img/ js/ rest-docs-archiva-rest-api/ rest-docs-archiva-rest-api/css... Date: Sun, 02 Jun 2013 11:47:21 -0000 To: commits@archiva.apache.org From: olamy@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20130602114737.E8EF42388AB9@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Added: archiva/site-content/docs/1.4.0-SNAPSHOT/adminguide/legacy.html URL: http://svn.apache.org/viewvc/archiva/site-content/docs/1.4.0-SNAPSHOT/adminguide/legacy.html?rev=1488677&view=auto ============================================================================== --- archiva/site-content/docs/1.4.0-SNAPSHOT/adminguide/legacy.html (added) +++ archiva/site-content/docs/1.4.0-SNAPSHOT/adminguide/legacy.html Sun Jun 2 11:47:02 2013 @@ -0,0 +1,446 @@ + + + + + + + + + Archiva Documentation - Apache Archiva legacy repository support configuration + + + + + + + + + + + + + + + + +

+ + +

+ +

+ + +

+ +

+ + +

+ +

Apache Archiva legacy repository support configuration

Archiva supports both Maven 1 and Maven 2 clients transparently when used as a proxy. The underlying managed repository can use either the default or legacy layout, and Archiva will convert the requested path to the expected internal format.

However, due to the lack of structure in maven 1 "legacy" artifact request format, Archiva must split the request path to discover artifactId, version and classifier - and this is not always deterministic. The strategy used by Archiva has been tested on many existing artifacts in the public central repository, but users may require support for private artifacts or for artifacts with classifiers.

Since version 1.0.1, Archiva provides a legacy support configuration to the administrator. It is possible to register some custom legacy path and the expected artifact reference. Archiva will check that the entered artifact reference matches the legacy path, to avoi d corrupted data in repository.

For example:

Path: jaxen/jars/jaxen-1.0-FCS-full.jar
Group ID: jaxen
Artifact ID: jaxen
Version: 1.0-FCS
Classifier: full
Type: jar

This prevents the artifact incorrectly getting translated to a version of 1.0 and a classifier of FCS-full.

Those custom legacy path are stored in the archiva.xml configuration file. By default, jaxen-1.0-FCS-full is registered, as it is used by some core Maven 1 plugins (however this is not the case if you upgraded from a previous version and retained your configuration file).

+ +

+ + + + \ No newline at end of file Added: archiva/site-content/docs/1.4.0-SNAPSHOT/adminguide/logging.html URL: http://svn.apache.org/viewvc/archiva/site-content/docs/1.4.0-SNAPSHOT/adminguide/logging.html?rev=1488677&view=auto ============================================================================== --- archiva/site-content/docs/1.4.0-SNAPSHOT/adminguide/logging.html (added) +++ archiva/site-content/docs/1.4.0-SNAPSHOT/adminguide/logging.html Sun Jun 2 11:47:02 2013 @@ -0,0 +1,384 @@ + + + + + + + + + + Archiva Documentation - Log Files + + + + + + + + + + + + + + + + +

+ + +

+ +

+ + +

Introduction
+ + + + Quick Start +
+ + + + Feature Tour +
+ + + + Release Notes +
+ + + + Downloads +
Users Guide
+ + + + Browsing +
+ + + + Searching +
+ + + + Deleting an Artifact +
+ + + + Using as a repository +
+ + + + Deploying to repository +
+ + + + Configuring Virtual Repositories +
+ + + + Rss Feeds in Archiva +
Administrators Guide
+ + + + Installing Archiva +
+ + + + Databases +
+ + + + Repositories Content Storage +
+ + + + Security +
+ + + + Archiva Configuration +
+ + + + REST Apis +
+ + + + Configuration Files +
+ + + + System Status +
+ + Log Files +
- + + + + Archiva Logs +
- + + + + Audit Logs +
- + + + + Security Logs +
+
+ + + + Reports +
Customising Archiva
+ + + + Writing a Consumer Plugin +
More Information
+ + + + Archiva Wiki +
ASF
+ + + + How Apache Works +
+ + + + Foundation +
+ + + + Sponsoring Apache +
+ + + + Thanks +
Project Documentation
+ + + + Project Information +

+ + + + + +

+ +

+ + + +

+ + Follow archiva + + +

+ +

+ + +

+ +

Log Files

To keep track of the Archiva p erformance and problems, log files are created during runtime. These files can be found in the logs/ directory.

archiva.log - contains all the start-up information and output logs for Archiva
archiva-audit.log - contains information regarding the operations performed against the repositories and configurations being modified. A good example is when an artifact is deployed to an Archiva repository. The operation will be logged in this file, with the date and timestamp of when the operation occurred, the userId of who performed the deployment, and the artifact that was deployed.
archiva-security-audit.log - contains information regarding Archiva's security. For example, a successful login of a user or a user account is created.

Note since 1.4-M4, the log4j2 asyncLogger feature is configured per default.

This mean per default AsyncLogger.WaitStrategy option is configured to Sleep.

If you are on a constrained environment, you can change it to Block (-DAsyncLogger.WaitStrategy=Block) (See log4j2 documentation )

+ +

+ + + + \ No newline at end of file Added: archiva/site-content/docs/1.4.0-SNAPSHOT/adminguide/network-configuration.html URL: http://svn.apache.org/viewvc/archiva/site-content/docs/1.4.0-SNAPSHOT/adminguide/network-configuration.html?rev=1488677&view=auto ============================================================================== --- archiva/site-content/docs/1.4.0-SNAPSHOT/adminguide/network-configuration.html (added) +++ archiva/site-content/docs/1.4.0-SNAPSHOT/adminguide/network-configuration.html Sun Jun 2 11:47:02 2013 @@ -0,0 +1,448 @@ + + + + + + + + + + + Archiva Documentation - Network Configuration + + + + + + + + + + + + + + + + +

+ + +

+ +

+ + +

+ +

+ + +

+ +

Network Configuration

To dow nload artifacts from remote repositories, Archiva use Apache Maven Wagon. This library use a connection pool mechanism. You can configure this pool to limit network access to external resources.

+ +

+ + + + \ No newline at end of file Added: archiva/site-content/docs/1.4.0-SNAPSHOT/adminguide/network-proxies.html URL: http://svn.apache.org/viewvc/archiva/site-content/docs/1.4.0-SNAPSHOT/adminguide/network-proxies.html?rev=1488677&view=auto ============================================================================== --- archiva/site-content/docs/1.4.0-SNAPSHOT/adminguide/network-proxies.html (added) +++ archiva/site-content/docs/1.4.0-SNAPSHOT/adminguide/network-proxies.html Sun Jun 2 11:47:02 2013 @@ -0,0 +1,446 @@ + + + + + + + + + Archiva Documentation - Understanding Network Proxy Configuration of Apache Archiva + + + + + + + + + + + + + + + + +

+ + +

+ +

+ + +

+ +

+ + +

+ +

Understanding Network Proxy Configuration of Apache Archiva

Archiva uses the terminology "proxy" for two different concepts:

The remote repository proxying cache, as configured through proxy connectors between repositories
Network proxies, which are traditional protocol based proxies (primarily for HTTP access to remote repositories over a firewall)

Network proxies are configured using standard HTTP proxy settings as provided by your network administrator.

Once configured, the network proxy can be attached to operations that access remote resources. At present, this is configured on the remote repository proxy connectors that need to access the remote repository over the HTTP protocol.

+ +

+ + + + \ No newline at end of file