[
https://issues.apache.org/jira/browse/SLING-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13807848#comment-13807848
]
Konrad Windszus commented on SLING-3100:
----------------------------------------
[~rombert] - do you have any information when the content-package plugin will
be Open Source as well? Otherwise we would need to come up with our own custom
plugin to configure content-packages correctly. Right now there is already a
dependency on "content-package" within the source code
(org.apache.sling.ide.eclipse.core.internal.ProjectHelper) .You can only
convert to a sling project in case the packaging is "content-package".
Therefore I would prefer to have it right now included in the Sling IDE
Tooling. As soon as the content-package is open source we could think about
moving the configurator to a separate plugin (probably linking it in the m2e
marketplace, http://wiki.eclipse.org/Submitting_M2E_marketplace_entries). What
do you think?
> Provide a m2e project configurator for packaging "content-package"
> ------------------------------------------------------------------
>
> Key: SLING-3100
> URL: https://issues.apache.org/jira/browse/SLING-3100
> Project: Sling
> Issue Type: New Feature
> Components: IDE
> Affects Versions: Sling Eclipse IDE 1.0.0
> Reporter: Konrad Windszus
> Fix For: Sling Eclipse IDE 1.0.2
>
> Attachments: SLING-3100-m2e-integration.patch
>
>
> To set up the appropriate project configuration just from the POM an
> according m2e project configurator is needed
> (http://wiki.eclipse.org/M2E_plugin_execution_not_covered#delegate_to_a_project_configurator_.28recommended.29)
> The m2e-war-plugin comes with a project configurator which works also for
> content-packages pretty well but it is currently hard to reuse for any other
> packaging than "war" (due to the delegate pattern being used internally,
> compare with https://bugs.eclipse.org/bugs/show_bug.cgi?id=412213). Only if
> the project is having the dynamic web project facet the following features in
> Eclipse are supported:
> - JSP include directives (considered for validation and supports ctrl+click
> to open linked file)
> - Tag Library Support (
> http://wiki.eclipse.org/WTP_FAQ#Why_isn.27t_the_JSP_editor.2Fvalidator_finding_my_custom_tag_libraries.3F
> )
> - probably other features as well.
> Apart from that a feature like overlays should be supported (
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=384154 ), as often
> content-package projects are referencing JSPs from other projects, and the
> IDE needs to know those, to complete the validation.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
