Project

General

Profile

Bug #3085

document the impact of re-deploying on metacat.properties

Added by Matt Jones over 12 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
metacat
Target version:
Start date:
01/22/2008
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
3085

Description

There is some confusion about the act of re-deploying the metacat.war file in the tomcat servlet container and the impact that this can have on a customized metacat.properties file. When redeploying, the default metacat.properties file from the war file overwrites the deployed version, possibly reverting property values. This is unexpected. We should explain in the install documentation how to avoid this issue when deploying, either by backing up the customized metacat.properties file and restoring it after the redeploy, or by modifying the source properties file in metacat/lib/metacat.properties when building the war file.

We may also want to consider how to protect the metacat.properties file during a re-deploy or an upgrade. This might be accomplished by storing the properties file under a different name and making sure its not lost upon redeployment.

History

#1 Updated by Redmine Admin over 7 years ago

Original Bugzilla ID was 3085

#2 Updated by ben leinfelder over 7 years ago

  • Target version changed from Unspecified to 2.1.0

Crucial properties are backed up and restored when upgrading metacat, though I believe this does not include passwords (which is probably for the best).

#3 Updated by ben leinfelder over 7 years ago

  • Status changed from New to Resolved

Added clarification and a note to documentation about what is backed up and when a full metacat.properties file should be backed up.

Also available in: Atom PDF