Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 1.0.2
-
Fix Version/s: 1.1
-
Component/s: repository interface
-
Labels:None
-
Environment:linux, jdk 1.6, tomcat 6
-
Number of attachments :
Description
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).
Issue Links
- relates to
-
MRM-827
Use a "work" directory for the repo path (e.g. if the repo definition root is mydir/ then put the actually repo under /mydir/repository)
-
is the problem here that it deletes it, or that it used the tomcat home as the location for the internal repository?