[
https://issues.apache.org/jira/browse/AVRO-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928720#action_12928720
]
Scott Carey commented on AVRO-693:
----------------------------------
Yes lets commit this now. Its one line and will be trivial to merge.
AVRO-647 runs into this too because different jars are in the classpath at
different times. Velocity magically switching around its logging context would
probably be a problem for others trying to use the Specific Compiler in various
contexts if we don't force it to use either nothing or SLF4J.
> Missing velocity logging configuration causes error in clean build
> -------------------------------------------------------------------
>
> Key: AVRO-693
> URL: https://issues.apache.org/jira/browse/AVRO-693
> Project: Avro
> Issue Type: Bug
> Components: java
> Environment: Linux 2.6.32-25-generic
> Reporter: Stephen Gargan
> Priority: Minor
> Fix For: 1.5.0
>
> Attachments: logchute.patch
>
>
> I'm seeing an issue with a clean build (ant clean dist) where the
> Initialization of the VelocityEngine in the SpecificCompiler fails. Its
> trying to obtain a Servlet context for the default ServletLogChute.
> Configuring the engine to use the NullLogChute fixes the issue.
> velocityEngine.setProperty("runtime.log.logsystem.class",
> "org.apache.velocity.runtime.log.NullLogChute");
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
