Syncope-master - Build # 1605 - Fixed

[Apache Jenkins Server]

The Apache Jenkins build system has built Syncope-master (build #1605)

Status: Fixed

Check console output at https://builds.apache.org/job/Syncope-master/1605/ to 
view the results.

[jira] [Commented] (SYNCOPE-700) Documentation artifacts

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395955#comment-15395955
 ] 

ASF subversion and git services commented on SYNCOPE-700:
-

Commit 012f97bcabaf257b6a8d93c49408930e2785e6ef in syncope's branch 
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=012f97b ]

[SYNCOPE-700] Introduction completed - at last


> Documentation artifacts
> ---
>
> Key: SYNCOPE-700
> URL: https://issues.apache.org/jira/browse/SYNCOPE-700
> Project: Syncope
>  Issue Type: Improvement
>  Components: documentation
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 2.0.0
>
>
> As [discussed|http://markmail.org/message/dpleneuzrfcsmq2r] in mailing list, 
> setup the {{asciidoctor-maven-plugin}} in order to generate, alongside with 
> the build, the project documentation in HTML and PDF.
> The generated documentation will then be part of release artifacts and always 
> up-to-date with current release.
> Preliminary results available at 
> http://syncope.apache.org/2.0.0-SNAPSHOT/docs/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SYNCOPE-909) Consolidate Camel Processors

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395840#comment-15395840
 ] 

ASF subversion and git services commented on SYNCOPE-909:
-

Commit 31dc4a2806628ac45d33fd8cdb39b8ebabc237e7 in syncope's branch 
refs/heads/master from [~coheigea]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=31dc4a2 ]

SYNCOPE-909 - Consolidate update functionality


> Consolidate Camel Processors
> 
>
> Key: SYNCOPE-909
> URL: https://issues.apache.org/jira/browse/SYNCOPE-909
> Project: Syncope
>  Issue Type: Improvement
>  Components: extensions
>Affects Versions: 2.0.0-M4
>Reporter: Colm O hEigeartaigh
>Assignee: Colm O hEigeartaigh
> Fix For: 2.0.0
>
>
> This task is to consolidate the Camel Processors. Currently, there is a lot 
> of duplicate functionality spread out for different processors for Users, 
> Groups, Any etc. This task will focus on consolidating on a single 
> implementation per operation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SYNCOPE-909) Consolidate Camel Processors

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395839#comment-15395839
 ] 

ASF subversion and git services commented on SYNCOPE-909:
-

Commit 377ce234bcabd209245e47c706760243c1539db2 in syncope's branch 
refs/heads/master from [~coheigea]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=377ce23 ]

SYNCOPE-909 - Consolidate "Create" functionality


> Consolidate Camel Processors
> 
>
> Key: SYNCOPE-909
> URL: https://issues.apache.org/jira/browse/SYNCOPE-909
> Project: Syncope
>  Issue Type: Improvement
>  Components: extensions
>Affects Versions: 2.0.0-M4
>Reporter: Colm O hEigeartaigh
>Assignee: Colm O hEigeartaigh
> Fix For: 2.0.0
>
>
> This task is to consolidate the Camel Processors. Currently, there is a lot 
> of duplicate functionality spread out for different processors for Users, 
> Groups, Any etc. This task will focus on consolidating on a single 
> implementation per operation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Eclipse Plugin [SYNCOPE-809] as GSoC 16 Project

[Tushar Mishra]

Thanks for addressing that. I'll rebase when I'm about to commit next.
I am working on the auto-format feature right now - XSLT editor already has
this feature (try using Ctrl+Shift+F).
I will create the tests after I build this for the HTML Editor.

On Wed, Jul 27, 2016 at 3:46 PM Francesco Chicchiriccò 
wrote:

