[ 
https://issues.apache.org/jira/browse/FELIX-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194952#comment-15194952
 ] 

Robert Munteanu commented on FELIX-4009:
----------------------------------------

{quote}i'm still not shure when this m2e-tycho plugin gets installed. {/quote}

It's the default configurator for maven-bundle-plugin projects in Eclipse, so 
if you import such a project it will be highlighted as having errors and you 
will have the option to start the m2e extension discovery process.

It's also (slightly relevant to your scenario) pulled in by the Sling IDE 
Tooling for Eclipse.

{quote}so my first option would be to make it configurable in the POM whether 
SCR metadata and manifest should be generated on incremental builds or 
not.{quote}

I have two basic ideas which together might make the plugin work transparently 
in Eclipse and in the CLI:

# create (by default) wildcard {{Service-Component}} headers, e.g. 
{{Service-Component: OSGI-INF/*.xml}} . That would remove the need for updating 
the MANIFEST whenever a SCR file changes
# hold a mapping of SCR annotations which is updated whenever the plugin is 
invoked. ISTR that this can be done for m2e-enabled mojos, but I forget whether 
this is done by reusing the same mojo instance ( so instance fields will be 
kept ) or by another mechanism

> maven bundle plugin should be integrated directly with eclipse
> --------------------------------------------------------------
>
>                 Key: FELIX-4009
>                 URL: https://issues.apache.org/jira/browse/FELIX-4009
>             Project: Felix
>          Issue Type: New Feature
>          Components: Maven Bundle Plugin
>    Affects Versions: maven-bundle-plugin-2.3.7
>            Reporter: Andrei Pozolotin
>            Assignee: Carsten Ziegeler
>              Labels: m2e
>             Fix For: maven-bundle-plugin-3.0.2
>
>
> Stuart:
> 1) currently, to integrate maven-bundle-plugin into m2e, one must  use tycho 
> configurator
> https://github.com/sonatype/m2eclipse-tycho
> which adds needles complexity, and makes few strange assumptions
> https://github.com/sonatype/m2eclipse-tycho/blob/master/org.sonatype.tycho.m2e/src/org/sonatype/tycho/m2e/internal/OsgiBundleProjectConfigurator.java#L74
> which no one it seems is there to care to correct
> https://github.com/sonatype/m2eclipse-tycho/pull/8
> 2) instead, I suggest maven-bundle-plugin to provide direct integration with 
> eclipse via
> http://wiki.eclipse.org/M2E_compatible_maven_plugins#BuildContext
> which I would expect to be more customizable / flexible for the end user.
> I recently made similar switch with my DS plugin, and life got easier :-)
> https://github.com/carrot-garden/carrot-maven/tree/master/carrot-maven-scr-plugin
> thanks.
> Andrei.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to