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

Konrad Windszus edited comment on SLING-6112 at 10/14/16 10:00 AM:
-------------------------------------------------------------------

There is an error marker in each pom.xml which is not setup correctly. This is 
probably the best way of doing it and Eclipse users should be familiar with 
looking at the Problems view and searching for quick fixes in case there are 
any errors exposed.


was (Author: kwin):
There is an error marker in each pom.xml which is not setup correctly. This is 
probably the best way of doing it and Eclipse user's should be familiar with 
looking at the Problems view and searching for quick fixes in case there are 
any errors exposed.

> 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
(v6.3.4#6332)

Reply via email to