[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=15060284#comment-15060284
 ] 

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

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

refactoring of CLI documentation, SYNCOPE-700


> 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] [Closed] (SYNCOPE-213) Fail to buid 1.0.2 tag

[Massimiliano Perrone (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Massimiliano Perrone closed SYNCOPE-213.


> Fail to buid 1.0.2 tag
> --
>
> Key: SYNCOPE-213
> URL: https://issues.apache.org/jira/browse/SYNCOPE-213
> Project: Syncope
>  Issue Type: Bug
>Affects Versions: 1.0.1-incubating, 1.0.2-incubating
>Reporter: Emmanuel Lecharny
> Attachments: cargo-output.log, cargo.log, core-connid.log, 
> core-persistence.log, core-rest.log, core-test.log, core.log
>
>
> The build fails on :
> Running org.apache.syncope.core.rest.NotificationTestITCase
> Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.44 sec <<< 
> FAILURE!
> Tested on OSX with Java 7, and also on Ubuntu, Java 6



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

[jira] [Assigned] (SYNCOPE-742) Upgrade to CXF 3.1.5

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò reassigned SYNCOPE-742:
--

Assignee: Francesco Chicchiriccò

> Upgrade to CXF 3.1.5
> 
>
> Key: SYNCOPE-742
> URL: https://issues.apache.org/jira/browse/SYNCOPE-742
> Project: Syncope
>  Issue Type: Improvement
>Affects Versions: 2.0.0-M1
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 2.0.0
>
> Attachments: 
> 0001-Using-CXF-3.1.4-as-no-3.1.5-SNAPSHOT-is-not-allowed.patch
>
>
> Currently the CXF dependency is set to 3.1.5-SNAPSHOT, which is going to be 
> released in (at least) one month time.
> Since some enhancements (compared to 3.1.4) are currently in use, this issue 
> is for tracking the changes required to track:
>  # the downgrade from 3.1.5-SNAPSHOT to 3.1.4 (for 2.0.0-M1)
>  # the upgrade from 3.1.4 to 3.1.5 (for 2.0.0)



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

[jira] [Updated] (SYNCOPE-742) Upgrade to CXF 3.1.5

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-742:
---
Attachment: 0001-Using-CXF-3.1.4-as-no-3.1.5-SNAPSHOT-is-not-allowed.patch

Brings everything from 3.1.5-SNAPSHOT to 3.1.4

Once applied, can be reverted - when CXF 3.1.5 will be available - via {{git 
apply -R path/file.patch}}

> Upgrade to CXF 3.1.5
> 
>
> Key: SYNCOPE-742
> URL: https://issues.apache.org/jira/browse/SYNCOPE-742
> Project: Syncope
>  Issue Type: Improvement
>Affects Versions: 2.0.0-M1
>Reporter: Francesco Chicchiriccò
> Fix For: 2.0.0
>
> Attachments: 
> 0001-Using-CXF-3.1.4-as-no-3.1.5-SNAPSHOT-is-not-allowed.patch
>
>
> Currently the CXF dependency is set to 3.1.5-SNAPSHOT, which is going to be 
> released in (at least) one month time.
> Since some enhancements (compared to 3.1.4) are currently in use, this issue 
> is for tracking the changes required to track:
>  # the downgrade from 3.1.5-SNAPSHOT to 3.1.4 (for 2.0.0-M1)
>  # the upgrade from 3.1.4 to 3.1.5 (for 2.0.0)



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

[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=15060304#comment-15060304
 ] 

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

Commit 1720391 from [~ilgrosso]
[ https://svn.apache.org/r1720391 ]

[SYNCOPE-700] Publish updated website

> 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] [Resolved] (SYNCOPE-213) Fail to buid 1.0.2 tag

[Massimiliano Perrone (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Massimiliano Perrone resolved SYNCOPE-213.
--
Resolution: Won't Fix

> Fail to buid 1.0.2 tag
> --
>
> Key: SYNCOPE-213
> URL: https://issues.apache.org/jira/browse/SYNCOPE-213
> Project: Syncope
>  Issue Type: Bug
>Affects Versions: 1.0.1-incubating, 1.0.2-incubating
>Reporter: Emmanuel Lecharny
> Attachments: cargo-output.log, cargo.log, core-connid.log, 
> core-persistence.log, core-rest.log, core-test.log, core.log
>
>
> The build fails on :
> Running org.apache.syncope.core.rest.NotificationTestITCase
> Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.44 sec <<< 
> FAILURE!
> Tested on OSX with Java 7, and also on Ubuntu, Java 6



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

Re: [DISCUSS] Next release(s)

[Francesco Chicchiriccò]

HI there,
as you might have noticed from the considerable e-mail flow, I have 
renamed 2.0.0 to 2.0.0-M1, created 2.0.0 and 2.1.0, and redistributed 
the open issues according to the discussion below.


The target is to attempt to release 2.0.0-M1 around Christmas - 
interesting the idea of Santa bringing the first release of Syncope 
2.0.0 under the Christmas tree :-)


Regards.

On 20/11/2015 13:18, Colm O hEigeartaigh wrote:

Sorry, a late +1 from me. Francesco, I'm happy to help with
reviewing/correcting any documentation - I don't have the time right now
unfortunately to write any from scratch.

Colm.

On Thu, Nov 12, 2015 at 8:10 AM, andrea 
wrote:



Il 11/11/2015 09:13, Francesco Chicchiriccò ha scritto:


On 11/11/2015 09:11, Francesco Chicchiriccò wrote:


Hi all,
this discussion is triggered by some request recently received on user@
[1] but also about the ongoing development effort towards 2.0.0.

AFAICT, the current status can be summarized as follows:

  1. feature-wise, core is currently in a quite self-consistent state,
even tough relevant new feature are ATM set to be implemented in 2.0.0
(mainly SYNCOPE-699 / SYNCOPE-129 / SYNCOPE-534); naturally, there might be
bugs, especially considering the great amount of additions compared to 1.2.X

  2. console is still under active development to reach usable state
(remember we started it from scratch in 2.0.0) - Fabio and Marco are on it

  3. enduser is more or less in the same situation of console, possibly a
bit more close to the end - Andrea is on it

On enduser there are two main points to consider:

1. eventual roles and resources management that is considered in user
create/update wizard, that can be postponed (or even omitted?).
2. enduser also needs to be "synchronized" with last core developments (on
virtual attributes for example).
So is correct to say that is more or less close to the end, but I wanted
to underline these two priority issues.


  4. cli should be almost complete - Massimiliano is on it

  5. documentation is less than half-way: getting started needs to be
adjusted with latest additions and reference guide is simply yet to be
written - I am on it, but seeking for contributions, especially by native
speakers - read Colm :-)

Given this overall situation, I would propose to:

  (i) keep pushing on 2, 3, 4 and 5 above
  (ii) fix on (1) on request
  (iii) as soon as 2 and 3 are in a presentable state, start thinking of
milestone releases (2.0.0-M1, 2.0.0-M2, etc)


Forgot to add:

 (iv) move all residual (and cool) features currently scheduled for
2.0.0 to 2.1.0

As far as I can see it, it would be really nice to cut 2.0.0-M1 before

the end of year.

WDYT?
Regards.

[1] http://markmail.org/message/ibcz7jx53su73dld


With M1 release I completely agree.

+1

Kind regards,
Andrea


--
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
http://home.apache.org/~ilgrosso/

Re: [DISCUSS] Next release(s)

[Francesco Chicchiriccò]

On 16 December 2015 18:09:11 CET, "Francesco Chicchiriccò" 
 wrote:
>HI there,
>as you might have noticed from the considerable e-mail flow, I have 
>renamed 2.0.0 to 2.0.0-M1, created 2.0.0 and 2.1.0, and redistributed 
>the open issues according to the discussion below.
>
>The target is to attempt to release 2.0.0-M1 around Christmas - 
>interesting the idea of Santa bringing the first release of Syncope 
>2.0.0 under the Christmas tree :-)

Forgot to add: here's the prospect of new website:

http://syncope.apache.org/2.0.0-SNAPSHOT/

Regards.

>On 20/11/2015 13:18, Colm O hEigeartaigh wrote:
>> Sorry, a late +1 from me. Francesco, I'm happy to help with
>> reviewing/correcting any documentation - I don't have the time right
>now
>> unfortunately to write any from scratch.
>>
>> Colm.
>>
>> On Thu, Nov 12, 2015 at 8:10 AM, andrea
>
>> wrote:
>>
>>>
>>> Il 11/11/2015 09:13, Francesco Chicchiriccò ha scritto:
>>>
 On 11/11/2015 09:11, Francesco Chicchiriccò wrote:

> Hi all,
> this discussion is triggered by some request recently received on
>user@
> [1] but also about the ongoing development effort towards 2.0.0.
>
> AFAICT, the current status can be summarized as follows:
>
>   1. feature-wise, core is currently in a quite self-consistent
>state,
> even tough relevant new feature are ATM set to be implemented in
>2.0.0
> (mainly SYNCOPE-699 / SYNCOPE-129 / SYNCOPE-534); naturally, there
>might be
> bugs, especially considering the great amount of additions
>compared to 1.2.X
>
>   2. console is still under active development to reach usable
>state
> (remember we started it from scratch in 2.0.0) - Fabio and Marco
>are on it
>
>   3. enduser is more or less in the same situation of console,
>possibly a
> bit more close to the end - Andrea is on it
>
> On enduser there are two main points to consider:
>>> 1. eventual roles and resources management that is considered in
>user
>>> create/update wizard, that can be postponed (or even omitted?).
>>> 2. enduser also needs to be "synchronized" with last core
>developments (on
>>> virtual attributes for example).
>>> So is correct to say that is more or less close to the end, but I
>wanted
>>> to underline these two priority issues.
>>>
   4. cli should be almost complete - Massimiliano is on it
>   5. documentation is less than half-way: getting started needs to
>be
> adjusted with latest additions and reference guide is simply yet
>to be
> written - I am on it, but seeking for contributions, especially by
>native
> speakers - read Colm :-)
>
> Given this overall situation, I would propose to:
>
>   (i) keep pushing on 2, 3, 4 and 5 above
>   (ii) fix on (1) on request
>   (iii) as soon as 2 and 3 are in a presentable state, start
>thinking of
> milestone releases (2.0.0-M1, 2.0.0-M2, etc)
>
 Forgot to add:

  (iv) move all residual (and cool) features currently scheduled
