[ https://issues.apache.org/jira/browse/SLING-3612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018021#comment-14018021 ]
Konrad Windszus edited comment on SLING-3612 at 6/4/14 7:12 PM: ---------------------------------------------------------------- You are right, that if now the plugin is installed all bundle projects would end up with the sling facet. I am not sure, how to check for the maven-sling-plugin, but probably I can figure out something. Does the Sling Facet do any harm? Also I am not sure that maven-sling-plugin is the right criteria, because even that could be used for non-Sling bundles (because it basically deploys via the Apache Felix Webconsole). was (Author: kwin): You are right, that if now the plugin is installed all bundle projects would end up with the sling facet. I am not sure, how to check for the maven-sling-plugin, but probably I can figure out something. Does the Sling Facet do any harm? > Provide a m2e project configurator for packaging "bundle" > --------------------------------------------------------- > > Key: SLING-3612 > URL: https://issues.apache.org/jira/browse/SLING-3612 > Project: Sling > Issue Type: Improvement > Components: IDE > Affects Versions: Sling Eclipse IDE 1.0.0 > Reporter: Konrad Windszus > Fix For: Sling Eclipse IDE 1.0.2 > > > That configurator should automatically setup the project with the correct > facets (to make it possible to deploy via Sling IDE Tools). That configurator > would e.g. be triggered, when a new project is imported into the IDE (e.g. > from an existing local Maven project, or via Subclipe/Subversive/eGit) -- This message was sent by Atlassian JIRA (v6.2#6252)