Sounds good. Thanks.
Do you also consider to split the feature? One problem of the ecj jar is
that it is > 2MB. As many
people will need the whiteboard feature I think it should be as small as
possible.
Christian
On 28.11.2014 09:44, Achim Nierbeck wrote:
I fixed that for Pax Web 4.1-SNAPSHOT
the ecj doesn't need to be wrapped anylonger
I'll backport this to 4.0.x line as soon as possible ...
regards, Achim
2014-11-28 9:38 GMT+01:00 Christian Schneider <[email protected]>:
I migrated a CXF pax exam itest to karaf 4.
The test failed with a MalformedUrlException that complained about the
wrap protocol.
The problem seems to be that the test dependencies are implemented as a
boot feature. The cxf-http feature references the http-whiteboard feature
which references the pax-http-whiteboard feature.
The pax feature uses wrap:mvn:org.eclipse.jdt.core.compiler/ecj/4.2.2
which seems to trigger the problem.
There are a few problems with that:
- At the time the wrap url is resolved the wrap feature does not yet seem
to be activated. So this fails. If we want to allow wrap in boot features
we need to fix this in karaf
- pax-http-whiteboard uses the wrap protocol. We might be able to pre wrap
the ecj compiler (in servicemix bundles?) to avoid this
- pax-http-whiteboard (version 4) now includes jsp support which is the
reason for the need of the ecj compiler. At least in cxf we do not need
this. So one other option might to extract the jsp support into its own
feature.
WDYT?
Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
