[DISCUSS] Drop Java 6 support in trunk
Hi all, this morning I was about to upgrade some dependencies in the trunk (mainly due to the fresh release of CXF 3.0.0): while many of them were upgraded. I had to give up with Commons DBCP since their latest stable release 2.0 requires Java 7 [1]. Now, since support for Java 6 was dropped a long while ago [1], and since I can see many other ASF projects setting Java 7 as their minimum requirement (besides Commons DBCP 2.0, also Tomcat = 8.0, Wicket 7, CXF is discussing about this step [3]), I would like to propose to switch to Java 7 as minimum requirement for the trunk. WDYT? Regards. [1] http://commons.apache.org/proper/commons-dbcp/ [2] https://blogs.oracle.com/java/entry/end_of_public_updates_for [3] http://cxf.547215.n5.nabble.com/DISCUSS-Short-term-plans-branching-td5744177.html -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Involved at The Apache Software Foundation: member, Syncope PMC chair, Cocoon PMC, Olingo PMC http://people.apache.org/~ilgrosso/
Re: [DISCUSS] Drop Java 6 support in trunk
On 05/20/2014 09:03 AM, Francesco Chicchiriccò wrote: Hi all, this morning I was about to upgrade some dependencies in the trunk (mainly due to the fresh release of CXF 3.0.0): while many of them were upgraded. I had to give up with Commons DBCP since their latest stable release 2.0 requires Java 7 [1]. Now, since support for Java 6 was dropped a long while ago [1], and since I can see many other ASF projects setting Java 7 as their minimum requirement (besides Commons DBCP 2.0, also Tomcat = 8.0, Wicket 7, CXF is discussing about this step [3]), I would like to propose to switch to Java 7 as minimum requirement for the trunk. WDYT? +1 Regards. [1] http://commons.apache.org/proper/commons-dbcp/ [2] https://blogs.oracle.com/java/entry/end_of_public_updates_for [3] http://cxf.547215.n5.nabble.com/DISCUSS-Short-term-plans-branching-td5744177.html -- 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)
Failed: apache/syncope#540 (trunk - 0eac50d)
Build Update for apache/syncope - Build: #540 Status: Failed Duration: 9 minutes and 7 seconds Commit: 0eac50d (trunk) Author: Francesco Chicchiriccò Message: Various dependency upgrades, including CXF 3.0.0 git-svn-id: https://svn.apache.org/repos/asf/syncope/trunk@1596120 13f79535-47bb-0310-9956-ffa450edef68 View the changeset: https://github.com/apache/syncope/compare/0a014dfce773...0eac50d83df7 View the full build log and details: https://travis-ci.org/apache/syncope/builds/25578565 -- You can configure recipients for build notifications in your .travis.yml file. See http://docs.travis-ci.com/user/notifications
Re: [DISCUSS] Drop Java 6 support in trunk
Il 20/05/2014 09:03, Francesco Chicchiriccò ha scritto: Hi all, this morning I was about to upgrade some dependencies in the trunk (mainly due to the fresh release of CXF 3.0.0): while many of them were upgraded. I had to give up with Commons DBCP since their latest stable release 2.0 requires Java 7 [1]. Now, since support for Java 6 was dropped a long while ago [1], and since I can see many other ASF projects setting Java 7 as their minimum requirement (besides Commons DBCP 2.0, also Tomcat = 8.0, Wicket 7, CXF is discussing about this step [3]), I would like to propose to switch to Java 7 as minimum requirement for the trunk. WDYT? I completely agree that it's time, +1 (non binding). Regards. [1] http://commons.apache.org/proper/commons-dbcp/ [2] https://blogs.oracle.com/java/entry/end_of_public_updates_for [3] http://cxf.547215.n5.nabble.com/DISCUSS-Short-term-plans-branching-td5744177.html Best regards, Andrea -- Dott. Andrea Patricelli Tel +393204524292 Junior Engineer @ Tirasa S.r.l. Viale D'Annunzio 267 - 65127 Pescara Tel +390859116307 / FAX +39 085973 http://www.tirasa.net
Re: [DISCUSS] Drop Java 6 support in trunk
Il giorno 20/mag/2014, alle ore 09:03, Francesco Chicchiriccò ilgro...@apache.org ha scritto: Hi all, this morning I was about to upgrade some dependencies in the trunk (mainly due to the fresh release of CXF 3.0.0): while many of them were upgraded. I had to give up with Commons DBCP since their latest stable release 2.0 requires Java 7 [1]. Now, since support for Java 6 was dropped a long while ago [1], and since I can see many other ASF projects setting Java 7 as their minimum requirement (besides Commons DBCP 2.0, also Tomcat = 8.0, Wicket 7, CXF is discussing about this step [3]), I would like to propose to switch to Java 7 as minimum requirement for the trunk. WDYT? +1 Marco Regards. [1] http://commons.apache.org/proper/commons-dbcp/ [2] https://blogs.oracle.com/java/entry/end_of_public_updates_for [3] http://cxf.547215.n5.nabble.com/DISCUSS-Short-term-plans-branching-td5744177.html -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Involved at The Apache Software Foundation: member, Syncope PMC chair, Cocoon PMC, Olingo PMC 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/
Fixed: apache/syncope#541 (trunk - e961029)
Build Update for apache/syncope - Build: #541 Status: Fixed Duration: 14 minutes and 23 seconds Commit: e961029 (trunk) Author: Francesco Chicchiriccò Message: Partially reverting bad commit: CXF's Spring XSD is not yet updated git-svn-id: https://svn.apache.org/repos/asf/syncope/trunk@1596124 13f79535-47bb-0310-9956-ffa450edef68 View the changeset: https://github.com/apache/syncope/compare/0eac50d83df7...e9610291a311 View the full build log and details: https://travis-ci.org/apache/syncope/builds/25579498 -- You can configure recipients for build notifications in your .travis.yml file. See http://docs.travis-ci.com/user/notifications
Re: [DISCUSS] Drop Java 6 support in trunk
Hi Francesco On 20/05/14 08:03, Francesco Chicchiriccò wrote: Hi all, this morning I was about to upgrade some dependencies in the trunk (mainly due to the fresh release of CXF 3.0.0): while many of them were upgraded. I had to give up with Commons DBCP since their latest stable release 2.0 requires Java 7 [1]. Now, since support for Java 6 was dropped a long while ago [1], and since I can see many other ASF projects setting Java 7 as their minimum requirement (besides Commons DBCP 2.0, also Tomcat = 8.0, Wicket 7, CXF is discussing about this step [3]), I would like to propose to switch to Java 7 as minimum requirement for the trunk. The only comment about CXF 3.0.0, Dan is planning to branch it out for Java 6 customers be able to switch to 3.0.0 from 2.7.x, CXF 3.1.0-SNAPSHOT will be indeed Java 7 based. It is probably not going to affect Syncope, but mentioning it just in case Cheers, Sergey WDYT? Regards. [1] http://commons.apache.org/proper/commons-dbcp/ [2] https://blogs.oracle.com/java/entry/end_of_public_updates_for [3] http://cxf.547215.n5.nabble.com/DISCUSS-Short-term-plans-branching-td5744177.html
[jira] [Commented] (SYNCOPE-447) Create a single task for all events into a given notification
[ https://issues.apache.org/jira/browse/SYNCOPE-447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14003015#comment-14003015 ] ASF subversion and git services commented on SYNCOPE-447: - Commit 1596167 from [~andrea.patricelli] in branch 'syncope/trunk' [ https://svn.apache.org/r1596167 ] [SYNCOPE-447] improved information sent to NotificationManager in AbstractTaskJob to create task (cumulative) notification, improved optin template to reflect task execution if present Create a single task for all events into a given notification - Key: SYNCOPE-447 URL: https://issues.apache.org/jira/browse/SYNCOPE-447 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.2.0 Reporter: fabio martelli Assignee: Andrea Patricelli Fix For: 1.2.0 Cumulative notification: create a single task for all events into a given notification. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SYNCOPE-447) Provide the ability to have a single (cumulative) notification for task execution
[ https://issues.apache.org/jira/browse/SYNCOPE-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-447: -- Description: A simple use case is user synchronization; a) if we want to have a notification task for each user creation/update coming from sync task we can configure notification task to generate notification on this event [SyncTask]:[user]:[resourceName]:[create]:[SUCCESS]. b) But if we do not want to have too many notifications, like point 1, we can configure notification to create a notification task only when synchronization job finishes, setting notification event to [TASK]:[SyncJob]:[]:[SyncJob]:[SUCCESS] instead of [SyncTask]:[user]:[resourceName]:[create]:[SUCCESS]. In case of a large number of users to synchronize b is preferable, and cumulative notification is sent. Improve notification messages to show a better and more complete notification message generated from jobs like SyncJob or PushJob and also provide new mail and text templates useful for use case exposed above. was:Cumulative notification: create a single task for all events into a given notification. Summary: Provide the ability to have a single (cumulative) notification for task execution (was: Create a single task for all events into a given notification) Provide the ability to have a single (cumulative) notification for task execution - Key: SYNCOPE-447 URL: https://issues.apache.org/jira/browse/SYNCOPE-447 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.2.0 Reporter: fabio martelli Assignee: Andrea Patricelli Fix For: 1.2.0 A simple use case is user synchronization; a) if we want to have a notification task for each user creation/update coming from sync task we can configure notification task to generate notification on this event [SyncTask]:[user]:[resourceName]:[create]:[SUCCESS]. b) But if we do not want to have too many notifications, like point 1, we can configure notification to create a notification task only when synchronization job finishes, setting notification event to [TASK]:[SyncJob]:[]:[SyncJob]:[SUCCESS] instead of [SyncTask]:[user]:[resourceName]:[create]:[SUCCESS]. In case of a large number of users to synchronize b is preferable, and cumulative notification is sent. Improve notification messages to show a better and more complete notification message generated from jobs like SyncJob or PushJob and also provide new mail and text templates useful for use case exposed above. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Issue Comment Deleted] (SYNCOPE-447) Provide the ability to have a single (cumulative) notification for task execution
[ https://issues.apache.org/jira/browse/SYNCOPE-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-447: -- Comment: was deleted (was: Mechanism of creating cumulative notifications is already available by a proper configuration of notification. A simple use case is user synchronization; a) if we want to have a notification task for each user creation/update coming from sync task we can configure notification task to generate notification on this event [SyncTask]:[user]:[resourceName]:[create]:[SUCCESS]. b) But if we do not want to have too many notifications, like point 1, we can configure notification to create a notification task only when synchronization job finishes, setting notification event to [TASK]:[SyncJob]:[]:[SyncJob]:[SUCCESS] instead of [SyncTask]:[user]:[resourceName]:[create]:[SUCCESS]. In case of a large number of users to synchronize b is preferable, and cumulative notification is sent. We can instead improve notification messages to show a better and more complete notification message generated from jobs like SyncJob or PushJob and also provide new mail and text templates useful for use case exposed above. ) Provide the ability to have a single (cumulative) notification for task execution - Key: SYNCOPE-447 URL: https://issues.apache.org/jira/browse/SYNCOPE-447 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.2.0 Reporter: fabio martelli Assignee: Andrea Patricelli Fix For: 1.2.0 A simple use case is user synchronization; a) if we want to have a notification task for each user creation/update coming from sync task we can configure notification task to generate notification on this event [SyncTask]:[user]:[resourceName]:[create]:[SUCCESS]. b) But if we do not want to have too many notifications, like point 1, we can configure notification to create a notification task only when synchronization job finishes, setting notification event to [TASK]:[SyncJob]:[]:[SyncJob]:[SUCCESS] instead of [SyncTask]:[user]:[resourceName]:[create]:[SUCCESS]. In case of a large number of users to synchronize b is preferable, and cumulative notification is sent. Improve notification messages to show a better and more complete notification message generated from jobs like SyncJob or PushJob and also provide new mail and text templates useful for use case exposed above. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SYNCOPE-447) Provide the ability to have a single (cumulative) notification for task execution
[ https://issues.apache.org/jira/browse/SYNCOPE-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli resolved SYNCOPE-447. --- Resolution: Fixed Provide the ability to have a single (cumulative) notification for task execution - Key: SYNCOPE-447 URL: https://issues.apache.org/jira/browse/SYNCOPE-447 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.2.0 Reporter: fabio martelli Assignee: Andrea Patricelli Fix For: 1.2.0 A simple use case is user synchronization; a) if we want to have a notification task for each user creation/update coming from sync task we can configure notification task to generate notification on this event [SyncTask]:[user]:[resourceName]:[create]:[SUCCESS]. b) But if we do not want to have too many notifications, like point 1, we can configure notification to create a notification task only when synchronization job finishes, setting notification event to [TASK]:[SyncJob]:[]:[SyncJob]:[SUCCESS] instead of [SyncTask]:[user]:[resourceName]:[create]:[SUCCESS]. In case of a large number of users to synchronize b is preferable, and cumulative notification is sent. Improve notification messages to show a better and more complete notification message generated from jobs like SyncJob or PushJob and also provide new mail and text templates useful for use case exposed above. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SYNCOPE-492) Provide possibility to activate/deactivate notifications
Andrea Patricelli created SYNCOPE-492: - Summary: Provide possibility to activate/deactivate notifications Key: SYNCOPE-492 URL: https://issues.apache.org/jira/browse/SYNCOPE-492 Project: Syncope Issue Type: Improvement Components: console, core Affects Versions: 1.2.0 Reporter: Andrea Patricelli Assignee: Andrea Patricelli Fix For: 1.2.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SYNCOPE-492) Provide possibility to activate/deactivate notifications
[ https://issues.apache.org/jira/browse/SYNCOPE-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli resolved SYNCOPE-492. --- Resolution: Fixed Provide possibility to activate/deactivate notifications Key: SYNCOPE-492 URL: https://issues.apache.org/jira/browse/SYNCOPE-492 Project: Syncope Issue Type: Improvement Components: console, core Affects Versions: 1.2.0 Reporter: Andrea Patricelli Assignee: Andrea Patricelli Fix For: 1.2.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-492) Provide possibility to activate/deactivate notifications
[ https://issues.apache.org/jira/browse/SYNCOPE-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14003366#comment-14003366 ] ASF subversion and git services commented on SYNCOPE-492: - Commit 1596264 from [~andrea.patricelli] in branch 'syncope/trunk' [ https://svn.apache.org/r1596264 ] [SYNCOPE-492] provided notification object with field to enable/disable it, updated tests and console accordingly Provide possibility to activate/deactivate notifications Key: SYNCOPE-492 URL: https://issues.apache.org/jira/browse/SYNCOPE-492 Project: Syncope Issue Type: Improvement Components: console, core Affects Versions: 1.2.0 Reporter: Andrea Patricelli Assignee: Andrea Patricelli Fix For: 1.2.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SYNCOPE-493) Provide new user and role mapping purpose NONE
Andrea Patricelli created SYNCOPE-493: - Summary: Provide new user and role mapping purpose NONE Key: SYNCOPE-493 URL: https://issues.apache.org/jira/browse/SYNCOPE-493 Project: Syncope Issue Type: Improvement Components: console, core Affects Versions: 1.1.8, 1.2.0 Reporter: Andrea Patricelli Assignee: Andrea Patricelli Fix For: 1.1.8, 1.2.0 Provide new mapping purpose called NONE to ignore the mapping with such purpose; this avoids deletion of (temporarily) unuseful or not required user/role mappings. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SYNCOPE-493) Provide new user and role mapping purpose NONE
[ https://issues.apache.org/jira/browse/SYNCOPE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-493: -- Component/s: (was: core) common Provide new user and role mapping purpose NONE Key: SYNCOPE-493 URL: https://issues.apache.org/jira/browse/SYNCOPE-493 Project: Syncope Issue Type: Improvement Components: common, console Affects Versions: 1.1.8, 1.2.0 Reporter: Andrea Patricelli Assignee: Andrea Patricelli Fix For: 1.1.8, 1.2.0 Provide new mapping purpose called NONE to ignore the mapping with such purpose; this avoids deletion of (temporarily) unuseful or not required user/role mappings. -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: [DISCUSS] Drop Java 6 support in trunk
I would prefer to keep Java 6 compatibility with Syncope 1.2 and then drop it for Syncope 1.3. Given that this aligns with the probably versions of CXF in both releases, it seems to make sense. Or are there any really pressing reasons to drop compability for Syncope 1.2? Colm. On Tue, May 20, 2014 at 9:42 AM, Sergey Beryozkin sberyoz...@gmail.comwrote: Hi Francesco On 20/05/14 08:03, Francesco Chicchiriccň wrote: Hi all, this morning I was about to upgrade some dependencies in the trunk (mainly due to the fresh release of CXF 3.0.0): while many of them were upgraded. I had to give up with Commons DBCP since their latest stable release 2.0 requires Java 7 [1]. Now, since support for Java 6 was dropped a long while ago [1], and since I can see many other ASF projects setting Java 7 as their minimum requirement (besides Commons DBCP 2.0, also Tomcat = 8.0, Wicket 7, CXF is discussing about this step [3]), I would like to propose to switch to Java 7 as minimum requirement for the trunk. The only comment about CXF 3.0.0, Dan is planning to branch it out for Java 6 customers be able to switch to 3.0.0 from 2.7.x, CXF 3.1.0-SNAPSHOT will be indeed Java 7 based. It is probably not going to affect Syncope, but mentioning it just in case Cheers, Sergey WDYT? Regards. [1] http://commons.apache.org/proper/commons-dbcp/ [2] https://blogs.oracle.com/java/entry/end_of_public_updates_for [3] http://cxf.547215.n5.nabble.com/DISCUSS-Short-term-plans- branching-td5744177.html -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
