Page tree
Skip to end of metadata
Go to start of metadata

Artifactory 1.3.0-RC2

We are pleased to announce the availability of Artifactory 1.3.0-RC2.

Major Features and Changes in This Release

  • Deleting (undeploying) artifacts immediately updates the relevant maven-metadata.xml.
  • Ability to upload and deploy a bundle of multiple artifacts (zip archive) arranged in m2 format.
  • Bug fixes.

Enjoy (smile)

The Artifactory Team

Artifactory is available for immediate download from here.
You can browse the full JIRA release notes here.


Please refer to the Installing section of the current user guide, which still applies.

Upgrading from 1.3.0-RC1

Just replace the war file. If you are running on Tomcat make sure to also remove the exploded artifactory webapp directory.

Upgrading from 1.2.2-rc0 through 1.3.0-beta-6.1

Upgrading Artifactory from older version can be done in two ways:

  1. From the UI
  2. By using the artadmin command line tool

Upgrading Using the Web UI

Upgrading from the UI is currently supported only from previous 1.3.0-x versions.

  1. From your old Artifactory installation run Full System Export and save the export to a destination directory.
  2. Perform a new clean server installation of the new Artifactory (It should not contain repository data or your customized version of the Artifactory configuration xml file).
  3. Install the new Artifactory version, go to Admin/Export&Import/System/Import System, select your previous export target directory and let the import run. That's it!

Upgrading Using the artadmin Tool

While upgrading from the web UI is easy and straightforward, sometimes the upgrade process can take a long time, especially with very large repositories. In such cases the original web request may time out and the upgrade progress will proceed in the background.
Therefore, if you wish to monitor the progress of the upgrade process in the most reliable way and gain access to more advanced dump options, it is recommended to use the artadmin command-line tool.
Here are step-by-step instructions:

  1. Stop your old Artifactory.
  2. Execute the artadmin dump command on the old $ARTIFACTORY_HOME or on a copy of it (recommended):
    artadmin dump $ARTIFACTORY_HOME
    This will generate a dumpExport folder under the current execution directory with the old repository data in a format suitable for importing into a current Artifactory.
    NOTE: By default, caches (e.g. repo1) are not exported. To export caches add the --caches parameter.
  3. Perform a new clean server installation of the new Artifactory (It should not contain repository data or your customized version of the Artifactory configuration xml file).
  4. Start the new Artifactory.
  5. Import the dumpExport folder into Artifactory, either from the UI, as explained in the previous section or by running:
    artadmin import dumpExport --username admin --password password
    The artadmin output will display the progress of the import. NOTE: If the artadmin process is killed, the import will still run in Artifactory.

Important Information

Please read this carefully before installing or upgrading:

  1. If you are running Artifactory under JDK 1.6 you MUST use JDK 1.6u4 and above due to incompatibilities with older JAXB versions embedded in previous JDK 1.6 releases. JDK 1.5 users are not affected by this.
  2. If you have used a previous version of Artifactory it is highly recommended to:
    1. Use a fresh version of Artifactory from the distribution and not try to patch the previous installation.
    2. Clear your browser's cache before using this version.
  3. The default Artifactory user for the standalone installation has been changed to artifactory (instead of jetty). You might have to update the provided install script or your file system permissions accordingly.
  4. Please note that not all documentation has been updated yet to reflect the latest changes in this release.

Important information about the import process

During the import binary artifacts are copied over into a working copy and are imported into Arifactory in by a background thread. This speeds up the import process dramatically and makes Artifactory ready for serving requests as soon as possible. The background import process will take some time to completes, depending on the size of your repository. During this time Artifactory might perform more slowly than usual, but it will still serve any artifact immediately. The log does provide visible information about the progress of this process.

Repeating the upgrade process

Should you wish to repeat the upgrade process from scratch, make sure to remove the $ARTIFACTORY_HOME/data folder from your new Artifactory installation before doing so.

Major Features and Changes in release 1.3.0-rc-1

  • Flexible validation for remote checksums: Generate if absent (the default), Fail, Ignore and generate and Pass-through (please see the UI for description of each policy).
  • Many bug fixes and stability improvements.
  • Better MySql support.
  • Improved support for Safari.
  • Artifactory and artadmin are now under a single downloadable distribution.
  • Better overall performance.

Major Features and Changes in release 1.3.0-beta-6

  • Artifactory is 100% configurable via the newly designed user interface
  • Support for running Artifactory with MySql for greater scalability, performance and tools support.
  • Support for running Artifactory under Websphere.
  • Install script for automatic set up under a dedicated Tomcat instance.
  • Ability to remove deployed versions with all their sub-artifacts in one go.
  • Dynamic log tailing from the UI.
  • Global offline flag for disconnected environments.
  • Out of the box support for running standalone Artifactory as a Windows service (in additional to the existing Unix service installer).
  • Unified artadmin CLI tool for all administrative tasks.
  • Greatly improved backup and restore speed.
  • Many internal performance and concurrency improvements.
  • The usual bug fixes.

Major Features and Changes in release 1.3.0-beta-5

  • In place incremental backup.
  • Performance improvements around security authentication and authorization.
  • Fixed a UI bug with remote repositories cache access control setup.

Major Features and Changes in release 1.3.0-beta-4

  • Improved LDAP Support - support for multiple DNs, for non-anonymous binding against MS Active Directory and for sub-tree searches.
  • Fixed a critical issue with deployment using the lightweight HTTP wagon (RTFACT-629).
  • UI and performance improvements and the usual bug fixes.

Major Features and Changes in release 1.3.0-beta-3

  • Group support with an intuitive powerful UI for groups management.
  • Improved permissions control for including/excluding specific repository paths (e.g. disallow certain users/groups from downloading sources). Simple management - no regexp gurus required.
  • Support for delete permission and for preventing users from overriding exiting artifacts.
  • Revised repository tree browsing using tabs and effective permissions per item view.
  • Improved import speed by committing binary imports asynchronously.
  • Improved #upgrade procedure.
  • Better transaction management using Spring Modules for JCR.
  • Even faster in-place incremental backup.
  • Low-level admin-only direct WebDAV access to the underlying jackrabbit repository (use: http://localhost:8081/artifactory/jcr/default/ to connect).
  • The usual bug fixes, stability and speed improvements.

The complete release notes from Jira are available here:


  • No labels