Even if it's in feature file, it's use Pax URL Aether to resolve the
URL, so I think it's in Pax URL.
By the way, Karaf 3.0.2/4.0.0 have been upgraded to Pax URL 2.0.1.
Regards
JB
On 09/16/2014 10:46 AM, Achim Nierbeck wrote:
one more question, is it in a features file or through the shell that you
get this issue?
Cause if it's the features file it could actually be an issue of Karaf
itself :D
Which should already be fixed for 3.0.2 and 2.3.8 and 4.0.0 of Karaf which
are only partially released ;)
regards, Achim
2014-09-16 10:43 GMT+02:00 Harald Wellmann <[email protected]>:
OK, I'll try the wrap for now. If there's really an issue in Pax URL, we
should fix it there, and I'm happy to do so, if you can point out the API
that Karaf is using here.
Thanks,
Harald
2014-09-16 10:39 GMT+02:00 Jean-Baptiste Onofré <[email protected]>:
Good idea Achim !
Anyway, it's something that we have to address at Pax URL.
Let me look for the Jira (else I will create one).
Regards
JB
On 09/16/2014 10:37 AM, Achim Nierbeck wrote:
There is a simple workaround available for that.
wrap the url :)
wrap:mvn:org.eclipse.jdt.core.compiler/ecj/4.4
that's what I did for Pax Web ;)
regards, Achim
2014-09-16 10:32 GMT+02:00 Harald Wellmann <[email protected]>:
Karaf 3.0.1 just gave me the following exception when I tried to
install
the ECJ bundle:
Manifest not present in the first entry of the zip
mvn:org.eclipse.jdt.core.compiler/ecj/4.4
I believe it's folklore that the manifest has to be the first entry in
a
JAR, but in fact, the spec [1] doesn't say so.
So why doesn't Karaf simply continue scanning the JAR entries until the
manifest is found?
[1] http://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html
Best regards,
Harald
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
