[jira] [Assigned] (SYNCOPE-242) Resolve dependency cycles between persistence and the rest of syncope core

2012-12-06 Thread JIRA

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

Jean-Baptiste Onofré reassigned SYNCOPE-242:


Assignee: Jean-Baptiste Onofré

 Resolve dependency cycles between persistence and the rest of syncope core
 --

 Key: SYNCOPE-242
 URL: https://issues.apache.org/jira/browse/SYNCOPE-242
 Project: Syncope
  Issue Type: Improvement
Affects Versions: 1.0.3-incubating
Reporter: Christian Schneider
Assignee: Jean-Baptiste Onofré
 Fix For: 1.0.4


 When analysing if we could move the persistence and persistence impl into 
 separate modules I found that there are a lot of dependency cycles in the 
 syncope core module. I have added a structure 101 diagram of the cycles to 
 the issue so you can take a look.
 Especially the cycles between persistence and the rest of core are important 
 as they prevent us from moving these packages out of core.
 I have already done some experimentations how to solve the cycles and am 
 pretty sure I can fix that.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


Re: Introducing myself and a proposal to modularize the core

2012-12-06 Thread Jean-Baptiste Onofré

+1

Regards
JB

On 12/06/2012 09:47 AM, Fabio Martelli wrote:

Hi guys,
I changed the fix version of SYNCOPE-242.
I think it should be 1.1.0. You agree, don't you?

Best regards,
F.

Il giorno 06/dic/2012, alle ore 09.39, Jean-Baptiste Onofré ha scritto:


Hi Christian,

About the itests, and your proposal, I think it's a good thing to split API, 
model and impl for persistence.

For the dependency cycle, I gonna take a look as I'm working on some modular 
enhancement (related to OSGi support).

The only point is (for SYNCOPE-242) to wait the changes in progress (started by 
Francesco).

Regards
JB

On 12/06/2012 09:35 AM, Christian Schneider wrote:

Hi Syncope team,

my name is Christian Schneider and I am working together with Jan
Bernhard on the CXF migration of Syncope.

We sometimes have problems running the rest itests in the core project
from eclipse. When looking into the reasons we found that eclipse
sometimes seems to overwrite the enhanced jpa classes with plain ones.
I thought about how to solve this and found that it may be a good idea
to split the persistence model and persistence impl out of core and into
two separate modules.
See: https://issues.apache.org/jira/browse/SYNCOPE-241

So what do you think about this idea? Does it make sense or are there
some good reasons to keep these packages in the core?

While analysing how to do this split I found that there are a lot of
dependency cycles in core. Especially the ones between persistence and
impl impede moving out these packages. So if we agree to move the
persistence we first have to solve the dependency cycles. I have added
another issue to track this:
https://issues.apache.org/jira/browse/SYNCOPE-242

The good thing is that it looks worse than it is. I experimented with
some ways to eliminate the cycles and am pretty sure I can do it. Jan
told me that Francesco is working on a refactoring of the role code. So
I would in any case wait till he has finished his work.

Best regards
Christian



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com




--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com


Syncope-CXF - Build # 10 - Unstable

2012-12-06 Thread Apache Jenkins Server
The Apache Jenkins build system has built Syncope-CXF (build #10)

Status: Unstable

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

Re: Property files

2012-12-06 Thread Fabio Martelli

Il giorno 06/dic/2012, alle ore 10.55, ernst Developer ha scritto:

 Hi,
 
 Syncope console has a property file named configuration.properties, that
 contains property values which are environment specific.
 Everytime Syncope is installed on some servlet container, I need to do a
 change property values in configuration.properties for the environment I am
 working on and do a build.
 
 I think that it is possible to move the configuration.properties out of the
 build, and configure the properties in a file per environment.
 
 We could do this by changing the
 console/src/main/resources/applicationContext.xml.
 
 Now the context file has for the configuration.properties file:
 
 * bean id=propertyConfigurer*
 *
 class=org.springframework.beans.factory.config.PropertyPlaceholderConfigurer
 *
 *property name=locations*
 *  list*
 *valueclasspath:configuration.properties/value*
 *  /list*
 */property*
 *  /bean*
 *
 *
 If we change this and add another bean:
 
 *bean id=propertyConfigurer2
 class=org.springframework.beans.factory.config.PropertyPlaceholderConfigurer
 *
 *property name=order value=1/*
 *property name=location
 value=file:#{(systemProperties['user.home'] +
 '/.configuration.properties')}/*
 *property name=ignoreResourceNotFound value=true/*
 *property name=ignoreUnresolvablePlaceholders value=true/*
 */bean*
 
 We only have to create a .configuration.properties file in the home
 directory of the user that runs the servlet container on which syncope is
 deployed. If the file is not found, it still the default
 configuration.properties file from within the war file is used.
 
 Easy right?

Hi Ernst, 
from my PPOV it sounds easy and good enough.

I think you can open a new issue to schedule this refactoring.

Best regards,
F.



Re: Shortly introduce myself

2012-12-06 Thread Fabio Martelli

Il giorno 06/dic/2012, alle ore 12.59, Andrei Shakirin ha scritto:

 Hi,
 
 I will start to work with Jan on migration of Syncope rest interface from 
 Spring to Apache CXF (I am committer for CXF project).
 Further we are going to improve and extend Syncope with new features.
 
 Look forward to work with you!


Hi Andrei, I'm very happy to read this email.
I look forward to have you officially on-board.

Best regards,
F.

[jira] [Updated] (SYNCOPE-243) Extended org.apache.rat exclude list for eclipse IDE

2012-12-06 Thread JIRA

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

Francesco Chicchiriccò updated SYNCOPE-243:
---

Component/s: parent

 Extended org.apache.rat exclude list for eclipse IDE
 

 Key: SYNCOPE-243
 URL: https://issues.apache.org/jira/browse/SYNCOPE-243
 Project: Syncope
  Issue Type: Improvement
  Components: parent
Affects Versions: 1.0.3-incubating
Reporter: Andrei Shakirin
 Fix For: 1.0.4, 1.1.0

 Attachments: parent-pom.patch


 Hi,
 I would propose to add Eclipse IDE artifacts into exclusion list of 
 org.apache.rat plugin.
 It makes build for Eclipse users more comfortable.
 Patch is attached.
 Regards,
 Andrei.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


Re: [INFO] OSGi Enhancements

2012-12-06 Thread Francesco Chicchiriccò

On 07/12/2012 08:43, Jean-Baptiste Onofré wrote:

Hi Francesco,

I'm stuck with a customer today, I will commit tonight.

Sorry for the delay.


Absolutely no problems at all, I understand you completely since I am 
exactly in the same situation.. :S


It's just to try to understand when we will be able to ignite the 
release process for 1.0.4 (yours is not the only one...)


Regards.


On 12/07/2012 08:39 AM, Francesco Chicchiriccò wrote:

On 04/12/2012 18:28, Jean-Baptiste Onofré wrote:

Hi guys,

FYI, I started the OSGi Enhancements on my local git repo and it looks
good.

FYI, I plan to commit it later tonight or tomorrow morning.


Hi Jean-Baptiste,
any timing for this?
Thanks.

Regards.




--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/