>for
 2.0.0 to 2.1.0

 As far as I can see it, it would be really nice to cut 2.0.0-M1
>before
> the end of year.
>
> WDYT?
> Regards.
>
> [1] http://markmail.org/message/ibcz7jx53su73dld
>
 With M1 release I completely agree.
>>> +1
>>>
>>> Kind regards,
>>> Andrea


-- 
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
http://people.apache.org/~ilgrosso/

[jira] [Commented] (SYNCOPE-156) New admin UI

[ASF subversion and git services (JIRA)]

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

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

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

[SYNCOPE-156] providing user and group ownership


> New admin UI
> 
>
> Key: SYNCOPE-156
> URL: https://issues.apache.org/jira/browse/SYNCOPE-156
> Project: Syncope
>  Issue Type: New Feature
>  Components: console
>Reporter: Francesco Chicchiriccò
> Fix For: 2.0.0
>
>
> Refactor and rewrite current console into a new, cleaner, admin UI.
> It is a important usability improvement to provide sensible and contextual 
> help messages on (mostly) each form field.
> [1] 
> http://syncope-dev.1063484.n5.nabble.com/About-admin-console-refactoring-td5710115.html
> [2] http://markmail.org/message/wtamknssq42pyjjc



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

[jira] [Created] (SYNCOPE-748) Selectively delete task executions