> Hi Tushar,
> FYI I have just pushed a commit
>
>
> https://github.com/apache/syncope/commit/1f62e6fb91d0766a85015a99bf1269ad6eadf6f5
>
> addressing some legal aspects of the new artifact (i.e. the Eclipse IDE
> Plugin) that will be downloadable since next stable release.
>
> About further tasks / improvements on SYNCOPE-809, I would enlist:
>
>   1. tests
>   2. auto-format feature for HTML / XSLT editors
>
> Regards.
>
> On 22/07/2016 12:32, Tushar Mishra wrote:
> > Thanks for the merge and the tweet. As I said before, I am working on the
> > tests for this module.
> > If there are any other improvements you have in mind, please do tell me
> so
> > I can work on them during the weekend.
> >
> > Regards,
> >
> > On Fri, Jul 22, 2016 at 3:58 PM Francesco Chicchiriccò <
> ilgro...@apache.org>
> > wrote:
> >
> >> As you might have seen, I have just merge PR #28 - this means we start
> >> having an Eclipse plugin, cool :-)
> >>
> >> Nice job so far: now we need to finalize some stuff to have it properly
> >> ready for wide usage.
> >>
> >> Regards.
> >>
> >> On 20/07/2016 16:46, Tushar Mishra wrote:
> >>> Update:
> >>> Solved issues #4 
> and
> >> #9
> >>>  and opened pull
> >> request
> >>> 
> >>>
> >>> I am making the suggested changes and preparing the next commit.
> >>>
> >>> On Mon, Jul 18, 2016 at 8:55 PM Tushar Mishra 
> >> wrote:
>  I've added an issue <
> https://github.com/tmess567/SYNCOPE-809/issues/21>
>  to track the progress on the p2 repository and I will resume work with
> >> the
>  pom manifest.
>  Also, I will try to start merging this project as a module of my fork
> of
>  syncope  to ensure rat and
>  checkstyle requirements are met.
> 
>  Regards,
> 
>  On Mon, Jul 18, 2016 at 8:33 PM Francesco Chicchiriccò <
>  ilgro...@apache.org> wrote:
> 
> > Please start a separate thread for this.
> > Regards.
> >
> > On 16/07/2016 07:49, Tushar Mishra wrote:
> >> I received an email from GSoC stating that during the final
> > evaluations, I
> >> will need to submit a link to the code written during the project.
> See
> >> https://developers.google.com/open-source/gsoc/help/work-product
> >>
> >> I believe that this should be the commits page
> >>  of my
> >> project
> >> repository . Will this be
> >> OK?
> >> I am also working on updating and maintaining a set of tagged posts
> on
> > my
> >> blog which can be added to the submitted links and might also be
> >> helpful in documentation.
> >>
> >> Regards,
>
> --
> Francesco Chicchiriccò
>
> Tirasa - Open Source Excellence
> http://www.tirasa.net/
>
> Involved at The Apache Software Foundation:
> member, Syncope PMC chair, Cocoon PMC, Olingo PMC,
> CXF Committer, OpenJPA Committer, PonyMail PPMC
> http://home.apache.org/~ilgrosso/
>
> --
Tushar Mishra
Website: tusharmishra.in
University of Petroleum and Energy Studies
Computer Science with specialization in ​Open Source Software and Open
Standards
Semester VII
+91-9675785996

Syncope-master - Build # 1604 - Failure

[Apache Jenkins Server]

The Apache Jenkins build system has built Syncope-master (build #1604)

Status: Failure

Check console output at https://builds.apache.org/job/Syncope-master/1604/ to 
view the results.

[jira] [Commented] (SYNCOPE-809) Eclipse plugin

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395586#comment-15395586
 ] 

ASF subversion and git services commented on SYNCOPE-809:
-

Commit 1b325bb8e8ed2305a69f85adca6478aadaf30cb2 in syncope's branch 
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=1b325bb ]

[SYNCOPE-809] Fixing -Psite build problems


> Eclipse plugin
> --
>
> Key: SYNCOPE-809
> URL: https://issues.apache.org/jira/browse/SYNCOPE-809
> Project: Syncope
>  Issue Type: Sub-task
>  Components: ide
> Environment: Eclipse
>Reporter: Francesco Chicchiriccò
>Assignee: Tushar Mishra
>  Labels: eclipse, gsoc2016
> Fix For: 2.0.0
>
>
> Develop a plug-in, according to what reported in SYNCOPE-770, working with 
> latest Eclipse version.
> See Google Summer of Code project proposal at 
> https://summerofcode.withgoogle.com/projects/#4822214733987840



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SYNCOPE-909) Consolidate Camel Processors

[Colm O hEigeartaigh (JIRA)]

Colm O hEigeartaigh created SYNCOPE-909:
---

 Summary: Consolidate Camel Processors
 Key: SYNCOPE-909
 URL: https://issues.apache.org/jira/browse/SYNCOPE-909
 Project: Syncope
  Issue Type: Improvement
  Components: extensions
Affects Versions: 2.0.0-M4
Reporter: Colm O hEigeartaigh
Assignee: Colm O hEigeartaigh
 Fix For: 2.0.0


This task is to consolidate the Camel Processors. Currently, there is a lot of 
duplicate functionality spread out for different processors for Users, Groups, 
Any etc. This task will focus on consolidating on a single implementation per 
operation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SYNCOPE-809) Eclipse plugin

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395380#comment-15395380
 ] 

