[ http://issues.apache.org/jira/browse/BEEHIVE-201?page=history ]
Jeremiah Johnson closed BEEHIVE-201:
------------------------------------
Looks good to me - this is the new output:
Buildfile: beehive-tools.xml
usage:
[echo]
[echo] The beehive-tools.xml file contains Ant macros which can be used
[echo] to build Beehive related source artifacts such as Controls, Page
Flows,
[echo] and XML Schemas. For examples of how to use these macros, see the
[echo] Beehive samples.
[echo]
[echo] Note, this build file does not contain targets that can be called
[echo] directly on the command line.
[echo]
BUILD SUCCESSFUL
> The usage targets in the build scripts in trunk/user don't work.
> ----------------------------------------------------------------
>
> Key: BEEHIVE-201
> URL: http://issues.apache.org/jira/browse/BEEHIVE-201
> Project: Beehive
> Type: Bug
> Components: Build
> Versions: V1Beta
> Environment: Java / Ant
> Reporter: Jeremiah Johnson
> Assignee: Jeremiah Johnson
> Priority: Trivial
> Fix For: V1
> Attachments: userBuildPatch.txt
>
> The usage targets in the build scripts in trunk/user don't work. These
> scripts are the tools available Beehive consumers, so the usage targets
> should be fixed.
> The files shouldn't be tested in the user directory as those are actually the
> source scripts used to generate the dist scripts. To reproduce this bug, use
> the main build.dist target and then do the following:
> cd <BeehiveDistRoot>/ant
> ant -f buildWebapp.xml
> ant -f webappRuntimeCore.xml
> You will see output like this:
> Buildfile: webappRuntimeCore.xml
> usage:
> [java] Buildfile: build.xml does not exist!
> [java] Build failed
> The correct result would be to see the -projecthelp information.
> - jeremiah
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
