[
https://issues.apache.org/jira/browse/SLING-3612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018035#comment-14018035
]
Robert Munteanu commented on SLING-3612:
----------------------------------------
I don't think it does any major harm, but basically it's unexpected. Also, we
enable the validation builder since we have our own validator, and that may not
be what the user wants.
Isn't it possible for the configurator to check for the maven-sling-plugin
instead of the maven-bundle-plugin? Or is that decided by the primary
configurator?
> 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)
