You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Stephen Gargan (JIRA)" <ji...@apache.org> on 2010/11/04 23:44:48 UTC
[jira] Created: (AVRO-693) Missing velocity logging configuration
causes error in clean build
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
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.
[jira] Commented: (AVRO-693) Missing velocity logging configuration
causes error in clean build
Posted by "Scott Carey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928428#action_12928428 ]
Scott Carey commented on AVRO-693:
----------------------------------
Same here. A fix for that is part of AVRO-647.
It is a little bit more involved than the one here -- it logs to a custom Slf4jLogChute if that is available, and NullLogChute otherwise.
> 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.
[jira] Resolved: (AVRO-693) Missing velocity logging configuration
causes error in clean build
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doug Cutting resolved AVRO-693.
-------------------------------
Resolution: Fixed
Assignee: Stephen Gargan
Hadoop Flags: [Reviewed]
I just committed this. Thanks, Stephen!
> 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
> Assignee: 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.
[jira] Updated: (AVRO-693) Missing velocity logging configuration
causes error in clean build
Posted by "Stephen Gargan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Gargan updated AVRO-693:
--------------------------------
Attachment: logchute.patch
> 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.
[jira] Commented: (AVRO-693) Missing velocity logging configuration
causes error in clean build
Posted by "Scott Carey (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (AVRO-693) Missing velocity logging configuration
causes error in clean build
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ 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.