ASF subversion and git services commented on SYNCOPE-809:
-

Commit b6bd80bee8fc9a3bfdc8b89c265d978d93c0a4e9 in syncope's branch 
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=b6bd80b ]

[SYNCOPE-809] Restoring build: need some adjustment to work with the site 
profile


> Eclipse plugin
> --
>
> Key: SYNCOPE-809
> URL: https://issues.apache.org/jira/browse/SYNCOPE-809
> Project: Syncope
>  Issue Type: Sub-task
>  Components: ide
> Environment: Eclipse
>Reporter: Francesco Chicchiriccò
>Assignee: Tushar Mishra
>  Labels: eclipse, gsoc2016
> Fix For: 2.0.0
>
>
> Develop a plug-in, according to what reported in SYNCOPE-770, working with 
> latest Eclipse version.
> See Google Summer of Code project proposal at 
> https://summerofcode.withgoogle.com/projects/#4822214733987840



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Eclipse Plugin [SYNCOPE-809] as GSoC 16 Project

[Francesco Chicchiriccò]

Hi Tushar,
FYI I have just pushed a commit

https://github.com/apache/syncope/commit/1f62e6fb91d0766a85015a99bf1269ad6eadf6f5

addressing some legal aspects of the new artifact (i.e. the Eclipse IDE 
Plugin) that will be downloadable since next stable release.


About further tasks / improvements on SYNCOPE-809, I would enlist:

 1. tests
 2. auto-format feature for HTML / XSLT editors

Regards.

On 22/07/2016 12:32, Tushar Mishra wrote:

Thanks for the merge and the tweet. As I said before, I am working on the
tests for this module.
If there are any other improvements you have in mind, please do tell me so
I can work on them during the weekend.

Regards,

On Fri, Jul 22, 2016 at 3:58 PM Francesco Chicchiriccò 
wrote:


As you might have seen, I have just merge PR #28 - this means we start
having an Eclipse plugin, cool :-)

Nice job so far: now we need to finalize some stuff to have it properly
ready for wide usage.

Regards.

On 20/07/2016 16:46, Tushar Mishra wrote:

Update:
Solved issues #4  and

#9

 and opened pull

request



I am making the suggested changes and preparing the next commit.

On Mon, Jul 18, 2016 at 8:55 PM Tushar Mishra 

wrote:

I've added an issue 
to track the progress on the p2 repository and I will resume work with

the

pom manifest.
Also, I will try to start merging this project as a module of my fork of
syncope  to ensure rat and
checkstyle requirements are met.

Regards,

On Mon, Jul 18, 2016 at 8:33 PM Francesco Chicchiriccò <
ilgro...@apache.org> wrote:


Please start a separate thread for this.
Regards.

On 16/07/2016 07:49, Tushar Mishra wrote:

I received an email from GSoC stating that during the final

evaluations, I

will need to submit a link to the code written during the project. See
https://developers.google.com/open-source/gsoc/help/work-product

I believe that this should be the commits page
 of my

project

repository . Will this be

OK?

I am also working on updating and maintaining a set of tagged posts on

my

blog which can be added to the submitted links and might also be
helpful in documentation.

Regards,


--
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC,
CXF Committer, OpenJPA Committer, PonyMail PPMC
http://home.apache.org/~ilgrosso/

[jira] [Commented] (SYNCOPE-809) Eclipse plugin

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395366#comment-15395366
 ] 

ASF subversion and git services commented on SYNCOPE-809:
-

Commit 1f62e6fb91d0766a85015a99bf1269ad6eadf6f5 in syncope's branch 
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=1f62e6f ]

[SYNCOPE-809] Adjusting LICENSE / NOTICE, release process and downloads


> Eclipse plugin
> --
>
> Key: SYNCOPE-809
> URL: https://issues.apache.org/jira/browse/SYNCOPE-809
> Project: Syncope
>  Issue Type: Sub-task
>  Components: ide
> Environment: Eclipse
>Reporter: Francesco Chicchiriccò
>Assignee: Tushar Mishra
>  Labels: eclipse, gsoc2016
> Fix For: 2.0.0
>
>
> Develop a plug-in, according to what reported in SYNCOPE-770, working with 
> latest Eclipse version.
> See Google Summer of Code project proposal at 
> https://summerofcode.withgoogle.com/projects/#4822214733987840



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [DISCUSS] Improving Camel-based provisioning

[Francesco Chicchiriccò]

Hi Colm,


I guess the routes look a bit nicer as well as we're calling the same component 
rather than individual processors etc.


Definitely, +1


