I tried to work on some Sling IDE Tooling issues and for that need to start
Eclipse with the tooling included in debug mode. There is even a laucher for
that included in
https://github.com/apache/sling-ide-tooling/blob/42a964b8961c4951f68053b9ac455abadd8595d6/eclipse/target-definition/Sling%20IDE%20Tooling.launch#L33
which lists all necessary plugins.
Unfortunately when I use this launcher config to debug Eclipse it emits the
following error message:
ENTRY org.apache.sling.ide.eclipse-core 4 0 2018-06-15 14:32:25.095
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module:
org.apache.sling.ide.eclipse-core [48]
Unresolved requirement: Import-Package: org.apache.sling.ide.artifacts
at org.eclipse.osgi.container.Module.start(Module.java:444)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1634)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1613)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1585)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1528)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
When I try open the provided launcher configuration in Eclipse it always shows
"Launch with all workspace and enabled target plugins" which does not work,
because shared/modules/artifacts is no longer detected as Eclipse plugin (and
still necessary to run Sling IDE Tooling).
I tried to set both target definitions (both dev and non-dev) but did not
succeed. Every time Eclipse is not launched with the module "artifacts".
I am using Eclipse 4.7.2 to launch.
Does anyone have any idea?
Also I am wondering, if it is the right approach to maintain both the required
plugins both in the target definition file (2 times, for dev and non-dev) and
also within the Eclipse launcher now. This seems to be a very error-prone
process...
Thanks,
Konrad
