Christian
Looks like it is only happening with the DOSGI, if you try to update it
to 3.2.0 - but does the issue you see with updating DOSGi to 3.2.0
warrants -1 ?
Can't you just wait till 3.2.1 ?
Cheers, Sergey
On 11/09/17 11:30, Christian Schneider wrote:
Reverting my vote to -1 until we have a decision about the issues I
found below.
I just tried to update cxf-dosgi to cxf 3.2.0. I get an error when
building the multi bundle distro.
[ERROR] Failed to execute goal
org.apache.karaf.tooling:karaf-maven-plugin:4.1.2:features-export-meta-data
(features-add-to-repository) on project
cxf-dosgi-multibundle-distribution: Error populating repository: Can't
resolve artifact
org.ops4j.pax.cdi:pax-cdi-features:xml:features:[1.0.0.RC1,2): Failure
to find org.ops4j.pax.cdi:pax-cdi-features:xml:features:[1.0.0.RC1,2) in
https://repo.maven.apache.org/maven2 was cached in the local repository,
resolution will not be reattempted until the update interval of central
has elapsed or updates are forced
So it seems like the karaf-maven-plugin does not work with a version
range in the feature file. I think this is a bug and will report and fix
it in karaf.
Even if this might be a problem in karaf I wonder if using a range in
the CXF feature is a good idea at this time. It will probably affect all
karaf users that build a custom distro.
I also tried to install the cxf-jaxrs-cdi feature from cxf 3.2.0 in
karaf. The installation works but uses the 1.0.0-SNAPSHOT of the pax-cdi
feature which is probably not what users expect.
Christian
On 06.09.2017 20:14, Daniel Kulp wrote:
It’s been 2 years since the last major CXF release. We have well
over 100 JIRA’s of new features and enhancements that are only
targeted toward 3.2. Let’s get it out!
Staging repo:
https://repository.apache.org/content/repositories/orgapachecxf-1102/
Tag:
https://git-wip-us.apache.org/repos/asf?p=cxf.git;a=tag;h=79c1486ed9cf34d90a04d943ed72475500f83c48
Here is my +1
