But...
I installed a fresh Karaf 2.3.3. I then used features:chooseurl to get
access to latest Camel features. Then I did "features:install
camel-spring". This succeeded and in that process spring-aop version
3.2.4.RELEASE was installed. How is this possible if that version doesn't
exist?
I noticed that the org.ops4j.pax.url.mvn.cfg file contains the following:
org.ops4j.pax.url.mvn.repositories= \
http://repo1.maven.org/maven2@id=central, \
http://svn.apache.org/repos/asf/servicemix/m2-repo@id=servicemix, \
http://repository.springsource.com/maven/bundles/release@id=springsource.release,
\
http://repository.springsource.com/maven/bundles/external@id=springsource.external,
\
http://oss.sonatype.org/content/repositories/releases/@id=sonatype
So I guess it is downloading directly from the Spring source EBR.
Can you explain this Achim?
/Bengt
2013/10/14 Achim Nierbeck <[email protected]>
> Hi Bengt,
>
> it might very well be that this is an issue with Camel, cause as you can
> see at [1].
> We upgraded to Spring 3.2.4 but no OSGi bundles are available at the EBR.
>
> regards, Achim
>
> [1] - https://issues.apache.org/jira/browse/KARAF-2458
>
>
>
> 2013/10/14 Bengt Rodehav <[email protected]>
>
>> See what you mean Achim... I can only find up to version 3.2.3 in the
>> Spring EBR not version 3.2.4. Then I would definitely call it a bug since
>> standard-2.3.3-features.xm
>> is referencing an artifact version that doesn't exist.
>>
>> I don't reference the 3.2.4 version myself but I think my upgrade to
>> Camel 2.12.1 caused this to happen.
>>
>> I will investigate this further but could this mean that Camel 2.12.1
>> (its features) is incompatible with Karaf 2.3.3?
>>
>> /Bengt
>>
>>
>> 2013/10/14 Bengt Rodehav <[email protected]>
>>
>>> OK - thanks. Will try adding the Spring repo tomorrow. Really strange
>>> that they don't use Maven central anymore. It complicates things for
>>> everyone.
>>>
>>> /Bengt
>>>
>>>
>>> 2013/10/14 Minto van der Sluis <[email protected]>
>>>
>>>> Hi Bengt,
>>>>
>>>> No it's not a bug.
>>>>
>>>> Have a look at https://issues.apache.org/jira/browse/KARAF-2430
>>>>
>>>> Regards,
>>>>
>>>> Minto
>>>>
>>>> Bengt Rodehav schreef op 14-10-2013 17:30:
>>>> > I just upgraded to from Karaf 2.3.1 to 2.3.3. When I build my custom
>>>> > server I try to download all the dependencies. I tried to use Spring
>>>> > version 3.2.4.RELEASE since that is now available in Karaf.
>>>> >
>>>> > Below is an excerpt from the "standard-2.3.3-features.xml" included in
>>>> > Karaf 2.3.3:
>>>> >
>>>> > <!-- Spring 3.2 support -->
>>>> >
>>>> > <feature name="spring" description="Spring 3.2.x support"
>>>> > version="3.2.4.RELEASE" resolver="(obr)">
>>>> > <bundle dependency="true"
>>>> >
>>>> start-level="30">mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.aopalliance/1.0_6</bundle>
>>>> > <bundle
>>>> >
>>>> start-level="30">mvn:org.springframework/org.springframework.core/3.2.4.RELEASE</bundle>
>>>> > <bundle
>>>> >
>>>> start-level="30">mvn:org.springframework/org.springframework.expression/3.2.4.RELEASE</bundle>
>>>> > <bundle
>>>> >
>>>> start-level="30">mvn:org.springframework/org.springframework.beans/3.2.4.RELEASE</bundle>
>>>> > <bundle
>>>> >
>>>> start-level="30">mvn:org.springframework/org.springframework.aop/3.2.4.RELEASE</bundle>
>>>> > <bundle
>>>> >
>>>> start-level="30">mvn:org.springframework/org.springframework.context/3.2.4.RELEASE</bundle>
>>>> > <bundle
>>>> >
>>>> start-level="30">mvn:org.springframework/org.springframework.context.support/3.2.4.RELEASE</bundle>
>>>> > </feature>
>>>> >
>>>> > All artifact names are "org.springframework.xyz". But in Maven central
>>>> > they seem to be called "spring-aop" etc. Is this a bug?
>>>> >
>>>> > /Bengt
>>>>
>>>>
>>>
>>
>
>
> --
>
> 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/>
>
