[JBoss JIRA] (JBIDE-21826) install-grinder failing again
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-21826:
----------------------------------
Summary: install-grinder failing again
Key: JBIDE-21826
URL: https://issues.jboss.org/browse/JBIDE-21826
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: install-tests, build
Affects Versions: 4.3.1.CR1, 4.4.0.Alpha1
Reporter: Nick Boldt
Install grinder is failing again in 4.3.1.CR1 and 4.4.0.Alpha1 builds.
Not sure what's blocking the UI this time, but on the plus side, at least Red Hat Central now reports when GTK2/3 is missing on the slave.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21802) Content assist for image names in "Deploy Docker Image" wizard
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21802?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-21802:
-----------------------------------
Resolution: (was: Done)
Assignee: Xavier Coulon (was: Andre Dietisheim)
Typing n returns a garbage list of <none>:<none>, see http://screencast.com/t/lA6PB0DfX
> Content assist for image names in "Deploy Docker Image" wizard
> ---------------------------------------------------------------
>
> Key: JBIDE-21802
> URL: https://issues.jboss.org/browse/JBIDE-21802
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.3.1.CR1
>
>
> The {{Image Name}} field could be enhanced with content assist based on the list of image names+tags retrieved from the selected Docker connection.
> If the user inputs a name that does not match the list, a warning on the page would inform him/her that a remote call to the registry would be performed upon page completion, ie, when clicking on the {{Next}} button.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3672) remove unneeded site/build.xml script
by Nick Boldt (JIRA)
Nick Boldt created JBDS-3672:
--------------------------------
Summary: remove unneeded site/build.xml script
Key: JBDS-3672
URL: https://issues.jboss.org/browse/JBDS-3672
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Components: build
Affects Versions: 10.0.0.Alpha1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 10.0.0.Alpha1
jbdevstudio-product/site/build.xml is no longer referenced by anything -- it's a leftover artifact from before we migrated the whole JBDS update site build to use maven mojos.
So... time to delete it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21817) Connection dialog: User is stuck by Sign In triggered via OpenShift 2 server adapter
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21817?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21817:
-----------------------------------------------
I opened an issue https://bugs.eclipse.org/bugs/show_bug.cgi?id=489165 and did my best to argue for what I do see wrong here.
Still, I know about this 'feature' for many years, and it is inevitable that a lot of other developers know about it, but it remains the same. So, whatever is the result of the appeal to Bugzilla, may we meanwhile commit this or similar workaround? [~adietish], what do you think of it?
> Connection dialog: User is stuck by Sign In triggered via OpenShift 2 server adapter
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-21817
> URL: https://issues.jboss.org/browse/JBIDE-21817
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Viacheslav Kabanovich
> Labels: openshift_v2
> Fix For: 4.3.1.CR1
>
> Attachments: jstack.txt, LockAtStart.png
>
>
> 1. Close Eclipse with
> - Server Editor for OpenShift 2 server adapter open;
> - password for an Opebshift 2 connection not saved in the secure storage;
> - OpenShift Explorer active (maybe not important).
> 2. Open Eclipse - Sign In to OpenShift wizard appears while the application window remains only partially loaded (see screenshot). Once this is reproduced, it is reproduced at each Eclipse start.
> 3. Enter password and finish.
> 4. Progress appears but job does not start (I checked it in debugger) - ui jobs are locked.
> 5. Only red button cancelling connection is active, press it, wizard is unlocked (null pointer exception is fixed in JBIDE-21707).
> 6. Press Cancel, wizard is closed, Application window completes loading. - That
> 7. Connection may be established by Refresh action.
> Stack trace that calls Sign In to Openshift wizard before main window is loaded, it shows that call is initiated by loading Server Editor:
> {code}
> Thread [main] (Suspended (breakpoint at line 274 in Window))
> WizardDialog(Window).<init>(IShellProvider) line: 274
> WizardDialog(Dialog).<init>(IShellProvider) line: 438
> WizardDialog(Dialog).<init>(Shell) line: 419
> WizardDialog(TrayDialog).<init>(Shell) line: 138
> WizardDialog(TitleAreaDialog).<init>(Shell) line: 130
> WizardDialog.<init>(Shell, IWizard) line: 308
> WizardUtils.openWizardDialog(IWizard, Shell) line: 242
> CredentialsPrompter$1.run() line: 44
> UISynchronizer(Synchronizer).syncExec(Runnable) line: 186
> UISynchronizer.syncExec(Runnable) line: 145
> Display.syncExec(Runnable) line: 4634
> CredentialsPrompter.promptAndAuthenticate(IConnection, Object) line: 33
> LazyCredentialsPrompter.promptAndAuthenticate(IConnection, Object) line: 39
> ExpressConnection.promptForCredentials() line: 284
> ExpressConnection.createUser() line: 218
> ExpressConnection.connect() line: 198
> ExpressServerUtils.getApplication(IServerAttributes) line: 161
> ExpressServerUtils.getDeployFolder(IServerAttributes) line: 251
> ExpressServerEditorSection.initWidgets() line: 117
> ExpressServerEditorSection.createSection(Composite) line: 100
> OverviewEditorPart(ServerEditorPart).insertSections(Composite, String) line: 327
> OverviewEditorPart.createPartControl(Composite) line: 279
> ServerEditor(MultiPageEditorPart).addPage(int, IEditorPart, IEditorInput) line: 244
> ServerEditor(MultiPageEditorPart).addPage(IEditorPart, IEditorInput) line: 214
> ServerEditor.createPages() line: 247
> ServerEditor(MultiPageEditorPart).createPartControl(Composite) line: 363
> CompatibilityEditor(CompatibilityPart).createPartControl(IWorkbenchPart, Composite) line: 151
> CompatibilityEditor.createPartControl(IWorkbenchPart, Composite) line: 99
> CompatibilityEditor(CompatibilityPart).create() line: 341
> NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
> NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62
> DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43
> Method.invoke(Object, Object...) line: 498
> MethodRequestor.execute() line: 56
> InjectorImpl.processAnnotated(Class<Annotation>, Object, Class<?>, PrimaryObjectSupplier, PrimaryObjectSupplier, ArrayList<Class<?>>) line: 925
> InjectorImpl.processAnnotated(Class<Annotation>, Object, Class<?>, PrimaryObjectSupplier, PrimaryObjectSupplier, ArrayList<Class<?>>) line: 906
> InjectorImpl.inject(Object, PrimaryObjectSupplier, PrimaryObjectSupplier) line: 148
> InjectorImpl.internalMake(Class<?>, PrimaryObjectSupplier, PrimaryObjectSupplier) line: 372
> InjectorImpl.make(Class<T>, PrimaryObjectSupplier) line: 291
> ContextInjectionFactory.make(Class<T>, IEclipseContext) line: 162
> ReflectionContributionFactory.createFromBundle(Bundle, IEclipseContext, IEclipseContext, URI) line: 105
> ReflectionContributionFactory.doCreate(String, IEclipseContext, IEclipseContext) line: 74
> ReflectionContributionFactory.create(String, IEclipseContext) line: 56
> ContributedPartRenderer.createWidget(MUIElement, Object) line: 129
> PartRenderingEngine.createWidget(MUIElement, Object) line: 976
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 652
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> StackRenderer.showTab(MUIElement) line: 1306
> StackRenderer(LazyStackRenderer).postProcess(MUIElement) line: 103
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 670
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> AreaRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine$1.run() line: 537
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement, Object, IEclipseContext) line: 521
> ElementReferenceRenderer.createWidget(MUIElement, Object) line: 70
> PartRenderingEngine.createWidget(MUIElement, Object) line: 976
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 652
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> SashRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> SashRenderer.processContents(MElementContainer<MUIElement>) line: 151
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> SashRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> SashRenderer.processContents(MElementContainer<MUIElement>) line: 151
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> SashRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> SashRenderer.processContents(MElementContainer<MUIElement>) line: 151
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> PerspectiveRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> PerspectiveRenderer.processContents(MElementContainer<MUIElement>) line: 49
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> PerspectiveStackRenderer.showTab(MUIElement) line: 82
> PerspectiveStackRenderer(LazyStackRenderer).postProcess(MUIElement) line: 103
> PerspectiveStackRenderer.postProcess(MUIElement) line: 63
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 670
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> SashRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> SashRenderer.processContents(MElementContainer<MUIElement>) line: 151
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> WBWRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> WBWRenderer.processContents(MElementContainer<MUIElement>) line: 614
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> PartRenderingEngine$4.run() line: 1066
> Realm.runWithDefault(Realm, Runnable) line: 336
> PartRenderingEngine.run(MApplicationElement, IEclipseContext) line: 1023
> E4Workbench.createAndRunUI(MApplicationElement) line: 157
> Workbench$5.run() line: 651
> Realm.runWithDefault(Realm, Runnable) line: 336
> Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 595
> PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 150
> IDEApplication.start(IApplicationContext) line: 138
> EclipseAppHandle.run(Object) line: 196
> EclipseAppLauncher.runApplication(Object) line: 134
> EclipseAppLauncher.start(Object) line: 104
> EclipseStarter.run(Object) line: 388
> EclipseStarter.run(String[], Runnable) line: 243
> NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
> NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62
> DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43
> Method.invoke(Object, Object...) line: 498
> Main.invokeFramework(String[], URL[]) line: 670
> Main.basicRun(String[]) line: 609
> Main.run(String[]) line: 1516
> Main.main(String[]) line: 1489
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21825) Application wizard: Duplicate templates in different OpenShift projects are not distinguishable from each other
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21825?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21825:
-------------------------------------
Labels: application_wizard openshift_v3 (was: )
> Application wizard: Duplicate templates in different OpenShift projects are not distinguishable from each other
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21825
> URL: https://issues.jboss.org/browse/JBIDE-21825
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Jeff Cantrill
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: screenshot-1.png, TemplateLableWithNamespace.png
>
>
> New app from template should allow a user to pick templates form either the 'OpenShift' project or their own and they should be able to tell the difference. The attached screen show displays the same template twice but actually, one is in the openshift project and the other is in the 'hello-world'
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-20568) Application wizard: Duplicate templates in different OpenShift projects are not distinguishable from each other
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20568?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20568:
-------------------------------------
Labels: application_wizard openshift_v3 (was: openshift_v3)
> Application wizard: Duplicate templates in different OpenShift projects are not distinguishable from each other
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20568
> URL: https://issues.jboss.org/browse/JBIDE-20568
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Jeff Cantrill
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: screenshot-1.png, TemplateLableWithNamespace.png
>
>
> New app from template should allow a user to pick templates form either the 'OpenShift' project or their own and they should be able to tell the difference. The attached screen show displays the same template twice but actually, one is in the openshift project and the other is in the 'hello-world'
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21823) Unable to re-edit Service config
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21823?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21823:
------------------------------------------
[~jcantrill] yes, exactly. Thx!
> Unable to re-edit Service config
> --------------------------------
>
> Key: JBIDE-21823
> URL: https://issues.jboss.org/browse/JBIDE-21823
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.3.1.CR1
>
>
> Once a service config has been changed, closing and reopening the config editor does not reveal the latest config, which then causes 409 error when saving subsequent changes, making it impossible to submit new changes.
> Steps to reproduce:
> - select a service in the OpenShift Explorer
> - click on the {{Edit...}} command.
> - in the JSON editor for the service config, note the resource version. Eg:
> {code}
> {
> "metadata" : {
> "name" : "jee-sample",
> "namespace" : "sample",
> "selfLink" : "/api/v1/namespaces/sample/services/jee-sample",
> "uid" : "5663ba0f-da47-11e5-ab9d-525400659b2e",
> "resourceVersion" : "38301",
> "creationTimestamp" : "2016-02-23T16:06:03Z",
> "labels" : {"app" : "jee-sample"},
> "annotations" : {"openshift.io/generated-by" : "OpenShiftWebConsole"}
> },
> ...
> {code}
> - make some changes and save
> - the service config version should have incremented:
> {code}
> {
> "kind" : "Service",
> "apiVersion" : "v1",
> "metadata" : {
> "name" : "jee-sample",
> "namespace" : "sample",
> "selfLink" : "/api/v1/namespaces/sample/services/jee-sample",
> "uid" : "5663ba0f-da47-11e5-ab9d-525400659b2e",
> "resourceVersion" : "38390",
> "creationTimestamp" : "2016-02-23T16:06:03Z",
> "labels" : {"app" : "jee-sample"},
> "annotations" : {"openshift.io/generated-by" : "OpenShiftWebConsole"}
> }
> ....
> {code}
> - close the config editor
> - re-open the config editor
> *ASSERT: the editor displays the latest config*
> *FAIL the editor displays the initial config*
> *Also, on subsequent changes, the OpenShift server responds with a {{409}} error because the new config to save is based out-dated version*
> {code}
> Could not update "[sample] Service : jee-sample.json" for project "sample" : services "jee-sample" cannot be updated: the object has been modified; please apply your changes to the latest version and try again
> Could not update resource jee-sample: {
> "kind": "Status",
> "apiVersion": "v1",
> "metadata": {},
> "status": "Failure",
> "message": "services \"jee-sample\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again",
> "reason": "Conflict",
> "details": {
> "name": "jee-sample",
> "kind": "services"
> },
> "code": 409
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month