[JBoss JIRA] (JBIDE-22166) NullPointerException in CDICoreNature.dispose
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22166?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22166:
--------------------------------------
Assignee: Viacheslav Kabanovich
> NullPointerException in CDICoreNature.dispose
> ---------------------------------------------
>
> Key: JBIDE-22166
> URL: https://issues.jboss.org/browse/JBIDE-22166
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.3.1.CR1
> Reporter: Automated Error Reporting Bot
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.x
>
>
> The following problem was reported via the automated error reporting:
> Message: Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.cdi.core.CDICoreNature.dispose(CDICoreNature.java:721)
> at org.jboss.tools.cdi.core.CDICorePlugin$RCL.resourceChanged(CDICorePlugin.java:96)
> at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:299)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:289)
> at org.eclipse.core.internal.events.NotificationManager.handleEvent(NotificationManager.java:265)
> at org.eclipse.core.internal.resources.Workspace.broadcastEvent(Workspace.java:368)
> at org.eclipse.core.internal.resources.Project.move(Project.java:964)
> at org.eclipse.jdt.internal.corext.refactoring.changes.RenameJavaProjectChange.doRename(RenameJavaProjectChange.java:76)
> at org.eclipse.jdt.internal.corext.refactoring.AbstractJavaElementRenameChange.perform(AbstractJavaElementRenameChange.java:89)
> at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278)
> at org.eclipse.jdt.internal.corext.refactoring.changes.DynamicValidationStateChange.access$0(DynamicValidationStateChange.java:1)
> at org.eclipse.jdt.internal.corext.refactoring.changes.DynamicValidationStateChange$1.run(DynamicValidationStateChange.java:113)
> at org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:39)
> at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:729)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
> at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:5409)
> at org.eclipse.jdt.internal.corext.refactoring.changes.DynamicValidationStateChange.perform(DynamicValidationStateChange.java:116)
> at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278)
> at org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
> at org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306)
> at org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92)
> at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:218)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
> at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> {noformat}
> Bundles:
> | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.11.0.v20160310-1245 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160222-1238 |
> | org.eclipse.jdt | 3.11.2.v20160212-1500 | 3.11.2.v20160212-1500 |
> | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.11.2.v20160128-0629 |
> | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.12.0.v20160118-2055 |
> | org.eclipse.ltk.core.refactoring | 3.6.201.v20150819-1034 | 3.7.0.v20160120-1732 |
> | org.eclipse.ltk.ui.refactoring | 3.7.200.v20140625-1835 | 3.8.0.v20151129-1935 |
> | org.eclipse.team.svn | 3.0.3.I20151228-1700 | 3.0.3.I20151228-1700 |
> | org.eclipse.team.svn.core | 3.0.3.I20151228-1700 | 3.0.3.I20151228-1700 |
> | org.eclipse.team.svn.ui | 3.0.3.I20151228-1700 | 3.0.3.I20151228-1700 |
> | org.eclipse.team.ui | 3.7.300.v20151117-1911 | 3.7.300.v20151117-1911 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20160108-0627 |
> | org.jboss.tools.cdi.core | 1.7.1.CR1-v20160129-2014-B69 | 1.8.0.Alpha1-v20160108-2123-B916 |
> Operating Systems:
> | Linux | 4.0.4 | 4.0.4 |
> | MacOSX | 10.10.5 | 10.11.3 |
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit [https://redhat.ctrlflow.com/reviewers/#!/problems/56cb04b0e4b0f02ab70a7d85 this page] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22166) NullPointerException in CDICoreNature.dispose
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22166?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22166:
-----------------------------------
Fix Version/s: 4.4.x
> NullPointerException in CDICoreNature.dispose
> ---------------------------------------------
>
> Key: JBIDE-22166
> URL: https://issues.jboss.org/browse/JBIDE-22166
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.3.1.CR1
> Reporter: Automated Error Reporting Bot
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.x
>
>
> The following problem was reported via the automated error reporting:
> Message: Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.cdi.core.CDICoreNature.dispose(CDICoreNature.java:721)
> at org.jboss.tools.cdi.core.CDICorePlugin$RCL.resourceChanged(CDICorePlugin.java:96)
> at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:299)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:289)
> at org.eclipse.core.internal.events.NotificationManager.handleEvent(NotificationManager.java:265)
> at org.eclipse.core.internal.resources.Workspace.broadcastEvent(Workspace.java:368)
> at org.eclipse.core.internal.resources.Project.move(Project.java:964)
> at org.eclipse.jdt.internal.corext.refactoring.changes.RenameJavaProjectChange.doRename(RenameJavaProjectChange.java:76)
> at org.eclipse.jdt.internal.corext.refactoring.AbstractJavaElementRenameChange.perform(AbstractJavaElementRenameChange.java:89)
> at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278)
> at org.eclipse.jdt.internal.corext.refactoring.changes.DynamicValidationStateChange.access$0(DynamicValidationStateChange.java:1)
> at org.eclipse.jdt.internal.corext.refactoring.changes.DynamicValidationStateChange$1.run(DynamicValidationStateChange.java:113)
> at org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:39)
> at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:729)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
> at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:5409)
> at org.eclipse.jdt.internal.corext.refactoring.changes.DynamicValidationStateChange.perform(DynamicValidationStateChange.java:116)
> at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278)
> at org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
> at org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306)
> at org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92)
> at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:218)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
> at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> {noformat}
> Bundles:
> | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.11.0.v20160310-1245 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160222-1238 |
> | org.eclipse.jdt | 3.11.2.v20160212-1500 | 3.11.2.v20160212-1500 |
> | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.11.2.v20160128-0629 |
> | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.12.0.v20160118-2055 |
> | org.eclipse.ltk.core.refactoring | 3.6.201.v20150819-1034 | 3.7.0.v20160120-1732 |
> | org.eclipse.ltk.ui.refactoring | 3.7.200.v20140625-1835 | 3.8.0.v20151129-1935 |
> | org.eclipse.team.svn | 3.0.3.I20151228-1700 | 3.0.3.I20151228-1700 |
> | org.eclipse.team.svn.core | 3.0.3.I20151228-1700 | 3.0.3.I20151228-1700 |
> | org.eclipse.team.svn.ui | 3.0.3.I20151228-1700 | 3.0.3.I20151228-1700 |
> | org.eclipse.team.ui | 3.7.300.v20151117-1911 | 3.7.300.v20151117-1911 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20160108-0627 |
> | org.jboss.tools.cdi.core | 1.7.1.CR1-v20160129-2014-B69 | 1.8.0.Alpha1-v20160108-2123-B916 |
> Operating Systems:
> | Linux | 4.0.4 | 4.0.4 |
> | MacOSX | 10.10.5 | 10.11.3 |
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit [https://redhat.ctrlflow.com/reviewers/#!/problems/56cb04b0e4b0f02ab70a7d85 this page] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3792) Installer - All installed components should be added to the path
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3792?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3792:
-----------------------------
> Installer - All installed components should be added to the path
> ----------------------------------------------------------------
>
> Key: JBDS-3792
> URL: https://issues.jboss.org/browse/JBDS-3792
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Labels: havoc
>
> The installer (jboss-devstudio-9.1.0.GA-v20160410-1849-B495-installer-eap) adds these components to the user's PATH:
> C:\DeveloperPlatform\vagrant\bin;
> c:\DeveloperPlatform\cdk\bin;
> c:\DeveloperPlatform\vagrant\bin;
> c:\DeveloperPlatform\cygwin\bin;
> It does not add these to the PATH:
> c:\DeveloperPlatform\jdk8\bin;
> c:\DeveloperPlatform\developer-studio
> If we don't add the JDK and JBDS to the PATH by default, then we should give the user the option to add these during the installation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3792) Installer - All installed components should be added to the path
by Len DiMaggio (JIRA)
Len DiMaggio created JBDS-3792:
----------------------------------
Summary: Installer - All installed components should be added to the path
Key: JBDS-3792
URL: https://issues.jboss.org/browse/JBDS-3792
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: installer
Affects Versions: 9.1.0.CR1
Reporter: Len DiMaggio
Assignee: Denis Golovin
The installer (jboss-devstudio-9.1.0.GA-v20160410-1849-B495-installer-eap) adds these components to the user's PATH:
C:\DeveloperPlatform\vagrant\bin;
c:\DeveloperPlatform\cdk\bin;
c:\DeveloperPlatform\vagrant\bin;
c:\DeveloperPlatform\cygwin\bin;
It does not add these to the PATH:
c:\DeveloperPlatform\jdk8\bin;
c:\DeveloperPlatform\developer-studio
If we don't add the JDK and JBDS to the PATH by default, then we should give the user the option to add these during the installation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3792) Installer - All installed components should be added to the path
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3792?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3792:
--------------------------------
> Installer - All installed components should be added to the path
> ----------------------------------------------------------------
>
> Key: JBDS-3792
> URL: https://issues.jboss.org/browse/JBDS-3792
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Labels: havoc
>
> The installer (jboss-devstudio-9.1.0.GA-v20160410-1849-B495-installer-eap) adds these components to the user's PATH:
> C:\DeveloperPlatform\vagrant\bin;
> c:\DeveloperPlatform\cdk\bin;
> c:\DeveloperPlatform\vagrant\bin;
> c:\DeveloperPlatform\cygwin\bin;
> It does not add these to the PATH:
> c:\DeveloperPlatform\jdk8\bin;
> c:\DeveloperPlatform\developer-studio
> If we don't add the JDK and JBDS to the PATH by default, then we should give the user the option to add these during the installation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3792) Installer - All installed components should be added to the path
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3792?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-3792:
-------------------------------
Labels: havoc (was: )
> Installer - All installed components should be added to the path
> ----------------------------------------------------------------
>
> Key: JBDS-3792
> URL: https://issues.jboss.org/browse/JBDS-3792
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Labels: havoc
>
> The installer (jboss-devstudio-9.1.0.GA-v20160410-1849-B495-installer-eap) adds these components to the user's PATH:
> C:\DeveloperPlatform\vagrant\bin;
> c:\DeveloperPlatform\cdk\bin;
> c:\DeveloperPlatform\vagrant\bin;
> c:\DeveloperPlatform\cygwin\bin;
> It does not add these to the PATH:
> c:\DeveloperPlatform\jdk8\bin;
> c:\DeveloperPlatform\developer-studio
> If we don't add the JDK and JBDS to the PATH by default, then we should give the user the option to add these during the installation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22129) Watches should not try to reconnect when a project has been deleted
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22129?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-22129:
---------------------------------------
yes. This is expected since we are trying to get a project and it doesn't exist. The server on purpose returns 403 instead of 404
> Watches should not try to reconnect when a project has been deleted
> -------------------------------------------------------------------
>
> Key: JBIDE-22129
> URL: https://issues.jboss.org/browse/JBIDE-22129
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Labels: respin-b
> Fix For: 4.3.1.CR1
>
>
> When a project has been deleted from the webconsole, the watchmanager in eclipse is not notified. Each watch that times out tries to reconnect to some of the dead project's urls. Each access is rejected with 403 errors (the project could exist but not be visible to the user).
> After each attempt, the watches will wait a little longer before trying to reconnect, until it eventually stops trying.
> Since the watch manager has access to the projects, it can try to check the project exists before connecting the watch
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22164) Enable addition of secrets for OpenShift 3 projects
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22164?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-22164:
---------------------------------------
Once we enable create resource that will allow someone to create secrets from a file until we can add a proper UI. If we do not already support a secret resource, it would still be available as a generic resource that is the default for kinds that don't have specific types.
> Enable addition of secrets for OpenShift 3 projects
> ---------------------------------------------------
>
> Key: JBIDE-22164
> URL: https://issues.jboss.org/browse/JBIDE-22164
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: openshift_v3
> Fix For: 4.4.x
>
>
> Not every developer will use only public git and docker repositories. Or there are other reasons for usage of secrets. It would be nice if we would have some simple wizard to add a secret for OpenShift project/connection (would be accessible for all projects of a connection).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22164) Enable addition of secrets for OpenShift 3 projects
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22164?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-22164:
-------------------------------------
OK, that seems non trivial. Not sure how we're gonna handle that.
We need to determine the priority on this. [~maxandersen], [~burrsutter], [~jcantrill]?
> Enable addition of secrets for OpenShift 3 projects
> ---------------------------------------------------
>
> Key: JBIDE-22164
> URL: https://issues.jboss.org/browse/JBIDE-22164
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: openshift_v3
> Fix For: 4.4.x
>
>
> Not every developer will use only public git and docker repositories. Or there are other reasons for usage of secrets. It would be nice if we would have some simple wizard to add a secret for OpenShift project/connection (would be accessible for all projects of a connection).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22157) On deployoment, utility JAR projects are being exploded on WEB-INF/LIB
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22157?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-22157:
-------------------------------------
See also: JBIDE-20577 Allow setting exploded or zipped on per-module basis
> On deployoment, utility JAR projects are being exploded on WEB-INF/LIB
> ----------------------------------------------------------------------
>
> Key: JBIDE-22157
> URL: https://issues.jboss.org/browse/JBIDE-22157
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Environment: Eclipse: Mars, latest version.
> Webserver: Wilfly 10.0.0
> Maven: 3.3.3
> JBoss Tools: Latest version.
> Reporter: Tiago Matias
> Assignee: Rob Stryker
> Fix For: 4.4.0.Alpha1
>
>
> Consider two eclipse maven projects: A Web project (WAR) and a Utility project JAR with a JSP TLD file inside.
> After building the project and deploying to Wildfly the utiltiy JAR will be exploded under WEB-INF/LIB of the WAR project.
> An exploded jar is incompatible with TLD files since the JSP engine search for the TLD file and then try to open/unzip the JAR. Since the JAR is just a folder, it causes an "Access Denied" exception, as shown below:
> org.apache.jasper.JasperException: java.io.FileNotFoundException: C:\Program Files\Java\wildfly-10.0.0.Final\standalone\deployments\portal.web.war\WEB-INF\lib\portal.framework-0.0.1-SNAPSHOT.jar (Acesso negado)
> org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:151)
> org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:412)
> org.apache.jasper.compiler.Parser.parseDirective(Parser.java:475)
> org.apache.jasper.compiler.Parser.parseElements(Parser.java:1456)
> org.apache.jasper.compiler.Parser.parse(Parser.java:143)
> A possible alternative would be to turnoff the option "Resolve dependencies from workspace projects" in Eclipse. In this scenario the JAR won't get exploded on WAR's WEB-INF/lib and everything works. However, any change to the JAR project won't get picked up and deployed to the target unless it's POM version is incremented which is incompatible with a development scenario where the projects are constantly updated and built.
> I request that the eclipse wildfly connector provides an option to control weather the dependency JAR's are exploded or not into the final deployment.
> Please note, this only applies to dependencies that are workspace projects. All the other dependencies (spring, hibernate, etc...) are simply copied as a JAR archive, as expected.
> Thank you.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years