[ http://issues.apache.org/jira/browse/BEEHIVE-376?page=all ]
Kyle Marvin resolved BEEHIVE-376:
---------------------------------
Resolution: Fixed
Implemented a bridge class (AptVelocityLogSystem) that bridges between the
Velocity and APT logging subsystems. This implements the standard Velocity
LogSystem interface and forwards all errors/warnings to the APT Messager
associated with the current processing environment.
This means:
- Both output/error streams go to a single location (wherever APT output/errors
are directed)
- Velocity errors will not appropriately cause a compile failure
- No more velocity.log droppings
> 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: V1
>
> 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
