[jira] [Created] (SYNCOPE-281) Refactor client module: Move common classes into common module

2013-01-21 Thread Jan Bernhardt (JIRA)
Jan Bernhardt created SYNCOPE-281: - Summary: Refactor client module: Move common classes into common module Key: SYNCOPE-281 URL: https://issues.apache.org/jira/browse/SYNCOPE-281 Project: Syncope

[jira] [Updated] (SYNCOPE-281) Refactor client module: Move common classes into common module

2013-01-21 Thread JIRA
[ https://issues.apache.org/jira/browse/SYNCOPE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-281: --- Component/s: common > Refactor client module: Move common classes into c

[jira] [Commented] (SYNCOPE-281) Refactor client module: Move common classes into common module

2013-01-21 Thread JIRA
[ https://issues.apache.org/jira/browse/SYNCOPE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558603#comment-13558603 ] Francesco Chicchiriccò commented on SYNCOPE-281: I've added a 'common' co

[jira] [Commented] (SYNCOPE-281) Refactor client module: Move common classes into common module

2013-01-21 Thread Jan Bernhardt (JIRA)
[ https://issues.apache.org/jira/browse/SYNCOPE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558604#comment-13558604 ] Jan Bernhardt commented on SYNCOPE-281: --- Wow, that was fast! I was just about doing

[jira] [Resolved] (SYNCOPE-280) Update some checked exceptions to runtime ones

2013-01-21 Thread Andrei Shakirin (JIRA)
[ https://issues.apache.org/jira/browse/SYNCOPE-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrei Shakirin resolved SYNCOPE-280. - Resolution: Fixed > Update some checked exceptions to runtime ones > ---

[jira] [Updated] (SYNCOPE-280) Update some checked exceptions to runtime ones

2013-01-21 Thread Andrei Shakirin (JIRA)
[ https://issues.apache.org/jira/browse/SYNCOPE-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrei Shakirin updated SYNCOPE-280: Fix Version/s: 1.1.0 > Update some checked exceptions to runtime ones > --

Re: Change console admin password and related documentation

2013-01-21 Thread dsigno
>> >>> Could you please add how to generate MD5 and SHA1 under Windows? >> >> As far as I know, Windows don't have native command line tools for md5 or >> sha1 evaluation. >> I have updated the related documentation page [1]. Regards. Denis. [1] - https://cwiki.apache.org/confluence/display/SYN

[jira] [Created] (SYNCOPE-282) Implement JAX-RS exception mapper for server side

2013-01-21 Thread Andrei Shakirin (JIRA)
Andrei Shakirin created SYNCOPE-282: --- Summary: Implement JAX-RS exception mapper for server side Key: SYNCOPE-282 URL: https://issues.apache.org/jira/browse/SYNCOPE-282 Project: Syncope Iss

[jira] [Commented] (SYNCOPE-281) Refactor client module: Move common classes into common module

2013-01-21 Thread Jan Bernhardt (JIRA)
[ https://issues.apache.org/jira/browse/SYNCOPE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558637#comment-13558637 ] Jan Bernhardt commented on SYNCOPE-281: --- OK, major changes are committed. All commi

[jira] [Commented] (SYNCOPE-281) Refactor client module: Move common classes into common module

2013-01-21 Thread JIRA
[ https://issues.apache.org/jira/browse/SYNCOPE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558641#comment-13558641 ] Francesco Chicchiriccò commented on SYNCOPE-281: Actually, console Seleni

[Discussion] Rest package names

2013-01-21 Thread Andrei Shakirin
Hi, I would like to make a proposal regarding some Rest package names: 1. Core services implementations: org.apache.syncope.core.services (actually org.apache.syncope.core.services.impl). "Impl" ending doesn't bring additional information and doesn't recommended by java best practices.

[jira] [Updated] (SYNCOPE-281) Refactor client module: Move common classes into common module

2013-01-21 Thread JIRA
[ https://issues.apache.org/jira/browse/SYNCOPE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-281: --- Attachment: SYNCOPE-281.selenium.patch SYNCOPE-281.selenium.patch makes the

[jira] [Commented] (SYNCOPE-281) Refactor client module: Move common classes into common module

2013-01-21 Thread JIRA
[ https://issues.apache.org/jira/browse/SYNCOPE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558645#comment-13558645 ] Francesco Chicchiriccò commented on SYNCOPE-281: Did you already check if

[jira] [Updated] (SYNCOPE-281) Refactor client module: Move common classes into common module

2013-01-21 Thread JIRA
[ https://issues.apache.org/jira/browse/SYNCOPE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-281: --- Attachment: (was: SYNCOPE-281.selenium.patch) > Refactor client modu

[jira] [Issue Comment Deleted] (SYNCOPE-281) Refactor client module: Move common classes into common module

2013-01-21 Thread JIRA
[ https://issues.apache.org/jira/browse/SYNCOPE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-281: --- Comment: was deleted (was: SYNCOPE-281.selenium.patch makes the selenium, de

[jira] [Commented] (SYNCOPE-281) Refactor client module: Move common classes into common module

2013-01-21 Thread Jan Bernhardt (JIRA)
[ https://issues.apache.org/jira/browse/SYNCOPE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558649#comment-13558649 ] Jan Bernhardt commented on SYNCOPE-281: --- Thanks for the hint about Selenium tests.

[jira] [Commented] (SYNCOPE-281) Refactor client module: Move common classes into common module

2013-01-21 Thread JIRA
[ https://issues.apache.org/jira/browse/SYNCOPE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558654#comment-13558654 ] Francesco Chicchiriccò commented on SYNCOPE-281: About Selenium, such tes

[jira] [Commented] (SYNCOPE-241) Move persistence and persistence impl into separate modules

2013-01-21 Thread JIRA
[ https://issues.apache.org/jira/browse/SYNCOPE-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558657#comment-13558657 ] Francesco Chicchiriccò commented on SYNCOPE-241: Is there still some work

[jira] [Commented] (SYNCOPE-281) Refactor client module: Move common classes into common module

2013-01-21 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/SYNCOPE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558662#comment-13558662 ] Hudson commented on SYNCOPE-281: Integrated in Syncope-trunk #458 (See [https://builds.a

[jira] [Commented] (SYNCOPE-281) Refactor client module: Move common classes into common module

2013-01-21 Thread Jan Bernhardt (JIRA)
[ https://issues.apache.org/jira/browse/SYNCOPE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558664#comment-13558664 ] Jan Bernhardt commented on SYNCOPE-281: --- OK, makes sense. I very happy to see, that

Re: [Discussion] Rest package names

2013-01-21 Thread Christian Schneider
On 21.01.2013 10:29, Andrei Shakirin wrote: > Hi, > > I would like to make a proposal regarding some Rest package names: > > 1. Core services implementations: org.apache.syncope.core.services > (actually org.apache.syncope.core.services.impl). "Impl" ending doesn't > bring additional info

RE: [Discussion] Rest package names

2013-01-21 Thread Andrei Shakirin
Hi Christian, > > 2. Resource comparators and server exception mapper: > org.apache.syncope.core.rest.utils (actually org.apache.syncope.core.rest). > It makes purpose of these classes more clear. > Generally I don't like util packages. I would put these helpers into the same > package as th

Re: [Discussion] Rest package names

2013-01-21 Thread Christian Schneider
On 21.01.2013 11:14, Andrei Shakirin wrote: > Hi Christian, > >>> 2. Resource comparators and server exception mapper: >> org.apache.syncope.core.rest.utils (actually org.apache.syncope.core.rest). >> It makes purpose of these classes more clear. >> Generally I don't like util packages. I wou

[jira] [Commented] (SYNCOPE-281) Refactor client module: Move common classes into common module

2013-01-21 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/SYNCOPE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558676#comment-13558676 ] Hudson commented on SYNCOPE-281: Integrated in Syncope-trunk #459 (See [https://builds.a

[DISCUSS] Moving issues from one version to another

2013-01-21 Thread Francesco Chicchiriccò
Hi all, following our recent discussion [1], I'd propose to: 1. move SYNCOPE-231 (e.g. CXF migration) and all subtasks to 1.1.0 2. move SYNCOPE-275 ("Upgrade Spring to 3.2") to 1.1.0 as it requires SYNCOPE-231 3. move SYNCOPE-204 ("Add Karaf features") to 1.2.0 4. move SYNCOPE-122 ("Password ch

RE: [Discussion] Rest package names

2013-01-21 Thread Andrei Shakirin
> The classes are referenced from the spring config but they belong to the impl > classes so why introduce a new package? Basically we can leave exception mapper and resource comparator in core.services, there is one thing that make me unsure: Exception mapper and resource comparator depend from

Re: Change console admin password and related documentation

2013-01-21 Thread Francesco Chicchiriccò
On 21/01/2013 09:35, dsigno wrote: Could you please add how to generate MD5 and SHA1 under Windows? As far as I know, Windows don't have native command line tools for md5 or sha1 evaluation. I have updated the related documentation page [1]. Thanks Denis! I've just made some minor tweaks. R

Re: [DISCUSS] Moving issues from one version to another

2013-01-21 Thread Fabio Martelli
Il giorno 21/gen/2013, alle ore 11.46, Francesco Chicchiriccò ha scritto: > Hi all, > following our recent discussion [1], I'd propose to: > > 1. move SYNCOPE-231 (e.g. CXF migration) and all subtasks to 1.1.0 > 2. move SYNCOPE-275 ("Upgrade Spring to 3.2") to 1.1.0 as it requires > SYNCOPE-231

RE: [DISCUSS] Moving issues from one version to another

2013-01-21 Thread Andrei Shakirin
Hi Francesco, +1 from my side for all four topics. Cheers, Andrei. > -Original Message- > From: Francesco Chicchiriccò [mailto:ilgro...@apache.org] > Sent: Montag, 21. Januar 2013 11:46 > To: dev@syncope.apache.org > Subject: [DISCUSS] Moving issues from one version to another > > Hi al

Re: [DISCUSS] Moving issues from one version to another

2013-01-21 Thread Francesco Chicchiriccò
On 21/01/2013 12:00, Fabio Martelli wrote: Il giorno 21/gen/2013, alle ore 11.46, Francesco Chicchiriccò ha scritto: Hi all, following our recent discussion [1], I'd propose to: 1. move SYNCOPE-231 (e.g. CXF migration) and all subtasks to 1.1.0 2. move SYNCOPE-275 ("Upgrade Spring to 3.2") to

[jira] [Assigned] (SYNCOPE-253) Upgrade Activiti to 5.11

2013-01-21 Thread JIRA
[ https://issues.apache.org/jira/browse/SYNCOPE-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò reassigned SYNCOPE-253: -- Assignee: Francesco Chicchiriccò > Upgrade Activiti to 5.11 >

Re: [DISCUSS] Moving issues from one version to another

2013-01-21 Thread Fabio Martelli
Il giorno 21/gen/2013, alle ore 12.04, Francesco Chicchiriccò ha scritto: > On 21/01/2013 12:00, Fabio Martelli wrote: >> Il giorno 21/gen/2013, alle ore 11.46, Francesco Chicchiriccò ha scritto: >> >>> Hi all, >>> following our recent discussion [1], I'd propose to: >>> >>> 1. move SYNCOPE-231

Re: [DISCUSS] Moving issues from one version to another

2013-01-21 Thread Marco Di Sabatino Di Diodoro
On Jan 21, 2013, at 12:11 PM, Fabio Martelli wrote: > > Il giorno 21/gen/2013, alle ore 12.04, Francesco Chicchiriccò ha scritto: > >> On 21/01/2013 12:00, Fabio Martelli wrote: >>> Il giorno 21/gen/2013, alle ore 11.46, Francesco Chicchiriccò ha scritto: >>> Hi all, following our re

Re: [DISCUSS] Moving issues from one version to another

2013-01-21 Thread Francesco Chicchiriccò
On 21/01/2013 12:13, Marco Di Sabatino Di Diodoro wrote: On Jan 21, 2013, at 12:11 PM, Fabio Martelli wrote: Il giorno 21/gen/2013, alle ore 12.04, Francesco Chicchiriccò ha scritto: On 21/01/2013 12:00, Fabio Martelli wrote: Il giorno 21/gen/2013, alle ore 11.46, Francesco Chicchiriccò ha s

[jira] [Resolved] (SYNCOPE-253) Upgrade Activiti to 5.11

2013-01-21 Thread JIRA
[ https://issues.apache.org/jira/browse/SYNCOPE-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-253. Resolution: Fixed http://svn.apache.org/viewvc?rev=1436280&view=rev

[jira] [Assigned] (SYNCOPE-249) Implement RoleOwnerSchema for role propagation and synchronization

2013-01-21 Thread JIRA
[ https://issues.apache.org/jira/browse/SYNCOPE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò reassigned SYNCOPE-249: -- Assignee: Francesco Chicchiriccò > Implement RoleOwnerSchema for r

Re: [DISCUSS] Moving issues from one version to another

2013-01-21 Thread Fabio Martelli
Il giorno 21/gen/2013, alle ore 12.19, Francesco Chicchiriccò ha scritto: > On 21/01/2013 12:13, Marco Di Sabatino Di Diodoro wrote: >> On Jan 21, 2013, at 12:11 PM, Fabio Martelli wrote: >> >>> Il giorno 21/gen/2013, alle ore 12.04, Francesco Chicchiriccò ha scritto: >>> On 21/01/2013 12:

[jira] [Commented] (SYNCOPE-253) Upgrade Activiti to 5.11

2013-01-21 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/SYNCOPE-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558711#comment-13558711 ] Hudson commented on SYNCOPE-253: Integrated in Syncope-trunk #461 (See [https://builds.a

Re: [DISCUSS] Moving issues from one version to another

2013-01-21 Thread Francesco Chicchiriccò
On 21/01/2013 12:47, Fabio Martelli wrote: [...] I think that SYNCOPE-122 and SYNCOPE-135 will not make the difference in reference to the load. I disagree on this point: anyway, keeping SYNCOPE-122 in 1.1.0 (point 4 of my initial checklist) and moving SYNCOPE-135 and SYNCOPE-136 from 1.2.0

RE: [DISCUSS] Moving issues from one version to another

2013-01-21 Thread Jan Bernhardt
> -Original Message- > From: Francesco Chicchiriccò [mailto:ilgro...@apache.org] > Sent: Montag, 21. Januar 2013 13:18 > To: dev@syncope.apache.org > Subject: Re: [DISCUSS] Moving issues from one version to another > > On 21/01/2013 12:47, Fabio Martelli wrote: > > [...] > > I think that S

Re: [DISCUSS] Moving issues from one version to another

2013-01-21 Thread Francesco Chicchiriccò
On 21/01/2013 13:51, Jan Bernhardt wrote: -Original Message- From: Francesco Chicchiriccò [mailto:ilgro...@apache.org] Sent: Montag, 21. Januar 2013 13:18 To: dev@syncope.apache.org Subject: Re: [DISCUSS] Moving issues from one version to another On 21/01/2013 12:47, Fabio Martelli wrote

RE: [DISCUSS] Moving issues from one version to another

2013-01-21 Thread Jan Bernhardt
> >> 1. move SYNCOPE-231 (e.g. CXF migration) and all subtasks to 1.1.0 2. > >> move > >> SYNCOPE-275 ("Upgrade Spring to 3.2") to 1.1.0 as it requires > >> SYNCOPE-231 > > Does this means that we will completely switch to CXF? I would be > completely happy about this! But until now I thought, that

[jira] [Commented] (SYNCOPE-281) Refactor client module: Move common classes into common module

2013-01-21 Thread Jan Bernhardt (JIRA)
[ https://issues.apache.org/jira/browse/SYNCOPE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558747#comment-13558747 ] Jan Bernhardt commented on SYNCOPE-281: --- Archetype was also working for me. Next, I

Re: [DISCUSS] Moving issues from one version to another

2013-01-21 Thread Francesco Chicchiriccò
On 21/01/2013 14:12, Jan Bernhardt wrote: 1. move SYNCOPE-231 (e.g. CXF migration) and all subtasks to 1.1.0 2. move SYNCOPE-275 ("Upgrade Spring to 3.2") to 1.1.0 as it requires SYNCOPE-231 Does this means that we will completely switch to CXF? I would be completely happy about this! But until

Re: [DISCUSS] Moving issues from one version to another

2013-01-21 Thread Fabio Martelli
Il giorno 21/gen/2013, alle ore 13.17, Francesco Chicchiriccò ha scritto: > On 21/01/2013 12:47, Fabio Martelli wrote: >> [...] >> I think that SYNCOPE-122 and SYNCOPE-135 will not make the difference in >> reference to the load. > > I disagree on this point: anyway, keeping SYNCOPE-122 in 1.1.

Re: [DISCUSS] Moving issues from one version to another

2013-01-21 Thread Marco Di Sabatino Di Diodoro
+1 On Jan 21, 2013, at 2:38 PM, Fabio Martelli wrote: > > Il giorno 21/gen/2013, alle ore 13.17, Francesco Chicchiriccò ha scritto: > >> On 21/01/2013 12:47, Fabio Martelli wrote: >>> [...] >>> I think that SYNCOPE-122 and SYNCOPE-135 will not make the difference in >>> reference to the load.

[jira] [Resolved] (SYNCOPE-281) Refactor client module: Move common classes into common module

2013-01-21 Thread Jan Bernhardt (JIRA)
[ https://issues.apache.org/jira/browse/SYNCOPE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Bernhardt resolved SYNCOPE-281. --- Resolution: Fixed > Refactor client module: Move common classes into common module > ---

RE: [DISCUSS] Moving issues from one version to another

2013-01-21 Thread Andrei Shakirin
> Hum, I actually thought you would have included the full CXF features in > 1.1.0 alongside with still running but deprecated Spring MVC interfaces. > If I was wrong, could this be done? It will be optimal for us, as far as we resolver list setters issue for TOs mentioned by Jan. What about int

RE: [DISCUSS] Moving issues from one version to another

2013-01-21 Thread Jan Bernhardt
> > But if I understand the description in SYNCOPE-275 correctly, it would cause > problems to switch to Spring 3.2 without removing all Spring MVC's > components. And of cause without Spring MVC's the old REST Interface could > not be used. Correct? > > You are right: we should then open another

Re: [DISCUSS] Moving issues from one version to another

2013-01-21 Thread Francesco Chicchiriccò
On 21/01/2013 15:04, Jan Bernhardt wrote: But if I understand the description in SYNCOPE-275 correctly, it would cause problems to switch to Spring 3.2 without removing all Spring MVC's components. And of cause without Spring MVC's the old REST Interface could not be used. Correct? You are righ

Re: [DISCUSS] Moving issues from one version to another

2013-01-21 Thread Francesco Chicchiriccò
On 21/01/2013 15:04, Andrei Shakirin wrote: Hum, I actually thought you would have included the full CXF features in 1.1.0 alongside with still running but deprecated Spring MVC interfaces. If I was wrong, could this be done? It will be optimal for us, as far as we resolver list setters issue fo

[jira] [Commented] (SYNCOPE-281) Refactor client module: Move common classes into common module

2013-01-21 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/SYNCOPE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558789#comment-13558789 ] Hudson commented on SYNCOPE-281: Integrated in Syncope-trunk #463 (See [https://builds.a

RE: [DISCUSS] Moving issues from one version to another

2013-01-21 Thread Andrei Shakirin
> See my latest reply to Jan: in this context (i.e. provide a transitional > version > for projects upgrading from 1_0_X), (B) makes more sense. Agree. A little bit dangerous is that CXF Rest impl in 1.1.0 can be broken by refactorings/bugs fixing and we do not see it immediately (integration te

Re: [DISCUSS] Moving issues from one version to another

2013-01-21 Thread Francesco Chicchiriccò
On 21/01/2013 15:57, Andrei Shakirin wrote: See my latest reply to Jan: in this context (i.e. provide a transitional version for projects upgrading from 1_0_X), (B) makes more sense. Agree. A little bit dangerous is that CXF Rest impl in 1.1.0 can be broken by refactorings/bugs fixing and we do

[jira] [Commented] (SYNCOPE-249) Implement RoleOwnerSchema for role propagation and synchronization

2013-01-21 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/SYNCOPE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558852#comment-13558852 ] Hudson commented on SYNCOPE-249: Integrated in Syncope-trunk #464 (See [https://builds.a

[jira] [Commented] (SYNCOPE-231) Using Standard JAX-RS API in Syncope (Replace Spring Webservice Stack with Apache CXF)

2013-01-21 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558851#comment-13558851 ] Hudson commented on SYNCOPE-231: Integrated in Syncope-trunk #464 (See [https://builds.a

[Question] ApplicationContextProvider in UnitTests

2013-01-21 Thread Jan Bernhardt
Hi, Since last SVN update, I cannot build syncope on my system, due to never ending UnitTests. While trying to investigate into this issue, I tried to run unit test in my eclipse IDE. Most test are ok, but some fail due to a NullpointerException. This exception is caused because "ApplicationCo

Re: [Question] ApplicationContextProvider in UnitTests

2013-01-21 Thread Francesco Chicchiriccò
On 21/01/2013 17:07, Jan Bernhardt wrote: Hi, Since last SVN update, I cannot build syncope on my system, due to never ending UnitTests. Which update? Was this incorporated in latest Jenkins build? [1] While trying to investigate into this issue, I tried to run unit test in my eclipse IDE.

RE: [Question] ApplicationContextProvider in UnitTests

2013-01-21 Thread Jan Bernhardt
> -Original Message- > From: Francesco Chicchiriccò [mailto:ilgro...@apache.org] > Sent: Montag, 21. Januar 2013 17:14 > To: dev@syncope.apache.org > Subject: Re: [Question] ApplicationContextProvider in UnitTests > > On 21/01/2013 17:07, Jan Bernhardt wrote: > > Hi, > > > > Since last SVN

Re: [Question] ApplicationContextProvider in UnitTests

2013-01-21 Thread Francesco Chicchiriccò
On 21/01/2013 17:23, Jan Bernhardt wrote: -Original Message- From: Francesco Chicchiriccò [mailto:ilgro...@apache.org] Sent: Montag, 21. Januar 2013 17:14 To: dev@syncope.apache.org Subject: Re: [Question] ApplicationContextProvider in UnitTests On 21/01/2013 17:07, Jan Bernhardt wrote:

RE: [Question] ApplicationContextProvider in UnitTests

2013-01-21 Thread Jan Bernhardt
> >>> Hi, > >>> > >>> Since last SVN update, I cannot build syncope on my system, due to > never ending UnitTests. > >> Which update? Was this incorporated in latest Jenkins build? [1] > > I guess my problems are related to: > > > > Revision 1436375 by ilgrosso: > > [SYNCOPE-249] core: extension fo

[jira] [Created] (SYNCOPE-283) website edits

2013-01-21 Thread Glen Mazza (JIRA)
Glen Mazza created SYNCOPE-283: -- Summary: website edits Key: SYNCOPE-283 URL: https://issues.apache.org/jira/browse/SYNCOPE-283 Project: Syncope Issue Type: Improvement Reporter: Gle

[jira] [Updated] (SYNCOPE-283) website edits

2013-01-21 Thread Glen Mazza (JIRA)
[ https://issues.apache.org/jira/browse/SYNCOPE-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glen Mazza updated SYNCOPE-283: --- Attachment: site.patch website patch > website edits > - > >