Hi Francesco and Fabio,
> > I hope you wouldn't use DAOs into integration test; I don't like it so much.
>
> While I find this wrong too, I can add that this is not even possible because
> the integration test classes do not have access to core's EntityManager.
Sure, DAO is no way for rest integ
[
https://issues.apache.org/jira/browse/SYNCOPE-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13555275#comment-13555275
]
Hudson commented on SYNCOPE-271:
Integrated in Syncope-trunk #445 (See
[https://builds.a
The Apache Jenkins build system has built Syncope-trunk (build #445)
Status: Fixed
Check console output at https://builds.apache.org/job/Syncope-trunk/445/ to
view the results.
It sounds good.
On my side, I gonna move forward around the OSGi support.
Thanks for the update.
Regards
JB
On 01/16/2013 06:47 PM, Christian Schneider wrote:
Jan contacted me that the E-Mail Server in the Bonn office is currently
down so he can not reply himself at the moment.
So I am reply
The Apache Jenkins build system has built Syncope-1_0_X (build #106)
Status: Unstable
Check console output at https://builds.apache.org/job/Syncope-1_0_X/106/ to
view the results.
Jan contacted me that the E-Mail Server in the Bonn office is currently
down so he can not reply himself at the moment.
So I am replying what he wrote me via Skype:
We currently have the plan to finish the CXF migration during the next
1.5 weeks with 4 developers. The issue is a little urgent as f
[
https://issues.apache.org/jira/browse/SYNCOPE-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-171.
Resolution: Fixed
Assignee: Francesco Chicchiriccò
Wiki pages and si
The Apache Jenkins build system has built Syncope-trunk (build #444)
Status: Still Failing
Check console output at https://builds.apache.org/job/Syncope-trunk/444/ to
view the results.
[
https://issues.apache.org/jira/browse/SYNCOPE-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13555145#comment-13555145
]
Hudson commented on SYNCOPE-241:
Integrated in Syncope-trunk #443 (See
[https://builds.a
The Apache Jenkins build system has built Syncope-trunk (build #443)
Status: Failure
Check console output at https://builds.apache.org/job/Syncope-trunk/443/ to
view the results.
On Jan 16, 2013, at 4:29 PM, Fabio Martelli wrote:
>
> Il giorno 16/gen/2013, alle ore 16.08, Francesco Chicchiriccò ha scritto:
>
>> On 16/01/2013 15:50, Jan Bernhardt wrote:
>>> Hi Syncopers,
>>>
>>> all preparation tasks are more or less done for CXF migration, so next we
>>> would like to
Il giorno 16/gen/2013, alle ore 16.08, Francesco Chicchiriccò ha scritto:
> On 16/01/2013 15:50, Jan Bernhardt wrote:
>> Hi Syncopers,
>>
>> all preparation tasks are more or less done for CXF migration, so next we
>> would like to start with actual CXF migration.
>>
>> Since we are planning t
The Apache Jenkins build system has built Syncope-trunk (build #442)
Status: Fixed
Check console output at https://builds.apache.org/job/Syncope-trunk/442/ to
view the results.
On 16.01.2013 15:58, Francesco Chicchiriccò wrote:
> On 16/01/2013 15:46, Christian Schneider wrote:
>> Hi Francesco,
>>
>> I put these interfaces in the beans package as they are referenced by
>> classes in persistence. You are right that they should go to a better
>> named package. The problem wi
On 16/01/2013 15:50, Jan Bernhardt wrote:
Hi Syncopers,
all preparation tasks are more or less done for CXF migration, so next we would
like to start with actual CXF migration.
Since we are planning to release Syncope 1.1.0 soon I can see two reasonable
solutions to continue.
1. Creat
On 16/01/2013 15:46, Christian Schneider wrote:
Hi Francesco,
I put these interfaces in the beans package as they are referenced by classes
in persistence. You are right that they should go to a better named package.
The problem with core.sync and core.propagation is that
these packages have h
Hi all!
Since we haven't discussed new Service Interfaces, I will send you a couple of
eMails within the next few days, to make sure we all agree on new service
interfaces. You can watch current state in client module under package
org.apache.syncope.services. Some methods are only present due
Hi Syncopers,
all preparation tasks are more or less done for CXF migration, so next we would
like to start with actual CXF migration.
Since we are planning to release Syncope 1.1.0 soon I can see two reasonable
solutions to continue.
1. Creating a release branch for 1.1.0 and making su
I think we have a consensus for alternative 1. So I will close the issue
and will not apply my last patch.
Christian
On 15.01.2013 15:58, Christian Schneider wrote:
> So I see two alternatives:
>
> 1. Keep persistence inside core but try to keep it as a separate
> architectural layer. This would
The Apache Jenkins build system has built Syncope-trunk (build #441)
Status: Failure
Check console output at https://builds.apache.org/job/Syncope-trunk/441/ to
view the results.
Hi Francesco,
I put these interfaces in the beans package as they are referenced by
classes in persistence. You are right that they should go to a better
named package. The problem with core.sync and core.propagation is that
these packages have heavy dependencies to most other parts of the system.
The Apache Jenkins build system has built Syncope-trunk (build #440)
Status: Fixed
Check console output at https://builds.apache.org/job/Syncope-trunk/440/ to
view the results.
Hi all,
while reviewing some wiki pages, I've unexpectedly found that
PropagationActions, SyncActions and SyncResult were put in package
org.apache.syncope.core.persistence.beans
This package, as its name suggests, is meant for JPA entities, not for
interfaces having their own package (org.ap
The Apache Jenkins build system has built Syncope-trunk (build #439)
Status: Failure
Check console output at https://builds.apache.org/job/Syncope-trunk/439/ to
view the results.
[
https://issues.apache.org/jira/browse/SYNCOPE-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13555020#comment-13555020
]
Hudson commented on SYNCOPE-268:
Integrated in Syncope-trunk #439 (See
[https://builds.a
Francesco Chicchiriccò created SYNCOPE-276:
--
Summary: Upgrade instructions from 1.0.X to 1.1.0
Key: SYNCOPE-276
URL: https://issues.apache.org/jira/browse/SYNCOPE-276
Project: Syncope
Francesco Chicchiriccò created SYNCOPE-275:
--
Summary: Upgrade Spring to 3.2
Key: SYNCOPE-275
URL: https://issues.apache.org/jira/browse/SYNCOPE-275
Project: Syncope
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SYNCOPE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-275:
---
Issue Type: Task (was: Bug)
> Upgrade Spring to 3.2
> -
On 16/01/2013 13:31, Jan Bernhardt wrote:
Hi Francesco,
I cannot access this restricted page [1] any longer! Can you please update the
permissions for this site.
Done; I don't know what happened, but Andrei's and your settings were
been wiped out.
Unfortunately I don't have enough karma to
Hi Francesco,
I cannot access this restricted page [1] any longer! Can you please update the
permissions for this site.
Regards.
Jan
> -Original Message-
> From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
> Sent: Dienstag, 15. Januar 2013 09:32
> To: dev@syncope.apache.org
> S
On 16/01/2013 13:03, Fabio Martelli wrote:
Il giorno 16/gen/2013, alle ore 11.57, Andrei Shakirin ha scritto:
Hi,
I have two questions regarding tasks in context of SYNCOPE-268:
1) Is there easy way to create Notification and Propagation tasks?
Tests issueSyncope81() and deal() delete
Il giorno 16/gen/2013, alle ore 11.57, Andrei Shakirin ha scritto:
> Hi,
>
> I have two questions regarding tasks in context of SYNCOPE-268:
>
>
> 1) Is there easy way to create Notification and Propagation tasks?
>
> Tests issueSyncope81() and deal() delete preconfigured Propagation tas
[
https://issues.apache.org/jira/browse/SYNCOPE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Bernhardt resolved SYNCOPE-259.
---
Resolution: Fixed
> Create transitional Service interfaces and switch tests and console
Hi,
I have two questions regarding tasks in context of SYNCOPE-268:
1) Is there easy way to create Notification and Propagation tasks?
Tests issueSyncope81() and deal() delete preconfigured Propagation task (id=1)
and Notification task (id=8).
To make tests re-runnable I need to recreate
[
https://issues.apache.org/jira/browse/SYNCOPE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13554934#comment-13554934
]
Hudson commented on SYNCOPE-259:
Integrated in Syncope-trunk #438 (See
[https://builds.a
Il giorno 16/gen/2013, alle ore 09.59, Francesco Chicchiriccò ha scritto:
> On 15/01/2013 15:58, Christian Schneider wrote:
>> Hi all,
>>
>> I am currently working on
>> https://issues.apache.org/jira/browse/SYNCOPE-241 .
>>
>> I succeeded in moving the production classes for the persistence la
Hi,
>From my perspective, we can stop activities related to SYNCOPE-241 with option
>(1) for now. I find refactoring already made by Christian very useful and
>important.
In perspective, let see if we will have some real requirements resulting to
split core module, for example:
- alternative p
[
https://issues.apache.org/jira/browse/SYNCOPE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13554857#comment-13554857
]
Hudson commented on SYNCOPE-172:
Integrated in Syncope-trunk #437 (See
[https://builds.a
[
https://issues.apache.org/jira/browse/SYNCOPE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13554856#comment-13554856
]
Hudson commented on SYNCOPE-259:
Integrated in Syncope-trunk #437 (See
[https://builds.a
On 15/01/2013 15:58, Christian Schneider wrote:
Hi all,
I am currently working on
https://issues.apache.org/jira/browse/SYNCOPE-241 .
I succeeded in moving the production classes for the persistence layer to a
separate module. One interesting last problem I solved there was that spring
did no
On 16/01/2013 09:25, Jan Bernhardt 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 ms5 or sha1
evaluation.
The best Microsoft native tool I found is "File Checksum Integrity Verifier"
utility [
> -Original Message-
> From: Denis Signoretto [mailto:denis.signore...@intesys.it]
> Sent: Dienstag, 15. Januar 2013 19:16
> To: dev@syncope.apache.org
> Subject: R: Change console admin password and related documentation
>
>
>
> > -Messaggio originale-
> > Da: Francesco Chicchir
42 matches
Mail list logo
