So I started experimenting a bit, and the second solution seems to be very
easy to implement.
I've been able to deploy an upgraded pax-web 4.2.3-SNAPSHOT with specific
Karaf 4 features and install pax-http without any problems (but the change
of a few imports in karaf to support pax-web 4.x).
So
+1 to handle older specs.
--
Uwe Barthel bart...@x-reizend.de
On June 11, 2015 5:22:32 PM Jamie G. jamie.goody...@gmail.com wrote:
Long as the patched Karaf can handle the older specs too then all is good :)
Once the new spec is in place I'll talk to the SDN community about the
changes and
Hi Guillaume,
I would do for the second one, I think it's easier and make sense for
backward compatibility.
Regards
JB
On 06/11/2015 08:51 AM, Guillaume Nodet wrote:
I want to work on a nice way to migrate to the new 1.3.0 schema for
features for downstream projects (pax-web, cxf,
I want to work on a nice way to migrate to the new 1.3.0 schema for
features for downstream projects (pax-web, cxf, activemq, etc…).
I have two possible ways in mind which I'd like to discuss.
The first one would be to write an additional mojo for the maven plugin
which would translate the new
2015-06-11 17:21 GMT+02:00 Jamie G. jamie.goody...@gmail.com:
Long as the patched Karaf can handle the older specs too then all is good
:)
Definitely !
What I've done, is very simple. It's just about removing the unsupported
xml elements when parsing the xml for a 1.3.0 schema, so that jaxb
It looks good to me !
Thanks,
Regards
JB
On 06/11/2015 05:26 PM, Guillaume Nodet wrote:
2015-06-11 17:21 GMT+02:00 Jamie G. jamie.goody...@gmail.com:
Long as the patched Karaf can handle the older specs too then all is good
:)
Definitely !
What I've done, is very simple. It's just about
Long as the patched Karaf can handle the older specs too then all is good :)
Once the new spec is in place I'll talk to the SDN community about the
changes and help them migrate as well.
Cheers,
Jamie
On Thu, Jun 11, 2015 at 12:33 PM, Guillaume Nodet gno...@apache.org wrote:
So I started
