Peter Johnson wrote:Change the directory security such that only the user account running JBossAS has access to server/xxx/tmp. (Recursively apply that same setting if you already have files in tmp.)
Andrew Monkhouse wrote:You might want to look at CVS keyword substitution. It has been a really long time since I played with anything like this, but you could try something like:
Check that into your source control system then check it out again. You should see it has been expanded by CVS into something like:
lalit upadheyay wrote:Ok. I was under impression that you have a separate code branch in CVS for different version of code and tagging is in place for the branches. So anytime you could have reverted to any of the existing versions with correct proeprty file in place.
BTW, how are you maintaing db version info in database ?
Are you just updating the same single row for upcoming versions ?
By db changes do you mean the schema enhancements ?
lalit upadheyay wrote:You can add a property file like application.properties in your code and load a property say app.version as System property at application startup so that it is accessible throught the code at runtime.
You can check in that to the repository (CVS) and update it for new code branches. As you create new branches, you only need to check out, update the app.version property and check in the property file.
At this time I can think of this way of tracking the application version. Someone having some other idea please do share.
Andrew Monkhouse wrote:Wow, I would love to help you, but its just too hard to read your post. Perhaps you should use real words.