Embedded Jetty. JSW launch scripts - runs as a service on windows and unix

Bundled Tomcat - runs as a service on Windows and Unix. Complete script for installation as a service on unix, includes: user creation, permission settings and service config. Complete script for installing a standalone Tomcat service on Unix.

Embedded Jetty. JSW launch scripts - runs as a service on windows and unix. Also Native Solaris Service Manager Scripts.

War

"Drop the War" - deploy into any servlet container with zero configuration.

no container configuration required to run the war.

OS packages

RPM for installing on YUM-enabled OSes. More packaging systems coming.

Cloud-based SaaS

Artifactory Online - private Artifactory instance in the cloud with full self service, pay-per-use model and always up-to-date with all the latest features

Extensible with custom Groovy plugins - schedule tasks, deploy artifacts, change resolution rules and download content, tend to any storage events etc. Plugin source files are redeployed on the fly during development and can be edited and debugged in your favorite IDE.

Fully extensible across the core components, REST API and UI. See the book and this post for more info.

Includes search for any jar resource, and showing the actual class found.

GAVC search

POM/XML search

Includes XPath search of any XML metadata. No need to customize anything for XML indexing.

Ivy modules search

Properties search

Search custom properties. Attach props to both files and folders via the UI (Pro) or via REST (OSS). No need for custom RDF uploads. Search results are can be manipulated as a bundle.

Custom metadata may be attached via the UI, Rest or by uploading an RDF file as part of your build. The metadata is indexed and searchable for files in Maven layout. (Pro)

OSGI Search

(1.4-M2)

Reports

Report for Problem Artifacts

By default blocks bad poms in runtime instead of polluting your repository and reporting after the fact (policy is configurable via UI)

RSS Feeds and UI viewer for bad checksums and artifacts with bad poms. Bad poms are allowed through by default because many times Maven can still use them. We don't believe that simply inserting a repo manager should cause things to suddenly fail from Central. The repo man should for the most part be transparent by default.

Move artifacts between repositories + dry-run to check for warnings + auto metadata recalculation. Also available via REST in Pro.

Copy Artifacts

(1.4-M1) via REST api only.

Cheap-copy of artifacts between repositories + dry-run to check for warnings + auto metadata recalculation (no extra space used due to pointer-based storage). Copying is often the best approach for exposing the same artifact under different secure locations. Also available via REST in Pro.

Upload Artifacts

With our without pom (will generate one if needed)

With our without pom (will generate one if needed). Upload multiple artifacts in one go. Edit the pom before deployment. Deploy to arbitrary (non-maven) paths via the UI.

With our without pom (will generate one if needed) Upload multiple artifacts (classifiers) at once.

Syntax Highlighting

Syntax highlighting + copy to clipboard support for dozens of known file types directly form the repository (including zip/jar sources).

Jar Browsing

Supports viewing the content of jar files, including show source for class files.

Tag files and folders with you user defined searchable properties via the UI. Prop-sets defined through UI as single/multi select or open, with the ability to assign default values, and associated with selected repos (Pro).

via Shiro + ExtJs user console. Full role based with the ability to specify permissions based on the path of the artifact (group/artifact/version) using regex if desired.

Support Prevention of Redeploy

Control over who can populate caches

Fully featured procurement support included in the pro version. This allows absolute control over the artifacts allowed through based on the artifact and user.

Support Protection of Sources / javadoc etc

Using Ant-like simple to understand patterns + OOTB templates for common include/excludes. Supports inclusion and exclusion so no need to used negative patterns for protecting sources etc.

Using the regex to control the paths, it is possible to secure separately any artifacts you want. Comes configured with targets to specify sources, which would allow you for example to have jars be downloaded anonymously but not the sources, even though they are sitting in the same repository.

Out of the box LDAP support

partially for authz

Configurable via the web UI.

Including role mappings, Active Directory support and more.

Able to use LDAP groups (authorization from ldap)

Including highly optimized caching and comprehensive UI integration in Pro.

(Open Sourced in 1.5+)

Supports multiple realms in order (ie LDAP then fallback to internal)

With control of whether to fallback to internal users or not. Including Kerberos and native NTLM in Pro.

ordered control of cascading though configured realms -- as many as you have installed.

SSO with any SAML IdP (Identity Provider). Artifactory can act as a SAML Service Provider.

Secured settings.xml passwords

functionality already available in Maven 2.1.0

Centrally-controlled encrypted password policy so admins do not have to rely on clients security policy. Auto-generated encrypted passwords can be used in your settings.xml or with non Maven REST clients, such as Ivy, Gradle etc. Overcomes Maven drawbacks (including Maven 2.1+) - Maven decrypts the password to clear-text on the client, and keeps a clear-text master password on the filesystem.

Via the User Token feature. The token is a random api key and is not reversible to your corporate password, even by Nexus administrators. This was co-developed with a stock market that needed higher security than was is available elsewhere.

Client features

Client settings generation (settings.xml etc.)

Out of the box generation of downloadable from the UI Maven's settings.xml, Ivy's settings.xml and Gradle's initial build script

Maven settings can be templatized and provisioned using Nexus Maven plugin (Pro)

Dedicated client plugins

All client plugins allow generation of build BOM on any CI server (inc. cloud-based and non-pluggable ones) or without using a CI server. Existing plugins:

Artifactory Gradle Plugin (with custom DSL)

Artifactory Maven Plugin

Artifactory MsBuild Plugin (works with and without NuGet dependency management)

Nexus Maven Plugin

CI Integration

Multiple CI servers support

Supports Jenkins/Hudson, TeamCity and Bamboo with full UI integration and any other CI server (inc. cloud-based and non-pluggable ones) by using Maven/Gradle plugins.Supports Microsoft Team Foundation Server (TFS) for working with .NET builds with and without NuGet.

Build Integration - Use the Hudson Artifactory Plugin, TeamCity Plugin or Bamboo Plugin to deploy builds to Artifactory from Hudson/TeamCity together with build-time information. View builds in Artifactory with information about the deployed artifacts and dependencies (all scopes) and runtime environment per build, and link back to the CI Server to obtain fully-reproducible builds (some functions only in Pro).

License Control (Pro) - Take full control over licenses used by third-party dependencies as part of your builds and/or any file. Receive immediate notifications about any libraries that violate your organization's license policy, so you can deal with licensing issues early on during development.