beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zach Smith (JIRA)" <...@beehive.apache.org>
Subject [jira] Closed: (BEEHIVE-376) Eliminate velocity.log droppings from the contro build process
Date Tue, 23 Aug 2005 18:04:08 GMT
     [ http://issues.apache.org/jira/browse/BEEHIVE-376?page=all ]
     
Zach Smith closed BEEHIVE-376:
------------------------------


verified no more velocity logs

> Eliminate velocity.log droppings from the contro build process
> --------------------------------------------------------------
>
>          Key: BEEHIVE-376
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-376
>      Project: Beehive
>         Type: Bug
>   Components: Controls
>     Versions: V1Beta
>     Reporter: Kyle Marvin
>     Assignee: Kyle Marvin
>     Priority: Minor
>      Fix For: v1m1

>
> The Controls build process uses Velocity for code generation, and the current configuration
(by default) leaves a velocity.log file in the local directory where the <apt> task
was invoked.   This information is generally useless to Control authors (it is mainly only
useful if you are modifying the Control velocity templates themselves) so really shouldn't
be generated in the default case.  There should be some type of 'verbose' mode that makes
them available, but not by default.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message