I think it needs to be shared and keep eclipse plugin with only
eclipse specifics as much as possible.
On 10/27/06, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
On 10/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Author: carlos
> URL: http://svn.apache.org/viewvc?view=rev&rev=468338
> Log: Add todo to move OSGi manifest work to use Felix
The main reason to create a different goal is that the Felix osgi
plugin actually generates the manifest during packaging: when working
with eclipse this is not acceptable, since PDE will only work with an
existing Manifest.
I had a few discussions with people from the Cocoon team at the
ApacheCon EU: they extended the eclipse plugin in order to simply keep
some bits of the manifest in sync with the pom, without having to use
the felix plugin in order to fully generate it. This made possible to
fully use PDE when developing osgi bundles.
There is surely some code that could be shared between the eclipse and
Felix plugin, but at the moment the purpose is a bit different: the
Felix plugin is more useful to package an artifact as an osgi bundle,
the eclipse plugin helps in working with osgi-bundle maven projects
with PDE.
Of course, sharing parts of the code would be great: what about asking
Felix people to move their plugin to the maven sandbox area and to
create something shared that could be used to manipulate osgi manifest
in different plugins?
fabrizio
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
