Archiva configuration file

For configuring a mirror repository in a remote repository, complete steps However, select maven2-repository.

Under the Management menu, click User management. Select the Repository Observer role next to mirror. You must create a separate repository for each Oracle Fusion Middleware environment that you want to target with a Maven build.

Oracle's support for one-off patching see Section 5. To ensure that your Maven builds are using the correct version of files, create and configure a group Maven repository for each target environment:. In the Admin: Add Managed Repository dialog box, specify the following details:.

Identifier : Provide an identifier, like dev , prod , qa , or test. Select the Repository Observer role next to the appropriate repository entry. From the Administration menu, click Repository Groups. In the Identifier field, specify a name that matches the repository that you created, with the addition of -group , for example, dev-group. Select your new repository, like dev , from the drop-down menu next to Add Repository and click Add Repository.

Repeat steps 3-a to 3-d to add mirror and snapshots. Repeat the repository and group creation steps for each repository type: test , qa , and prod. To support deployment in your internal repository, you must add at least one user with appropriate permissions:. Click Create New User to add a user. Then, specify the required details like name, email address, and password.

After the user is added, you are directed to a Role Administration dialog box for that user. To customize or change the role, in the User Roles section, add a new more limited role and assign it to the appropriate users.

Typically, you want to create a new user for each individual with access to the repository. For Hudson, to publish build output to the repository, each user who accesses the repository should have their own user ID, and you should create an additional user with deployment permissions.

After you have completed installation and configuration of Archiva as detailed in this chapter and Maven as detailed in Chapter 5 , you should populate your Archiva repository with the Oracle-provided artifacts, as described in Section 5. Archiva retains an instance of a particular snapshot-versioned artifact for every successfully deployed job. When you request a snapshot artifact, the most recent snapshot is obtained. Maven examines the associated metadata in the repository to determine the correct copy to download.

The Maven Repository Manager maintains each copy with a unique timestamp and build number. For example, the contents of the repository directory for an artifact should look similar to the following:. You can directly request a specific snapshot of your requirement by referencing timestamp and build numbers in your version, for example, 2.

Usually, only the latest snapshot is required for proper operation of continuous integration builds. Retention of older instances of a snapshot is helpful for troubleshooting purposes when the continuous integration server indicates that a snapshot dependency change has broken the integration process. Auto Login Settings security. Default Username Values redback. However any number of people may be assigned full administrator roles. Security Policies security.

Password Rules security. LDAP settings Ldap can be used as a readonly user manager, however the role assignment is still managed entirely within the given database store. User Manager Implementation s to use user. Archiva will check how old the artifact is and if it is older than the set number of days in this field, then the artifact will be deleted respecting the retention count of course.

In order to disable the purge by number of days old and set Archiva to purge by retention count, just set the repository purge field to 0.

The maximum number of days which can be set here is See the Repository Purge section below for more details. Retention Count The second option for repository purge. When running the repository purge, Archiva will retain only the number of artifacts set for this field for a specific snapshot version. Description Additional information about the repository. Releases Specifies whether there are released artifacts in the repository. Snapshots Specifies whether there are snapshot artifacts in the repository.

Block Redeployments Specifies whether released artifacts that are already existing in the repository can be overwritten. Note that this only take effects for non-snapshot deployments. Scanned Specifies whether the repository can be scanned, meaning it is a local repository which should be indexed, purged, etc. Delete Released Snapshots Specifies whether to remove those snapshot artifacts which already has release versions of it in the repository during repository purge.

Staging Repository Automatic creation of a stage repository for this local repository. Remote Repository A remote repository is a repository which resides remotely. Remote repository fields: Id The identifier of the remote repository. Name The name of the remote repository. Url The url of the remote repository. Be careful that if this local repository is a managed repository of archiva which has some proxies connectors, those ones won't be triggered.

Username The username if authentication is needed to be used to access the repository. Password The password if authentication is needed to be used to access the repository. Download Timeout The time in seconds after which a download from the remote repository is stopped. Type The layout maven 2 or maven 1 of the remote repository. Download Remote Index To activate downloading remote index to add available remote artifacts in search queries.

Remote Index Url Can be relative to Url - path of the remote index directory. You will need to obtain the derby. Early versions of Archiva 1. Please note, when running the tomcat service on a bit Windows 7 machine, you can find the procrun node under wow These instructions explain how to deploy the unreleased Archiva 1.

This example lists out the docBase to the war file itself. The Tomcat 5. JNDI mail sessions will not work.