[VOTE] Apache Syncope 1.0.8
I've created a 1.0.8 release, with the following artifacts up for a vote: SVN source tag (r1469201): https://svn.apache.org/repos/asf/syncope/tags/syncope-1.0.8/ List of changes: https://svn.apache.org/repos/asf/syncope/tags/syncope-1.0.8/CHANGES Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-116/ Source release (checksums and signatures are available at the same location): https://repository.apache.org/content/repositories/orgapachesyncope-116/org/apache/syncope/syncope-root/1.0.8/syncope-root-1.0.8-source-release.zip Staging site: http://syncope.apache.org/1.0.8/ PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
[DISCUSS] Apache Syncope 1.0.8
Discussion thread for vote on 1.0.8 release, with SVN source tag (r1469201). For more information on the release process, check out http://www.apache.org/dev/release.html Some of the things to check before voting are: - does mvn apache-rat:check pass on the source - can you build the contents of source release zip and SVN tag - do all of the staged jars/wars/zips contain the required LICENSE and NOTICE files - are all of the staged jars/wars/zips signed and the signature verifiable - is the signing key in the project's KEYS file and on a public server (i.e. http://www.apache.org/dist/syncope/) -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
Re: [PROPOSAL] Move full OSGi support to 1.2.0
Gents, any news about this? Regards. On 02/04/2013 14:53, Colm O hEigeartaigh wrote: Sounds good thanks! Colm. On Tue, Apr 2, 2013 at 1:16 PM, Francesco Chicchiriccò ilgro...@apache.orgwrote: On 02/04/2013 13:55, Colm O hEigeartaigh wrote: Hi Francesco, We have not been able to sort out the OSGi issues as of yet. One of the problems seems to be a conflict between the different versions of Spring used by Syncope + CXF, which is resulting in the exceptions reported in SYNCOPE-337. For the moment I propose moving SYNCOPE-337 to 1.1.1. If we can't fix the OSGi issues in a relatively simple way then we can move it to 1.2. I would like to keep the changes made as part of SYNCOPE-203 in place, as it doesn't affect the Tomcat deployment + it would require additional changes on some downstream code that we have. Fine to me: I'll proceed then to: 1. create new branch 1_1_X from trunk + set trunk version to 1.2.0-SNAPSHOT 2. create Jenkins job for 1_1_X 3. create JIRA version 1.1.1 4. move SYNCOPE-337 to 1.1.1 Nothing will be done in respect of SYNCOPE-203. Regards. On Tue, Apr 2, 2013 at 8:00 AM, ilgrosso ilgro...@apache.org wrote: Colm O hEigeartaigh wrote Hi Francesco, I don't see why the merges for SYNCOPE-203 need to be reverted as they are not breaking anything. I would prefer to leave things as they are but not claim full OSGi support in the 1.1.0 release. I guess you are concerned that these issues will hold up the 1.1.0 release and so I propose the following. Give us until the end of the week to find a solution for SYNCOPE-337 (and any related problems). If we have not found a solution by then, then this JIRA can be moved to the next release (1.1.1 if it can be considered a bug based on 1.1.0, otherwise 1.2). Does this work? Hi Colm, is there any progress about this? I think we should be able to at least think starting the 1.1.0 release process this week, hence understanding how to handle the OSGi features is quite important right now. Regards. -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
RE: [VOTE] Apache Syncope 1.0.8
+1 (non-binding) -Original Message- From: Francesco Chicchiriccò [mailto:ilgro...@apache.org] Sent: Donnerstag, 18. April 2013 11:06 To: dev@syncope.apache.org Subject: [VOTE] Apache Syncope 1.0.8 I've created a 1.0.8 release, with the following artifacts up for a vote: SVN source tag (r1469201): https://svn.apache.org/repos/asf/syncope/tags/syncope-1.0.8/ List of changes: https://svn.apache.org/repos/asf/syncope/tags/syncope-1.0.8/CHANGES Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-116/ Source release (checksums and signatures are available at the same location): https://repository.apache.org/content/repositories/orgapachesyncope- 116/org/apache/syncope/syncope-root/1.0.8/syncope-root-1.0.8-source- release.zip Staging site: http://syncope.apache.org/1.0.8/ PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
Re: [VOTE] Apache Syncope 1.0.8
On Apr 18, 2013, at 11:05 AM, Francesco Chicchiriccò wrote: I've created a 1.0.8 release, with the following artifacts up for a vote: SVN source tag (r1469201): https://svn.apache.org/repos/asf/syncope/tags/syncope-1.0.8/ List of changes: https://svn.apache.org/repos/asf/syncope/tags/syncope-1.0.8/CHANGES Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-116/ Source release (checksums and signatures are available at the same location): https://repository.apache.org/content/repositories/orgapachesyncope-116/org/apache/syncope/syncope-root/1.0.8/syncope-root-1.0.8-source-release.zip Staging site: http://syncope.apache.org/1.0.8/ PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) +1 BR Marco -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/ -- 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
Syncope-1_0_X - Build # 189 - Failure
The Apache Jenkins build system has built Syncope-1_0_X (build #189) Status: Failure Check console output at https://builds.apache.org/job/Syncope-1_0_X/189/ to view the results.
Re: [VOTE] Apache Syncope 1.0.8
+1 Il 18/04/2013 11:05, Francesco Chicchiriccò ha scritto: I've created a 1.0.8 release, with the following artifacts up for a vote: SVN source tag (r1469201): https://svn.apache.org/repos/asf/syncope/tags/syncope-1.0.8/ List of changes: https://svn.apache.org/repos/asf/syncope/tags/syncope-1.0.8/CHANGES Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-116/ Source release (checksums and signatures are available at the same location): https://repository.apache.org/content/repositories/orgapachesyncope-116/org/apache/syncope/syncope-root/1.0.8/syncope-root-1.0.8-source-release.zip Staging site: http://syncope.apache.org/1.0.8/ PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Massimiliano Perrone Tel +39 393 9121310 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/~massi/ L'apprendere molte cose non insegna l'intelligenza (Eraclito)
[jira] [Updated] (SYNCOPE-337) ClassNotFoundException in karaf osgi container
[ https://issues.apache.org/jira/browse/SYNCOPE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated SYNCOPE-337: Fix Version/s: (was: 1.1.1) ClassNotFoundException in karaf osgi container -- Key: SYNCOPE-337 URL: https://issues.apache.org/jira/browse/SYNCOPE-337 Project: Syncope Issue Type: Bug Components: console, core Affects Versions: 1.1.0 Environment: apache karaf 2.3.1 Reporter: Roman Minko Attachments: MANIFEST(console).MF, MANIFEST(core).MF Install war feature and try to install syncope core and console wars. Different dependencies issues and finally ClassNotFoundException in logs appeared. Syncope already include all the dependent jars in the lib/ folder of the war. But the MANIFEST files in the syncope-core and syncope-console are not correct enough, Bundle-ClassPath: , Web-ContextPath: should be added into MANIFEST. After manually adding Bundle-ClassPath: and update Import-Package: nothing dependencies bundles needed and no ClassNotFoundException. Pom files of core and console project should be updated to generate correct Bundle-ClassPath and Import-Package in MANIFEST. Or make changes on the MANIFEST directly during the build at least. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [PROPOSAL] Move full OSGi support to 1.2.0
No update at this point afaik. I removed the fix for version that was 1.1.1. If we don't get it done in time for 1.1.2 then I'll move it to 1.2. Colm. On Thu, Apr 18, 2013 at 11:27 AM, Francesco Chicchiriccò ilgro...@apache.org wrote: Gents, any news about this? Regards. On 02/04/2013 14:53, Colm O hEigeartaigh wrote: Sounds good thanks! Colm. On Tue, Apr 2, 2013 at 1:16 PM, Francesco Chicchiriccò ilgro...@apache.orgwrote: On 02/04/2013 13:55, Colm O hEigeartaigh wrote: Hi Francesco, We have not been able to sort out the OSGi issues as of yet. One of the problems seems to be a conflict between the different versions of Spring used by Syncope + CXF, which is resulting in the exceptions reported in SYNCOPE-337. For the moment I propose moving SYNCOPE-337 to 1.1.1. If we can't fix the OSGi issues in a relatively simple way then we can move it to 1.2. I would like to keep the changes made as part of SYNCOPE-203 in place, as it doesn't affect the Tomcat deployment + it would require additional changes on some downstream code that we have. Fine to me: I'll proceed then to: 1. create new branch 1_1_X from trunk + set trunk version to 1.2.0-SNAPSHOT 2. create Jenkins job for 1_1_X 3. create JIRA version 1.1.1 4. move SYNCOPE-337 to 1.1.1 Nothing will be done in respect of SYNCOPE-203. Regards. On Tue, Apr 2, 2013 at 8:00 AM, ilgrosso ilgro...@apache.org wrote: Colm O hEigeartaigh wrote Hi Francesco, I don't see why the merges for SYNCOPE-203 need to be reverted as they are not breaking anything. I would prefer to leave things as they are but not claim full OSGi support in the 1.1.0 release. I guess you are concerned that these issues will hold up the 1.1.0 release and so I propose the following. Give us until the end of the week to find a solution for SYNCOPE-337 (and any related problems). If we have not found a solution by then, then this JIRA can be moved to the next release (1.1.1 if it can be considered a bug based on 1.1.0, otherwise 1.2). Does this work? Hi Colm, is there any progress about this? I think we should be able to at least think starting the 1.1.0 release process this week, hence understanding how to handle the OSGi features is quite important right now. Regards. -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~**ilgrosso/http://people.apache.org/~ilgrosso/ -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
Syncope-1_0_X - Build # 190 - Fixed
The Apache Jenkins build system has built Syncope-1_0_X (build #190) Status: Fixed Check console output at https://builds.apache.org/job/Syncope-1_0_X/190/ to view the results.
[jira] [Created] (SYNCOPE-360) Removing Role mapping from External Resource fails
Martin van Es created SYNCOPE-360: - Summary: Removing Role mapping from External Resource fails Key: SYNCOPE-360 URL: https://issues.apache.org/jira/browse/SYNCOPE-360 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.0 Environment: Linux/Tomcat Reporter: Martin van Es Today I was experimenting with role assignment and tried to map internal ROLE/RoleId to a column in my synchronisation CSVdir resource. While syncing I got an error of Objectclasses not matching so I wanted to remove this relationship by clicking the checkbox in from of it, which succeeded. But after saving the new settings and inspecting the resource role mapping, the old role relation was still there, effectively leaving me with a broken resource. I had to manually remove the role map using my database gui to be able to use the resource again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
