|
From: Yoav L. <yla...@gm...> - 2007-04-13 16:59:31
|
We will look into the checksum warnings. Thanks. On 4/13/07, Jorg Heymans <jor...@gm...> wrote: > > The permission bugs seem to have been ironed out, thanks ! I find the new > mechanism a bit more intuitive as well. > > One small thing though, i always get checksum errors on deployment. Is > this still a known bug ? > > [INFO] Retrieving previous build number from test-snapshot > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > '48cbd5f13a2b1e3ca5d78aeb45e3ab > a20065a407'; remote = 'da39a3ee5e6b4b0d3255bfef95601890afd80709' - > RETRYING > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > '48cbd5f13a2b1e3ca5d78aeb45e3ab > a20065a407'; remote = 'da39a3ee5e6b4b0d3255bfef95601890afd80709' - > IGNORING > Uploading: > http://server/artifactory/test-snapshot-repo/my/groupid/myartifact/0.1-SNAPSHOT/myartifact-0.1-20070413.112354-4.pom > 809b uploaded > [INFO] Retrieving previous metadata from test-snapshot > [WARNING] *** CHECKSUM FAILED - Error retrieving checksum file for > my/groupid/myartifact/maven-metad > ata.xml - IGNORING > [INFO] Uploading repository metadata for: 'artifact my.groupid:myartifact' > [INFO] Retrieving previous metadata from test-snapshot > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > '0dbc902360478efc3d8ecfc7068870 > 43f3059cec'; remote = 'da39a3ee5e6b4b0d3255bfef95601890afd80709' - > RETRYING > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > '0dbc902360478efc3d8ecfc7068870 > 43f3059cec'; remote = 'da39a3ee5e6b4b0d3255bfef95601890afd80709' - > IGNORING > > > On 4/13/07, Yoav Landman <yla...@gm...> wrote: > > > We are pleased to announce the availability of Artifactory 1.2.1-rc0. > > This is the first release candidate towards the final release of 1.2.1. > > > > Major changes in this release > > ------------------------------------------- > > - Security permission targets are now both repository-based and > > path-based > > - More complete security enforcement > > - Downgraded the required JDK in web-application deployment style to 1.5 > > - Improvements to the UI-based deployment > > - Ability to change own password > > - Bug fixes, bug fixes... > > > > The complete list of changes see: https://www.jfrog.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10186 > > > > and 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.0.x > > ---------------------------------- > > You can upgrade your repositories content and configuration from the > > previous versions. > > To upgrade the configuration copy the > > $ARTIFACTORY_HOME/etc/artifactory.config.xml file over to the new > > installation. > > To upgrade repositories content, either use the UI's import/export > > facility from the old version (preferable) or copy over the > > $ARTIFACTORY_HOME/repos/jcr folder from the old version to > > ARTIFACTORY_HOME/data/jcr. > > Unfortunately, security settings have dramatically changed and cannot be > > imported. > > > > A note about security changes > > --------------------------------------------- > > This version introduces an improved 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 > > > > > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share > > your > > opinions on IT & business topics through brief surveys-and earn cash > > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > Artifactory-users mailing list > > Art...@li... > > https://lists.sourceforge.net/lists/listinfo/artifactory-users > > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Artifactory-users mailing list > Art...@li... > https://lists.sourceforge.net/lists/listinfo/artifactory-users > > |