Syncope-trunk - Build # 258 - Fixed

2013-07-22 Thread Apache Jenkins Server
The Apache Jenkins build system has built Syncope-trunk (build #258) Status: Fixed Check console output at https://builds.apache.org/job/Syncope-trunk/258/ to view the results.

[jira] [Commented] (SYNCOPE-286) Remove Spring MVC

2013-07-22 Thread JIRA
[ https://issues.apache.org/jira/browse/SYNCOPE-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715286#comment-13715286 ] Francesco Chicchiriccò commented on SYNCOPE-286: Removing Spring MVC from

[jira] [Resolved] (SYNCOPE-403) Enrich PropagationStatusTO to report possible propagation exception message

2013-07-22 Thread Marco Di Sabatino Di Diodoro (JIRA)
[ https://issues.apache.org/jira/browse/SYNCOPE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-403. -- Resolution: Fixed http://svn.apache.org/viewvc?view=revision&r

Re: [DISCUSS] Replace logback with log4j 2

2013-07-22 Thread Marco Di Sabatino Di Diodoro
+1 Marco -- Dott. Marco Di Sabatino Di Diodoro Tel. +39 3939065570 Tirasa S.r.l. Viale D'Annunzio 267 - 65127 Pescara Tel +39 0859116307 / FAX +39 085973 http://www.tirasa.net Apache Syncope PMC Member http://people.apache.org/~mdisabatino/ Il giorno 22/lug/2013, alle ore 14:52, Fabio Mar

[jira] [Updated] (SYNCOPE-403) Enrich PropagationStatusTO to report possible propagation exception message

2013-07-22 Thread Andrea Patricelli (JIRA)
[ https://issues.apache.org/jira/browse/SYNCOPE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-403: -- Attachment: MissingExtend.patch > Enrich PropagationStatusTO to report possible pr

[jira] [Reopened] (SYNCOPE-403) Enrich PropagationStatusTO to report possible propagation exception message

2013-07-22 Thread Andrea Patricelli (JIRA)
[ https://issues.apache.org/jira/browse/SYNCOPE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli reopened SYNCOPE-403: --- FailureMessageModalPage.html missing tag > Enrich PropagationStatusTO

Re: [DISCUSS] Replace logback with log4j 2

2013-07-22 Thread Fabio Martelli
+1 F. Il 22/07/2013 12:41, Francesco Chicchiriccò ha scritto: Hi all, I have recently read a stunning post from Christian Grobmeier [1] and I was thinking why not to switch the trunk (1.2.0) from logback to log4j 2 (with new AsyncLoggers, of course!). I was also thinking to keep the SLF4J laye

Re: [DISCUSS] Replace logback with log4j 2

2013-07-22 Thread Colm O hEigeartaigh
+1. Colm. On Mon, Jul 22, 2013 at 11:41 AM, Francesco Chicchiriccò < ilgro...@apache.org> wrote: > Hi all, > I have recently read a stunning post from Christian Grobmeier [1] and I > was thinking why not to switch the trunk (1.2.0) from logback to log4j 2 > (with new AsyncLoggers, of course!).

Re: [DISCUSS] Replace logback with log4j 2

2013-07-22 Thread Francesco Chicchiriccò
On 22/07/2013 14:29, Oliver Wulff wrote: I assume there are no dependencies within the code which would allow the users to still give the option to use logback? There are also direct references in the source code to Logback internal classes (the LoggerController, for example) since the SLF4J

RE: [DISCUSS] Replace logback with log4j 2

2013-07-22 Thread Oliver Wulff
I assume there are no dependencies within the code which would allow the users to still give the option to use logback? log4j 2 is still in beta. Do we know when it should be released? Just my two cents... Thanks Oli From: cschneider...@gmail.com [cschne

Syncope-trunk - Build # 257 - Failure

2013-07-22 Thread Apache Jenkins Server
The Apache Jenkins build system has built Syncope-trunk (build #257) Status: Failure Check console output at https://builds.apache.org/job/Syncope-trunk/257/ to view the results.

Re: [DISCUSS] Replace logback with log4j 2

2013-07-22 Thread Christian Schneider
+1 For switching to log4j. I would also keep the slf4j layer. This minimizes direct dependencies on the log framework and also works great in OSGi. Christian 2013/7/22 Francesco Chicchiriccò > Hi all, > I have recently read a stunning post from Christian Grobmeier [1] and I > was thinking why

RE: [DISCUSS] Replace logback with log4j 2

2013-07-22 Thread Jan Bernhardt
Excellent idea! > -Original Message- > From: Francesco Chicchiriccò [mailto:ilgro...@apache.org] > Sent: Montag, 22. Juli 2013 12:42 > To: dev@syncope.apache.org > Subject: [DISCUSS] Replace logback with log4j 2 > > Hi all, > I have recently read a stunning post from Christian Grobmeier [

Re: [DISCUSS] Replace logback with log4j 2

2013-07-22 Thread andrea patricelli
Il 22/07/2013 12:50, Massimiliano Perrone ha scritto: On 22/07/2013 12:45, Francesco Chicchiriccò wrote: On 22/07/2013 12:41, Francesco Chicchiriccò wrote: Hi all, I have recently read a stunning post from Christian Grobmeier [1] and I was thinking why not to switch the trunk (1.2.0) from logb

Re: [DISCUSS] Replace logback with log4j 2

2013-07-22 Thread Massimiliano Perrone
On 22/07/2013 12:45, Francesco Chicchiriccò wrote: On 22/07/2013 12:41, Francesco Chicchiriccò wrote: Hi all, I have recently read a stunning post from Christian Grobmeier [1] and I was thinking why not to switch the trunk (1.2.0) from logback to log4j 2 (with new AsyncLoggers, of course!). I

Re: [DISCUSS] Replace logback with log4j 2

2013-07-22 Thread Francesco Chicchiriccò
On 22/07/2013 12:41, Francesco Chicchiriccò wrote: Hi all, I have recently read a stunning post from Christian Grobmeier [1] and I was thinking why not to switch the trunk (1.2.0) from logback to log4j 2 (with new AsyncLoggers, of course!). I was also thinking to keep the SLF4J layer, so that c

[DISCUSS] Replace logback with log4j 2

2013-07-22 Thread Francesco Chicchiriccò
Hi all, I have recently read a stunning post from Christian Grobmeier [1] and I was thinking why not to switch the trunk (1.2.0) from logback to log4j 2 (with new AsyncLoggers, of course!). I was also thinking to keep the SLF4J layer, so that code changes would be minimal. Besides performance

[jira] [Resolved] (SYNCOPE-404) LDAP Roles lose entitlement upon LDAP synchronization

2013-07-22 Thread JIRA
[ https://issues.apache.org/jira/browse/SYNCOPE-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-404. Resolution: Fixed Assignee: Francesco Chicchiriccò 1_1_X: http://svn