FYI.
I proxied the following repositories in our Nexus repository server (they
are listed on the FAQ on the Springsource EBR):
<repository>
<id>com.springsource.repository.bundles.release</id>
<name>SpringSource Enterprise Bundle Repository - SpringSource Bundle
Releases</name>
<url>http://repository.springsource.com/maven/bundles/release</url>
</repository>
<repository>
<id>com.springsource.repository.bundles.external</id>
<name>SpringSource Enterprise Bundle Repository - External Bundle
Releases</name>
<url>http://repository.springsource.com/maven/bundles/external</url>
</repository>
I then browsed them via Nexus Web GUI and found that the 3.2.4.RELEASE is
available there. I was also able to build correctly now.
So, in short:
- The 3.2.4.RELEASE version of Spring IS available in the Springsource EBR
even if you can't find it when you use their search facility. So, no bug in
Karaf's feature file. It's just a little sad that you cant find these
artifacts on Maven central.
- The camel-spring feature uses the version range "[3.1,3.3)" for the
spring feature which means that it will try to pick up the 3.2.4.RELEASE
version of the spring feature which is what caused my problems at first.
My problems are solved. Hope this helps anyone else encountering these
problems.
/Bengt
2013/10/15 Achim Nierbeck <[email protected]>
> plainly, no.
> I've no idea what spring is up to.
>
> I just can help you with stuff I've seen already asked. And people told us
> that 3.2.4 is not available as OSGi bundles from EBR.
> As you can see at the issue that I linked for your convenience.
>
>
> regards, Achim
>
>
>
>
> 2013/10/15 Bengt Rodehav <[email protected]>
>
>> 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/>
>>>
>>
>>
>
>
> --
>
> 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/>
>
