September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23165) application wizard: IllegalArgumentException in New OpenShift Application Wizard

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23165?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23165: ------------------------------------- Sprint: devex #121 October 2016 > application wizard: IllegalArgumentException in New OpenShift Application Wizard > -------------------------------------------------------------------------------- > > Key: JBIDE-23165 > URL: https://issues.jboss.org/browse/JBIDE-23165 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Environment: Windows 10 Home > OpenJDK 1.8 > Reporter: Denis Golovin > Assignee: Dmitrii Bocharov > Labels: application_wizard, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: error-verifying-user-credentials.png, oc3iare.gif > > > {code}java.lang.IllegalArgumentException: > at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63) > at org.eclipse.core.runtime.Assert.isLegal(Assert.java:47) > at org.jboss.tools.openshift.internal.ui.wizard.connection.AdvancedConnectionEditor$ConnectionAdvancedPropertiesProvider.update(AdvancedConnectionEditor.java:191) > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage.onPageWillGetDeactivated(ConnectionWizardPage.java:370) > at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage$3.handlePageChanging(AbstractOpenShiftWizardPage.java:121) > at org.eclipse.jface.wizard.WizardDialog$7.run(WizardDialog.java:1540) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.wizard.WizardDialog.firePageChanging(WizardDialog.java:1537) > at org.eclipse.jface.wizard.WizardDialog.doPageChanging(WizardDialog.java:890) > at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1177) > at org.eclipse.jface.wizard.WizardDialog.backPressed(WizardDialog.java:404) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:415) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4410) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4228) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3816) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269) > at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290) > 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) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:488) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:353) > at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:155) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565) > at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4410) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4228) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3816) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) > at org.eclipse.equinox.launcher.Main.run(Main.java:1519) > at org.eclipse.equinox.launcher.Main.main(Main.java:1492) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22727) Openshift resources managed by explorer and watcher are declared in both place leading to inconsistency

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22727?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-22727: ------------------------------------- Sprint: devex #121 October 2016 (was: devex #120 September 2016) > Openshift resources managed by explorer and watcher are declared in both place leading to inconsistency > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22727 > URL: https://issues.jboss.org/browse/JBIDE-22727 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.x > > > The kind of Openshift resources are declated in 2 different places: WatchManager and ConnectionWrapper. This increases the technical debt and may lead to resources displayed by the explorer but not refreshed by the watcher. > The task requires investigation about ResourceKind.IMAGE_STREAM_TAG, which is present in ConnectionWrapper, but there is no such element in WatchManager's array. See discussion [here|https://github.com/jbosstools/jbosstools-openshift/pull/1272#discuss...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22803) When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-22803: ------------------------------------- Sprint: devex #121 October 2016 (was: devex #120 September 2016) > When OS projects are created and deleted, seems Openshift explorer restores non existing values > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-22803 > URL: https://issues.jboss.org/browse/JBIDE-22803 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.x > > Attachments: after application creation.png, after build finished.png, Openshift Web Console.png, screenshot-1.png > > > EXEC: create an Openshift project > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > ASSERT: wait for the pod to be available > EXEC: delete the Openshit project > EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists) > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > EXEC: expand the nodejs-example node > ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3834) Install fail - what next?

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3834?page=com.atlassian.jira.plugin.... ] Misha Ali commented on JBDS-3834: --------------------------------- I'd also request an exit button in case of a failure that requires exiting the installer. Clicking the X at the edge of the window seems like an ungraceful way to exit the installer. > Install fail - what next? > ------------------------- > > Key: JBDS-3834 > URL: https://issues.jboss.org/browse/JBDS-3834 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Misha Ali > Assignee: Denis Golovin > Fix For: 10.2.0.AM1 > > Attachments: error.PNG, fail_install.PNG > > > Testing the Installer a bit more and I realize this is currently tech preview but when one (or more) components fail, there is no next step for users. There is no cancel or quit button to exit the failed install, nor is there a retry for the failed component, nor any error message at all. As a user, I'd be confused about what I should do next at this stage. I think this might be worth looking into with UX for the 9.1 GA++ release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-918) additional features screen in standalone installer: s/location/feature

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-918?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-918. ------------------------------ Resolution: Duplicate Issue Thanks [~mhusnain] - closing this as a duplicate of https://issues.jboss.org/browse/JBTIS-869 This will be fixed in the 10.x DEVSTUDIOIS > additional features screen in standalone installer: s/location/feature > ---------------------------------------------------------------------- > > Key: JBTIS-918 > URL: https://issues.jboss.org/browse/JBTIS-918 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: build > Reporter: Misha Ali > Assignee: Paul Leacu > Attachments: devstudioIS.png > > > Not sure if the component is correct, so please reassign if required. I was testing the standalone installer for documentation and notices that the features listed in the installer are under the title "location", which doesn't seem accurate in this context. Screenshot attached, logging a bug to fix this minor issue for a later release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-918) additional features screen in standalone installer: s/location/feature

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-918?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-918: -------------------------------- Assignee: Paul Leacu > additional features screen in standalone installer: s/location/feature > ---------------------------------------------------------------------- > > Key: JBTIS-918 > URL: https://issues.jboss.org/browse/JBTIS-918 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: build > Reporter: Misha Ali > Assignee: Paul Leacu > Attachments: devstudioIS.png > > > Not sure if the component is correct, so please reassign if required. I was testing the standalone installer for documentation and notices that the features listed in the installer are under the title "location", which doesn't seem accurate in this context. Screenshot attached, logging a bug to fix this minor issue for a later release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18725) HTML Validation: Ability to perform custom validation for tags, attributes and attribute values in WTP

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18725?page=com.atlassian.jira.plugi... ] Victor Rubezhny updated JBIDE-18725: ------------------------------------ Story Points: 1 > HTML Validation: Ability to perform custom validation for tags, attributes and attribute values in WTP > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18725 > URL: https://issues.jboss.org/browse/JBIDE-18725 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html-source-editing, upstream > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Labels: new_and_noteworthy > Fix For: 4.3.x > > > WTP HTML validator marks any custom html tags as unknown. It's possible to disable this validation at all: Window->Preferences->Web->HTML Files->Validation ==> Set Elements -> Unknown tag name severity to "Ignore": > But these days there are many frameworks provide an ability to create custom tags and attributes, so there cannot be some static schema created in order to help to validate such pages. > We need to add a possibility to provide a custom validator for tags/attributes/values for WTP, so it could be called to validate a page elements. > See discussions here: JBIDE-18387 and here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=443097. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18725) HTML Validation: Ability to perform custom validation for tags, attributes and attribute values in WTP

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18725?page=com.atlassian.jira.plugi... ] Victor Rubezhny updated JBIDE-18725: ------------------------------------ Sprint: devex #120 September 2016 > HTML Validation: Ability to perform custom validation for tags, attributes and attribute values in WTP > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18725 > URL: https://issues.jboss.org/browse/JBIDE-18725 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html-source-editing, upstream > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Labels: new_and_noteworthy > Fix For: 4.3.x > > > WTP HTML validator marks any custom html tags as unknown. It's possible to disable this validation at all: Window->Preferences->Web->HTML Files->Validation ==> Set Elements -> Unknown tag name severity to "Ignore": > But these days there are many frameworks provide an ability to create custom tags and attributes, so there cannot be some static schema created in order to help to validate such pages. > We need to add a possibility to provide a custom validator for tags/attributes/values for WTP, so it could be called to validate a page elements. > See discussions here: JBIDE-18387 and here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=443097. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ERT-321) JavaScript as-you-type validation shouldn't appear for non-jJSDT projects [EBZ#491637]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-321?page=com.atlassian.jira.plugin.sy... ] Victor Rubezhny updated ERT-321: -------------------------------- Sprint: devex #118 July 2016, devex #120 September 2016 (was: devex #118 July 2016) > JavaScript as-you-type validation shouldn't appear for non-jJSDT projects [EBZ#491637] > -------------------------------------------------------------------------------------- > > Key: ERT-321 > URL: https://issues.jboss.org/browse/ERT-321 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: General, bzira > > JavaScript as-you-type validation works even if a project doesn't have a JSDT nature. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22581) Create and use Neon.1 target platform

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22581?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22581: ------------------------------------ Tested TP in Eclipse Dev + build jbosstools-openshift without problems > Create and use Neon.1 target platform > ------------------------------------- > > Key: JBIDE-22581 > URL: https://issues.jboss.org/browse/JBIDE-22581 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: target-platform > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.2.AM2 > > Attachments: jbosstools.p2diff.summary.txt, jbosstools.p2diff.txt, jbtcentral.p2diff.txt > > > Once available in late August or early September, we should move up to Neon.1. > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > jbt tp, > jbds tp, > central tp; > jbt-build-sites, > jbds site build; > update install/matrix jobs to use new Eclipse JEE/platform binary; > mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 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 September 2016