Hi Colm, You are right, the versions seem to be correct. I will have a look into the commons-collections bundle again ;)
Regards, Ernst 2013/6/25 Colm O hEigeartaigh <cohei...@apache.org> > Hi Ernst, > > Have you started the commons-collection bundle in your container? I don't > see anything wrong with the configuration + exactly the same values are > used in Syncope 1.1.0 as in 1.1.2. > > Colm. > > > On Wed, Jun 19, 2013 at 9:29 AM, ernst Developer < > ernst.develo...@gmail.com> wrote: > >> Hi, >> >> Until today we were using Syncope version 1.1.0. We run this version of >> Syncope on Virgo (OSGI). Pefect. >> >> Today I ran the maven archetype to create a Syncope 1.1.2 instance. I had >> to copy over the maven plugin maven-bundle-plugin to the new created >> project (core and console pom.xml had to be changed). Without any further >> changes I deploy the war files to Virgo. >> >> *On deployment I get an error:* >> *An Import-Package could not be resolved. Resolver error data >> <Import-Package: org.apache.commons.collections.keyvalue; >> version="[3.2.0,4.0.0)">. Caused by missing constraint in bundle >> <org.apache.syncope.core_6.1.0.SNAPSHOT>* >> * constraint: <Import-Package: >> org.apache.commons.collections.keyvalue; version="[3.2.0,4.0.0)">* >> >> *If I run a maven dependeny:tree, I get the following result on >> commons-collections:* >> * +- org.apache.velocity:velocity:jar:1.7:compile* >> *[INFO] | \- commons-collections:commons-collections:jar:3.2.1:compile* >> >> *This seems to be the wrong version, because in the maven-bundle-plugin >> is defined:* >> *org.apache.commons.collections.keyvalue;version="[3.2,4)", >> * >> >> My question: is this a configuration problem in the Syncope project, or >> am I doing something wrong here? >> >> Kind regards, >> Ernst >> > > > > -- > Colm O hEigeartaigh > > Talend Community Coder > http://coders.talend.com >
