Well guys,
I investigated.
Actually, Pax Web 4.2.8 already provides the capability header in the
MANIFEST. Unfortunately, the WebContainer service is not part of this
header :(
So basically, we could consider this as a bug in Pax Web.
It requires a new Pax Web 4.2.9 release.
What I'm proposing:
- let's continue the Karaf 4.0.6 vote ending and release this version
- in the mean time, I'm preparing Pax Web 4.2.9 release
- once, Pax Web 4.2.9 will be released, I will quickly prepare Karaf
4.0.7 including Pax Web 4.2.9
I think it makes sense to move this way.
Deal ?
Regards
JB
On 08/26/2016 02:36 PM, Jean-Baptiste Onofré wrote:
Fair enough, but we have to stand quickly.
IMHO, as it doesn't cost so much, I would cancel this vote and fix that
in Pax Web.
I can do it today and start a new vote tonight or tomorrow.
Regards
JB
On 08/26/2016 02:31 PM, Achim Nierbeck wrote:
That's a good question.
In light of that question, it might be good to cancel this vote so we can
fix those capabilities on Pax-Web and redo the release on a Pax-Web 4.2.9
Thoughts?
regards, Achim
2016-08-26 14:23 GMT+02:00 Markus Rathgeb <maggu2...@gmail.com>:
I propose:
- don't cancel this vote as it's an expected behavior
- fix the service capability in Pax Web
Thoughts ?
One remaining question:
The Pax Web version and so the Pax Web features that are shipped with
Karaf 4.0.6 will contain the service capability or do not have the
capability?
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
