[GitHub] cxf pull request: Tentative pom to create an OBR index for CXF run...

GitHub user mrulli opened a pull request: https://github.com/apache/cxf/pull/101 Tentative pom to create an OBR index for CXF runtime This is just tentative and I would like to collect some feedbacks for further improvements. In particular I don't like the fact that so many

Package versions in OSGI on master are still 3.1.2?

When I build on Master, I see things like: Export-Package: org.apache.cxf;version="3.1.2",org.apache.cxf.annotation s;version="3.1.2"

Re: elements here and there

BTW, the sticking point is: [ERROR] Failed to execute goal on project cxf-core: Could not resolve dependencies for project org.apache.cxf:cxf-core:bundle:3.2.0-SNAPSHOT: The following artifacts could not be resolved: org.springframework:org.springframework.aop:jar:2.5.6.SEC01,

Re: elements here and there

> On Dec 11, 2015, at 8:29 AM, Benson Margulies wrote: > When I try to build master in my usual config with a Nexus mirror, I > fail to find some Spring artifacts. > > Usually, this is because there's a element for some > repository I have to exempt from my mirror. The

Re: Karaf

Hey Benson, Seems like missed runtime dependency for Java EL implementation, org.glassfish/javax.el, never tried validation with Karaf though. Thanks. Best Regards, Andriy Redko BM> I'll stick to 3.0.2 on 3.1.x, and when master has it's OSGi versions BM> in order, off to 4. BM> Meanwhile,

Karaf

I propose to add some Karaf integration tests under osgi/karaf/itests. I will code them for Karaf 4 unless someone expresses deep sadness at this prospect. I will do this work on the 3.1.x branch and merge it to master, since the OSGi versions appear to be in an odd state on master.

Re: [1/2] cxf git commit: CXF-6705: supply hibernate with all of its dependencies.

Benson, I believe a bunch of these dependencies have version numbers defined in the parent pom. I know joda-time should, the stax-api, (which shouldn’t even be there as that’s pulled in via cxf-specs feature, likewise for woodstox), etc… Dan > On Dec 11, 2015, at 11:14 AM,

Re: elements here and there

I excluded these from the dependencies so this shouldn’t be an issue now. Thanks! Dan > On Dec 11, 2015, at 8:55 AM, Benson Margulies wrote: > > BTW, the sticking point is: > > [ERROR] Failed to execute goal on project cxf-core: Could not resolve > dependencies for

elements here and there

When I try to build master in my usual config with a Nexus mirror, I fail to find some Spring artifacts. Usually, this is because there's a element for some repository I have to exempt from my mirror. The question is, why are there these elements in several poms, and not just in the parent?

Import order

What's the correct order for the following? I'm not using Eclipse. import java.util.ArrayList; import java.util.List; //CHECKSTYLE:OFF import javax.validation.ValidationProviderResolver; import javax.validation.ValidatorFactory; import javax.validation.spi.ValidationProvider; import

Re: Karaf

I'll stick to 3.0.2 on 3.1.x, and when master has it's OSGi versions in order, off to 4. Meanwhile, I have a test case of mine which seems to work great with the code I was about to commit. But when I put, essentially, the same test case into the existing itest, and run with Karaf 3, I am back