On 01/12/2014 12:33, Francesco Chicchiriccò wrote:
On 01/12/2014 10:58, Guido Wimmel wrote:
Hi,
actually, this only applies to Syncope-based projects which have
the log4j 1.X API on the classpath. For Syncope plain this is not the
case, so Velocity falls back to CommonsLogLogChute anyway (which
[
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
[
https://issues.apache.org/jira/browse/SYNCOPE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229748#comment-14229748
]
ASF subversion and git services commented on SYNCOPE-612:
-
Commit
Nicola Baiocco created SYNCOPE-613:
--
Summary: delete overridable connector configuration property of
type array String in resource edit panel
Key: SYNCOPE-613
URL: https://issues.apache.org/jira/browse/SYNCOPE-61
On 01/12/2014 10:58, Guido Wimmel wrote:
Hi,
actually, this only applies to Syncope-based projects which have
the log4j 1.X API on the classpath. For Syncope plain this is not the
case, so Velocity falls back to CommonsLogLogChute anyway (which is tried
next after Log4jLogChute).
Still, I think
Hi,
actually, this only applies to Syncope-based projects which have
the log4j 1.X API on the classpath. For Syncope plain this is not the
case, so Velocity falls back to CommonsLogLogChute anyway (which is tried
next after Log4jLogChute).
Still, I think it's more robust to configure the Velocity
[
https://issues.apache.org/jira/browse/SYNCOPE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guido Wimmel resolved SYNCOPE-612.
--
Resolution: Fixed
> explicit configuration of Velocity logging
> --
[
https://issues.apache.org/jira/browse/SYNCOPE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229608#comment-14229608
]
ASF subversion and git services commented on SYNCOPE-612:
-
Commit
[
https://issues.apache.org/jira/browse/SYNCOPE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229606#comment-14229606
]
ASF subversion and git services commented on SYNCOPE-612:
-
Commit
[
https://issues.apache.org/jira/browse/SYNCOPE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guido Wimmel updated SYNCOPE-612:
-
Description:
If the log4j 1.x API is on the classpath (e.g. in a Syncope-based project with
addi
[
https://issues.apache.org/jira/browse/SYNCOPE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guido Wimmel updated SYNCOPE-612:
-
Description:
If the log4j 1.x API is on the classpath (e.g. in a Syncope-based project with
addi
[
https://issues.apache.org/jira/browse/SYNCOPE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guido Wimmel updated SYNCOPE-612:
-
Description:
Syncope >= 1.2.0 tries to write a velocity.log-File. Startup fails if this is
not p
Guido Wimmel created SYNCOPE-612:
Summary: prevent writing of velocity.log
Key: SYNCOPE-612
URL: https://issues.apache.org/jira/browse/SYNCOPE-612
Project: Syncope
Issue Type: Bug
C
13 matches
Mail list logo