|
[
Permlink
| « Hide
]
Mark Chaimungkalanont [Atlassian] added a comment - 13/Mar/07 02:15 PM
Perhaps if it can't find anything, it can default to BAMBOO_HOME instead
As of 1.0.2 this can be achieved by setting -Dbamboo.home=<dir> as a JVM parameter.
AFAIK, there is no way for a wrapper start script to inject parameters into bamboo's start script, which makes upgrading Bamboo using the standalone installation a tedious task. If the start script used some parameters such as JAVA_OPTS and did something like:
java $JAVA_OPTS bamboo.jar $BAMBOO_OPTS where BAMBOO_OPTS is built it up the parameters required to setup Bamboo correctly & JAVA_OPTS is JVM params, it would make upgrading a lot easier. (This also applies to allowing the wrapper script to set the web-context-path & port that Bamboo starts up with.) BAMBOO_HOME can now be used as the home variable. Bamboo will still look for bamboo.home first. If it can't find it, then it'll look for BAMBOO_HOME
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||