| commit | 33ded84e1faa9bd04eb23982dc580fb4bd05ccbb | [log] [tgz] |
|---|---|---|
| author | Robert Munteanu <rombert@apache.org> | Mon Apr 16 23:56:31 2018 +0300 |
| committer | Robert Munteanu <robert.munteanu@gmail.com> | Tue Apr 17 10:39:31 2018 +0300 |
| tree | 0cc95a2221759bc18361baaf4d27a952a709a4e7 | |
| parent | d64693aeeaee9e771d72900e972a43bdac0cf4e8 [diff] |
SLING-7585 - Fix Eclipse in-IDE errors after creating shared modules Move vlt-wrapper under shared/p2 . This artifact is only needed in Eclipse, where OSGi bundles need to come from p2 repos, so it's not really needed in the 'shared/modules' part. Additionally, the packages it exports are not available in Eclipse and cause compiler errors (although Tycho works fine). The module could have ended up under eclipse/, but in order to build the shared p2 feature we need a bundle providing javax.jcr.* and a couple of Jackrabbit packages, so we went with shared/p2.
This module is part of the Apache Sling project.
For using the IDE tooling, please see the Sling IDE Tooling documentation page.
The modules are split into two sub-trees
to ensure that the reusable code is available for usage in other IDEs or environments.
The modules placed under shared/modules should bring as few external dependencies as possible, and must not depend on IDE-specific APIs, such as Eclipse or OSGi.
The modules placed under eclipse may depend on any Eclipse-specific APIs.
To make the shared modules consumable by the Maven + Tycho toolchain, a separate shared/p2 sub-tree contains a Maven + Tycho build which creates a p2 update site. That update site in turn is consumed by the eclipse build.
This howto assumes that you are running Eclipse Oxygen or later with the Plug-In Development Environment and Maven features installed. You should have previously built the projects using
./build-eclipse.sh
to ensure that Maven artifacts which are not available on p2 update sites are included in the workspace.
To start with, import all the projects in Eclipse as Maven projects. Eclipse might prompt you to install an additional m2eclipse configurator for PDE projects, as it's needed for bridging between Maven and PDE projects.
After the projects are imported, you need to set your target environment to ensure that all dependencies are met and that you are working against the project's declared baseline. To do that, open the following file in Eclipse
target-definition/org.apache.sling.ide.target-definition-dev.target
In the target editor which appears, click ‘Set as Target Platform’. Once the target platform is set up, you can create a new launch configuration.
NOTE: if you don‘t see a target editor, but an XML editor, try right-clicking on the file and choosing File -> Open With -> Target Editor. If you don’t see that option, you don't have PDE installed.
Now you can use the ‘Sling IDE Tooling’ launch configuration which is present in the org.apache.sling.ide.target-definition project to launch a local instance of Eclipse with Sling IDE Tooling plug-ins picked up from the local workspace.