March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20558) org.jboss.tools.common.validation.JBTValidationException at org.jboss.tools.common.validation.AsYouTypeValidatorManager.

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20558?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20558: ------------------------------- Fix Version/s: 4.4.4.AM3 (was: 4.4.4.AM2) > org.jboss.tools.common.validation.JBTValidationException at org.jboss.tools.common.validation.AsYouTypeValidatorManager. > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20558 > URL: https://issues.jboss.org/browse/JBIDE-20558 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, common > Affects Versions: 4.3.0.Beta2 > Reporter: The Alchemist > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.4.4.AM3 > > > {noformat} > org.jboss.tools.common.validation.JBTValidationException > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:187) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateJavaElement(AsYouTypeValidatorManager.java:222) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateJavaElement(AsYouTypeValidatorManager.java:217) > at org.jboss.tools.common.validation.java.JavaDirtyRegionProcessor.endProcessing(JavaDirtyRegionProcessor.java:507) > at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:697) > Caused by: java.lang.NullPointerException > at org.jboss.tools.cdi.core.CDIUtil.collectAdditionalInterceptorBindingDeclaratios(CDIUtil.java:1114) > at org.jboss.tools.cdi.core.CDIUtil.collectAdditionalInterceptorBindingDeclaratios(CDIUtil.java:1118) > at org.jboss.tools.cdi.core.CDIUtil.getAllInterceptorBindingDeclaratios(CDIUtil.java:1110) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.hasConflictedInterceptorBindings(CDICoreValidator.java:984) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateInterceptorBindings(CDICoreValidator.java:970) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateClassBean(CDICoreValidator.java:952) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateBean(CDICoreValidator.java:792) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateResource(CDICoreValidator.java:641) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validate(CDICoreValidator.java:574) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183) > ... 4 more > {noformat} > I wish I could see which class is causing this error... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20569) OpenShift Explorer : "Import Application" menu is confusing

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20569?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20569: ------------------------------- Fix Version/s: 4.4.4.AM3 (was: 4.4.4.AM2) > OpenShift Explorer : "Import Application" menu is confusing > ----------------------------------------------------------- > > Key: JBIDE-20569 > URL: https://issues.jboss.org/browse/JBIDE-20569 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: explorer, ux > Fix For: 4.4.4.AM3 > > Attachments: import-application.png > > > [~sspeiche] finds the "Import Application" menu in OpenShift Explorer is confusing: does it mean import from eclipse to openshift or the other way around (it's the latter). Needs better wording. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21593) Application wizard: Opening wizard and creating required project (clean connection) makes wizard unusable

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21593?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-21593: ------------------------------- Fix Version/s: 4.4.4.AM3 (was: 4.4.4.AM2) > Application wizard: Opening wizard and creating required project (clean connection) makes wizard unusable > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21593 > URL: https://issues.jboss.org/browse/JBIDE-21593 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: Fedora 22, GTK 3. > Reporter: Marián Labuda > Labels: application_wizard, explorer, openshift_v3 > Fix For: 4.4.4.AM3 > > Attachments: empty_project.png > > > When I am opening a new OpenShift application wizard on OpenShift 3 connection where are no projects yet, at first project dialog to create a new project is opened. Upon creation of a new project, dialog is closed and I am "redirected" back to application wizard, where newly created project should be preselected. Problem is the new project is shown as empty tree item in OpenShift explorer (this happens also if new project dialog is opened directly from the context menu of a clean connection) what makes new OpenShift application wizard unusable, because there are no projects in combo, no matter what. See following screenshot > !empty_project.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21895) Application wizard: Resource name collisions after deleting and recreating the application

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21895?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-21895: ------------------------------- Fix Version/s: 4.4.4.AM3 (was: 4.4.4.AM2) > Application wizard: Resource name collisions after deleting and recreating the application > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21895 > URL: https://issues.jboss.org/browse/JBIDE-21895 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.4.4.AM3 > > Attachments: 1st-child-of-project.png, Screen Shot 2016-03-17 at 16.19.05.png, Screenshot 2017-02-02 18.22.34.png, Screenshot 2017-02-02 18.22.43.png, os-resources-empty.png > > > 1) Create e.g. node application in a openshift project > 2) Right click from project explorer -> Delete the application > 3) repeat step 1) > Result: > !Screen Shot 2016-03-17 at 16.19.05.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21895) Application wizard: Resource name collisions after deleting and recreating the application

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21895?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-21895: ------------------------------------ To be tested because we think this is already implemented > Application wizard: Resource name collisions after deleting and recreating the application > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21895 > URL: https://issues.jboss.org/browse/JBIDE-21895 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.4.4.AM3 > > Attachments: 1st-child-of-project.png, Screen Shot 2016-03-17 at 16.19.05.png, Screenshot 2017-02-02 18.22.34.png, Screenshot 2017-02-02 18.22.43.png, os-resources-empty.png > > > 1) Create e.g. node application in a openshift project > 2) Right click from project explorer -> Delete the application > 3) repeat step 1) > Result: > !Screen Shot 2016-03-17 at 16.19.05.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22191) Application wizard: Support list of application creation with JSON

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22191?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22191: ------------------------------- Fix Version/s: 4.4.4.AM3 (was: 4.4.4.AM2) > Application wizard: Support list of application creation with JSON > ------------------------------------------------------------------ > > Key: JBIDE-22191 > URL: https://issues.jboss.org/browse/JBIDE-22191 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Aurélien Pupier > Fix For: 4.4.4.AM3 > > Attachments: screenshot-1.png > > > Currently, if we provide a Local template, which is a list of templates, there is a popup with an error. > {noformat} > java.lang.ClassCastException: com.openshift.internal.restclient.model.List cannot be cast to com.openshift.restclient.model.template.ITemplate > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.getLocalTemplate(NewApplicationWizardModel.java:107) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.updateSelectedTemplate(NewApplicationWizardModel.java:86) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.update(NewApplicationWizardModel.java:78) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.setLocalTemplateFileName(NewApplicationWizardModel.java:315) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateListPage.setLocalTemplate(TemplateListPage.java:511) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateListPage.access$6(TemplateListPage.java:506) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateListPage$14.widgetSelected(TemplateListPage.java:696) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4362) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1113) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4180) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3769) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:279) > at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270) > at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:34) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > {noformat} > You can use the template used by Fuse to reproduce: https://raw.githubusercontent.com/jboss-fuse/application-templates/master... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22964) Fuse examples are found even though Fuse is not installed (and is not available in Central)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22964?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22964: ------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM2) > Fuse examples are found even though Fuse is not installed (and is not available in Central) > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22964 > URL: https://issues.jboss.org/browse/JBIDE-22964 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.4.1.AM3 > Environment: Devstudio 10.1.0.AM3-v20160809-0722-B5729 > Reporter: Radim Hopp > Fix For: 4.4.4.Final > > > After turning Early Access on, camel, fuse, brms examples can be looked up in Central even though Integration stack is not on the Software/Update page. > That is probably because _jboss.discovery.site.integration-stack.url_ and _jboss.discovery.earlyaccess.site.integration-stack.url_ properties are configured in ide-config.properties. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23626) Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23626?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23626: ------------------------------- Fix Version/s: 4.4.4.AM3 (was: 4.4.4.AM2) > Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23626 > URL: https://issues.jboss.org/browse/JBIDE-23626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Labels: oc_binary, preferences > Fix For: 4.4.4.AM3 > > > oc 1.4, which is available from github is not compatible with the lastest CDK 2.3 (it's only compatible oc 1.3). Futhermore there are specific enterprise oc binaries which follow the OSE versioning scheme 3.2, 3.3 etc. making it hard for the user to know what oc he should use. > Our preferences offer a link to the github releases but there's no info nor logic that makes sure that the user will use compatible combinations (oc 1.4 with CDK 2.3, oc 1.2 with CDK 2.3 etc.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23403) As a user I need to be able to inspect the state of my EAP deployments

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23403?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23403: ------------------------------- Fix Version/s: 4.4.4.AM3 (was: 4.4.4.AM2) > As a user I need to be able to inspect the state of my EAP deployments > ---------------------------------------------------------------------- > > Key: JBIDE-23403 > URL: https://issues.jboss.org/browse/JBIDE-23403 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Labels: openshift_v3, server, web_console > Fix For: 4.4.4.AM3 > > > The web console for eap was disabled in the eap image that we have in OpenShift. It's therefore not possible for users to inspect the state of their deployment. > The only there is to do such thing is to inspect jolokia informations. There is no such tooling in Eclipse yet. Furthermore the url to access those is non-obvious as one can see [here|http://developers.redhat.com/blog/2016/03/30/jolokia-jvm-monitoring-...]. I therefore suggest that we should provide help/tooling that allows users to easily access and manipulate those informations. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23711) Properites: "Edit default route" on Build config does nothing

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23711?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23711: ------------------------------- Fix Version/s: 4.4.4.AM3 (was: 4.4.4.AM2) > Properites: "Edit default route" on Build config does nothing > ------------------------------------------------------------- > > Key: JBIDE-23711 > URL: https://issues.jboss.org/browse/JBIDE-23711 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Radim Hopp > Labels: openshift_v3, properties > Fix For: 4.4.4.AM3 > > > Context menu of build configs in properties view has entry "Edit default route..." which does nothing. Is it even supposed to be there? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 March 2017