[JBoss JIRA] (JBIDE-26548) Nullpointer when renaming inner class java variables - JSFRenameFieldParticipant
by Thomas Zauner (Jira)
[ https://issues.jboss.org/browse/JBIDE-26548?page=com.atlassian.jira.plugi... ]
Thomas Zauner updated JBIDE-26548:
----------------------------------
Description:
Renaming of inner class java variables leads to an Nullpointer in JSFRenameFieldParticipant. The second rename is working, since the JSFRenameFieldParticipant is removed due to the exception.
{noformat}
!ENTRY org.eclipse.ltk.core.refactoring 4 10009 2019-02-07 08:02:57.183
!MESSAGE Participant 'org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant' removed due to the following exception
!STACK 0
java.lang.NullPointerException
at org.jboss.tools.jsf.model.pv.JSFProjectsTree.getProjectsRoot(JSFProjectsTree.java:45)
at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldHelper.getBeanList(JSFRenameFieldHelper.java:48)
at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant.createChange(JSFRenameFieldParticipant.java:68)
at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.createChange(ProcessorBasedRefactoring.java:309)
at org.eclipse.jdt.internal.ui.refactoring.RefactoringExecutionHelper$Operation.run(RefactoringExecutionHelper.java:102)
at org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:41)
at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:736)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2295)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2322)
at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:5810)
at org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:108)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
{noformat}
{code:java}
public class JavaClass {
private boolean first; // rename will work
public class InnerClass {
private boolean second; // rename leads to NPE
}
}
{code}
was:
Renaming of inner class java variables leads to an Nullpointer in JSFRenameFieldParticipant. The second rename is working, since the JSFRenameFieldParticipant is removed due to the exception.
!ENTRY org.eclipse.ltk.core.refactoring 4 10009 2019-02-07 08:02:57.183
!MESSAGE Participant 'org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant' removed due to the following exception
!STACK 0
java.lang.NullPointerException
at org.jboss.tools.jsf.model.pv.JSFProjectsTree.getProjectsRoot(JSFProjectsTree.java:45)
at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldHelper.getBeanList(JSFRenameFieldHelper.java:48)
at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant.createChange(JSFRenameFieldParticipant.java:68)
at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.createChange(ProcessorBasedRefactoring.java:309)
at org.eclipse.jdt.internal.ui.refactoring.RefactoringExecutionHelper$Operation.run(RefactoringExecutionHelper.java:102)
at org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:41)
at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:736)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2295)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2322)
at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:5810)
at org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:108)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
public class JavaClass {
private boolean first; // rename will work
public class InnerClass {
private boolean second; // rename leads to NPE
}
}
> Nullpointer when renaming inner class java variables - JSFRenameFieldParticipant
> --------------------------------------------------------------------------------
>
> Key: JBIDE-26548
> URL: https://issues.jboss.org/browse/JBIDE-26548
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.10.0.AM1
> Environment: Linux with Eclipse 2018-12
> Reporter: Thomas Zauner
> Priority: Major
>
> Renaming of inner class java variables leads to an Nullpointer in JSFRenameFieldParticipant. The second rename is working, since the JSFRenameFieldParticipant is removed due to the exception.
> {noformat}
> !ENTRY org.eclipse.ltk.core.refactoring 4 10009 2019-02-07 08:02:57.183
> !MESSAGE Participant 'org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant' removed due to the following exception
> !STACK 0
> java.lang.NullPointerException
> at org.jboss.tools.jsf.model.pv.JSFProjectsTree.getProjectsRoot(JSFProjectsTree.java:45)
> at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldHelper.getBeanList(JSFRenameFieldHelper.java:48)
> at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant.createChange(JSFRenameFieldParticipant.java:68)
> at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.createChange(ProcessorBasedRefactoring.java:309)
> at org.eclipse.jdt.internal.ui.refactoring.RefactoringExecutionHelper$Operation.run(RefactoringExecutionHelper.java:102)
> at org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:41)
> at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:736)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2295)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2322)
> at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:5810)
> at org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:108)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
> {noformat}
> {code:java}
> public class JavaClass {
> private boolean first; // rename will work
> public class InnerClass {
> private boolean second; // rename leads to NPE
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (JBIDE-26548) Nullpointer when renaming inner class java variables - JSFRenameFieldParticipant
by Thomas Zauner (Jira)
Thomas Zauner created JBIDE-26548:
-------------------------------------
Summary: Nullpointer when renaming inner class java variables - JSFRenameFieldParticipant
Key: JBIDE-26548
URL: https://issues.jboss.org/browse/JBIDE-26548
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 4.10.0.AM1
Environment: Linux with Eclipse 2018-12
Reporter: Thomas Zauner
Renaming of inner class java variables leads to an Nullpointer in JSFRenameFieldParticipant. The second rename is working, since the JSFRenameFieldParticipant is removed due to the exception.
!ENTRY org.eclipse.ltk.core.refactoring 4 10009 2019-02-07 08:02:57.183
!MESSAGE Participant 'org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant' removed due to the following exception
!STACK 0
java.lang.NullPointerException
at org.jboss.tools.jsf.model.pv.JSFProjectsTree.getProjectsRoot(JSFProjectsTree.java:45)
at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldHelper.getBeanList(JSFRenameFieldHelper.java:48)
at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant.createChange(JSFRenameFieldParticipant.java:68)
at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.createChange(ProcessorBasedRefactoring.java:309)
at org.eclipse.jdt.internal.ui.refactoring.RefactoringExecutionHelper$Operation.run(RefactoringExecutionHelper.java:102)
at org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:41)
at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:736)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2295)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2322)
at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:5810)
at org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:108)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
public class JavaClass {
private boolean first; // rename will work
public class InnerClass {
private boolean second; // rename leads to NPE
}
}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (JBIDE-26547) NoClassDefFoundError in RenameProcessorRunner with Eclipse 20181214-0600
by Thomas Zauner (Jira)
[ https://issues.jboss.org/browse/JBIDE-26547?page=com.atlassian.jira.plugi... ]
Thomas Zauner commented on JBIDE-26547:
---------------------------------------
Okay, thanks for the hint. Just tested the Nightly 4.10 which leads to another exception with 2018-12 but at least the JSFRenameFieldParticipant is removed due to the exception and second rename works again.
I will check and may open another issue for the current Nullpointer.
> NoClassDefFoundError in RenameProcessorRunner with Eclipse 20181214-0600
> ------------------------------------------------------------------------
>
> Key: JBIDE-26547
> URL: https://issues.jboss.org/browse/JBIDE-26547
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.9.0.Final
> Environment: Linux with Eclipse 20181214-0600
> Reporter: Thomas Zauner
> Priority: Major
>
> When refactoring variables/methods this fails silent and changes are reverted. This is caused by the following error:
> Caused by: java.lang.NoClassDefFoundError: org/eclipse/jdt/internal/corext/refactoring/tagging/IReferenceUpdating
> at org.jboss.tools.common.model.refactoring.RenameProcessorRunner.updateReferences(RenameProcessorRunner.java:52)
> at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant.updateReferences(JSFRenameFieldParticipant.java:121)
> at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant.createChange(JSFRenameFieldParticipant.java:61)
> at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.createChange(ProcessorBasedRefactoring.java:309)
> at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:125)
> at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:210)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2295)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2322)
> at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:89)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (JBIDE-26547) NoClassDefFoundError in RenameProcessorRunner with Eclipse 20181214-0600
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26547?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-26547:
------------------------------------
JBoss Tools 4.9.0 is validated against 2018-09 not 2018-12
> NoClassDefFoundError in RenameProcessorRunner with Eclipse 20181214-0600
> ------------------------------------------------------------------------
>
> Key: JBIDE-26547
> URL: https://issues.jboss.org/browse/JBIDE-26547
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.9.0.Final
> Environment: Linux with Eclipse 20181214-0600
> Reporter: Thomas Zauner
> Priority: Major
>
> When refactoring variables/methods this fails silent and changes are reverted. This is caused by the following error:
> Caused by: java.lang.NoClassDefFoundError: org/eclipse/jdt/internal/corext/refactoring/tagging/IReferenceUpdating
> at org.jboss.tools.common.model.refactoring.RenameProcessorRunner.updateReferences(RenameProcessorRunner.java:52)
> at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant.updateReferences(JSFRenameFieldParticipant.java:121)
> at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant.createChange(JSFRenameFieldParticipant.java:61)
> at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.createChange(ProcessorBasedRefactoring.java:309)
> at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:125)
> at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:210)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2295)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2322)
> at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:89)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (JBIDE-26547) NoClassDefFoundError in RenameProcessorRunner with Eclipse 20181214-0600
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26547?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-26547.
------------------------------
Resolution: Won't Do
> NoClassDefFoundError in RenameProcessorRunner with Eclipse 20181214-0600
> ------------------------------------------------------------------------
>
> Key: JBIDE-26547
> URL: https://issues.jboss.org/browse/JBIDE-26547
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.9.0.Final
> Environment: Linux with Eclipse 20181214-0600
> Reporter: Thomas Zauner
> Priority: Major
>
> When refactoring variables/methods this fails silent and changes are reverted. This is caused by the following error:
> Caused by: java.lang.NoClassDefFoundError: org/eclipse/jdt/internal/corext/refactoring/tagging/IReferenceUpdating
> at org.jboss.tools.common.model.refactoring.RenameProcessorRunner.updateReferences(RenameProcessorRunner.java:52)
> at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant.updateReferences(JSFRenameFieldParticipant.java:121)
> at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant.createChange(JSFRenameFieldParticipant.java:61)
> at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.createChange(ProcessorBasedRefactoring.java:309)
> at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:125)
> at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:210)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2295)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2322)
> at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:89)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (JBIDE-26547) NoClassDefFoundError in RenameProcessorRunner with Eclipse 20181214-0600
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26547?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26547:
-------------------------------
Component/s: jsf
> NoClassDefFoundError in RenameProcessorRunner with Eclipse 20181214-0600
> ------------------------------------------------------------------------
>
> Key: JBIDE-26547
> URL: https://issues.jboss.org/browse/JBIDE-26547
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.9.0.Final
> Environment: Linux with Eclipse 20181214-0600
> Reporter: Thomas Zauner
> Priority: Major
>
> When refactoring variables/methods this fails silent and changes are reverted. This is caused by the following error:
> Caused by: java.lang.NoClassDefFoundError: org/eclipse/jdt/internal/corext/refactoring/tagging/IReferenceUpdating
> at org.jboss.tools.common.model.refactoring.RenameProcessorRunner.updateReferences(RenameProcessorRunner.java:52)
> at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant.updateReferences(JSFRenameFieldParticipant.java:121)
> at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant.createChange(JSFRenameFieldParticipant.java:61)
> at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.createChange(ProcessorBasedRefactoring.java:309)
> at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:125)
> at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:210)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2295)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2322)
> at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:89)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (JBDS-4730) [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBDS-4730?page=com.atlassian.jira.plugin.... ]
Jeff MAURY commented on JBDS-4730:
----------------------------------
[~tnolan] [~sjcox] [~james.cobb] who'is in charge of providing us with the updated graphics ?
> [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text
> ----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4730
> URL: https://issues.jboss.org/browse/JBDS-4730
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build, installer
> Affects Versions: 12.9.0.AM3
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 12.11.0.AM1
>
> Attachments: CR-Studio_wordmarks.zip
>
>
> Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "Red Hat CodeReady Studio".
> As we did recently in JBDS-4706, we'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/
> We'll need this rebrand done for the upcoming December release. All changes need to be done by November 6 so they can be included in the AM1 feature complete release on Nov 13, in support of the docs team, updating screenshots, install instructions, etc.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (JBDS-4730) [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text
by Nick Boldt (Jira)
[ https://issues.jboss.org/browse/JBDS-4730?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4730:
----------------------------------
Here are the wordmarks for CR Studio: [^CR-Studio_wordmarks.zip]
[~jeffmaury] FYI ^
> [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text
> ----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4730
> URL: https://issues.jboss.org/browse/JBDS-4730
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build, installer
> Affects Versions: 12.9.0.AM3
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 12.11.0.AM1
>
> Attachments: CR-Studio_wordmarks.zip
>
>
> Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "Red Hat CodeReady Studio".
> As we did recently in JBDS-4706, we'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/
> We'll need this rebrand done for the upcoming December release. All changes need to be done by November 6 so they can be included in the AM1 feature complete release on Nov 13, in support of the docs team, updating screenshots, install instructions, etc.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (JBDS-4730) [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text
by Nick Boldt (Jira)
[ https://issues.jboss.org/browse/JBDS-4730?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4730:
-----------------------------
Attachment: CR-Studio_wordmarks.zip
> [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text
> ----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4730
> URL: https://issues.jboss.org/browse/JBDS-4730
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build, installer
> Affects Versions: 12.9.0.AM3
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 12.11.0.AM1
>
> Attachments: CR-Studio_wordmarks.zip
>
>
> Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "Red Hat CodeReady Studio".
> As we did recently in JBDS-4706, we'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/
> We'll need this rebrand done for the upcoming December release. All changes need to be done by November 6 so they can be included in the AM1 feature complete release on Nov 13, in support of the docs team, updating screenshots, install instructions, etc.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month