regarding the last question, only with OBR resolving enabled (and to my knowledge you need an OBR-resolver present) you'll achiev what you want, and only if the dependency is gracefull with the version range, so if the camel-cxf feature asks for 2.3.0 as minimum it'll be satisfied if 2.3.1 is present and won't look for a 2.3.2, if it's requesting 2.3.2 it'll always look for 2.3.2 even if a 2.3.1 is available and might be good enough.
regards, Achim 2013/7/30 Michael Täschner <[email protected]> > I checked and fixed an issue with our Maven proxy server where the spring > repos were configured but not mapped to the internally available repository > groups. > > No I do not use OBR resolver. Goal is to have spring pre-installed via > customized karaf assembly but I tested via features:install command on > karaf shell. > > Any feedback regarding my second question available? Should installation > of a feature (camel-cxf) that has the spring feature as dependency install > the latest spring feature even though a matching spring feature with lower > version is already installed ? > > Regards, > Michael > > > 2013/7/30 Achim Nierbeck <[email protected]> > >> Could it be that your local repo does have entries for spring 3.2.3? >> Did you use the OBR resolver, and did you install the obr feature, in >> that case it should work as you guessed. >> >> regards, Achim >> >> >> 2013/7/25 Michael Täschner <[email protected]> >> >>> Hi, >>> >>> I do have EBR (release and external) configured in our proxy maven repo >>> but was unable to resolve artifacts against it today. >>> >>> Still, what about my second question: why does Karaf try to install the >>> spring/3.2.3 feature even if spring/3.1.4 is already installed (manually) >>> and satisfies the spring;version="[3.1,4)" requirement of camel-cxf feature >>> (2.11.1) ? Should it not try to check for already provided features/bundles >>> to satisfy requirements ? >>> >>> Thanks and Regards, >>> Michael >>> >>> >>> 2013/7/24 Jason <[email protected]> >>> >>>> Seems like I was only using the external repository, but not the >>>> release repository. Adding both works. >>>> >>>> http://ebr.springsource.com/repository/app/faq#q8 >>>> >>>> Thanks, >>>> Jason >>>> >>>> >>>> On 07/24/2013 03:26 PM, Achim Nierbeck wrote: >>>> >>>> You'll need to add the http://ebr.springsource.com/repository/app/ >>>> since the latest Spring jars are no osgi bundles anymore. >>>> >>>> regards, Achim >>>> >>>> >>>> 2013/7/24 Jason <[email protected]> >>>> >>>>> Adding to this.... >>>>> >>>>> I have a Karaf customized distribution project ( >>>>> http://karaf.apache.org/manual/latest-2.3.x/developers-guide/custom-distribution.html) >>>>> where when I use Karaf 2.3.2, I get the following build error: >>>>> >>>>> [ERROR] Failed to execute goal >>>>> org.apache.karaf.tooling:features-maven-plugin:2.3.2:add-features-to-repo >>>>> (add-features-to-repo) on project mapseq-server: Can't resolve bundle >>>>> org.springframework:org.springframework.beans:jar:3.2.3.RELEASE: Could >>>>> not find artifact >>>>> org.springframework:org.springframework.beans:jar:3.2.3.RELEASE >>>>> >>>>> >>>>> Using the following repositories: >>>>> >>>>> [ERROR] renci.repository >>>>> (http://ci-dev.renci.org/nexus/content/repositories/public, >>>>> releases=true, snapshots=true), >>>>> >>>>> [ERROR] fusesource >>>>> (http://repo.fusesource.com/nexus/content/groups/public, releases=true, >>>>> snapshots=false), >>>>> >>>>> [ERROR] apache-public >>>>> (https://repository.apache.org/content/groups/public/, releases=true, >>>>> snapshots=true), >>>>> >>>>> [ERROR] prime-repo (http://repository.primefaces.org, releases=true, >>>>> snapshots=true), >>>>> >>>>> [ERROR] com.springsource.repository.bundles.external >>>>> (http://repository.springsource.com/maven/bundles/external, >>>>> releases=true, snapshots=true), >>>>> >>>>> [ERROR] ibiblio.repository >>>>> (http://mirrors.ibiblio.org/pub/mirrors/maven2, releases=true, >>>>> snapshots=true), >>>>> >>>>> [ERROR] biojava-maven-repo (http://www.biojava.org/download/maven, >>>>> releases=true, snapshots=true), >>>>> >>>>> [ERROR] central (http://repo1.maven.org/maven2, releases=true, >>>>> snapshots=false) >>>>> >>>>> >>>>> When I revert back to Karaf 2.3.1, the project builds cleanly. >>>>> >>>>> Regards, >>>>> Jason >>>>> >>>>> >>>>> >>>>> On 07/24/2013 06:08 AM, Michael Täschner wrote: >>>>> >>>>> Hi again, >>>>> >>>>> being curious I tried the same with Karaf 2.3.1. As >>>>> spring/3.2.3.RELEASE is not available in the standard features repository, >>>>> camel-cxf seems to be content with using spring/3.1.4.RELEASE. I wonder >>>>> why >>>>> using Karaf 2.3.2 it tries to install spring/3.2.3.RELEASE even though >>>>> spring/3.1.4.RELEASE already active and fullfilling the version >>>>> requirement >>>>> (see first mail) ? >>>>> >>>>> So what could be a workaround to get camel-cxf running in Karaf 2.3.2 >>>>> ? >>>>> >>>>> Thanks and Regards, >>>>> Michael >>>>> >>>>> P.S.: sorry for the bad formatting of the initial mail - I don't know >>>>> how it turned out like this using gmail web client ?! >>>>> >>>>> >>>>> 2013/7/24 Michael Täschner <[email protected]> >>>>> >>>>>> Hi, >>>>>> >>>>>> I am trying to install camel-cxf feature in plain Karaf 2.3.2 >>>>>> container via camel feature repository. This results in error: >>>>>> >> Error executing command: URL >>>>>> [mvn:org.springframework/org.springframework.core/3.2.3.RELEASE] could >>>>>> not >>>>>> be resolved. >>>>>> >>>>>> I looked at the spring repositories and see the artifacts are rather >>>>>> located under: mvn:org.springframework/spring-core/3.2.3.RELEASE (using >>>>>> repos declared by spring: " >>>>>> http://maven.springframework.org/release/org/springframework/"; , " >>>>>> http://repo.springsource.org/release/org/springframework/";). >>>>>> Strangely enough the Spring Enterprise Bundle Repository (EBR) uses the >>>>>> "org.springframework.core" notation as declared in the karaf feature but >>>>>> the repository where it is hosted is not accessible currently: " >>>>>> http://repository.springsource.com/maven/bundles/release"; >>>>>> >>>>>> So my questions are: >>>>>> - the spring/3.0.7 and spring/3.1.4 use the >>>>>> org.springframework/spring-core notation and bundles can be resolved. Is >>>>>> it >>>>>> a bug that for spring/3.2.3 the >>>>>> org.springframework/org.springframework.core notation is used ? >>>>>> - camel requires camel-spring feature which requires bundle spring >>>>>> with version="[3.1,3.3)" - why does the same error message as above occur >>>>>> if I install spring/3.1.4.RELEASE via karaf console before trying to >>>>>> install camel-cxf again ? >>>>>> >>>>>> Thanks and Regards, >>>>>> Michael >>>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> Apache Karaf <http://karaf.apache.org/> Committer & PMC >>>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> >>>> Committer & Project Lead >>>> OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> >>>> Commiter & Project Lead >>>> blog <http://notizblog.nierbeck.de/> >>>> >>>> >>>> >>> >> >> >> -- >> >> Apache Karaf <http://karaf.apache.org/> Committer & PMC >> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer >> & Project Lead >> OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> >> Commiter & Project Lead >> blog <http://notizblog.nierbeck.de/> >> > > -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project Lead blog <http://notizblog.nierbeck.de/>
