Re: [RESULT] [VOTE] Release Apache Sling Commons Log 5.5.0
Hi Robert. I think you may have missed the step that pushes the release to maven central for this one? The 5.5.0 version is not on maven central and the staging repository still exists. Regards, Eric On Tue, Feb 6, 2024 at 5:17 AM Robert Munteanu wrote: > Hi, > > The vote has passed with the following result: > > +1 (binding): Robert Munteanu, Stefan Seifert, Carsten Ziegeler, Joerg > Hoh, Eric Norman > +1 (non-binding): none > > I will copy this release to the Sling dist directory and > promote the artifacts to the central Maven repository. > > Regards, > Robert Munteanu > >
[jira] [Updated] (SLING-12249) Clarify "ADDED" resource changes for ancestor nodes of path
[ https://issues.apache.org/jira/browse/SLING-12249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-12249: Description: Similar to what was clarified in SLING-6066, events for ancestors of the registered path may not only be received for "REMOVED" resource changes but also for "ADDED" resource changes. This happens e.g. for moving resources with the JCR Resource Provider which uses internally the semantics from https://issues.apache.org/jira/browse/OAK-1459?focusedCommentId=13911484&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-13911484 was: Similar to what was clarified in SLING-6066, events outside the path may not only be received for "REMOVED" resource changes but also for "ADDED" resource changes. This happens e.g. for moving resources with the JCR Resource Provider which uses internally the semantics from https://issues.apache.org/jira/browse/OAK-1459?focusedCommentId=13911484&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-13911484 > Clarify "ADDED" resource changes for ancestor nodes of path > --- > > Key: SLING-12249 > URL: https://issues.apache.org/jira/browse/SLING-12249 > Project: Sling > Issue Type: Improvement > Components: API >Affects Versions: API 2.15.0 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > > Similar to what was clarified in SLING-6066, events for ancestors of the > registered path may not only be received for "REMOVED" resource changes but > also for "ADDED" resource changes. > This happens e.g. for moving resources with the JCR Resource Provider which > uses internally the semantics from > https://issues.apache.org/jira/browse/OAK-1459?focusedCommentId=13911484&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-13911484 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] SLING-12249 Clarify that both REMOVED and ADDED events may be received [sling-org-apache-sling-api]
sonarcloud[bot] commented on PR #51: URL: https://github.com/apache/sling-org-apache-sling-api/pull/51#issuecomment-1932702058 ## [![Quality Gate Passed](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/checks/QualityGateBadge/qg-passed-20px.png 'Quality Gate Passed')](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-api&pullRequest=51) **Quality Gate passed** Kudos, no new issues were introduced! [0 New issues](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-api&pullRequest=51&resolved=false&inNewCodePeriod=true) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-api&pullRequest=51&resolved=false&inNewCodePeriod=true) No data about Coverage [0.0% Duplication on New Code](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-api&pullRequest=51&metric=new_duplicated_lines_density&view=list) [See analysis details on SonarCloud](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-api&pullRequest=51) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] SLING-12249 Clarify that both REMOVED and ADDED events may be received [sling-org-apache-sling-api]
kwin opened a new pull request, #51: URL: https://github.com/apache/sling-org-apache-sling-api/pull/51 for ancestors of registered path. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (SLING-12249) Clarify "ADDED" resource changes for ancestor nodes of path
Konrad Windszus created SLING-12249: --- Summary: Clarify "ADDED" resource changes for ancestor nodes of path Key: SLING-12249 URL: https://issues.apache.org/jira/browse/SLING-12249 Project: Sling Issue Type: Improvement Components: API Affects Versions: API 2.15.0 Reporter: Konrad Windszus Assignee: Konrad Windszus Similar to what was clarified in SLING-6066, events outside the path may not only be received for "REMOVED" resource changes but also for "ADDED" resource changes. This happens e.g. for moving resources with the JCR Resource Provider which uses internally the semantics from https://issues.apache.org/jira/browse/OAK-1459?focusedCommentId=13911484&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-13911484 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SLING-12245) Sling Rewriter does not detect configuration changes coming in via move
[ https://issues.apache.org/jira/browse/SLING-12245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17815401#comment-17815401 ] Konrad Windszus commented on SLING-12245: - [~cziegeler] Do we need another flag in Oak named {{withIncludeAncestorsAdd()}} similar to {{withIncludeAncestorsRemove}} introduced with OAK-5020? What was the original reason why only remove was considered in that flag in the first place? > Sling Rewriter does not detect configuration changes coming in via move > --- > > Key: SLING-12245 > URL: https://issues.apache.org/jira/browse/SLING-12245 > Project: Sling > Issue Type: Improvement >Affects Versions: Rewriter 1.3.10 >Reporter: Konrad Windszus >Priority: Major > > If one renames/moves a JCR node from {{/apps/my/config/invalid-rewriter}} to > {{/apps/my/config/rewriter}} the new rewriter configuration is not being > detected by the {{ProcessorManagerImpl}} due to the > {{ResourceChangeListener}} only being configured to listen for changes below > the {{rewriter}} resource > (https://github.com/apache/sling-org-apache-sling-rewriter/blob/4d1952648e35e7001236f282040a78479f7726d4/src/main/java/org/apache/sling/rewriter/impl/ProcessorManagerImpl.java#L69). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (SLING-12245) Sling Rewriter does not detect configuration changes coming in via move
[ https://issues.apache.org/jira/browse/SLING-12245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17815393#comment-17815393 ] Konrad Windszus edited comment on SLING-12245 at 2/7/24 6:33 PM: - Debugging revealed the following: When renaming a working rewriter pipeline config from {{/apps/system/config/rewriter2}} to {{/apps/system/config/rewriter}} the following {{ResourceChange}} is received: {code} ResourceChange[type=ADDED, path=/apps/system/config/rewriter, external=false] {code} which is ignored in {{ProcessorManagerImpl.onChange(...)}} However when renaming a working rewriter pipeline config from {{/apps/system/config/rewriter}} to {{/apps/system/config/rewriter2}} the following {{ResourceChanges}} are received: {code} ResourceChange[type=REMOVED, path=/apps/system/config/rewriter, external=false] ResourceChange[type=REMOVED, path=/apps/system/config/rewriter/custom, external=false] {code} which leads to removing the config at {{/apps/system/config/rewriter}} in {{ProcessorManagerImpl.onChange(...)}} (in case it was previously registered). This is due to the fact how the JCR Event Listener is being registered in https://github.com/apache/sling-org-apache-sling-jcr-resource/blob/8fb5a3d44de01f05964028debcf24531f2f65747/src/main/java/org/apache/sling/jcr/resource/internal/JcrListenerBaseConfig.java#L104. Looks like the OakEventFilter does not behave synchronously here, i.e. in case of renames only notifies about each removal of a subtree, but not for the addition for each addition of a subtree. was (Author: kwin): Debugging revealed the following: When renaming a working rewriter pipeline config from {{/apps/system/config/rewriter2}} to {{/apps/system/config/rewriter}} the following {{ResourceChange}} is received: {code} ResourceChange[type=ADDED, path=/apps/system/config/rewriter, external=false] {code} which is ignored in {{ProcessorManagerImpl.onChange(...)}} However when renaming a working rewriter pipeline config from {{/apps/system/config/rewriter}} to {{/apps/system/config/rewriter2}} the following {{ResourceChanges}} are received: {code} ResourceChange[type=REMOVED, path=/apps/system/config/rewriter, external=false] ResourceChange[type=REMOVED, path=/apps/system/config/rewriter/custom, external=false] {code} which leads to removing the config at {{/apps/system/config/rewriter}} in {{ProcessorManagerImpl.onChange(...)}} (in case it was previously registered). > Sling Rewriter does not detect configuration changes coming in via move > --- > > Key: SLING-12245 > URL: https://issues.apache.org/jira/browse/SLING-12245 > Project: Sling > Issue Type: Improvement >Affects Versions: Rewriter 1.3.10 >Reporter: Konrad Windszus >Priority: Major > > If one renames/moves a JCR node from {{/apps/my/config/invalid-rewriter}} to > {{/apps/my/config/rewriter}} the new rewriter configuration is not being > detected by the {{ProcessorManagerImpl}} due to the > {{ResourceChangeListener}} only being configured to listen for changes below > the {{rewriter}} resource > (https://github.com/apache/sling-org-apache-sling-rewriter/blob/4d1952648e35e7001236f282040a78479f7726d4/src/main/java/org/apache/sling/rewriter/impl/ProcessorManagerImpl.java#L69). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SLING-12245) Sling Rewriter does not detect configuration changes coming in via move
[ https://issues.apache.org/jira/browse/SLING-12245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17815393#comment-17815393 ] Konrad Windszus commented on SLING-12245: - Debugging revealed the following: When renaming a working rewriter pipeline config from {{/apps/system/config/rewriter2}} to {{/apps/system/config/rewriter}} the following {{ResourceChange}} is received: {code} ResourceChange[type=ADDED, path=/apps/system/config/rewriter, external=false] {code} which is ignored in {{ProcessorManagerImpl.onChange(...)}} However when renaming a working rewriter pipeline config from {{/apps/system/config/rewriter}} to {{/apps/system/config/rewriter2}} the following {{ResourceChanges}} are received: {code} ResourceChange[type=REMOVED, path=/apps/system/config/rewriter, external=false] ResourceChange[type=REMOVED, path=/apps/system/config/rewriter/custom, external=false] {code} which leads to removing the config at {{/apps/system/config/rewriter}} in {{ProcessorManagerImpl.onChange(...)}} (in case it was previously registered). > Sling Rewriter does not detect configuration changes coming in via move > --- > > Key: SLING-12245 > URL: https://issues.apache.org/jira/browse/SLING-12245 > Project: Sling > Issue Type: Improvement >Affects Versions: Rewriter 1.3.10 >Reporter: Konrad Windszus >Priority: Major > > If one renames/moves a JCR node from {{/apps/my/config/invalid-rewriter}} to > {{/apps/my/config/rewriter}} the new rewriter configuration is not being > detected by the {{ProcessorManagerImpl}} due to the > {{ResourceChangeListener}} only being configured to listen for changes below > the {{rewriter}} resource > (https://github.com/apache/sling-org-apache-sling-rewriter/blob/4d1952648e35e7001236f282040a78479f7726d4/src/main/java/org/apache/sling/rewriter/impl/ProcessorManagerImpl.java#L69). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-12247) Provide component property type for (External)ResourceChangeListener
[ https://issues.apache.org/jira/browse/SLING-12247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-12247: Component/s: Resource Observation Annotations > Provide component property type for (External)ResourceChangeListener > > > Key: SLING-12247 > URL: https://issues.apache.org/jira/browse/SLING-12247 > Project: Sling > Issue Type: Improvement > Components: Resource Observation Annotations >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > > In order to ease registration of Sling ResourceChangeListeners a [component > property type > |https://docs.osgi.org/specification/osgi.cmpn/7.0.0/service.component.html#service.component-component.property.types] > should be provided with elements for all supported properties. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] SLING-12246 Add tests for move and orderBefore operations [sling-org-apache-sling-jcr-resource]
sonarcloud[bot] commented on PR #41: URL: https://github.com/apache/sling-org-apache-sling-jcr-resource/pull/41#issuecomment-1932163631 ## [![Quality Gate Passed](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/checks/QualityGateBadge/qg-passed-20px.png 'Quality Gate Passed')](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-jcr-resource&pullRequest=41) **Quality Gate passed** The SonarCloud Quality Gate passed, but some issues were introduced. [3 New issues](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-resource&pullRequest=41&resolved=false&inNewCodePeriod=true) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-resource&pullRequest=41&resolved=false&inNewCodePeriod=true) No data about Coverage [0.0% Duplication on New Code](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-resource&pullRequest=41&metric=new_duplicated_lines_density&view=list) [See analysis details on SonarCloud](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-jcr-resource&pullRequest=41) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (SLING-12246) Support Event.NODE_MOVED in JcrResourceListener
[ https://issues.apache.org/jira/browse/SLING-12246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17815320#comment-17815320 ] Konrad Windszus commented on SLING-12246: - Indeed {{Session.move()}} always emits "NODE_DELETE" and "NODE_ADDED" for the root paths in Oak. There is no event currently emitted for {{Node.orderBefore(...)}} (only a "NODE_MOVED") is sent for that operation). > Support Event.NODE_MOVED in JcrResourceListener > --- > > Key: SLING-12246 > URL: https://issues.apache.org/jira/browse/SLING-12246 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR Resource 3.2.4 >Reporter: Konrad Windszus >Priority: Major > > Currently the event type NODE_MOVED > (https://developer.adobe.com/experience-manager/reference-materials/spec/jcr/2.0/12_Observation.html#12.3.3%20Event%20Information%20on%20Move%20and%20Order) > is not supported in {{JcrResourceListener}} > (https://github.com/apache/sling-org-apache-sling-jcr-resource/blob/8fb5a3d44de01f05964028debcf24531f2f65747/src/main/java/org/apache/sling/jcr/resource/internal/JcrResourceListener.java#L117). > Although the support in Oak is limited > (https://jackrabbit.apache.org/oak/docs/differences.html#observation) the > even type is still used. > IMHO it should be translated into two {{ResourceChange}} events: > # one change on the source path > # one change on the destination path > The path handling for > https://sling.apache.org/apidocs/sling12/org/apache/sling/api/resource/observation/ResourceChangeListener.html#PATHS > must be the same as for remove events (i.e. changed parent paths will also > trigger it) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] SLING-12246 Add tests for move and orderBefore operations [sling-org-apache-sling-jcr-resource]
kwin opened a new pull request, #41: URL: https://github.com/apache/sling-org-apache-sling-jcr-resource/pull/41 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (SLING-12247) Provide component property type for (External)ResourceChangeListener
[ https://issues.apache.org/jira/browse/SLING-12247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17815248#comment-17815248 ] Konrad Windszus commented on SLING-12247: - I created the new repo https://github.com/apache/sling-org-apache-sling-resource-observation-annotations for it. > Provide component property type for (External)ResourceChangeListener > > > Key: SLING-12247 > URL: https://issues.apache.org/jira/browse/SLING-12247 > Project: Sling > Issue Type: Improvement >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > > In order to ease registration of Sling ResourceChangeListeners a [component > property type > |https://docs.osgi.org/specification/osgi.cmpn/7.0.0/service.component.html#service.component-component.property.types] > should be provided with elements for all supported properties. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [I] NoSuchNodeTypeException [sling-org-apache-sling-starter]
rombert closed issue #304: NoSuchNodeTypeException URL: https://github.com/apache/sling-org-apache-sling-starter/issues/304 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] NoSuchNodeTypeException [sling-org-apache-sling-starter]
rombert commented on issue #304: URL: https://github.com/apache/sling-org-apache-sling-starter/issues/304#issuecomment-1931637459 Hi @StupidSmart and thanks for your report. Please use the users mailing list ( https://sling.apache.org/project-information.html#mailing-lists-1 ) for support queries. There seems to be a very similar post at https://lists.apache.org/thread/kmxc48soggf3vpnwo9prm10zs9so1b6n, perhaps you can join the conversation there? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] NoSuchNodeTypeException [sling-org-apache-sling-starter]
rombert closed issue #304: NoSuchNodeTypeException URL: https://github.com/apache/sling-org-apache-sling-starter/issues/304 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (SLING-12248) Sling IDE Tools 1.2.2 looking for non-existent class, org.eclipse.m2e.core.internal.index.IndexListener
Dat Huynh created SLING-12248: - Summary: Sling IDE Tools 1.2.2 looking for non-existent class, org.eclipse.m2e.core.internal.index.IndexListener Key: SLING-12248 URL: https://issues.apache.org/jira/browse/SLING-12248 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: OSGi Feature Maven Plugin 1.8.0 Environment: Eclipse 2023-12, Maven 3.8.1, Java 11, AEM 1.3.0, Sling IDE Tools 1.2.2 Reporter: Dat Huynh AEM (Adobe Experience Manager) Developer Tool latest version with latest Sling IDE tool depends on a non-existent Java class of M2E, org.eclipse.m2e.core.internal.index.IndexListener. {code:java} java.lang.NoClassDefFoundError: org/eclipse/m2e/core/internal/index/IndexListener at java.base/java.lang.ClassLoader.defineClass1(Native Method) at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1027) at org.eclipse.osgi.internal.loader.ModuleClassLoader.defineClass(ModuleClassLoader.java:283) at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.defineClass(ClasspathManager.java:716) at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findClassImpl(ClasspathManager.java:639) at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClassImpl(ClasspathManager.java:607) at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClassImpl(ClasspathManager.java:587) at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:566) at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:335) at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:397) at org.eclipse.osgi.internal.loader.BundleLoader.findClass0(BundleLoader.java:500) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:416) at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:168) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:526) at org.apache.sling.ide.eclipse.ui.wizards.np.AbstractNewMavenBasedSlingApplicationWizard.addPages(AbstractNewMavenBasedSlingApplicationWizard.java:72) at org.eclipse.jface.wizard.WizardSelectionPage.getNextPage(WizardSelectionPage.java:119) at org.eclipse.ui.internal.dialogs.WorkbenchWizardSelectionPage.getNextPage(WorkbenchWizardSelectionPage.java:98) at org.eclipse.ui.internal.dialogs.NewWizardSelectionPage.advanceToNextPageOrFinish(NewWizardSelectionPage.java:73) at org.eclipse.ui.internal.dialogs.NewWizardNewPage.lambda$0(NewWizardNewPage.java:342) at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:780) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:47) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:174) at org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:777) at org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSelect(AbstractTreeViewer.java:1559) at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1210) at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:272) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:329) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4273) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1066) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4071) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3659) at org.eclipse.jface.window.Window.runEventLoop(Window.java:823) at org.eclipse.jface.window.Window.open(Window.java:799) at org.eclipse.ui.actions.NewProjectAction.run(NewProjectAction.java:119) at org.eclipse.jface.action.Action.runWithEvent(Action.java:474) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:580) at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:414) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4273) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1066) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4071) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3659) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:342) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1046) at org.eclipse.e4.ui.internal.workbench.E4