[SLING-8700] Unexpected compiler errors in Eclipse during development

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: Sling Eclipse IDE 2.0.0
• Component/s: IDE
• Assignee: Robert Munteanu
• Reporter: Robert Munteanu
• Created: 12/Sep/19 10:26
• Updated: 05/Jul/23 07:24

Description

1. Change any code in eclipse-ui module in Eclipse
2. Run the plug-ins as an Eclipse Application (Sling IDE Tooling shared launch config)

Result: eclipse-ui fails to start, logged event An error occurred while automatically activating bundle org.apache.sling.ide.eclipse-ui (536). Error is attached, but root cause are compilation errors in org.apache.sling.ide.eclipse.ui.internal.Activator.<init>, e.g.

AbstractUIPlugin cannot be resolved to a type
ServiceTracker cannot be resolved to a type
SerializationManager cannot be resolved to a type
SerializationManager cannot be resolved to a type
ServiceTracker cannot be resolved to a type
FilterLocator cannot be resolved to a type
FilterLocator cannot be resolved to a type

Note that these errors are not reflected in the editor.

Solution is usually to clean the affected project.

The same applies to the eclipse-core plug-in, so I assume this is not isolated to a single Eclipse project. Iit does not apply to org.apache.sling.ide.api or org.apache.sling.ide.artifacts, so I assume this is related to the projects under '/eclipse' only, not to those under '/shared'.

It also happens that when editing a class ( e.g. JcrNode ), random compiler errors pop up in the same project.

Issue Links

• links to: Eclipse Bug 551051: Unexpected compilation errors when changing code of a class from a plug-in project