Hi there –
As I was building the Beehive svn source tree and deploying
web apps using the alpha distribution, I found myself needing to adjust the
BEEHIVE_HOME setting, depending on what I was doing. It got annoying. The
problem is that this environment variable is overloaded. Do you think we
should have something like a BEEHIVE_DEV_HOME in addition to BEEHIVE_HOME? (I
believe this idea was proposed before.)
I can list some pros and cons of adding BEEHIVE_DEV_HOME:
Pros:
-
Removes ambiguity. No need to
adjust BEEHIVE_HOME for different purpose.
-
We could add an ant task to
update one’s local Beehive distribution with his/her own build (you
basically copy jars and other compiled results from your $BEEHIVE_DEV_HOME to
$BEEHIVE_HOME). No interference between building Beehive source tree and
building web apps.
-
No impact to Beehive users, only
required if you need to build Beehive source.
Cons:
-
It is yet another environment
variable
I did not enter a JIRA issue since this does not
seem like a bug. Hopefully it is appropriate as a discussion topic.
Thanks,
Xibin Zeng