[JIRA]

Francesco Chicchiriccò created SYNCOPE-748:
--

 Summary: Selectively delete task executions
 Key: SYNCOPE-748
 URL: https://issues.apache.org/jira/browse/SYNCOPE-748
 Project: Syncope
  Issue Type: Improvement
  Components: core
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
 Fix For: 1.2.7


Introduce the ability to delete executions of a given task, with date 
parameters (before, after, ...).



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

[jira] [Updated] (SYNCOPE-748) Selectively delete task executions

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-748:
---
Fix Version/s: 2.0.0-M1

> Selectively delete task executions
> --
>
> Key: SYNCOPE-748
> URL: https://issues.apache.org/jira/browse/SYNCOPE-748
> Project: Syncope
>  Issue Type: Improvement
>  Components: core
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>  Labels: rest
> Fix For: 1.2.7, 2.0.0-M1
>
>
> Introduce the ability to delete executions of a given task, with date 
> parameters (before, after, ...).



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

[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=15059902#comment-15059902
 ] 

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

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

installer, SYNCOPE-700


> 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-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=15059903#comment-15059903
 ] 

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

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

installer, SYNCOPE-700


> 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-740) Website update for 2.0.0

[ASF subversion and git services (JIRA)]

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

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

Commit 1720362 from [~ilgrosso]
[ https://svn.apache.org/r1720362 ]

[SYNCOPE-740] Publish updated website

> Website update for 2.0.0
> 
>
> Key: SYNCOPE-740
> URL: https://issues.apache.org/jira/browse/SYNCOPE-740
> Project: Syncope
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 2.0.0
>
>
> In preparation to 2.0.0, the project website needs some adjustments:
>  # Add some introductory text to {{index}} (possibly by fetching / 
> re-adapting from getting started)
>  # Re-write {{features}} and add it to getting started
>  # Re-write {{architecture}} by porting it from getting started
>  # Refactor and update {{release-process}}
> Draft is published at http://syncope.apache.org/2.0.0-SNAPSHOT/



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

