|
From: Yoav L. <yla...@gm...> - 2007-05-25 07:29:06
|
It was disabled on purpose for a single artifact in order to force removal by folder. We did this as a temp replacement to supporting real undeploy, but will make it enabled again since the results of this are not desired. There's already an open issue for that ( https://www.jfrog.org/jira/browse/RTFACT-143). The rationale was that you can rarely remove just a single artifact (pom/jar/metadata etc.) without affecting the consistency of your repository. We do intend to support true undeployment in the future (RTFACT-58) to solve this in a more elegant way. On 5/23/07, David Corbin <dc...@al...> wrote: > > I'm browsing the repository. I right click on an artifact, and Remove is > disabled. I'm logged in as administrator. Why is Remove disabled? > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Artifactory-users mailing list > Art...@li... > https://lists.sourceforge.net/lists/listinfo/artifactory-users > |