[
http://jira.codehaus.org/browse/MRM-789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137300#action_137300
]
Maria Odea Ching commented on MRM-789:
--------------------------------------
Yeah, creating a "work" directory would ensure this but I'm hesitant in having
a "work" directory. Doing this would require importing the contents of the
repository into the "work" directory. This would mean that there'll be
duplicate copies of the repo in the filesystem.. do we really want that? I'm
also taking into account how long it would take to add a new managed repo if
the contents would have to be imported.. it might take a while if it's a large
repo. Maybe we should bring this up to the dev list..
Anyway, I'll move the checking of the system properties to when a managed repo
is created instead of during delete.
Thanks for your suggestions Brill!
> Archiva may delete you app server installation
> ----------------------------------------------
>
> Key: MRM-789
> URL: http://jira.codehaus.org/browse/MRM-789
> Project: Archiva
> Issue Type: Bug
> Components: repository interface
> Affects Versions: 1.0.2
> Environment: linux, jdk 1.6, tomcat 6
> Reporter: Brill Pappin
> Assignee: Maria Odea Ching
> Priority: Critical
> Fix For: 1.1
>
>
> I installed the WAR version of Archiva into my tomcat instance... no problem
> so far.
> I then attempted to delete the default "internal" repository. I hit the
> delete config and contents button.
> At that moment I noticed that the repository directory was the tomcat home
> directory.
> Archiva managed to completely delete my Tomcat installation.
> To reproduce this, install it as a war, point a repo dir at your app server
> home, and hit the delete button (make sure you have a backup).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
