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
[
https://issues.apache.org/jira/browse/SYNCOPE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13554934#comment-13554934
]
Hudson commented on SYNCOPE-259:
Integrated in Syncope-trunk #438 (See
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
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
[
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
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
[
https://issues.apache.org/jira/browse/SYNCOPE-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13555020#comment-13555020
]
Hudson commented on SYNCOPE-268:
Integrated in Syncope-trunk #439 (See
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.
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 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
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 with
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 to release
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.
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
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
[
https://issues.apache.org/jira/browse/SYNCOPE-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13555275#comment-13555275
]
Hudson commented on SYNCOPE-271:
Integrated in Syncope-trunk #445 (See
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
17 matches
Mail list logo