[ https://issues.apache.org/jira/browse/SLING-8700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16928546#comment-16928546 ]
Robert Munteanu edited comment on SLING-8700 at 9/12/19 1:52 PM: ----------------------------------------------------------------- This I've tried and did not work: - disabling the Maven Builder for the affected project - deleting .settings/.classpath/.project and reimporting all projects - upgrading to Eclipse 2019-09 It's interesting that at some point during import output directories named {{bin}} are created, but they don't seem to be updated. Maybe a side effect of the configurators? {noformat} $ find -name ServerUtil.class | xargs stat File: ./target/classes/org/apache/sling/ide/eclipse/core/ServerUtil.class Size: 6375 Blocks: 16 IO Block: 4096 regular file Device: 10303h/66307d Inode: 542140737 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ robert) Gid: ( 100/ users) Access: 2019-09-12 15:30:22.765170216 +0200 Modify: 2019-09-12 15:30:22.757170234 +0200 Change: 2019-09-12 15:30:22.757170234 +0200 Birth: 2019-09-12 15:27:42.041547537 +0200 File: ./bin/src/org/apache/sling/ide/eclipse/core/ServerUtil.class Size: 6667 Blocks: 16 IO Block: 4096 regular file Device: 10303h/66307d Inode: 1074448344 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ robert) Gid: ( 100/ users) Access: 2019-09-12 15:31:21.841031527 +0200 Modify: 2019-09-12 15:26:43.545684863 +0200 Change: 2019-09-12 15:26:43.545684863 +0200 Birth: 2019-09-12 15:26:43.545684863 +0200 {noformat} In this example the {{ServerUtil}} class in target/classes is newer than the one in bin. The simplest way to reproduce: * Open {{ServerUtil}} * add a dummy change, save * add another dummy change, save At this point I get some compiltation errors in ServerUtil but also in SlingLaunchpadBehaviour !compiler-errors-screenshot.png|width=500! In the screenshot it's clearly visible that the error is present on the method invocation, but not on the type name and not on the import. [~kwin] - does this problem happen to you as well? was (Author: rombert): This I've tried and did not work: - disabling the Maven Builder for the affected project - deleting .settings/.classpath/.project and reimporting all projects - upgrading to Eclipse 2019-09 It's interesting that at some point during import output directories named {{bin}} are created, but they don't seem to be updated. Maybe a side effect of the configurators? {noformat} $ find -name ServerUtil.class | xargs stat File: ./target/classes/org/apache/sling/ide/eclipse/core/ServerUtil.class Size: 6375 Blocks: 16 IO Block: 4096 regular file Device: 10303h/66307d Inode: 542140737 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ robert) Gid: ( 100/ users) Access: 2019-09-12 15:30:22.765170216 +0200 Modify: 2019-09-12 15:30:22.757170234 +0200 Change: 2019-09-12 15:30:22.757170234 +0200 Birth: 2019-09-12 15:27:42.041547537 +0200 File: ./bin/src/org/apache/sling/ide/eclipse/core/ServerUtil.class Size: 6667 Blocks: 16 IO Block: 4096 regular file Device: 10303h/66307d Inode: 1074448344 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ robert) Gid: ( 100/ users) Access: 2019-09-12 15:31:21.841031527 +0200 Modify: 2019-09-12 15:26:43.545684863 +0200 Change: 2019-09-12 15:26:43.545684863 +0200 Birth: 2019-09-12 15:26:43.545684863 +0200 {noformat} In this example the {{ServerUtil}} class in target/classes is newer than the one in bin. The simplest way to reproduce: * Open {{ServerUtil}} * add a dummy change, save * add another dummy change, save At this point I get some compiltation errors in ServerUtil but also in SlingLaunchpadBehaviour !compiler-errors-screenshot.png|thumbnail! In the screenshot it's clearly visible that the error is present on the method invocation, but not on the type name and not on the import. [~kwin] - does this problem happen to you as well? > 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 1.2.4 > > 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.3.2#803003)