You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Georg Henzler (JIRA)" <ji...@apache.org> on 2013/10/24 10:01:05 UTC

[jira] [Updated] (SLING-3100) Provide a m2e project configurator for packaging "content-package"

     [ https://issues.apache.org/jira/browse/SLING-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Georg Henzler updated SLING-3100:
---------------------------------

    Attachment: SLING-3100-m2e-integration.patch

SLING-3100-m2e-integration.patch configures a project for eclipse on "Import..." -> "Existing Maven Project" and Right-Click on Project -> "Maven" 
 * -> "Update Project..."

Notes:
* There is no dependency to m2e-wtp
* I added a log method to the activator
* I could not entirely rely on import-package and had to use require-bundle for some imports to work (fix it if you know how!)
* ConfigurationHelper.convertToContentPackageProject() is used for adding the basic sling facet and to configure jcr root
* There is a set of maven properties (sling.ide.m2e.contentpackage.*) that allow to configure how the eclipse project should be set up
* Optionally (enabled via mvn prop), it is possible to create a war-like setup
     PRO: Validation (and possibly some other aspects) and JSP code completion work better if the wtp-war facets are set in the project 
     CON: There is additional virtual project folders (e.g. "JAX WS Web Services") that may confuse the user. 



> 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)