[
https://issues.apache.org/jira/browse/AVRO-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928588#action_12928588
]
Doug Cutting commented on AVRO-693:
-----------------------------------
I always run 'ant clean test' before I commit, and that works. So an
underlying problem is that the classpath is different for 'ant clean dist' than
'ant clean test'. In particular, the bug is that the jars from the ivy "tools"
configuration are retrieved into build/lib/tools, but only things from the
"default" ivy configuration should be in build/lib. But I assume that AVRO-647
fixes that underlying problem, so it's probably not worth addressing it at this
point.
Should we commit the attached patch today, independent of AVRO-647, so that
trunk's not broken?
> 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.
