[
http://jira.codehaus.org/browse/MRM-789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133624#action_133624
]
Brill Pappin commented on MRM-789:
----------------------------------
The delete worked flawlessly... and that was and was not the problem because it
was pointed at tomcat home by default (or at least it was without me setting
it).
A quick fix would be to make sure you append you own dir name on the end of
whatever path chosen, that way a delete won't wipe out a complex app server
installation.
I was very luck in that this particular host was entirely in SVN, so I was able
to get the whole thing going again in a minute or so... but anyone else that
tries this is not going to be so lucky.
> 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
> Priority: Critical
>
> 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
