On 02/04/2013 13:55, Colm O hEigeartaigh wrote: > Hi Francesco, > > We have not been able to sort out the OSGi issues as of yet. One of the > problems seems to be a conflict between the different versions of Spring > used by Syncope + CXF, which is resulting in the exceptions reported in > SYNCOPE-337. > > For the moment I propose moving SYNCOPE-337 to 1.1.1. If we can't fix the > OSGi issues in a relatively simple way then we can move it to 1.2. I would > like to keep the changes made as part of SYNCOPE-203 in place, as it > doesn't affect the Tomcat deployment + it would require additional changes > on some downstream code that we have.
Fine to me: I'll proceed then to: 1. create new branch 1_1_X from trunk + set trunk version to 1.2.0-SNAPSHOT 2. create Jenkins job for 1_1_X 3. create JIRA version 1.1.1 4. move SYNCOPE-337 to 1.1.1 Nothing will be done in respect of SYNCOPE-203. Regards. > On Tue, Apr 2, 2013 at 8:00 AM, ilgrosso <ilgro...@apache.org> wrote: > >> 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. 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 propose the following. Give us until the end of the week to find >>> a >>> solution for SYNCOPE-337 (and any related problems). If we have not found >>> a >>> solution by then, then this JIRA can be moved to the next release (1.1.1 >>> if >>> it can be considered a "bug" based on 1.1.0, otherwise 1.2). >>> >>> Does this work? >> Hi Colm, >> is there any progress about this? >> >> I think we should be able to at least think starting the 1.1.0 release >> process this week, hence understanding how to handle the OSGi features is >> quite important right now. >> >> Regards. -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
