February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-22894) ResourceException below IDETernProject.getTernProject (thrown in Project.checkAccessible)

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22894?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-22894: ----------------------------------------- https://github.com/angelozerr/tern.java/issues/440 is fixed in Tern.java's master branch > ResourceException below IDETernProject.getTernProject (thrown in Project.checkAccessible) > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22894 > URL: https://issues.jboss.org/browse/JBIDE-22894 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, upstream > Affects Versions: 4.3.0.Final > Reporter: Automated Error Reporting Bot > Assignee: Victor Rubezhny > Fix For: 4.4.x > > > The following problem was reported via the automated error reporting: > Message: Error while tern file synchronization > {noformat} > org.eclipse.core.internal.resources.ResourceException: Resource '/reporting-app' is not open. > at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:143) > at org.eclipse.core.internal.resources.Resource.checkAccessibleAndLocal(Resource.java:214) > at org.eclipse.core.internal.resources.Resource.getSessionProperty(Resource.java:1206) > at tern.eclipse.ide.internal.core.resources.IDETernProject.getTernProject(IDETernProject.java:708) > at tern.eclipse.ide.internal.core.resources.IDETernProjectSynchronizer.disposeTernProject(IDETernProjectSynchronizer.java:93) > at tern.eclipse.ide.internal.core.resources.IDETernProjectSynchronizer.resourceChanged(IDETernProjectSynchronizer.java:69) > 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.Resource.broadcastPreDeleteEvent(Resource.java:1884) > at org.eclipse.core.internal.resources.Resource.delete(Resource.java:766) > at org.eclipse.core.internal.resources.Project.delete(Project.java:323) > at org.eclipse.ltk.core.refactoring.resource.DeleteResourceChange.perform(DeleteResourceChange.java:160) > at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) > 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} > The reporter(s) left the following comment(s): > --- Anonymous wrote on [1935|https://redhat.ctrlflow.com/reviewers/#!/incidents/57a208eee4b0fe642...]: --- > To reporoduce: > 1. delete project file from fs: .project > 2. delete project from eclipse without removing fs > --- Chris Stone wrote on [ba6d|https://redhat.ctrlflow.com/reviewers/#!/incidents/5769adebe4b024630...]: --- > Deleting a closed project, including files on disk. > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 | > | org.eclipse.core.resources | 3.10.0.v20150423-0755 | 3.11.0.v20160503-1608 | > | org.eclipse.core.runtime | 3.11.0.v20150405-1723 | 3.12.0.v20160606-1342 | > | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.12.0.v20160516-2131 | > | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.12.0.v20160525-1829 | > | org.eclipse.jface | 3.11.0.v20150602-1400 | 3.12.0.v20160518-1929 | > | org.eclipse.ltk.core.refactoring | 3.6.200.v20140826-0859 | 3.7.0.v20160419-0705 | > | org.eclipse.ltk.ui.refactoring | 3.7.200.v20140625-1835 | 3.8.0.v20160518-1817 | > | org.eclipse.rse.files.ui | 3.2.200.201502052140 | 3.2.200.201507172213 | > | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 | > | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 | > | org.eclipse.ui.navigator.resources | 3.5.1.v20160128-1644 | 3.5.100.v20160518-1929 | > | org.eclipse.ui.views | 3.8.0.v20150422-0725 | 3.8.0.v20150422-0725 | > | tern.eclipse.ide.core | 1.1.0.201511082254 | 1.2.0.201606211556 | > Operating Systems: > | Linux | 2.6.32.1 | 4.6.4.fc24 | > | MacOSX | 10.10.5 | 10.11.6 | > | Windows | 6.1.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5762a96fe4b075777d...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23821) Server adapter wizard: NPE when trying to create OS3 adapter while server exists whose code doesnt

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23821?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23821: ------------------------------------- Story Points: 2 Sprint: devex #127 February 2017 > Server adapter wizard: NPE when trying to create OS3 adapter while server exists whose code doesnt > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-23821 > URL: https://issues.jboss.org/browse/JBIDE-23821 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.4.3.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23821) Server adapter wizard: NPE when trying to create OS3 adapter while server exists whose code doesnt

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-23821: ---------------------------------------- Summary: Server adapter wizard: NPE when trying to create OS3 adapter while server exists whose code doesnt Key: JBIDE-23821 URL: https://issues.jboss.org/browse/JBIDE-23821 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.3.AM2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.4.3.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23821) Server adapter wizard: NPE when trying to create OS3 adapter while server exists whose code doesnt

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23821?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23821: ------------------------------------- Labels: openshift_v3 server_adapter_wizard (was: ) > Server adapter wizard: NPE when trying to create OS3 adapter while server exists whose code doesnt > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-23821 > URL: https://issues.jboss.org/browse/JBIDE-23821 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.4.3.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23707) Explorer: Job that initially loads resources for connection displays "Load Project"

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23707?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-23707. ------------------------------ Verified in devstudio 10.3.0.AM2. Closing. > Explorer: Job that initially loads resources for connection displays "Load Project" > ----------------------------------------------------------------------------------- > > Key: JBIDE-23707 > URL: https://issues.jboss.org/browse/JBIDE-23707 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: explorer, openshift_v3 > Fix For: 4.4.3.AM2 > > Attachments: load-project-job.png > > > # ASSERT: make sure that you have a connection to an OpenShift server that is *NOT* running > # EXEC: restart your eclipse and unfold the connection > # ASSERT: a child "Loading...." is appearing below the connection item in the OpenShift Explorer > # EXEC: look at the status bar and the Progress view to inspect what the job is reporting > Result: > The job is reporting "Load Project" which is not very insightful. I'd expect something like "Loading resources for server 10.1.2.2:8443..." > !load-project-job.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23764) Scaling To: wrong number of current replicas shown at times

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23764?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-23764. ------------------------------ I'm unable to reprodce this in Devstudio 10.3.0.AM2. Closing. > Scaling To: wrong number of current replicas shown at times > ----------------------------------------------------------- > > Key: JBIDE-23764 > URL: https://issues.jboss.org/browse/JBIDE-23764 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, scaling_pods_wizard > Fix For: 4.4.3.AM2 > > Attachments: scale-to-dialog.png > > > Even though I tried very hard I unfortunately cannot provide steps to replicate this erroneous behaviour. But it happened to me here and there. > The tooling provides a way to have a specified number of pods for a service. This is available via the context menu of a service (and other items in the tree and in the properties). > !scale-to-dialog.png! > The dialog that allows you to scale the number of replicas to a specific number initially shows the current number of replicas. You can then provide a specific number of replicas that you want to have, enabling the "OK" button. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4259) Could not resolve module: org.eclipse.recommenders

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4259?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-4259. ------------------------------ Verified in 10.3-0.20170201.0749.el7. Problem solved, thanks. > Could not resolve module: org.eclipse.recommenders > -------------------------------------------------- > > Key: JBDS-4259 > URL: https://issues.jboss.org/browse/JBDS-4259 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm > Affects Versions: 10.3.0.GA > Environment: RHEL7, RHSCL 2.4 alpha 1.0 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 10.3.0.GA > > Attachments: rh-eclipse46-devstudio10.3.log.20170131-1103.txt > > > I got errors during start of Devstudio 10.3-0.20170131.0115.el7. There are errors like this: > {code} > org.osgi.framework.BundleException: Could not resolve module: org.eclipse.recommenders.apidocs.rcp [1085] > Unresolved requirement: Import-Package: com.google.common.annotations; version="[15.0.0,16.0.0)" > {code} > Log: [^rh-eclipse46-devstudio10.3.log.20170131-1103.txt] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20048) Explorer: No feedback on failed removal of kubernetes services

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20048?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-20048. ------------------------------ I'm also unable to reproduce it. Closing. > Explorer: No feedback on failed removal of kubernetes services > -------------------------------------------------------------- > > Key: JBIDE-20048 > URL: https://issues.jboss.org/browse/JBIDE-20048 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.4.3.AM2 > > Attachments: kuebernetes-services.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23591) Integration tests global refactoring: org.jboss.tools.runtime.as.ui.bot.test

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23591?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-23591. ------------------------------ > Integration tests global refactoring: org.jboss.tools.runtime.as.ui.bot.test > ---------------------------------------------------------------------------- > > Key: JBIDE-23591 > URL: https://issues.jboss.org/browse/JBIDE-23591 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: runtime-detection > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Rob Stryker > Labels: integration, integration_tests, runtime > Fix For: 4.4.3.AM2 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.runtime.as.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23765) Scale To: deployment that is being scaled is not show in the scaling dialog

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23765?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-23765. ------------------------------ Verified in Devstudio 10.3.0.AM2. Closing. > Scale To: deployment that is being scaled is not show in the scaling dialog > --------------------------------------------------------------------------- > > Key: JBIDE-23765 > URL: https://issues.jboss.org/browse/JBIDE-23765 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, scaling_pods_wizard > Fix For: 4.4.3.AM2 > > Attachments: scaling-deployment-dialog.png, scaling-deployment-eap.png > > > The "Scale To" dialog, that you get when you pick "Scale > To" in the context menu of a service in the OpenShift Explorer (and also in the Properties) wont tell you what deployment you are about to scale. > !scaling-deployment-dialog.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2017