April 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22962) NullPointerException in JSPTextEditor$1.run

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22962?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22962: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > NullPointerException in JSPTextEditor$1.run > ------------------------------------------- > > Key: JBIDE-22962 > URL: https://issues.jboss.org/browse/JBIDE-22962 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Reporter: Automated Error Reporting Bot > Assignee: Ilya Buziuk > Fix For: 4.6.x > > > The following problem was reported via the automated error reporting: > Message: Unhandled event loop exception > {noformat} > java.lang.NullPointerException: null > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPTextEditor$1.run(JSPTextEditor.java:258) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPTextEditor.getPageContext(JSPTextEditor.java:270) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPTextEditor.updateModification(JSPTextEditor.java:486) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor.nodeChanged(JSPMultiPageEditor.java:791) > at org.jboss.tools.common.model.util.XModelTreeListenerSWTASync$R.run(XModelTreeListenerSWTASync.java:84) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4155) > {noformat} > Bundles: > | org.eclipse.swt | 3.104.1.v20150825-0743 | 3.105.0.v20160317-0027 | > | org.jboss.tools.common.model | 3.7.1.Final-v20160408-2358-B112 | 3.7.1.Final-v20160408-2358-B112 | > | org.jboss.tools.jst.web.ui | 3.7.1.Final-v20160331-0256-B96 | 3.7.1.Final-v20160331-0256-B96 | > Operating Systems: > | Linux | 3.19.0 | 4.5.6.fc23 | > | 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/5717e8a7e4b032f683...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20977) XML identation size is not editable

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20977?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20977: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > XML identation size is not editable > ----------------------------------- > > Key: JBIDE-20977 > URL: https://issues.jboss.org/browse/JBIDE-20977 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.CR1b, Eclipse 4.4 > I have Fedora 19, Java 1.7_60, Gnome3, it is both case for JBDS 8.x and Eclipse 4.4 > Colleague of mine has RHEL7 with Gnome, tested on JBDS 8.x as well. > Reporter: Stefan Miklosovic > Assignee: Snjezana Peco > Fix For: 4.6.x > > Attachments: xml-preferences.png > > > !xml-preferences.png! > Window -> Preferencies -> XML -> XML Files -> Editor > Ident using spaces is checked. > Identation size field is not editable, there is still "1" in it. Clicking at arrows (or + - buttons) does not work. I can not rise it to 4 spaces. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22695) Environment Variables of application deployment should have different workflow

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22695?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22695: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Environment Variables of application deployment should have different workflow > ------------------------------------------------------------------------------ > > Key: JBIDE-22695 > URL: https://issues.jboss.org/browse/JBIDE-22695 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Marián Labuda > Priority: Critical > Labels: env_var_wizard, openshift_v3 > Fix For: 4.6.x > > > Reset All button in Environment Var wizard dialog should get application to default state. At the moment it reset environment variables in the table just to the values at the point of opening the wizard. If I would delete some environment variables and confirm changes, but I would find out I broke something and I would like to rollback it to original state, I would try to reset it with Reset All button. But it won't work for me. This is causing the more serious issue: > Because we edit same deployment configuration and start deployments from it and in the same time we set number of replicas in other deployment configs to zero. So we don't have the original deployment config and thus we cannot rollback easily (well there is a way but nasty one - edit replication controller, copy and paste environment variables to the deployment config, save it and deploy latest). > There are 2 options: > a) Create a new deployment configuration for a new (modified) set of environment variables and create a new replication controller (deployment) from this deployment configuration. There is one con - it can lead to many deployment configurations and replication controllers (for each deployment configuration there would be one replication controller). > b) Just edit current replication controller (deployment) of an application or create a new one from an existing but with modified env. vars and with correct amount of replicas and set replicas in the previous to 0. And then let respin pods with correct setup. One of those approaches (create/edit RC) would be, I think, more satisfying. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17483) Quick Fix for Console configuration "" does not exist

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17483?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-17483: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Quick Fix for Console configuration "" does not exist > ----------------------------------------------------- > > Key: JBIDE-17483 > URL: https://issues.jboss.org/browse/JBIDE-17483 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Reporter: Burr Sutter > Assignee: Koen Aers > Fix For: 4.6.x > > Attachments: JBIDE-17483-webnate.zip > > > When using Maven import on "someone else's" project, it is fairly common to get a complaint about the missing Console Configuration. Numerous workarounds have been documented and can be found via Google - some work, some do not - ideally we would offer a quickfix to help address this common error message inside of the IDE. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18516) JAX-RS Validator should report problem when @DefaultValue is used alone

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18516?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-18516: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > JAX-RS Validator should report problem when @DefaultValue is used alone > ----------------------------------------------------------------------- > > Key: JBIDE-18516 > URL: https://issues.jboss.org/browse/JBIDE-18516 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.2.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: jax-rs > Fix For: 4.6.x > > > If a method parameter is annotated with {{@DefaultValue}} but has _no_ {{@QueryParam}} (or similar) annotation, then the application will most certainly fail with an error message such as: > {code} > failed to execute: javax.ws.rs.NotSupportedException: Could not find message body reader for type: int of content type: */* > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23466) Refactor ConnectionWrapper class for better support of mulithreading

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23466?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23466: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Refactor ConnectionWrapper class for better support of mulithreading > -------------------------------------------------------------------- > > Key: JBIDE-23466 > URL: https://issues.jboss.org/browse/JBIDE-23466 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Dmitrii Bocharov > Labels: openshift_v3, watcher > Fix For: 4.6.x > > > The initial discussion started here: https://github.com/jbosstools/jbosstools-openshift/pull/1359#discussion_r... > The problem is that ConnectionWrapper contains a lot of synchronized blocks, that can be bottlenecks. We need to think about using ConcurentHashMap for projects Map or refactor the whole logic of using global variables: projects and resourceCache to make them work synchronously. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19568) Disable the "Check for update" button while a check for update is in progress

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19568?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-19568: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Disable the "Check for update" button while a check for update is in progress > ----------------------------------------------------------------------------- > > Key: JBIDE-19568 > URL: https://issues.jboss.org/browse/JBIDE-19568 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Fix For: 4.6.x > > > while trying to check JBIDE-18559 I clicked "checked for updates" in central and got nothing, not even a dialog. > In error log it was reporting this: > org.eclipse.equinox.p2.core.ProvisionException: No repository found at file:/Users/max/code/jbdevstudio/linuxtools-docker/org.eclipse.linuxtools.docker.core/target/. > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395) > at sun.reflect.GeneratedMethodAccessor97.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.eclipse.oomph.util.ReflectUtil.invokeMethod(ReflectUtil.java:116) > at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.fail(CachingRepositoryManager.java:284) > at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:191) > at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager$Metadata.loadRepository(CachingRepositoryManager.java:378) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102) > at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:83) > at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > would have expected we told the user about this error. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23654) Remember last Project type, build system and stack used to create a new project using the forge tooling

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23654?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23654: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Remember last Project type, build system and stack used to create a new project using the forge tooling > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23654 > URL: https://issues.jboss.org/browse/JBIDE-23654 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.4.2.Final > Reporter: Aurélien Pupier > Fix For: 4.6.x > > Attachments: image-2016-12-19-13-21-02-213.png > > > When using the Forge tooling to create a new project, it would be nice to remember the last project type, build system and stack used on the first wizard page. > !image-2016-12-19-13-21-02-213.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22755) Add support for Service catalog

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22755?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22755: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Add support for Service catalog > ------------------------------- > > Key: JBIDE-22755 > URL: https://issues.jboss.org/browse/JBIDE-22755 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Fred Bricon > Fix For: 4.6.x > > > Kubernetes is introducing the concept of service catalog (https://github.com/kubernetes/kubernetes/pull/17543) > This ticket is meant to discuss the potential impacts on the OpenShift tooling, in other words: do we need to do anything to support service catalogs? > - on the rest client level > - on the UI level (new actions, wizards) > The PR has not been merged upstream yet, so it's obviously too early to discuss implementation details, but at least we planted the seed for future discussions. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20124) NPE when removing a returned class in JAX-RS resource method does not exist

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20124?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20124: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > NPE when removing a returned class in JAX-RS resource method does not exist > --------------------------------------------------------------------------- > > Key: JBIDE-20124 > URL: https://issues.jboss.org/browse/JBIDE-20124 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.3.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.6.x > > > If a project contains a method such as > {code} > @Path("/{id}/comments") > public Foo addComments() { > return null; > } > {code} > while {{Foo}} does not exist, the JAX-RS Metamodel builder will fail with the following exception: > {code} > java.lang.NullPointerException > at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.findSubtypes(JdtUtils.java:905) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsEndpointFactory.createEndpointsFromSubresourceLocator(JaxrsEndpointFactory.java:145) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsElementChangedProcessorDelegate.processSubresourceLocatorAddition(JaxrsElementChangedProcessorDelegate.java:285) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsElementChangedProcessorDelegate.processAddition(JaxrsElementChangedProcessorDelegate.java:191) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsElementChangedProcessorDelegate.processEvent(JaxrsElementChangedProcessorDelegate.java:70) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processElementChange(JaxrsMetamodel.java:751) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.add(JaxrsMetamodel.java:720) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsBaseElement.joinMetamodel(JaxrsBaseElement.java:127) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsResourceMethod$Builder.buildInResource(JaxrsResourceMethod.java:181) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createElements(JaxrsElementFactory.java:211) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createElements(JaxrsElementFactory.java:65) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processJavaElementChange(JaxrsMetamodel.java:420) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processJavaElementChange(JaxrsMetamodel.java:392) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.run(JavaElementChangedBuildJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 April 2018