Cool! Yeah, this is sort of what I'm working on now for the distribution but haven't gotten around to doing it internally.
What build.xml file does this patch? There are several of them. <g>
It patches /trunk/build.xml
It might be worth having a standalone build file that can be included with a webapp rather than a single one to use for all webapps. The targets would be the same but the BEEHIVE_PROJECT environment variable would be set in the build file itself and probably just point to ${basedir}.
What would you think about that?
Doing this could present a couple difficulties:
-if the canonical project build.xml gets updated, then you'll have to be sure to remember copy that build.xml file to all your projects. This could lead to projects with build.xml files that are out of sync
-unless creating a webapp is somehow automated, this places an extra burden on developers to copy the appropriate build.xml to their new webapp
Also, it might be worth getting the Tomcat deploy / undeploy targets wired in -- these would use the same ${basedir} for the webapp root and would need a context root property as well.
Yes, that would be useful.
Bryan
