[
https://issues.apache.org/jira/browse/SYNCOPE-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13581106#comment-13581106
]
Hudson commented on SYNCOPE-315:
Integrated in Syncope-1_0_X #148 (See
[
https://issues.apache.org/jira/browse/SYNCOPE-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13581112#comment-13581112
]
Hudson commented on SYNCOPE-315:
Integrated in Syncope-trunk #99 (See
[
https://issues.apache.org/jira/browse/SYNCOPE-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13581113#comment-13581113
]
Hudson commented on SYNCOPE-257:
Integrated in Syncope-trunk #99 (See
Colm O hEigeartaigh created SYNCOPE-318:
---
Summary: No way to see Connector help message for multi-valued
property
Key: SYNCOPE-318
URL: https://issues.apache.org/jira/browse/SYNCOPE-318
Hi all,
Following the query on the CSV SNAPSHOT in Syncope, just wondering why are
we including 0.6.1-SNAPSHOT on trunk instead of 0.7-SNAPSHOT? The former
does not include the fixes I made recently (in particular the properties
file is in the wrong package name, and so the correct property keys
[
https://issues.apache.org/jira/browse/SYNCOPE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-318:
---
Component/s: console
No way to see Connector help message for
[
https://issues.apache.org/jira/browse/SYNCOPE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-318:
---
Fix Version/s: 1.1.0
No way to see Connector help message for
On 19/02/2013 11:13, Colm O hEigeartaigh wrote:
Hi all,
Following the query on the CSV SNAPSHOT in Syncope, just wondering why are
we including 0.6.1-SNAPSHOT on trunk instead of 0.7-SNAPSHOT? The former
does not include the fixes I made recently (in particular the properties
file is in the
When using the CSVDir 0.7-SNAPSHOT we would be forced to use ConnId
1.3.3-SNAPSHOT instead of 1.3.2.
Is there any reason why we can't just do that on trunk anyway? I assume
we're going to release Syncope 1.1 with ConnId 1.3.3 anyway?
Why not backporting your fix on 0.7-SNAPSHOT to
Il giorno 19/feb/2013, alle ore 11.44, Colm O hEigeartaigh ha scritto:
Guys, I'd prefere to keep the 1.3.2 for Syncope 1.1.0.
Since we are expecting to release soon I'd like to be sure about the
reliability of the 1.1.0.
Why do you think 1.3.3 would be particularly unreliable? There
On 19/02/2013 12:03, Colm O hEigeartaigh wrote:
Hi Fabio,
OK Colm, probably we can do the following.
Since I'd like to maintain the possibility to switch from a newest
connector version to an old one I'd ask you to verify before the
possibility to run, for example, CsvDir 0.6.1-SNAPSHOT with
[
https://issues.apache.org/jira/browse/SYNCOPE-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò reassigned SYNCOPE-209:
--
Assignee: Francesco Chicchiriccò (was: fabio martelli)
DB Table
Francesco Chicchiriccò created SYNCOPE-319:
--
Summary: Provide feature for reloading all connectors
Key: SYNCOPE-319
URL: https://issues.apache.org/jira/browse/SYNCOPE-319
Project: Syncope
[
https://issues.apache.org/jira/browse/SYNCOPE-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò reassigned SYNCOPE-319:
--
Assignee: Francesco Chicchiriccò
Provide feature for reloading
How about a new branch for the LDAP + DB bundles that I can backport fixes
to?
In terms of the DB Connector first, trunk is at 2.1.5-SNAPSHOT. How about I
update trunk to 2.2-SNAPSHOT + create a new branch called 2.1.X (with
version 2.1.5-SNAPSHOT) before the recent revisions were made? I will
On 19/02/2013 12:51, Colm O hEigeartaigh wrote:
How about a new branch for the LDAP + DB bundles that I can backport fixes to?
In terms of the DB Connector first, trunk is at 2.1.5-SNAPSHOT. How about I
update trunk to 2.2-SNAPSHOT + create a new branch called 2.1.X (with
version
Hi Francesco,
I thought we could avoid this branching if we are able to verify that you
can use old (e.g. compiled against ConnId 1.3.2) connectors with new
(e.g. 1.3.3-SNAPSHOT) framework,
Ok, I guess I misunderstood. I understand that we want to run an old
connector with the new framework,
On 19/02/2013 13:04, Colm O hEigeartaigh wrote:
Hi Francesco,
I thought we could avoid this branching if we are able to verify that you can use old
(e.g. compiled against ConnId 1.3.2) connectors with new
(e.g. 1.3.3-SNAPSHOT) framework,
Ok, I guess I misunderstood. I understand that we
Le 2/18/13 4:08 PM, Colm O hEigeartaigh a écrit :
attribute name, whereas LDAPMembershipSyncActions has uniquemember. Is
there a reason why it is different in both cases? Shouldn't they also
check
the value of the groupMemberAttribute property of the LDAP Connector?
Could you explain the
Hi all,
Is there any reason 'content.xml' in the Archetype core
(src/main/resources) has a handful of schema type definitions, etc.? I
would have thought it would make more sense to have the most minimal set of
configuration that you can use to set up a Syncope install. Obviously, the
content.xml
On 19/02/2013 14:44, Colm O hEigeartaigh wrote:
Hi all,
Is there any reason 'content.xml' in the Archetype core
(src/main/resources) has a handful of schema type definitions, etc.? I
would have thought it would make more sense to have the most minimal set of
configuration that you can use to
Given the retro-compatibility feature reported above, if confirmed
working, I think that we can move Syncope 1.1.0 to ConnId 1.3.3-SNAPSHOT,
thus avoid branching.
Sorry for not having made this re-thinking clear.
Ah, ok got it, thanks.
Colm.
On Tue, Feb 19, 2013 at 12:30 PM, Francesco
[
https://issues.apache.org/jira/browse/SYNCOPE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated SYNCOPE-293:
Attachment: Screenshot from 2013-02-19 15.png
Here is a SNAPSHOT of the
[
https://issues.apache.org/jira/browse/SYNCOPE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh reopened SYNCOPE-293:
-
Show information (version, license, ...)
[
https://issues.apache.org/jira/browse/SYNCOPE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13581373#comment-13581373
]
Massimiliano Perrone commented on SYNCOPE-293:
--
Running -Pdev in trunk
These are needed, indeed:
- SyncopeConf confKey=smtp.host confValue=not-existing/
- SyncopeConf confKey=smtp.port confValue=25/
- !-- notificationjob.cronExpression:
- + not existing: NotificationJob runs according to
Notification.DEFAULT_CRON_EXP
- + provided as empty string:
Ok can revert - but why are they needed if you are not intending to create
any notification jobs?
Colm.
On Tue, Feb 19, 2013 at 3:43 PM, Francesco Chicchiriccò ilgro...@apache.org
wrote:
These are needed, indeed:
- SyncopeConf confKey=smtp.host confValue=not-existing/
- SyncopeConf
On 19/02/2013 16:49, Colm O hEigeartaigh wrote:
Ok can revert - but why are they needed if you are not intending to create
any notification jobs?
The SMTP stuff is needed not only for notifications, it is a general
conf param.
About notification cron expression, if you remove that comment
[
https://issues.apache.org/jira/browse/SYNCOPE-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabio martelli resolved SYNCOPE-257.
Resolution: Fixed
Schema Mapping for propagation and synchronization
[
https://issues.apache.org/jira/browse/SYNCOPE-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13581581#comment-13581581
]
Hudson commented on SYNCOPE-257:
Integrated in Syncope-trunk #101 (See
30 matches
Mail list logo
