[
https://issues.apache.org/jira/browse/SYNCOPE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13558603#comment-13558603
]
Francesco Chicchiriccò commented on SYNCOPE-281:
I've added a 'common'
[
https://issues.apache.org/jira/browse/SYNCOPE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13558641#comment-13558641
]
Francesco Chicchiriccò commented on SYNCOPE-281:
Actually, console
Hi,
I would like to make a proposal regarding some Rest package names:
1. Core services implementations: org.apache.syncope.core.services
(actually org.apache.syncope.core.services.impl). Impl ending doesn't bring
additional information and doesn't recommended by java best practices.
[
https://issues.apache.org/jira/browse/SYNCOPE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13558645#comment-13558645
]
Francesco Chicchiriccò commented on SYNCOPE-281:
Did you already check if
[
https://issues.apache.org/jira/browse/SYNCOPE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-281:
---
Attachment: (was: SYNCOPE-281.selenium.patch)
Refactor client
[
https://issues.apache.org/jira/browse/SYNCOPE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13558654#comment-13558654
]
Francesco Chicchiriccò commented on SYNCOPE-281:
About Selenium, such
[
https://issues.apache.org/jira/browse/SYNCOPE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13558662#comment-13558662
]
Hudson commented on SYNCOPE-281:
Integrated in Syncope-trunk #458 (See
[
https://issues.apache.org/jira/browse/SYNCOPE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13558664#comment-13558664
]
Jan Bernhardt commented on SYNCOPE-281:
---
OK, makes sense. I very happy to see, that
On 21.01.2013 10:29, Andrei Shakirin wrote:
Hi,
I would like to make a proposal regarding some Rest package names:
1. Core services implementations: org.apache.syncope.core.services
(actually org.apache.syncope.core.services.impl). Impl ending doesn't
bring additional information
Hi Christian,
2. Resource comparators and server exception mapper:
org.apache.syncope.core.rest.utils (actually org.apache.syncope.core.rest).
It makes purpose of these classes more clear.
Generally I don't like util packages. I would put these helpers into the same
package as the
Hi all,
following our recent discussion [1], I'd propose to:
1. move SYNCOPE-231 (e.g. CXF migration) and all subtasks to 1.1.0
2. move SYNCOPE-275 (Upgrade Spring to 3.2) to 1.1.0 as it requires
SYNCOPE-231
3. move SYNCOPE-204 (Add Karaf features) to 1.2.0
4. move SYNCOPE-122 (Password change
The classes are referenced from the spring config but they belong to the impl
classes so why introduce a new package?
Basically we can leave exception mapper and resource comparator in
core.services, there is one thing that make me unsure:
Exception mapper and resource comparator depend from
Il giorno 21/gen/2013, alle ore 11.46, Francesco Chicchiriccò ha scritto:
Hi all,
following our recent discussion [1], I'd propose to:
1. move SYNCOPE-231 (e.g. CXF migration) and all subtasks to 1.1.0
2. move SYNCOPE-275 (Upgrade Spring to 3.2) to 1.1.0 as it requires
SYNCOPE-231
3.
On 21/01/2013 12:00, Fabio Martelli wrote:
Il giorno 21/gen/2013, alle ore 11.46, Francesco Chicchiriccò ha scritto:
Hi all,
following our recent discussion [1], I'd propose to:
1. move SYNCOPE-231 (e.g. CXF migration) and all subtasks to 1.1.0
2. move SYNCOPE-275 (Upgrade Spring to 3.2) to
Il giorno 21/gen/2013, alle ore 12.04, Francesco Chicchiriccò ha scritto:
On 21/01/2013 12:00, Fabio Martelli wrote:
Il giorno 21/gen/2013, alle ore 11.46, Francesco Chicchiriccò ha scritto:
Hi all,
following our recent discussion [1], I'd propose to:
1. move SYNCOPE-231 (e.g. CXF
On 21/01/2013 12:47, Fabio Martelli wrote:
[...]
I think that SYNCOPE-122 and SYNCOPE-135 will not make the difference in
reference to the load.
I disagree on this point: anyway, keeping SYNCOPE-122 in 1.1.0 (point 4
of my initial checklist) and moving SYNCOPE-135 and SYNCOPE-136 from
1.2.0
On 21/01/2013 13:51, Jan Bernhardt wrote:
-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Montag, 21. Januar 2013 13:18
To: dev@syncope.apache.org
Subject: Re: [DISCUSS] Moving issues from one version to another
On 21/01/2013 12:47, Fabio Martelli
-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Montag, 21. Januar 2013 17:14
To: dev@syncope.apache.org
Subject: Re: [Question] ApplicationContextProvider in UnitTests
On 21/01/2013 17:07, Jan Bernhardt wrote:
Hi,
Since last SVN update, I
Hi,
Since last SVN update, I cannot build syncope on my system, due to
never ending UnitTests.
Which update? Was this incorporated in latest Jenkins build? [1]
I guess my problems are related to:
Revision 1436375 by ilgrosso:
[SYNCOPE-249] core: extension for propagation
Glen Mazza created SYNCOPE-283:
--
Summary: website edits
Key: SYNCOPE-283
URL: https://issues.apache.org/jira/browse/SYNCOPE-283
Project: Syncope
Issue Type: Improvement
Reporter:
20 matches
Mail list logo
