On 19/03/2013 03:17, Edward Siewick wrote:
Hi.
With v1.0.6, LdapConnector 1.3.3 and openLDAP 2.4.28, there are a
number of attributes that aren't appearing in the External
Attributes pulldown. I have the same object classes defined for the
connector as are in use in openLDAP (Top, Person,
[
https://issues.apache.org/jira/browse/SYNCOPE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Osadchiy updated SYNCOPE-337:
---
Attachment: MANIFEST(core).MF
I've attached updated MANIFEST for syncope-core.
On 19/03/2013 11:14, xie@swm.de wrote:
Dear Sir or Madam,
I have a question about syncope 1.1.0-SNAPSHOT.
The following is an excerpt of the method create in UserServiceImpl:
UserTO created = userController.createInternal(userTO);
But there is no annotation @preAuthorize at the method
I would favour continuing to use Apache Jenkins for continuous integration
but to disable the cargo tests on it, and then using a external CI instance
with more firepower for the cargo tests.
Colm.
On Fri, Mar 15, 2013 at 10:58 AM, Francesco Chicchiriccò
ilgro...@apache.org wrote:
On
[
https://issues.apache.org/jira/browse/SYNCOPE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13606212#comment-13606212
]
Francesco Chicchiriccò commented on SYNCOPE-337:
So, no updated
On 19/03/2013 11:38, Colm O hEigeartaigh wrote:
I would favour continuing to use Apache Jenkins for continuous integration
but to disable the cargo tests on it, and then using a external CI instance
with more firepower for the cargo tests.
+1 looks reasonable to me.
My choice goes to Travis
Looks good now, thanks!
Colm.
On Thu, Mar 14, 2013 at 1:02 PM, Francesco Chicchiriccò ilgro...@apache.org
wrote:
On 14/03/2013 10:56, Colm O hEigeartaigh wrote:
Has anyone tried Syncope trunk lately in Chrome? The layout appears to be
completely broken if you go into Schema.
Hi Colm,
Hi all,
Two questions on the Resource mapping windows in the Console following the
merge to be able to have different mappings for propagation/synchronization:
a) The panel is not wide enough on my resolution to accomodate the
purpose tab - should it be made wider?
b) Should we default to BOTH
Il giorno 19/mar/2013, alle ore 12.18, Colm O hEigeartaigh ha scritto:
Hi all,
Two questions on the Resource mapping windows in the Console following the
merge to be able to have different mappings for propagation/synchronization:
a) The panel is not wide enough on my resolution to
No, not yet. Still waiting for some feedback from INFRA here:
https://issues.apache.org/jira/browse/INFRA-5837
Colm.
On Tue, Mar 19, 2013 at 10:40 AM, Francesco Chicchiriccò
ilgro...@apache.org wrote:
On 19/03/2013 11:38, Colm O hEigeartaigh wrote:
I would favour continuing to use Apache
[
https://issues.apache.org/jira/browse/SYNCOPE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13606269#comment-13606269
]
Hudson commented on SYNCOPE-326:
Integrated in Syncope-trunk #159 (See
The Apache Jenkins build system has built Syncope-trunk (build #159)
Status: Fixed
Check console output at https://builds.apache.org/job/Syncope-trunk/159/ to
view the results.
fabio martelli created SYNCOPE-339:
--
Summary: enum schema multivalue doesn't work
Key: SYNCOPE-339
URL: https://issues.apache.org/jira/browse/SYNCOPE-339
Project: Syncope
Issue Type: Bug
Hi all,
currently we have on trunk (e.g. 1.1.0-SNAPSHOT) a first OSGi support
for all modules as per SYNCOPE-203.
However, this seems not to be working (see SYNCOPE-337), even if
changing the build for generating MANIFEST.MF according to the ones
attached there.
From the other side, this
[
https://issues.apache.org/jira/browse/SYNCOPE-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò reassigned SYNCOPE-338:
--
Assignee: Francesco Chicchiriccò
Some CXF REST services can be
[
https://issues.apache.org/jira/browse/SYNCOPE-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabio martelli resolved SYNCOPE-336.
Resolution: Fixed
Use a auto-complete textfield to chose for external attribute to
[
https://issues.apache.org/jira/browse/SYNCOPE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabio martelli reassigned SYNCOPE-339:
--
Assignee: fabio martelli
enum schema multivalue doesn't work
[
https://issues.apache.org/jira/browse/SYNCOPE-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-338.
Resolution: Fixed
http://svn.apache.org/r1458326
Some
Il giorno 19/mar/2013, alle ore 15.40, Francesco Chicchiriccò ha scritto:
Hi all,
currently we have on trunk (e.g. 1.1.0-SNAPSHOT) a first OSGi support for all
modules as per SYNCOPE-203.
However, this seems not to be working (see SYNCOPE-337), even if changing the
build for generating
On Mar 19, 2013, at 3:40 PM, Francesco Chicchiriccò wrote:
Hi all,
currently we have on trunk (e.g. 1.1.0-SNAPSHOT) a first OSGi support for all
modules as per SYNCOPE-203.
However, this seems not to be working (see SYNCOPE-337), even if changing the
build for generating MANIFEST.MF
Hi all (but especially the CXF squad),
what's the best practice for generating HTML pages from JAX-RS annotations?
Now that we have this in place it would be nice to put on the website
such HTML pages, together with Javadocs.
Regards.
--
Francesco Chicchiriccò
ASF Member, Apache Syncope PMC
[
https://issues.apache.org/jira/browse/SYNCOPE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabio martelli resolved SYNCOPE-339.
Resolution: Fixed
enum schema multivalue doesn't work
Il 19/03/2013 15:40, Francesco Chicchiriccò ha scritto:
Hi all,
currently we have on trunk (e.g. 1.1.0-SNAPSHOT) a first OSGi support
for all modules as per SYNCOPE-203.
However, this seems not to be working (see SYNCOPE-337), even if
changing the build for generating MANIFEST.MF according
[
https://issues.apache.org/jira/browse/SYNCOPE-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-137:
---
Fix Version/s: (was: 1.3.0)
1.1.0
Support more
Hi Francesco,
I don't see why the merges for SYNCOPE-203 need to be reverted as they are
not breaking anything. I would prefer to leave things as they are but not
claim full OSGi support in the 1.1.0 release.
I guess you are concerned that these issues will hold up the 1.1.0 release
and so I
Hi
We've just had a Swagger in CXF thread [1] where Swagger (finally
confirmed to be working with CXF) and RestDoc have been mentioned.
Enunciate has been mentioned today/yesterday.
Other approaches likely work too, but as far as I'm concerned I'm quite
keen to get an auto-generated WADL
[
https://issues.apache.org/jira/browse/SYNCOPE-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13606424#comment-13606424
]
Hudson commented on SYNCOPE-338:
Integrated in Syncope-trunk #160 (See
[
https://issues.apache.org/jira/browse/SYNCOPE-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13606425#comment-13606425
]
Hudson commented on SYNCOPE-336:
Integrated in Syncope-trunk #160 (See
On 19/03/2013 16:33, Colm O hEigeartaigh wrote:
Hi Francesco,
I don't see why the merges for SYNCOPE-203 need to be reverted as they are
not breaking anything.
They don't break anything as long as you don't use OSGi.
This of course does not apply to SYNCOPE-239 (e.g. OSGi support for the
[
https://issues.apache.org/jira/browse/SYNCOPE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13606460#comment-13606460
]
Hudson commented on SYNCOPE-339:
Integrated in Syncope-1_0_X #166 (See
[
https://issues.apache.org/jira/browse/SYNCOPE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13606513#comment-13606513
]
Hudson commented on SYNCOPE-339:
Integrated in Syncope-trunk #161 (See
31 matches
Mail list logo