[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=15060087#comment-15060087
 ] 

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

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

Added debian packages, SYNCOPE-700


> 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-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=15059958#comment-15059958
 ] 

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

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

removed old images and added common directory, SYNCOPE-700


> 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] [Updated] (SYNCOPE-679) Deferred tasks

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-679:
---
Fix Version/s: (was: 2.0.0-M1)
   2.0.0

> Deferred tasks
> --
>
> Key: SYNCOPE-679
> URL: https://issues.apache.org/jira/browse/SYNCOPE-679
> Project: Syncope
>  Issue Type: Improvement
>Reporter: Francesco Chicchiriccò
> Fix For: 2.0.0
>
>
> The current {{SchedTask}} / {{SyncTask}} / {{PushTask}} are immediately set 
> for execution - with or without cron expression.
> This aspect can be enhanced by adding an instant in the future when the given 
> task will be scheduled from.



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

[jira] [Updated] (SYNCOPE-204) Add Karaf features

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-204:
---
Fix Version/s: (was: 2.0.0-M1)

> Add Karaf features
> --
>
> Key: SYNCOPE-204
> URL: https://issues.apache.org/jira/browse/SYNCOPE-204
> Project: Syncope
>  Issue Type: Improvement
>  Components: core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>
> In order to deploy Syncope directly in Apache Karaf (OSGi container), I will 
> provide:
> - a Karaf feature descriptor
> - a set of Karaf commands to manipulate Syncope resources (users, groups, 
> etc).



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

[jira] [Updated] (SYNCOPE-337) ClassNotFoundException in karaf osgi container

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-337:
---
Fix Version/s: (was: 2.0.0-M1)

> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SYNCOPE-534) OAuth 2.0 Service Provider

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-534:
---
Fix Version/s: (was: 2.0.0-M1)
   2.1.0

