You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (Jira)" <ji...@apache.org> on 2025/04/11 14:31:00 UTC

[jira] [Updated] (SLING-8700) Unexpected compiler errors in Eclipse during development

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

Robert Munteanu updated SLING-8700:
-----------------------------------
    Fix Version/s: Sling Eclipse IDE 2.0.2
                   Sling Eclipse IDE 2.0.2
                       (was: Sling Eclipse IDE 2.0.0)

> Unexpected compiler errors in Eclipse during development
> --------------------------------------------------------
>
>                 Key: SLING-8700
>                 URL: https://issues.apache.org/jira/browse/SLING-8700
>             Project: Sling
>          Issue Type: Task
>          Components: IDE
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>            Priority: Major
>             Fix For: Sling Eclipse IDE 2.0.2
>
>         Attachments: compiler-errors-screenshot.png
>
>
> 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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)