Yeah, I agree with this; thanks for bringing it up.

The BEEHIVE_HOME environment variable should be used by Beehive *users* and the distribution.

Having BEEHIVE_DEV_HOME makes the build more obvious because there's no ambiguity between an install and an SVN tree. For those who might wonder, we use BEEHIVE_DEV_HOME so that there's a reliable way to reference the root of the source tree. This fixes some issues with running Ant targets and relative references, so we don't end up with things like "../../../" in Ant files.

  I'd be for going ahead and doing this work.  In the build, we'd need to:

- adjust the build to replace all BEEHIVE_HOME references with BEEHIVE_DEV_HOME

Then, all Beehive developers would need to:

- fix their environments to set BEEHIVE_DEV_HOME

There's definitely a little impact on devs here, but it seems better to do this sooner rather than later. The longer we wait, the harder it is to change. :)

  Anyone see any issues with this?  Can we vote on this today?

  +1 for me.

Eddie




Xibin Zeng wrote:
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






Reply via email to