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. Colm. On Tue, Apr 2, 2013 at 8:00 AM, ilgrosso <[email protected]> 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. > > > > -- > View this message in context: > http://syncope-dev.1063484.n5.nabble.com/PROPOSAL-Move-full-OSGi-support-to-1-2-0-tp5713275p5713409.html > Sent from the syncope-dev mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
