Menu
▾
▴
[Artifactory-users] [ANN] Artifactory 1.2.1-rc1
|
From: Yoav L. <yla...@gm...> - 2007-04-27 08:06:55
|
We are pleased to announce the availability of Artifactory 1.2.1-rc1. Major changes since 1.2.0 ------------------------------------------- - Security permission targets are now both repository-based and path-based - More complete security enforcement - Downgraded the JDK requirements to JDK 1.5 - More 'intelligent' UI-based deployment - Ability to change own password - Resolved metadata merging and checksum warnings - Resolved concurrent node locking issues - Moved to Jackrabbit 1.3 - Updated to wicket-1.3.0-incubating-beta1 - Bug fixes, minor performance improvements and minor UI improvements For a complete list of changes see: https://www.jfrog.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10187 The full 1.2.1 road-map is here: https://www.jfrog.org/jira/secure/IssueNavigator.jspa?reset=true&pid=10070&fixfor=10160 Upgrading from 1.2.1-rc0 ---------------------------------- While Artifactory is down: - Make a backup of the $ARTIFACTORY_HOME folder. - Remove the artifactory.config.xml file from the extracted zip. - Copy the extracted zip content over to your exiting $ARTIFACTORY_HOME, overwriting exiting files. If you are using the standalone version on Linux, also reinstall the artifactoryctl init script. Upgrading from 1.2.0.x ---------------------------------- Make a backup of the $ARTIFACTORY_HOME folder.. To upgrade the configuration copy the $ARTIFACTORY_HOME/etc/artifactory.config.xml file over to the new installation. To upgrade repositories content, please export your repositories from the old version and re-import them into the current one using the web UI. Unfortunately, security settings have dramatically changed from 1.2.0.x and cannot be imported. A note about security changes --------------------------------------------- This version introduces an enhanced version of the security model. The new model allows for setting permissions on targets that are a combination of a repository and a path prefix inside a repository. The following permission-targets samples should make this concept clearer: lib-releases:org/apache refers to any artifact deployed under the "org/apache" path (including sub paths) inside the "lib-releases" repository ANY:org/apache refers to any artifact deployed under the "org/apache" path (including sub paths) inside any repository plugin-snapshots:ANY refers to any artifact deployed under any path inside the "plugin-snapshots" repository ANY:ANY refers to any artifact deployed under any path inside any repository (this is useful for allowing global read permission for authenticated users, where anonymous download is not enabled) The roles of admins, deployers and readers are still applicable for this new type of permission-targets. The admin role is now fully functional for setting permissions to other users inside a permission-target you are an admin of. Documentation ----------------------- Please note that since this is only a release candidate not all docs have been updated to reflect the latest changes. Enjoy! The Artifactory Team |
