You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Harald Wellmann <hw...@gmail.com> on 2014/09/16 10:32:11 UTC
Manifest position
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
Re: Manifest position
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Harald,
I think the problem is not in Karaf itself, but more on Pax URL.
AFAIR, I already created a Jira at Pax URL for that.
Let me double check.
Regards
JB
On 09/16/2014 10:32 AM, Harald Wellmann wrote:
> 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é
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Manifest position
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Yes, 2.1.0, sorry.
Regards
JB
On 09/16/2014 10:57 AM, Harald Wellmann wrote:
>> By the way, Karaf 3.0.2/4.0.0 have been upgraded to Pax URL 2.0.1.
>>
>>
> You mean Pax URL 2.1.0?
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Manifest position
Posted by Harald Wellmann <hw...@gmail.com>.
I just tried
bundle:install mvn:org.eclipse.jdt.core.compiler/ecj/4.4
and that works without problems. So it seems the issue is related to
feature resolution.
2014-09-16 10:57 GMT+02:00 Harald Wellmann <hw...@gmail.com>:
>
> By the way, Karaf 3.0.2/4.0.0 have been upgraded to Pax URL 2.0.1.
>>
>>
> You mean Pax URL 2.1.0?
>
Re: Manifest position
Posted by Harald Wellmann <hw...@gmail.com>.
> By the way, Karaf 3.0.2/4.0.0 have been upgraded to Pax URL 2.0.1.
>
>
You mean Pax URL 2.1.0?
Re: Manifest position
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
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 <hw...@gmail.com>:
>
>> 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é <jb...@nanthrax.net>:
>>
>>> 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 <hw...@gmail.com>:
>>>>
>>>> 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é
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>
>
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Manifest position
Posted by Achim Nierbeck <bc...@googlemail.com>.
ha,
no 2.3.8 is on Vote right now, while 3.0.2 and 4.0.0 are still snapshots :D
regards, Achim
2014-09-16 10:55 GMT+02:00 Harald Wellmann <hw...@gmail.com>:
> It's a features file containing a feature with the following line:
>
> <bundle>mvn:org.eclipse.jdt.core.compiler/ecj/4.4</bundle>
>
> I got the exception when installing the feature from the Karaf shell via
> feature:install.
>
> BTW, what do you mean by "partially released" - only the good parts? ;-)
>
> Regards,
> Harald
>
> 2014-09-16 10:46 GMT+02:00 Achim Nierbeck <bc...@googlemail.com>:
>
> > 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 <hw...@gmail.com>:
> >
> > > 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é <jb...@nanthrax.net>:
> > >
> > > > 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 <hwellmann.de@gmail.com
> >:
> > > >>
> > > >> 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é
> > > > jbonofre@apache.org
> > > > http://blog.nanthrax.net
> > > > Talend - http://www.talend.com
> > > >
> > >
> >
> >
> >
> > --
> >
> > Apache Member
> > Apache Karaf <http://karaf.apache.org/> Committer & PMC
> > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer
> &
> > Project Lead
> > blog <http://notizblog.nierbeck.de/>
> >
> > Software Architect / Project Manager / Scrum Master
> >
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Software Architect / Project Manager / Scrum Master
Re: Manifest position
Posted by Achim Nierbeck <bc...@googlemail.com>.
Usually there is no issue with jar generated bundles. To me it always
happened if the bundle has been altered after wards.
Regards, Achim
sent from mobile device
Am 17.09.2014 03:46 schrieb "Matt Sicker" <bo...@gmail.com>:
> I've even had this error in the past when the manifest WAS the first file
> in the zip. The jar command always makes it first (or generates one if none
> is there). Never figured out why it happened because it was somewhat
> random, and reinstalling things tended to fix it.
>
> On 16 September 2014 04:46, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>
> > It's what I said to Achim on IRC: it's already fixed for 3.0.2.
> >
> > Regards
> > JB
> >
> >
> > On 09/16/2014 11:12 AM, Harald Wellmann wrote:
> >
> >> I've just downloaded the latest 3.0.2 SNAPSHOT and I can't reproduce the
> >> issue, so it seems to be fixed already, as Achim suggested.
> >>
> >> Regards,
> >> Harald
> >>
> >> 2014-09-16 11:03 GMT+02:00 Jean-Baptiste Onofré <jb...@nanthrax.net>:
> >>
> >> FYI:
> >>>
> >>> https://issues.apache.org/jira/browse/KARAF-3232
> >>>
> >>> Regards
> >>> JB
> >>>
> >>>
> >>> On 09/16/2014 11:01 AM, Jean-Baptiste Onofré wrote:
> >>>
> >>> Actually, the problem is in Karaf (I thought you use bundle:install).
> >>>>
> >>>> It works fine using bundle:install directly:
> >>>>
> >>>> karaf@root()> bundle:install
> mvn:org.eclipse.jdt.core.compiler/ecj/4.4
> >>>> Bundle ID: 78
> >>>> karaf@root()> bundle:start 78
> >>>> karaf@root()>
> >>>>
> >>>> I'm creating the corresponding Jira and fix that for 3.0.2 (planned on
> >>>> Friday).
> >>>>
> >>>> Regards
> >>>> JB
> >>>>
> >>>> On 09/16/2014 10:55 AM, Harald Wellmann wrote:
> >>>>
> >>>> It's a features file containing a feature with the following line:
> >>>>>
> >>>>> <bundle>mvn:org.eclipse.jdt.core.compiler/ecj/4.4</bundle>
> >>>>>
> >>>>> I got the exception when installing the feature from the Karaf shell
> >>>>> via
> >>>>> feature:install.
> >>>>>
> >>>>> BTW, what do you mean by "partially released" - only the good parts?
> >>>>> ;-)
> >>>>>
> >>>>> Regards,
> >>>>> Harald
> >>>>>
> >>>>> 2014-09-16 10:46 GMT+02:00 Achim Nierbeck <bc...@googlemail.com>:
> >>>>>
> >>>>> 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 <hwellmann.de@gmail.com
> >:
> >>>>>>
> >>>>>> 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é <jb...@nanthrax.net>:
> >>>>>>>
> >>>>>>> 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 <
> hwellmann.de@gmail.com
> >>>>>>>>> >:
> >>>>>>>>>
> >>>>>>>>> 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é
> >>>>>>>> jbonofre@apache.org
> >>>>>>>> http://blog.nanthrax.net
> >>>>>>>> Talend - http://www.talend.com
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>> --
> >>>>>>
> >>>>>> Apache Member
> >>>>>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> >>>>>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
> >>>>>> Committer &
> >>>>>> Project Lead
> >>>>>> blog <http://notizblog.nierbeck.de/>
> >>>>>>
> >>>>>> Software Architect / Project Manager / Scrum Master
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>> --
> >>> Jean-Baptiste Onofré
> >>> jbonofre@apache.org
> >>> http://blog.nanthrax.net
> >>> Talend - http://www.talend.com
> >>>
> >>>
> >>
> > --
> > Jean-Baptiste Onofré
> > jbonofre@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
>
Re: Manifest position
Posted by Matt Sicker <bo...@gmail.com>.
I've even had this error in the past when the manifest WAS the first file
in the zip. The jar command always makes it first (or generates one if none
is there). Never figured out why it happened because it was somewhat
random, and reinstalling things tended to fix it.
On 16 September 2014 04:46, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> It's what I said to Achim on IRC: it's already fixed for 3.0.2.
>
> Regards
> JB
>
>
> On 09/16/2014 11:12 AM, Harald Wellmann wrote:
>
>> I've just downloaded the latest 3.0.2 SNAPSHOT and I can't reproduce the
>> issue, so it seems to be fixed already, as Achim suggested.
>>
>> Regards,
>> Harald
>>
>> 2014-09-16 11:03 GMT+02:00 Jean-Baptiste Onofré <jb...@nanthrax.net>:
>>
>> FYI:
>>>
>>> https://issues.apache.org/jira/browse/KARAF-3232
>>>
>>> Regards
>>> JB
>>>
>>>
>>> On 09/16/2014 11:01 AM, Jean-Baptiste Onofré wrote:
>>>
>>> Actually, the problem is in Karaf (I thought you use bundle:install).
>>>>
>>>> It works fine using bundle:install directly:
>>>>
>>>> karaf@root()> bundle:install mvn:org.eclipse.jdt.core.compiler/ecj/4.4
>>>> Bundle ID: 78
>>>> karaf@root()> bundle:start 78
>>>> karaf@root()>
>>>>
>>>> I'm creating the corresponding Jira and fix that for 3.0.2 (planned on
>>>> Friday).
>>>>
>>>> Regards
>>>> JB
>>>>
>>>> On 09/16/2014 10:55 AM, Harald Wellmann wrote:
>>>>
>>>> It's a features file containing a feature with the following line:
>>>>>
>>>>> <bundle>mvn:org.eclipse.jdt.core.compiler/ecj/4.4</bundle>
>>>>>
>>>>> I got the exception when installing the feature from the Karaf shell
>>>>> via
>>>>> feature:install.
>>>>>
>>>>> BTW, what do you mean by "partially released" - only the good parts?
>>>>> ;-)
>>>>>
>>>>> Regards,
>>>>> Harald
>>>>>
>>>>> 2014-09-16 10:46 GMT+02:00 Achim Nierbeck <bc...@googlemail.com>:
>>>>>
>>>>> 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 <hw...@gmail.com>:
>>>>>>
>>>>>> 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é <jb...@nanthrax.net>:
>>>>>>>
>>>>>>> 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 <hwellmann.de@gmail.com
>>>>>>>>> >:
>>>>>>>>>
>>>>>>>>> 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é
>>>>>>>> jbonofre@apache.org
>>>>>>>> http://blog.nanthrax.net
>>>>>>>> Talend - http://www.talend.com
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Apache Member
>>>>>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>>>>>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
>>>>>> Committer &
>>>>>> Project Lead
>>>>>> blog <http://notizblog.nierbeck.de/>
>>>>>>
>>>>>> Software Architect / Project Manager / Scrum Master
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>> --
>>> Jean-Baptiste Onofré
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
--
Matt Sicker <bo...@gmail.com>
Re: Manifest position
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
It's what I said to Achim on IRC: it's already fixed for 3.0.2.
Regards
JB
On 09/16/2014 11:12 AM, Harald Wellmann wrote:
> I've just downloaded the latest 3.0.2 SNAPSHOT and I can't reproduce the
> issue, so it seems to be fixed already, as Achim suggested.
>
> Regards,
> Harald
>
> 2014-09-16 11:03 GMT+02:00 Jean-Baptiste Onofré <jb...@nanthrax.net>:
>
>> FYI:
>>
>> https://issues.apache.org/jira/browse/KARAF-3232
>>
>> Regards
>> JB
>>
>>
>> On 09/16/2014 11:01 AM, Jean-Baptiste Onofré wrote:
>>
>>> Actually, the problem is in Karaf (I thought you use bundle:install).
>>>
>>> It works fine using bundle:install directly:
>>>
>>> karaf@root()> bundle:install mvn:org.eclipse.jdt.core.compiler/ecj/4.4
>>> Bundle ID: 78
>>> karaf@root()> bundle:start 78
>>> karaf@root()>
>>>
>>> I'm creating the corresponding Jira and fix that for 3.0.2 (planned on
>>> Friday).
>>>
>>> Regards
>>> JB
>>>
>>> On 09/16/2014 10:55 AM, Harald Wellmann wrote:
>>>
>>>> It's a features file containing a feature with the following line:
>>>>
>>>> <bundle>mvn:org.eclipse.jdt.core.compiler/ecj/4.4</bundle>
>>>>
>>>> I got the exception when installing the feature from the Karaf shell via
>>>> feature:install.
>>>>
>>>> BTW, what do you mean by "partially released" - only the good parts? ;-)
>>>>
>>>> Regards,
>>>> Harald
>>>>
>>>> 2014-09-16 10:46 GMT+02:00 Achim Nierbeck <bc...@googlemail.com>:
>>>>
>>>> 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 <hw...@gmail.com>:
>>>>>
>>>>> 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é <jb...@nanthrax.net>:
>>>>>>
>>>>>> 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 <hw...@gmail.com>:
>>>>>>>>
>>>>>>>> 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é
>>>>>>> jbonofre@apache.org
>>>>>>> http://blog.nanthrax.net
>>>>>>> Talend - http://www.talend.com
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Apache Member
>>>>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>>>>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
>>>>> Committer &
>>>>> Project Lead
>>>>> blog <http://notizblog.nierbeck.de/>
>>>>>
>>>>> Software Architect / Project Manager / Scrum Master
>>>>>
>>>>>
>>>>
>>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Manifest position
Posted by Achim Nierbeck <bc...@googlemail.com>.
One reminder though :)
If the feature should be "compatible" with older versions of Karaf, you'll
need to add the wrap: anyway. It's what I did for Pax Web 4.0 too. That
version is supposed to play nicely with Karaf 4 (not released yet) but some
people are already using it with older Karaf versions.
regards, Achim
2014-09-16 11:12 GMT+02:00 Harald Wellmann <hw...@gmail.com>:
> I've just downloaded the latest 3.0.2 SNAPSHOT and I can't reproduce the
> issue, so it seems to be fixed already, as Achim suggested.
>
> Regards,
> Harald
>
> 2014-09-16 11:03 GMT+02:00 Jean-Baptiste Onofré <jb...@nanthrax.net>:
>
> > FYI:
> >
> > https://issues.apache.org/jira/browse/KARAF-3232
> >
> > Regards
> > JB
> >
> >
> > On 09/16/2014 11:01 AM, Jean-Baptiste Onofré wrote:
> >
> >> Actually, the problem is in Karaf (I thought you use bundle:install).
> >>
> >> It works fine using bundle:install directly:
> >>
> >> karaf@root()> bundle:install mvn:org.eclipse.jdt.core.compiler/ecj/4.4
> >> Bundle ID: 78
> >> karaf@root()> bundle:start 78
> >> karaf@root()>
> >>
> >> I'm creating the corresponding Jira and fix that for 3.0.2 (planned on
> >> Friday).
> >>
> >> Regards
> >> JB
> >>
> >> On 09/16/2014 10:55 AM, Harald Wellmann wrote:
> >>
> >>> It's a features file containing a feature with the following line:
> >>>
> >>> <bundle>mvn:org.eclipse.jdt.core.compiler/ecj/4.4</bundle>
> >>>
> >>> I got the exception when installing the feature from the Karaf shell
> via
> >>> feature:install.
> >>>
> >>> BTW, what do you mean by "partially released" - only the good parts?
> ;-)
> >>>
> >>> Regards,
> >>> Harald
> >>>
> >>> 2014-09-16 10:46 GMT+02:00 Achim Nierbeck <bc...@googlemail.com>:
> >>>
> >>> 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 <hw...@gmail.com>:
> >>>>
> >>>> 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é <jb...@nanthrax.net>:
> >>>>>
> >>>>> 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 <hwellmann.de@gmail.com
> >:
> >>>>>>>
> >>>>>>> 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é
> >>>>>> jbonofre@apache.org
> >>>>>> http://blog.nanthrax.net
> >>>>>> Talend - http://www.talend.com
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>>
> >>>> Apache Member
> >>>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> >>>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
> >>>> Committer &
> >>>> Project Lead
> >>>> blog <http://notizblog.nierbeck.de/>
> >>>>
> >>>> Software Architect / Project Manager / Scrum Master
> >>>>
> >>>>
> >>>
> >>
> > --
> > Jean-Baptiste Onofré
> > jbonofre@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Software Architect / Project Manager / Scrum Master
Re: Manifest position
Posted by Harald Wellmann <hw...@gmail.com>.
I've just downloaded the latest 3.0.2 SNAPSHOT and I can't reproduce the
issue, so it seems to be fixed already, as Achim suggested.
Regards,
Harald
2014-09-16 11:03 GMT+02:00 Jean-Baptiste Onofré <jb...@nanthrax.net>:
> FYI:
>
> https://issues.apache.org/jira/browse/KARAF-3232
>
> Regards
> JB
>
>
> On 09/16/2014 11:01 AM, Jean-Baptiste Onofré wrote:
>
>> Actually, the problem is in Karaf (I thought you use bundle:install).
>>
>> It works fine using bundle:install directly:
>>
>> karaf@root()> bundle:install mvn:org.eclipse.jdt.core.compiler/ecj/4.4
>> Bundle ID: 78
>> karaf@root()> bundle:start 78
>> karaf@root()>
>>
>> I'm creating the corresponding Jira and fix that for 3.0.2 (planned on
>> Friday).
>>
>> Regards
>> JB
>>
>> On 09/16/2014 10:55 AM, Harald Wellmann wrote:
>>
>>> It's a features file containing a feature with the following line:
>>>
>>> <bundle>mvn:org.eclipse.jdt.core.compiler/ecj/4.4</bundle>
>>>
>>> I got the exception when installing the feature from the Karaf shell via
>>> feature:install.
>>>
>>> BTW, what do you mean by "partially released" - only the good parts? ;-)
>>>
>>> Regards,
>>> Harald
>>>
>>> 2014-09-16 10:46 GMT+02:00 Achim Nierbeck <bc...@googlemail.com>:
>>>
>>> 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 <hw...@gmail.com>:
>>>>
>>>> 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é <jb...@nanthrax.net>:
>>>>>
>>>>> 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 <hw...@gmail.com>:
>>>>>>>
>>>>>>> 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é
>>>>>> jbonofre@apache.org
>>>>>> http://blog.nanthrax.net
>>>>>> Talend - http://www.talend.com
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Apache Member
>>>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>>>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
>>>> Committer &
>>>> Project Lead
>>>> blog <http://notizblog.nierbeck.de/>
>>>>
>>>> Software Architect / Project Manager / Scrum Master
>>>>
>>>>
>>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: Manifest position
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
FYI:
https://issues.apache.org/jira/browse/KARAF-3232
Regards
JB
On 09/16/2014 11:01 AM, Jean-Baptiste Onofré wrote:
> Actually, the problem is in Karaf (I thought you use bundle:install).
>
> It works fine using bundle:install directly:
>
> karaf@root()> bundle:install mvn:org.eclipse.jdt.core.compiler/ecj/4.4
> Bundle ID: 78
> karaf@root()> bundle:start 78
> karaf@root()>
>
> I'm creating the corresponding Jira and fix that for 3.0.2 (planned on
> Friday).
>
> Regards
> JB
>
> On 09/16/2014 10:55 AM, Harald Wellmann wrote:
>> It's a features file containing a feature with the following line:
>>
>> <bundle>mvn:org.eclipse.jdt.core.compiler/ecj/4.4</bundle>
>>
>> I got the exception when installing the feature from the Karaf shell via
>> feature:install.
>>
>> BTW, what do you mean by "partially released" - only the good parts? ;-)
>>
>> Regards,
>> Harald
>>
>> 2014-09-16 10:46 GMT+02:00 Achim Nierbeck <bc...@googlemail.com>:
>>
>>> 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 <hw...@gmail.com>:
>>>
>>>> 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é <jb...@nanthrax.net>:
>>>>
>>>>> 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 <hw...@gmail.com>:
>>>>>>
>>>>>> 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é
>>>>> jbonofre@apache.org
>>>>> http://blog.nanthrax.net
>>>>> Talend - http://www.talend.com
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Apache Member
>>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
>>> Committer &
>>> Project Lead
>>> blog <http://notizblog.nierbeck.de/>
>>>
>>> Software Architect / Project Manager / Scrum Master
>>>
>>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Manifest position
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Actually, the problem is in Karaf (I thought you use bundle:install).
It works fine using bundle:install directly:
karaf@root()> bundle:install mvn:org.eclipse.jdt.core.compiler/ecj/4.4
Bundle ID: 78
karaf@root()> bundle:start 78
karaf@root()>
I'm creating the corresponding Jira and fix that for 3.0.2 (planned on
Friday).
Regards
JB
On 09/16/2014 10:55 AM, Harald Wellmann wrote:
> It's a features file containing a feature with the following line:
>
> <bundle>mvn:org.eclipse.jdt.core.compiler/ecj/4.4</bundle>
>
> I got the exception when installing the feature from the Karaf shell via
> feature:install.
>
> BTW, what do you mean by "partially released" - only the good parts? ;-)
>
> Regards,
> Harald
>
> 2014-09-16 10:46 GMT+02:00 Achim Nierbeck <bc...@googlemail.com>:
>
>> 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 <hw...@gmail.com>:
>>
>>> 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é <jb...@nanthrax.net>:
>>>
>>>> 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 <hw...@gmail.com>:
>>>>>
>>>>> 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é
>>>> jbonofre@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>
>>
>>
>>
>> --
>>
>> Apache Member
>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
>> Project Lead
>> blog <http://notizblog.nierbeck.de/>
>>
>> Software Architect / Project Manager / Scrum Master
>>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Manifest position
Posted by Harald Wellmann <hw...@gmail.com>.
It's a features file containing a feature with the following line:
<bundle>mvn:org.eclipse.jdt.core.compiler/ecj/4.4</bundle>
I got the exception when installing the feature from the Karaf shell via
feature:install.
BTW, what do you mean by "partially released" - only the good parts? ;-)
Regards,
Harald
2014-09-16 10:46 GMT+02:00 Achim Nierbeck <bc...@googlemail.com>:
> 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 <hw...@gmail.com>:
>
> > 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é <jb...@nanthrax.net>:
> >
> > > 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 <hw...@gmail.com>:
> > >>
> > >> 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é
> > > jbonofre@apache.org
> > > http://blog.nanthrax.net
> > > Talend - http://www.talend.com
> > >
> >
>
>
>
> --
>
> Apache Member
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
> Project Lead
> blog <http://notizblog.nierbeck.de/>
>
> Software Architect / Project Manager / Scrum Master
>
Re: Manifest position
Posted by Achim Nierbeck <bc...@googlemail.com>.
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 <hw...@gmail.com>:
> 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é <jb...@nanthrax.net>:
>
> > 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 <hw...@gmail.com>:
> >>
> >> 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é
> > jbonofre@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Software Architect / Project Manager / Scrum Master
Re: Manifest position
Posted by Harald Wellmann <hw...@gmail.com>.
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é <jb...@nanthrax.net>:
> 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 <hw...@gmail.com>:
>>
>> 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é
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: Manifest position
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
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 <hw...@gmail.com>:
>
>> 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é
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Manifest position
Posted by Achim Nierbeck <bc...@googlemail.com>.
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 <hw...@gmail.com>:
> 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
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Software Architect / Project Manager / Scrum Master