Re: [DISCUSS] Remove Jenkins integration with JIRA
FYI: https://issues.apache.org/jira/browse/INFRA-7006 On 14/11/2013 11:10, Colm O hEigeartaigh wrote: Sure, makes sense to me. Colm. On Thu, Nov 14, 2013 at 9:08 AM, Francesco Chicchiriccò wrote: Hi all, recently we've got back the feature of generating JIRA comments from SVN commits, disabled a while ago as you might remember because of some malfunctioning of that plugin. At that time we requested to enable the Jenkins integration with JIRA in order to have some automatic mechanism to bind commits (mentioned by Jenkins builds) to JIRA issues. Nowadays this is no more necessary; moreover, Jenkins often fails for various reasons - most times it is just some network issue while deploying artifacts to Nexus - but we end up with some ugly FAILURE comments on our JIRA issues. Hence my proposal: request INFRA to disable the Jenkins2JIRA integration and manually handle Jenkins failures - as we are doing currently. I remember that, driven by our github mirror, we also have Travis [1] taking care of CI. WDYT? [1] https://travis-ci.org/apache/syncope -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
[jira] [Created] (SYNCOPE-440) Timestamp based synchronization miss events
Timo created SYNCOPE-440: Summary: Timestamp based synchronization miss events Key: SYNCOPE-440 URL: https://issues.apache.org/jira/browse/SYNCOPE-440 Project: Syncope Issue Type: Bug Affects Versions: 1.1.3 Reporter: Timo Priority: Critical Fix For: 1.1.5, 1.2.0 The order and logic of sync and getLastSyncToken operations should be fixed Discussed: http://mail-archives.apache.org/mod_mbox/syncope-user/201311.mbox/%3C52850FC0.2080802%40gmail.com%3E -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-439) Embed Activiti modeler for graphical workflow editing
[ https://issues.apache.org/jira/browse/SYNCOPE-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823260#comment-13823260 ] Hudson commented on SYNCOPE-439: SUCCESS: Integrated in Syncope-trunk #502 (See [https://builds.apache.org/job/Syncope-trunk/502/]) Preparations for SYNCOPE-439: now Activiti workflow definition can be read and set either as XML and JSON (ilgrosso: rev 1541959) * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/ConfigurationService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/WorkflowService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/WorkflowDefinitionTO.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/AttributableType.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/AuditElements.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/RESTHeaders.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/ResourceOperation.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/SyncopeSession.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/HttpResourceStream.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/Configuration.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/WorkflowRestClient.java * /syncope/trunk/core/pom.xml * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/WorkflowController.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/utils/RestServiceExceptionMapper.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/ConfigurationServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/ConnectorServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/NotificationServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/ReportServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/ResourceServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/RoleServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/SchemaServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/TaskServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/UserSelfServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/UserServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/WorkflowServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/WorkflowAdapter.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/WorkflowDefinitionFormat.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/role/NoOpRoleWorkflowAdapter.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/user/NoOpUserWorkflowAdapter.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/user/activiti/ActivitiImportUtils.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/user/activiti/ActivitiUserWorkflowAdapter.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/user/activiti/ActivitiWorkflowLoader.java * /syncope/trunk/core/src/main/resources/userWorkflow.bpmn20.xml * /syncope/trunk/core/src/main/resources/workflowContext.xml * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/AbstractTest.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/ConfigurationTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/ReportTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/WorkflowTestITCase.java * /syncope/trunk/core/src/test/resources/content.xml * /syncope/trunk/pom.xml > Embed Activiti modeler for graphical workflow editing > - > > Key: SYNCOPE-439 > URL: https://issues.apache.org/jira/browse/SYNCOPE-439 > Project: Syncope > Issue Type: Improvement >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Labels: activiti, editor, workflow > Fix For: 1.2.0 > > > Activiti, the default user workflow engine, is shipping in its latest > versions the open source version of the KIS BPM process solution. > Basically, a web editor that can be used to author BPMN 2.0 compliant > processes graphically. More information at: > http://www.activiti.org/components.html > The idea is to embed such component in the admin console, next to the current > XML-based editor. -- This message was sent by Atlassian JIRA (v6.1#6144
Syncope-trunk - Build # 502 - Fixed
The Apache Jenkins build system has built Syncope-trunk (build #502) Status: Fixed Check console output at https://builds.apache.org/job/Syncope-trunk/502/ to view the results.
[jira] [Commented] (SYNCOPE-439) Embed Activiti modeler for graphical workflow editing
[ https://issues.apache.org/jira/browse/SYNCOPE-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13822569#comment-13822569 ] ASF subversion and git services commented on SYNCOPE-439: - Commit 1541959 from [~ilgrosso] in branch 'syncope/trunk' [ https://svn.apache.org/r1541959 ] Preparations for SYNCOPE-439: now Activiti workflow definition can be read and set either as XML and JSON > Embed Activiti modeler for graphical workflow editing > - > > Key: SYNCOPE-439 > URL: https://issues.apache.org/jira/browse/SYNCOPE-439 > Project: Syncope > Issue Type: Improvement >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Labels: activiti, editor, workflow > Fix For: 1.2.0 > > > Activiti, the default user workflow engine, is shipping in its latest > versions the open source version of the KIS BPM process solution. > Basically, a web editor that can be used to author BPMN 2.0 compliant > processes graphically. More information at: > http://www.activiti.org/components.html > The idea is to embed such component in the admin console, next to the current > XML-based editor. -- This message was sent by Atlassian JIRA (v6.1#6144)
Re: R: Java Client API for Apache Syncope and Apache Syncope 1.1.x
On 14/11/2013 14:27, Denis Signoretto wrote: Hi Francesco, we are currently working on 1.1.X. I guess the project we are working on will end up in a two or three of months. Do you know (or can give us a forecast) about 1.2.0 release date? Uh, hard guess: IMO we are not even at 50% of 1.2.0 features. Anyway, as reported in the roadmap, I would say that it should see the light in Q1 2013. Naturally, there is always chance to speed up by providing some help ;-) Regards. -Messaggio originale- Da: Francesco Chicchiriccò [mailto:ilgro...@apache.org] Inviato: mercoledì 13 novembre 2013 09.50 A: dev@syncope.apache.org Oggetto: Re: Java Client API for Apache Syncope and Apache Syncope 1.1.x On 12/11/2013 16:16, Denis Signoretto wrote: Hi, I've just read the Francesco blog post about "Java REST client library for Apache Syncope 1.2.0" [1]. I think it's a great feature that can simplify integration of external Java applications with Syncope core. Thanks Denis :-) As can I understand, it's a new Java API Client Library that rely on Java REST API refactor [2] already introduced in 1.1.X version. I'm wondering if it can be used with Apache Syncope 1.1.X or only with Apache Syncope releases >= 1.2.0. Hum, this is a bit more complicated. In Syncope 1.1.X, both Spring MVC and CXF are available, hence there are two different ways to construct client code (see this project of mine [3] to get an idea) that will interact with two different RESTful interfaces. One can think to backport SyncopeClient from 1.2.X and only provide support for CXF services; unfortunately there are some unfinished aspects with CXF in 1.1.X that were completed in 1.2.X (SYNCOPE-285 and related, for example) that would result in a somehow limited SyncopeClient capabilities. Again, at least part of such "incompleteness" can be backported as well but the whole task can become quite large. Personally, I have not enough spare cycles to dedicate to this, but I am available to help anyone else willing to step in. Regards. [1] http://blog.tirasa.net/blogs/index.php/ilgrosso/java-rest-client-libra ry-for [2] https://issues.apache.org/jira/browse/SYNCOPE-231 [3] https://github.com/ilgrosso/syncopeRestClient/tree/SYNCOPE-1_1_X -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
[jira] [Assigned] (SYNCOPE-439) Embed Activiti modeler for graphical workflow editing
[ https://issues.apache.org/jira/browse/SYNCOPE-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò reassigned SYNCOPE-439: -- Assignee: Francesco Chicchiriccò > Embed Activiti modeler for graphical workflow editing > - > > Key: SYNCOPE-439 > URL: https://issues.apache.org/jira/browse/SYNCOPE-439 > Project: Syncope > Issue Type: Improvement >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Labels: activiti, editor, workflow > Fix For: 1.2.0 > > > Activiti, the default user workflow engine, is shipping in its latest > versions the open source version of the KIS BPM process solution. > Basically, a web editor that can be used to author BPMN 2.0 compliant > processes graphically. More information at: > http://www.activiti.org/components.html > The idea is to embed such component in the admin console, next to the current > XML-based editor. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (SYNCOPE-439) Embed Activiti modeler for graphical workflow editing
Francesco Chicchiriccò created SYNCOPE-439: -- Summary: Embed Activiti modeler for graphical workflow editing Key: SYNCOPE-439 URL: https://issues.apache.org/jira/browse/SYNCOPE-439 Project: Syncope Issue Type: Improvement Reporter: Francesco Chicchiriccò Fix For: 1.2.0 Activiti, the default user workflow engine, is shipping in its latest versions the open source version of the KIS BPM process solution. Basically, a web editor that can be used to author BPMN 2.0 compliant processes graphically. More information at: http://www.activiti.org/components.html The idea is to embed such component in the admin console, next to the current XML-based editor. -- This message was sent by Atlassian JIRA (v6.1#6144)
R: Java Client API for Apache Syncope and Apache Syncope 1.1.x
Hi Francesco, we are currently working on 1.1.X. I guess the project we are working on will end up in a two or three of months. Do you know (or can give us a forecast) about 1.2.0 release date? Many thanks, Denis. -Messaggio originale- Da: Francesco Chicchiriccò [mailto:ilgro...@apache.org] Inviato: mercoledì 13 novembre 2013 09.50 A: dev@syncope.apache.org Oggetto: Re: Java Client API for Apache Syncope and Apache Syncope 1.1.x On 12/11/2013 16:16, Denis Signoretto wrote: > Hi, > > I've just read the Francesco blog post about "Java REST client library for > Apache Syncope 1.2.0" [1]. > I think it's a great feature that can simplify integration of external Java > applications with Syncope core. Thanks Denis :-) > As can I understand, it's a new Java API Client Library that rely on Java > REST API refactor [2] already introduced in 1.1.X version. > > I'm wondering if it can be used with Apache Syncope 1.1.X or only with Apache > Syncope releases >= 1.2.0. Hum, this is a bit more complicated. In Syncope 1.1.X, both Spring MVC and CXF are available, hence there are two different ways to construct client code (see this project of mine [3] to get an idea) that will interact with two different RESTful interfaces. One can think to backport SyncopeClient from 1.2.X and only provide support for CXF services; unfortunately there are some unfinished aspects with CXF in 1.1.X that were completed in 1.2.X (SYNCOPE-285 and related, for example) that would result in a somehow limited SyncopeClient capabilities. Again, at least part of such "incompleteness" can be backported as well but the whole task can become quite large. Personally, I have not enough spare cycles to dedicate to this, but I am available to help anyone else willing to step in. Regards. > [1] > http://blog.tirasa.net/blogs/index.php/ilgrosso/java-rest-client-libra > ry-for [2] https://issues.apache.org/jira/browse/SYNCOPE-231 [3] https://github.com/ilgrosso/syncopeRestClient/tree/SYNCOPE-1_1_X -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
Re: [DISCUSS] Remove Jenkins integration with JIRA
Sure, makes sense to me. Colm. On Thu, Nov 14, 2013 at 9:08 AM, Francesco Chicchiriccò wrote: > Hi all, > recently we've got back the feature of generating JIRA comments from SVN > commits, disabled a while ago as you might remember because of some > malfunctioning of that plugin. > > At that time we requested to enable the Jenkins integration with JIRA in > order to have some automatic mechanism to bind commits (mentioned by > Jenkins builds) to JIRA issues. > Nowadays this is no more necessary; moreover, Jenkins often fails for > various reasons - most times it is just some network issue while deploying > artifacts to Nexus - but we end up with some ugly FAILURE comments on our > JIRA issues. > > Hence my proposal: request INFRA to disable the Jenkins2JIRA integration > and manually handle Jenkins failures - as we are doing currently. I > remember that, driven by our github mirror, we also have Travis [1] taking > care of CI. > > WDYT? > > [1] https://travis-ci.org/apache/syncope > > -- > Francesco Chicchiriccò > > Tirasa - Open Source Excellence > http://www.tirasa.net/ > > ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member > http://people.apache.org/~ilgrosso/ > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
[jira] [Issue Comment Deleted] (SYNCOPE-437) Wrong ID generation for new Notification instances
[ https://issues.apache.org/jira/browse/SYNCOPE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-437: --- Comment: was deleted (was: FAILURE: Integrated in Syncope-trunk #501 (See [https://builds.apache.org/job/Syncope-trunk/501/]) [SYNCOPE-437] Reworked the patch a bit for trunk, then applied, thanks (ilgrosso: rev 1541487) * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/beans/Notification.java * /syncope/trunk/core/src/main/resources/META-INF/orm.xml * /syncope/trunk/core/src/main/resources/META-INF/orm.xml.oracle * /syncope/trunk/core/src/main/resources/META-INF/orm.xml.sqlserver * /syncope/trunk/core/src/test/java/org/apache/syncope/core/persistence/dao/NotificationTest.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/NotificationTestITCase.java * /syncope/trunk/core/src/test/resources/content.xml ) > Wrong ID generation for new Notification instances > -- > > Key: SYNCOPE-437 > URL: https://issues.apache.org/jira/browse/SYNCOPE-437 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.1.4 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.1.5, 1.2.0 > > Attachments: SYNCOPE-437.patch > > > When creating a new instance of Notification, IDs of created instances start > from 1 and not from 100 as expected; this is due to the AUTO generation of > IDs for Notification entity. > This may lead to possible primary key violation errors; in particular if > importing from content.xml notification instances as happens in "dev" > profile. -- This message was sent by Atlassian JIRA (v6.1#6144)
[DISCUSS] Remove Jenkins integration with JIRA
Hi all, recently we've got back the feature of generating JIRA comments from SVN commits, disabled a while ago as you might remember because of some malfunctioning of that plugin. At that time we requested to enable the Jenkins integration with JIRA in order to have some automatic mechanism to bind commits (mentioned by Jenkins builds) to JIRA issues. Nowadays this is no more necessary; moreover, Jenkins often fails for various reasons - most times it is just some network issue while deploying artifacts to Nexus - but we end up with some ugly FAILURE comments on our JIRA issues. Hence my proposal: request INFRA to disable the Jenkins2JIRA integration and manually handle Jenkins failures - as we are doing currently. I remember that, driven by our github mirror, we also have Travis [1] taking care of CI. WDYT? [1] https://travis-ci.org/apache/syncope -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
