You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@felix.apache.org by Graham Charters <gc...@gmail.com> on 2012/07/03 12:13:28 UTC
Empty header generation using maven-bundle-plugin
Hi,
It seems to be becoming a more common practice to have extender opt-in
manifest headers that contain no value by default (e.g.
Meta-Persistence). I tried to generate such a header with the
maven-bundle-plugin using
<instructions>
<Meta-Persistence> </Meta-Persistence>
</instructions>
but it seems if the entry only contains whitespace, then the header is
omitted. Is there a way to generate empty headers using the
maven-bundle-plugin, or would this need an enhancement?
Many thanks for any help.
Regards, Graham.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: Empty header generation using maven-bundle-plugin
Posted by Neil Bartlett <nj...@gmail.com>.
Great! It's just a shame that it looks like shit ;-)
On Tue, Jul 3, 2012 at 11:40 AM, Graham Charters <gc...@gmail.com> wrote:
> Thanks, Neil, that worked a treat! :)
>
> Graham.
>
> On 3 July 2012 11:28, Neil Bartlett <nj...@gmail.com> wrote:
>> Yup, bnd discards empty headers; this is quite often helpful if you
>> use a wildcard or a macro expansion. Anyway in "raw" bnd you can
>> explicitly create an empty header as follows:
>>
>> Meta-Persistence: <<EMPTY>>
>>
>> I guess that in the bundle-plugin this might translate to:
>>
>> <Meta-Persistence><<EMPTY>></Meta-Persistence>
>>
>> ... but I don't have an easy way to try this out!
>>
>> Neil
>>
>> On Tue, Jul 3, 2012 at 11:13 AM, Graham Charters <gc...@gmail.com> wrote:
>>> Hi,
>>>
>>> It seems to be becoming a more common practice to have extender opt-in
>>> manifest headers that contain no value by default (e.g.
>>> Meta-Persistence). I tried to generate such a header with the
>>> maven-bundle-plugin using
>>>
>>> <instructions>
>>> <Meta-Persistence> </Meta-Persistence>
>>> </instructions>
>>>
>>> but it seems if the entry only contains whitespace, then the header is
>>> omitted. Is there a way to generate empty headers using the
>>> maven-bundle-plugin, or would this need an enhancement?
>>>
>>> Many thanks for any help.
>>>
>>> Regards, Graham.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: Empty header generation using maven-bundle-plugin
Posted by Graham Charters <gc...@gmail.com>.
Thanks, Neil, that worked a treat! :)
Graham.
On 3 July 2012 11:28, Neil Bartlett <nj...@gmail.com> wrote:
> Yup, bnd discards empty headers; this is quite often helpful if you
> use a wildcard or a macro expansion. Anyway in "raw" bnd you can
> explicitly create an empty header as follows:
>
> Meta-Persistence: <<EMPTY>>
>
> I guess that in the bundle-plugin this might translate to:
>
> <Meta-Persistence><<EMPTY>></Meta-Persistence>
>
> ... but I don't have an easy way to try this out!
>
> Neil
>
> On Tue, Jul 3, 2012 at 11:13 AM, Graham Charters <gc...@gmail.com> wrote:
>> Hi,
>>
>> It seems to be becoming a more common practice to have extender opt-in
>> manifest headers that contain no value by default (e.g.
>> Meta-Persistence). I tried to generate such a header with the
>> maven-bundle-plugin using
>>
>> <instructions>
>> <Meta-Persistence> </Meta-Persistence>
>> </instructions>
>>
>> but it seems if the entry only contains whitespace, then the header is
>> omitted. Is there a way to generate empty headers using the
>> maven-bundle-plugin, or would this need an enhancement?
>>
>> Many thanks for any help.
>>
>> Regards, Graham.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: Empty header generation using maven-bundle-plugin
Posted by Felix Meschberger <fm...@adobe.com>.
Hi,
Am 03.07.2012 um 12:28 schrieb Neil Bartlett:
> Yup, bnd discards empty headers; this is quite often helpful if you
> use a wildcard or a macro expansion. Anyway in "raw" bnd you can
> explicitly create an empty header as follows:
>
> Meta-Persistence: <<EMPTY>>
>
> I guess that in the bundle-plugin this might translate to:
>
> <Meta-Persistence><<EMPTY>></Meta-Persistence>
>
> ... but I don't have an easy way to try this out!
Thanks for the hint. Just tested in bundle plugin 2.3.7 and it seems to work.
Regards
Felix
>
> Neil
>
> On Tue, Jul 3, 2012 at 11:13 AM, Graham Charters <gc...@gmail.com> wrote:
>> Hi,
>>
>> It seems to be becoming a more common practice to have extender opt-in
>> manifest headers that contain no value by default (e.g.
>> Meta-Persistence). I tried to generate such a header with the
>> maven-bundle-plugin using
>>
>> <instructions>
>> <Meta-Persistence> </Meta-Persistence>
>> </instructions>
>>
>> but it seems if the entry only contains whitespace, then the header is
>> omitted. Is there a way to generate empty headers using the
>> maven-bundle-plugin, or would this need an enhancement?
>>
>> Many thanks for any help.
>>
>> Regards, Graham.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: Empty header generation using maven-bundle-plugin
Posted by Neil Bartlett <nj...@gmail.com>.
Yup, bnd discards empty headers; this is quite often helpful if you
use a wildcard or a macro expansion. Anyway in "raw" bnd you can
explicitly create an empty header as follows:
Meta-Persistence: <<EMPTY>>
I guess that in the bundle-plugin this might translate to:
<Meta-Persistence><<EMPTY>></Meta-Persistence>
... but I don't have an easy way to try this out!
Neil
On Tue, Jul 3, 2012 at 11:13 AM, Graham Charters <gc...@gmail.com> wrote:
> Hi,
>
> It seems to be becoming a more common practice to have extender opt-in
> manifest headers that contain no value by default (e.g.
> Meta-Persistence). I tried to generate such a header with the
> maven-bundle-plugin using
>
> <instructions>
> <Meta-Persistence> </Meta-Persistence>
> </instructions>
>
> but it seems if the entry only contains whitespace, then the header is
> omitted. Is there a way to generate empty headers using the
> maven-bundle-plugin, or would this need an enhancement?
>
> Many thanks for any help.
>
> Regards, Graham.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org