> OAuth 2.0 Service Provider
> --
>
> Key: SYNCOPE-534
> URL: https://issues.apache.org/jira/browse/SYNCOPE-534
> Project: Syncope
>  Issue Type: New Feature
>Reporter: Francesco Chicchiriccò
>Assignee: Jean-Baptiste Onofré
> Fix For: 2.1.0
>
>
> As discussed in mailing list [1] [2] [3], add OAuth 2.0 service providing 
> feature, possibly leveraging CXF support [4].
> [1] http://markmail.org/message/s6i7fnnsk222dego
> [2] http://markmail.org/message/rwdfyrhf6jskqtit
> [3] http://markmail.org/message/zr3nw5c7v62lclji
> [4] https://cxf.apache.org/docs/jax-rs-oauth2.html



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

[jira] [Updated] (SYNCOPE-155) Better way to override console components

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-155:
---
Fix Version/s: (was: 2.0.0-M1)

> Better way to override console components
> -
>
> Key: SYNCOPE-155
> URL: https://issues.apache.org/jira/browse/SYNCOPE-155
> Project: Syncope
>  Issue Type: Improvement
>  Components: console
>Reporter: Francesco Chicchiriccò
>
> Better way to override console components (for WAR overlays).



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

[jira] [Updated] (SYNCOPE-738) Startup errors with Wildfly due to Camel route loading

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-738:
---
Fix Version/s: (was: 2.0.0-M1)
   2.0.0

