You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by Peter Neubauer <pe...@neubauer.se> on 2006/11/30 11:29:42 UTC
Which OSGi plugin to bet on?
Hi gang,
we are wondering which Maven OSGi plugin we should bet on when
starting to make some changes to support things like Require-Bundle
statements etc from the POM? Peters BND sounds very nice but it seems
the older one is more stable etc etc.
Cheers
/peter
Re: Which OSGi plugin to bet on?
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Steven E. Harris wrote:
> "Richard S. Hall" <he...@ungoverned.org> writes:
>
>
>> http://cwiki.apache.org/FELIX/bundle-plugin-for-maven-bnd.html
>>
>
> The documentation states that the default behavior for Import-Package
> is as follows:
>
> <Import-Package> is assumed to be "*", which imports everything
> referred to by the bundle content, but not contained in the bundle.
>
> When I create my bundles, packages that I export that /are/ contained
> in the bundle still get mentioned in the Import-Package header. Is
> this intended?
I guess that wording should be changed slightly.
Yes, that is intended because it allows those packages to be
substitutable with other providers. If your bundle only exported them,
then it would always get them from itself, even in cases where there was
another provider already in use. This would then limit interoperability,
because your bundle would not be able to interact with bundles using the
other provider's packages. You can explicitly tell the plugin to not
import an exported package if you do not want this behavior.
-> richard
Re: Which OSGi plugin to bet on?
Posted by "Steven E. Harris" <se...@panix.com>.
"Richard S. Hall" <he...@ungoverned.org> writes:
> http://cwiki.apache.org/FELIX/bundle-plugin-for-maven-bnd.html
The documentation states that the default behavior for Import-Package
is as follows:
<Import-Package> is assumed to be "*", which imports everything
referred to by the bundle content, but not contained in the bundle.
When I create my bundles, packages that I export that /are/ contained
in the bundle still get mentioned in the Import-Package header. Is
this intended?
--
Steven E. Harris
Re[2]: Which OSGi plugin to bet on?
Posted by Peter Kriens <Pe...@aQute.biz>.
>> Transitioning back to maven-bundle-plugin didn't take too long, but I
>> do miss the auto-Activator detection feature, despite its lack of
>> specificity making me uncomfortable at first.
RSH> I like activator detection too and I have asked Peter to include an
RSH> instruction for it too. He complains that auto-detection is not perfect,
RSH> but in many cases it works well so I think we should include it in the
RSH> new plugin too. (Are you listening Peter?)
No :-)
Kind regards,
Peter Kriens
->> richard
--
Peter Kriens Tel +33467542167
9C, Avenue St. Drézéry AOL,Yahoo: pkriens
34160 Beaulieu, France ICQ 255570717
Skype pkriens Fax +1 8153772599
Re: Which OSGi plugin to bet on?
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Steven E. Harris wrote:
> "Richard S. Hall" <he...@ungoverned.org> writes:
>
>
>> Perhaps I will add a "deprecated" comment in the title of the old
>> plugin's page and add a reference to the new one.
>>
>
> That would have saved me plenty of effort. I noticed both plugins, but
> decided that "maven-osgi-plugin" /sounded/ like a newer name than
> "maven-bundle-plugin", and went off and started using the former in
> five different POMs.
>
Well, I didn't try to deprecate the original plugin at first because I
didn't want to presume to make a decision for the entire community since
the two plugins have quite different approaches. However, now that the
community is moving more toward the new plugin, it makes more sense to
somehow indicate this in the documentation. I have just added a note at
the beginning of the old plugin's documentation.
> Transitioning back to maven-bundle-plugin didn't take too long, but I
> do miss the auto-Activator detection feature, despite its lack of
> specificity making me uncomfortable at first.
>
I like activator detection too and I have asked Peter to include an
instruction for it too. He complains that auto-detection is not perfect,
but in many cases it works well so I think we should include it in the
new plugin too. (Are you listening Peter?)
-> richard
Re: Which OSGi plugin to bet on?
Posted by "Steven E. Harris" <se...@panix.com>.
"Richard S. Hall" <he...@ungoverned.org> writes:
> Perhaps I will add a "deprecated" comment in the title of the old
> plugin's page and add a reference to the new one.
That would have saved me plenty of effort. I noticed both plugins, but
decided that "maven-osgi-plugin" /sounded/ like a newer name than
"maven-bundle-plugin", and went off and started using the former in
five different POMs.
Transitioning back to maven-bundle-plugin didn't take too long, but I
do miss the auto-Activator detection feature, despite its lack of
specificity making me uncomfortable at first.
--
Steven E. Harris
Re: Which OSGi plugin to bet on?
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Enrique Rodriguez wrote:
> On 11/30/06, Richard S. Hall <he...@ungoverned.org> wrote:
>> Yes, that is the old plugin. It hasn't been officially killed off, but
>> perhaps it is a victim waiting to happen...
>
> ... along with the old Confluence site at Safehaus. Having two sites
> and two plugins is confusing.
We should for sure nuke the old Confluence site at Safehaus. As far as I
know, everything there was moved to our wiki and I haven't touched that
site in ages.
> I agree the newer 'maven-bundle-plugin' based on BND is the way forward.
Perhaps I will add a "deprecated" comment in the title of the old
plugin's page and add a reference to the new one.
-> richard
Re: Which OSGi plugin to bet on?
Posted by Enrique Rodriguez <en...@gmail.com>.
On 11/30/06, Richard S. Hall <he...@ungoverned.org> wrote:
> Yes, that is the old plugin. It hasn't been officially killed off, but
> perhaps it is a victim waiting to happen...
... along with the old Confluence site at Safehaus. Having two sites
and two plugins is confusing.
I agree the newer 'maven-bundle-plugin' based on BND is the way forward.
Enrique
Re: Which OSGi plugin to bet on?
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Steven E. Harris wrote:
> "Richard S. Hall" <he...@ungoverned.org> writes:
>
>
>> No, the new one is maven-bundle-plugin
>>
>
> I'll look into transitioning to that one.
>
> Is maven-osgi-plugin still under development? Is that the "old"
> plugin?
>
Yes, that is the old plugin. It hasn't been officially killed off, but
perhaps it is a victim waiting to happen...
-> richard
Re: Which OSGi plugin to bet on?
Posted by "Steven E. Harris" <se...@panix.com>.
"Richard S. Hall" <he...@ungoverned.org> writes:
> No, the new one is maven-bundle-plugin
I'll look into transitioning to that one.
Is maven-osgi-plugin still under development? Is that the "old"
plugin?
--
Steven E. Harris
Re: Which OSGi plugin to bet on?
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Steven E. Harris wrote:
> "John E. Conlon" <jc...@verticon.com> writes:
>
>
>> I'd like to put in a plug for the new plugin;-)
>>
>
> Is the new plugin the one called "maven-osgi-plugin"? That's what I've
> been using, but I too have been confused as to which one is the latest
> and greatest.
>
No, the new one is maven-bundle-plugin, doc are here:
http://cwiki.apache.org/FELIX/bundle-plugin-for-maven-bnd.html
-> richard
Re: Which OSGi plugin to bet on?
Posted by "Steven E. Harris" <se...@panix.com>.
"John E. Conlon" <jc...@verticon.com> writes:
> I'd like to put in a plug for the new plugin;-)
Is the new plugin the one called "maven-osgi-plugin"? That's what I've
been using, but I too have been confused as to which one is the latest
and greatest.
--
Steven E. Harris
Re: Which OSGi plugin to bet on?
Posted by "John E. Conlon" <jc...@verticon.com>.
I'd like to put in a plug for the new plugin;-)
One notable functionality versus the old plugin, is that it helps to
reduce the manual entry of exports and thus it reduces pom brittleness
and complexity. (Refactoring of package names will not be as prone to
breaking a bundle.)
The other benefit of the new plugin is that if you like to validate your
newly created bundles (like me) you can use* the plugin's command line
sibling (Of course you can use it with any bundle...):
java -jar bnd-0.0.98.jar \
print /home/jconlon/projects/svns/apacheDS/sandbox/jconlon/osgi-
apacheds/core-osgi/target/apacheds-core-osgi-1.5.0-SNAPSHOT.jar
*tip - it's easy to copy and past the bundle jar path output from your
'mvn install' command.
And last but not least, Peter's support is outstanding!
cheers,
John
On Thu, 2006-11-30 at 15:37 +0100, Peter Kriens wrote:
> There are no outstanding issues as far as I know.
>
> If you use the new plugin as you would use the old plugin, there would
> have been no bugs. This bnd plugin has considerably more horse power. The
> plugin allows you to control the manifest headers in very fine grained
> detail, something that was not possible with the old. Most errors we
> found were actually verification issues, the plugin was sometimes a
> bit too pedantic and overzealous in checking.
>
> So I would definitely go for the bnd based plugin, I promise to fix
> anything quickly when you run into an issue.
>
> Kind regards,
>
> Peter Kriens
>
>
> PN> Hi gang,
> PN> we are wondering which Maven OSGi plugin we should bet on when
> PN> starting to make some changes to support things like Require-Bundle
> PN> statements etc from the POM? Peters BND sounds very nice but it seems
> PN> the older one is more stable etc etc.
>
> PN> Cheers
>
> PN> /peter
>
Re[2]: Which OSGi plugin to bet on?
Posted by Peter Kriens <Pe...@aQute.biz>.
Let me know if I can help or if you have ideas for improvement.
Kind regards,
Peter Kriens
PN> Ok,
PN> great, we will take a look at the BND plugin!
PN> /peter
PN> On 11/30/06, Peter Kriens <Pe...@aqute.biz> wrote:
>> There are no outstanding issues as far as I know.
>>
>> If you use the new plugin as you would use the old plugin, there would
>> have been no bugs. This bnd plugin has considerably more horse power. The
>> plugin allows you to control the manifest headers in very fine grained
>> detail, something that was not possible with the old. Most errors we
>> found were actually verification issues, the plugin was sometimes a
>> bit too pedantic and overzealous in checking.
>>
>> So I would definitely go for the bnd based plugin, I promise to fix
>> anything quickly when you run into an issue.
>>
>> Kind regards,
>>
>> Peter Kriens
>>
>>
>> PN> Hi gang,
>> PN> we are wondering which Maven OSGi plugin we should bet on when
>> PN> starting to make some changes to support things like Require-Bundle
>> PN> statements etc from the POM? Peters BND sounds very nice but it seems
>> PN> the older one is more stable etc etc.
>>
>> PN> Cheers
>>
>> PN> /peter
>>
>> --
>> Peter Kriens Tel +33467542167
>> 9C, Avenue St. Drézéry AOL,Yahoo: pkriens
>> 34160 Beaulieu, France ICQ 255570717
>> Skype pkriens Fax +1 8153772599
>>
>>
--
Peter Kriens Tel +33467542167
9C, Avenue St. Drézéry AOL,Yahoo: pkriens
34160 Beaulieu, France ICQ 255570717
Skype pkriens Fax +1 8153772599
Re: Which OSGi plugin to bet on?
Posted by Peter Neubauer <pe...@neubauer.se>.
Ok,
great, we will take a look at the BND plugin!
/peter
On 11/30/06, Peter Kriens <Pe...@aqute.biz> wrote:
> There are no outstanding issues as far as I know.
>
> If you use the new plugin as you would use the old plugin, there would
> have been no bugs. This bnd plugin has considerably more horse power. The
> plugin allows you to control the manifest headers in very fine grained
> detail, something that was not possible with the old. Most errors we
> found were actually verification issues, the plugin was sometimes a
> bit too pedantic and overzealous in checking.
>
> So I would definitely go for the bnd based plugin, I promise to fix
> anything quickly when you run into an issue.
>
> Kind regards,
>
> Peter Kriens
>
>
> PN> Hi gang,
> PN> we are wondering which Maven OSGi plugin we should bet on when
> PN> starting to make some changes to support things like Require-Bundle
> PN> statements etc from the POM? Peters BND sounds very nice but it seems
> PN> the older one is more stable etc etc.
>
> PN> Cheers
>
> PN> /peter
>
> --
> Peter Kriens Tel +33467542167
> 9C, Avenue St. Drézéry AOL,Yahoo: pkriens
> 34160 Beaulieu, France ICQ 255570717
> Skype pkriens Fax +1 8153772599
>
>
Re: Which OSGi plugin to bet on?
Posted by Peter Kriens <Pe...@aQute.biz>.
There are no outstanding issues as far as I know.
If you use the new plugin as you would use the old plugin, there would
have been no bugs. This bnd plugin has considerably more horse power. The
plugin allows you to control the manifest headers in very fine grained
detail, something that was not possible with the old. Most errors we
found were actually verification issues, the plugin was sometimes a
bit too pedantic and overzealous in checking.
So I would definitely go for the bnd based plugin, I promise to fix
anything quickly when you run into an issue.
Kind regards,
Peter Kriens
PN> Hi gang,
PN> we are wondering which Maven OSGi plugin we should bet on when
PN> starting to make some changes to support things like Require-Bundle
PN> statements etc from the POM? Peters BND sounds very nice but it seems
PN> the older one is more stable etc etc.
PN> Cheers
PN> /peter
--
Peter Kriens Tel +33467542167
9C, Avenue St. Drézéry AOL,Yahoo: pkriens
34160 Beaulieu, France ICQ 255570717
Skype pkriens Fax +1 8153772599
Re: Which OSGi plugin to bet on?
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Peter Neubauer wrote:
> we are wondering which Maven OSGi plugin we should bet on when
> starting to make some changes to support things like Require-Bundle
> statements etc from the POM? Peters BND sounds very nice but it seems
> the older one is more stable etc etc.
Good question. The older one probably was more stable since it has been
used a little longer, but there have been a spate of fixes to BND since
it started to get more use, so it seems pretty decent now. I am sure
there are still some issues to be fix, but my vote is for the new plugin.
-> richard