Manager can not manipulate a GO setting if the setting is unspecified in config file

[gitblit]

Originally reported on Google Code with ID 85

Manager can not manipulate a GO setting if the setting is unspecified in config file

Reported by James.Moger on 2012-04-12 13:18:00

[gitblit]

Reported by James.Moger on 2012-06-15 12:26:42

• Status changed: Queued

[gitblit]

Resolved in v1.0.0.

Reported by James.Moger on 2012-07-14 04:44:17

• Status changed: Done

[gitblit]

I thought this was fixed but it turns out my weak description of the problem was insufficient
to remind me what I needed to do.  This is still an issue in 1.0.0.

Problem only affects GO.  If we want to manipulate a setting that exists in the reference.properties
but does not exist in gitblit.properties we can not do that because gitblit.properties
is manipulated using a regex, not properties.load.  I do that so that setting documentation
is not stripped from the file, which it would be if I used the properties class to
manipulate the settings.

Need to handle case where content does not change after regex substitution.

Reported by James.Moger on 2012-08-03 14:54:40

• Status changed: Started
• Labels added: Milestone-1.0.1
• Labels removed: Milestone-1.0.0

[gitblit]

Reported by James.Moger on 2012-08-06 21:43:50

• Status changed: Queued

[gitblit]

Reported by James.Moger on 2012-08-20 02:06:35

• Labels added: Milestone-1.1.0
• Labels removed: Milestone-1.0.1

[gitblit]

Fix/change released in 1.1.0.

Reported by James.Moger on 2012-08-25 12:20:42

• Status changed: Fixed