Actually I think I can have just a single implementation per user/group/etc, 
just by checking to see what the type of the Object stored on the exchange is, 
so something like the following would work for user/group/any etc.:




That's nice improvement as well.

Thanks: are you going to open an improvement on JIRA for your work?
Regards.


On Tue, Jul 26, 2016 at 5:35 PM, Colm O hEigeartaigh  
wrote:


Thanks Francesco!

I did a quick POC for the user create route + got it working locally. Any
thoughts on what the route should look like? I could create a separate
component for each of the user/groups/any etc., so the route would look
something like:




Or I could have a single component that does something like:




etc.  WDYT?

BTW I'm not sure that this change is really buying us much improvement, as
the java logic looks more or less the same, from what I've done so far. I
guess one improvement is that we do away with all of the @Component Camel
Processor implementations (instead replacing them with Camel
DefaultProducer implementations that are controlled by the component). I
guess the routes look a bit nicer as well as we're calling the same
component rather than individual processors etc.

Colm.

On Tue, Jul 26, 2016 at 11:54 AM, Francesco Chicchiriccò  
wrote:


Hi,
FYI I have just committed


https://git1-us-west.apache.org/repos/asf?p=syncope.git;a=commit;h=945be877

a modification that should be simplifying the usage
PropagationTaskExecutor / PropagationReporter

Regards.


On 22/07/2016 13:45, Colm O hEigeartaigh wrote:


Hi Francesco,

I think a dedicated feature branch will not be necessary. I'll probably
do
it over a few commits, maybe do an operation at a time so as not to break
the tests.

Colm.

On Fri, Jul 22, 2016 at 7:59 AM, Francesco Chicchiriccò <
ilgro...@apache.org>wrote:

Hi Colm,

as it seems that Giacomo as well is happy if you can take this task, can
you please describe how are you going to work on it? Dedicated feature
branch? Or you expect to be simple enough to stay in a single commit?

Thanks!
Regards.


On 20/07/2016 13:45, Francesco Chicchiriccò wrote:

On 20/07/2016 13:17, Colm O hEigeartaigh wrote:

Hi Francesco,

It should be fairly straightforward I'd say. Is there reasonable test
coverage of the camel routes in the build?

As you can see from [3] the "all" profile (featuring Activiti, Camel

and
Swagger) is active by default, so the whole integration test suite is
run
with Camel routes by default.

I'd like to volunteer to take it on, given that I plan on talking about


Syncope + Camel, unless you or Giacomo would like to implement it?

This sounds great to me, and I would also say that there is no

particular
rush to finish before releasing 2.0.0: such an improvement can also
come
afterwards (2.0.1, 2.0.2, ...).

Regards.

On Wed, Jul 20, 2016 at 12:03 PM, Francesco Chicchiriccò <


ilgro...@apache.org> wrote:

On 19/07/2016 17:46, Colm O hEigeartaigh wrote:


Hi Francesco,


How do you envisage this change would be made? The Processors in
question
pretty much all call the PropagationManager to create some tasks and
then
execute them using the PropagationTaskExecutor. We could create a
new
Camel
component to encapsulate all of this functionality, and then just
refer to
it in the Spring DSL. Something like "
considering my (very limited) understanding of Camel, I would have
expected exactly something like this.

How difficult would it be to implement?

Regards.


On Mon, Jul 18, 2016 at 1:39 PM, Giacomo Lamonaco <

giacomo.lamon...@tirasa.net> wrote:

Hi Francesco,

I think it would be great! Currently camel routes are defined using

 Spring DSL: as you can image we need to understand if the
logic you
described can be expressed using that DSL. IMHO that's not a
difficult
task and it would be great to develop a POC. Otherwise we can
investigate other DSLs (equivalent to Spring DSL of course).

Best Regards,
Giacomo

Il giorno ven, 15/07/2016 alle 18.16 +0200, Francesco Chicchiriccò
ha
scritto:

Hi all,


as you know, Camel-based provisioning is one of the coolest
features
among the several cool features in 2.0.

The implementation is essentially done this way: each method in
CamelUserProvisioningManager [1] (and similarly for groups and any
objects) invokes some Camel route, then at the end of the route,
some
'processor' is invoked (as [2] for example, when user is created).

As you might see from [2] and all similar classes in that package,
there
is still some relevant logic implemented in Java, which might be
moved
back to the route definition, hence increasing the general
benefits
of
the whole concept of Camel-based provisioning.

Do you also see this as an enhancement? Do you think it is
possible
/
feasible to implement with limited effort?

Regards.

[1] 
https://github.com/apache/syncope/blob/master/ext/camel