Robert Munteanu commented on SLING-6112:

In my opinion the right thing to do would be to rely on the bnd-maven-plugin 
and not install the tycho-m2e feature at all. We're stuck with an old version 

This however comes with the drawback that

- we no longer support older versions of the maven-bundle-plugin
- we require users to configure newer versions of the maven-bundle-plugin for 
correct execution

which is IMO a blocker at the moment. Not even the Sling project has moved to 
the bnd-maven-plugin, and we are quite quick to adopt new stuff.

So in my opinion what would be good to have is to have this tycho-m2e feature 
opt-in, rather than mandatory, so that it can be disabled/uninstalled by those 
who don't want it, but it still works for those who (like me initially) have no 
idea about old vs new maven-bundle-plugin and why the bnd-maven-plugin is good 
to go. Not to mention those that can't migrate.


> Make Sling IDE independent of m2e-tycho
> ---------------------------------------
>                 Key: SLING-6112
>                 URL: https://issues.apache.org/jira/browse/SLING-6112
>             Project: Sling
>          Issue Type: Improvement
>          Components: Tooling
>    Affects Versions: Sling Eclipse IDE 1.1.0
>            Reporter: Konrad Windszus
>            Assignee: Robert Munteanu
>             Fix For: Sling Eclipse IDE 1.1.2
>         Attachments: SLING-6112-v01.patch, SLING-6112-v02.patch, 
> SLING-6112-v03.patch
> Currently Sling IDE requires the installation of m2e-tycho. This was being 
> added in https://issues.apache.org/jira/browse/SLING-3608. Now that the 
> maven-bundle-plugin ships with m2e support OOTB (FELIX-4009) we should get 
> rid of that dependency.
> This is also important since newer versions of the maven-bundle-plugin 
> conflict with that extension 
> (https://issues.apache.org/jira/browse/FELIX-4009?focusedCommentId=15192263&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15192263).
> See also the discussion at 
> http://www.mail-archive.com/dev@sling.apache.org/msg60112.html.

This message was sent by Atlassian JIRA

Reply via email to