[
https://issues.apache.org/jira/browse/SYNCOPE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229749#comment-14229749
]
ASF subversion and git services commented on SYNCOPE-612:
---------------------------------------------------------
Commit 96c857d4ea25bd5818840f4163b392c48c3db4a0 in syncope's branch
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=96c857d ]
[SYNCOPE-612] White noise
> explicit configuration of Velocity logging
> ------------------------------------------
>
> Key: SYNCOPE-612
> URL: https://issues.apache.org/jira/browse/SYNCOPE-612
> Project: Syncope
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.2.1
> Reporter: Guido Wimmel
> Assignee: Guido Wimmel
> Priority: Minor
> Fix For: 1.2.2, 1.3.0
>
>
> If the log4j 1.x API is on the classpath (e.g. in a Syncope-based project
> with additional dependencies), Syncope >= 1.2.0 tries to write a
> velocity.log-File. Startup fails if this is not possible, e.g. because write
> access to the file system is not granted to the Tomcat process. This used to
> work in Syncope 1.1.X.
> Syncope's VelocityEngineFactoryBean should explicitly configure Velocity to
> use Commons Logging, as Spring's VelocityEngineFactory bean does, which was
> used in 1.1.X.
> See the discussion on the dev mailing list:
> http://syncope-dev.1063484.n5.nabble.com/prevent-writing-of-velocity-log-in-Syncope-1-2-X-master-td5716396.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