> Startup errors with Wildfly due to Camel route loading
> --
>
> Key: SYNCOPE-738
> URL: https://issues.apache.org/jira/browse/SYNCOPE-738
> Project: Syncope
>  Issue Type: Bug
>  Components: extensions
>Affects Versions: 2.0.0-M1
> Environment: Wildfly 9 + Camel extension
>Reporter: Francesco Chicchiriccò
>Priority: Minor
> Fix For: 2.0.0
>
>
> With Camel extension enabled and Wildfly, the following exception is raised 
> during Syncope core startup:
> {code}
> ClassNotFoundException: 
> com.sun.org.apache.xerces.internal.dom.DOMXSImplementationSourceImpl
> {code}
> This is related to [WFLY-4416|https://issues.jboss.org/browse/WFLY-4416], a 
> bug currently open in Wildfly.



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

[jira] [Updated] (SYNCOPE-681) i18n labels for schema names

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-681:
---
Fix Version/s: (was: 2.0.0-M1)
   2.1.0

> i18n labels for schema names
> 
>
> Key: SYNCOPE-681
> URL: https://issues.apache.org/jira/browse/SYNCOPE-681
> Project: Syncope
>  Issue Type: Improvement
>Reporter: Francesco Chicchiriccò
> Fix For: 2.1.0
>
>
> Schema names can be "ugly" text, but there should be a REST service providing 
> optional i18n labels.



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

[jira] [Updated] (SYNCOPE-680) Recipient provider extension class

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-680:
---
Fix Version/s: (was: 2.0.0-M1)
   2.0.0

> Recipient provider extension class
> --
>
> Key: SYNCOPE-680
> URL: https://issues.apache.org/jira/browse/SYNCOPE-680
> Project: Syncope
>  Issue Type: Improvement
>Reporter: Francesco Chicchiriccò
> Fix For: 2.0.0
>
>
> Notification recipients are currently set either statically or dynamically 
> (via FIQL).
> An extension point - by letting users provide their own specific recipient 
> provider class, for each notification - can be added.



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

[jira] [Updated] (SYNCOPE-699) Apache Shiro integration

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-699:
---
Fix Version/s: (was: 2.0.0-M1)
   2.1.0

> Apache Shiro integration
> 
>
> Key: SYNCOPE-699
> URL: https://issues.apache.org/jira/browse/SYNCOPE-699
> Project: Syncope
>  Issue Type: New Feature
>Reporter: Francesco Chicchiriccò
> Fix For: 2.1.0
>
>
> Heading to 2.0.0, a proposal is [being 
> discussed|https://cwiki.apache.org/confluence/display/SYNCOPE/%5BDISCUSS%5D+Apache+Shiro+integration+for+authentication+and+authorization]
>  for replacing the current authorization / implementation with something new 
> based on Apache Shiro.



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

[jira] [Closed] (SYNCOPE-155) Better way to override console components

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò closed SYNCOPE-155.
--
Resolution: Won't Fix

See SYNCOPE-156

> Better way to override console components
> -
>
> Key: SYNCOPE-155
> URL: https://issues.apache.org/jira/browse/SYNCOPE-155
> Project: Syncope
>  Issue Type: Improvement
>  Components: console
>Reporter: Francesco Chicchiriccò
>
> Better way to override console components (for WAR overlays).



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

[jira] [Updated] (SYNCOPE-730) Datetime picker component is not working properly with some date formats

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-730:
---
Fix Version/s: (was: 2.0.0-M1)
   2.0.0

> Datetime picker component is not working properly with some date formats
> 
>
> Key: SYNCOPE-730
> URL: https://issues.apache.org/jira/browse/SYNCOPE-730
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.0-M1
>Reporter: fabio martelli
> Fix For: 2.0.0
>
>
> Datetime picker component is not working properly with some *java* date 
> formats. The difference between java and javascript date format 
> representations seems to cause a lot of trouble.
> Try the default java date format (ISO8601) to reproduce the issue.



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

[jira] [Updated] (SYNCOPE-737) UserWizardBuilder, the store internally password flag is not set properly

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-737:
---
Fix Version/s: (was: 2.0.0-M1)
   2.0.0

> UserWizardBuilder, the store internally password flag is not set properly
> -
>
> Key: SYNCOPE-737
> URL: https://issues.apache.org/jira/browse/SYNCOPE-737
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.0-M1
>Reporter: Marco Di Sabatino Di Diodoro
> Fix For: 2.0.0
>
>
> In the creation of a new user by the wizard, the storePassword field is not 
> set properly.



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

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

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-700:
---
Fix Version/s: (was: 2.0.0-M1)
   2.0.0

> 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] [Updated] (SYNCOPE-719) UI enhancements

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-719:
---
Fix Version/s: (was: 2.0.0-M1)
   2.0.0

> UI enhancements
> ---
>
> Key: SYNCOPE-719
> URL: https://issues.apache.org/jira/browse/SYNCOPE-719
> Project: Syncope
>  Issue Type: Sub-task
>  Components: enduser
>Affects Versions: 2.0.0-M1
>Reporter: Andrea Patricelli
> Fix For: 2.0.0
>
>
> Enhancements to implement:
> - Add form frontend validation through AngularJS built-in form services.
> - Secure authentication process: at the moment username and password are 
> passed "clearly" to wicket resource in the payload of the POST. to achieve 
> this configure HTTPS connection.
> - Realms management (if needed): Add http resource to get available realms 
> and possibiltity to select realm in user form.
> - Uploaded file preview (trivial, can even be ignored)
> - Add loading spinner to application: 
> http://mvnrepository.com/artifact/org.webjars.bower/angular-spinner
> - Add Group and Resource management to create/edit user wizard (if needed).
> - AngularJS unit testing: implement unit tests for angular frontend and 
> possibly integrate them with maven build lifecycle.
> - Improve date management edit/create form: add timepicker when needed.
> - Improve error and exception management: especially messages sent by 
> resource to angular frontend.
> - Add password stregth validator to user creation form.
> - Add javadoc and if possible javascript doc



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

[jira] [Updated] (SYNCOPE-701) New end-user UI

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-701:
---
Fix Version/s: (was: 2.0.0-M1)
   2.0.0

> New end-user UI
> ---
>
> Key: SYNCOPE-701
> URL: https://issues.apache.org/jira/browse/SYNCOPE-701
> Project: Syncope
>  Issue Type: New Feature
>Reporter: Francesco Chicchiriccò
>Assignee: Andrea Patricelli
> Fix For: 2.0.0
>
>
> Before SYNCOPE-156, the admin console used to offer self-service features 
> like as self-registration, profile maintenance and password reset.
> The idea is to built a separate web application providing such features; some 
> requirements:
>  # extremely customizable on deployment basis: not only look & feel, but also 
> application logic (this sets one of glamour JS frameworks -as AngularJS - as 
> candidate)
>  # keep admin UI attitude of being gateway for accessing REST services 
> exposed by core: this might require to build a sort of 'proxy' application to 
> be contacted by client-side JS code



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

[jira] [Created] (SYNCOPE-743) Complete Topology

[JIRA]

Francesco Chicchiriccò created SYNCOPE-743:
--

 Summary: Complete Topology
 Key: SYNCOPE-743
 URL: https://issues.apache.org/jira/browse/SYNCOPE-743
 Project: Syncope
  Issue Type: Sub-task
  Components: console
Reporter: Francesco Chicchiriccò
 Fix For: 2.0.0


Complete the current Topology page with latest enhancements for connectors and 
external resources, and task management.



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

[jira] [Created] (SYNCOPE-745) Complete Configuration

[JIRA]

Francesco Chicchiriccò created SYNCOPE-745:
--

 Summary: Complete Configuration
 Key: SYNCOPE-745
 URL: https://issues.apache.org/jira/browse/SYNCOPE-745
 Project: Syncope
  Issue Type: Sub-task
  Components: console
Reporter: Francesco Chicchiriccò
 Fix For: 2.0.0


Various items are missing:

 # roles
 # general parameters
 # reports
 # notifications
 # policies
 # logs



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

[jira] [Updated] (SYNCOPE-156) New admin UI

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-156:
---
Fix Version/s: (was: 2.0.0-M1)
   2.0.0

> New admin UI
> 
>
> Key: SYNCOPE-156
> URL: https://issues.apache.org/jira/browse/SYNCOPE-156
> Project: Syncope
>  Issue Type: New Feature
>  Components: console
>Reporter: Francesco Chicchiriccò
> Fix For: 2.0.0
>
>
> Refactor and rewrite current console into a new, cleaner, admin UI.
> It is a important usability improvement to provide sensible and contextual 
> help messages on (mostly) each form field.
> [1] 
> http://syncope-dev.1063484.n5.nabble.com/About-admin-console-refactoring-td5710115.html
> [2] http://markmail.org/message/wtamknssq42pyjjc



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

[jira] [Created] (SYNCOPE-746) Migrate console extension mechanism from 1.2

[JIRA]

Francesco Chicchiriccò created SYNCOPE-746:
--

 Summary: Migrate console extension mechanism from 1.2
 Key: SYNCOPE-746
 URL: https://issues.apache.org/jira/browse/SYNCOPE-746
 Project: Syncope
  Issue Type: Sub-task
  Components: console, extensions
Reporter: Francesco Chicchiriccò
 Fix For: 2.0.0


Complete migration and verify that the admin console extension mechanism is 
working.



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

[jira] [Resolved] (SYNCOPE-637) Let user choose extensions

[Massimiliano Perrone (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Massimiliano Perrone resolved SYNCOPE-637.
--
Resolution: Fixed

> Let user choose extensions
> --
>
> Key: SYNCOPE-637
> URL: https://issues.apache.org/jira/browse/SYNCOPE-637
> Project: Syncope
>  Issue Type: Improvement
>  Components: installer
>Reporter: Francesco Chicchiriccò
>Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> After SYNCOPE-620, the project generated by installer does not include 
> neither Activiti workflow adapter nor Camel-based provisioning manager, but 
> their respective "plain Java" counterparts.
> It should be possible to let user choose which workflow adapter and 
> provisioning manager to include.
> Moreover, the optional Swagger component can be chosen to be included or not,



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