April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19630) v3 connections: store to default url based persistence vs custom json format

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19630?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19630: ------------------------------------------ merged and pushed to upstream/master > v3 connections: store to default url based persistence vs custom json format > ---------------------------------------------------------------------------- > > Key: JBIDE-19630 > URL: https://issues.jboss.org/browse/JBIDE-19630 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > In JBIDE-19374 loading/saving was implemented using a custom json based format. We should drop this and use what we use for v2 connections. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19247) Switch Tern.java dependency version range to the only version after code freeze

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19247?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19247: ---------------------------------- Summary: Switch Tern.java dependency version range to the only version after code freeze (was: Switch Tern.java dependency version range to the only version before code freeze) > Switch Tern.java dependency version range to the only version after code freeze > ------------------------------------------------------------------------------- > > Key: JBIDE-19247 > URL: https://issues.jboss.org/browse/JBIDE-19247 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > In master tern.java dependencies have open range starting from 0.6.0 after https://github.com/jbosstools/jbosstools-jst/pull/429 was applied. > For every development/stable release the open range should be replaced to specific version. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19630) v3 connections: store to default url based persistence vs custom json format

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19630?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19630: ------------------------------------- Component/s: openshift > v3 connections: store to default url based persistence vs custom json format > ---------------------------------------------------------------------------- > > Key: JBIDE-19630 > URL: https://issues.jboss.org/browse/JBIDE-19630 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > In JBIDE-19374 loading/saving was implemented using a custom json based format. We should drop this and use what we use for v2 connections. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19586) Explorer: If Authentication fails, the error is not shown in tree, "Loading" stays

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19586?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19586: ------------------------------------------ moving this non-critical issue to 4.3.0.Beta1 > Explorer: If Authentication fails, the error is not shown in tree, "Loading" stays > ---------------------------------------------------------------------------------- > > Key: JBIDE-19586 > URL: https://issues.jboss.org/browse/JBIDE-19586 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > Attachments: loading-v3-connection.png, unauthorized-error-dialog.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19586) Explorer: If Authentication fails, the error is not shown in tree, "Loading" stays

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19586?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19586: ------------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Explorer: If Authentication fails, the error is not shown in tree, "Loading" stays > ---------------------------------------------------------------------------------- > > Key: JBIDE-19586 > URL: https://issues.jboss.org/browse/JBIDE-19586 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > Attachments: loading-v3-connection.png, unauthorized-error-dialog.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19609) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Aerogear]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19609?page=com.atlassian.jira.plugi... ] Gorkem Ercan closed JBIDE-19609. -------------------------------- Assignee: Gorkem Ercan Resolution: Done > For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Aerogear] > ------------------------------------------------------- > > Key: JBIDE-19609 > URL: https://issues.jboss.org/browse/JBIDE-19609 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, cordovasim > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Priority: Blocker > Labels: task > Fix For: 4.3.0.Alpha2 > > > For JBIDE 4.3.0.Alpha2 [Aerogear]: Please perform the following tasks: > 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha2 > [Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100. > *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Alpha2-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2; > {code} > mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT) > mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released) > {code} > 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Alpha2x > git push origin jbosstools-4.3.0.Alpha2x > {code} > 5. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19603) NPE in openshift application wizard after several attempts to remember credentials

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19603?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19603: ---------------------------------- Attachment: open-shift-npe.mp4 See attached mp4 files for exact steps. > NPE in openshift application wizard after several attempts to remember credentials > ---------------------------------------------------------------------------------- > > Key: JBIDE-19603 > URL: https://issues.jboss.org/browse/JBIDE-19603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Environment: Linux > Reporter: Denis Golovin > Assignee: Andre Dietisheim > Attachments: open-shift-npe.mp4 > > > I was trying to recover my password with try and fail method and finally succeeded to recover it but next step I got NPE's after pushing Browse button. > Authorization error was: > {code}com.openshift.client.InvalidCredentialsOpenShiftException: Your credentials are not authorized to access "https://openshift.redhat.com/broker/rest/user" > at com.openshift.internal.client.RestService.request(RestService.java:114) > at com.openshift.internal.client.RestService.request(RestService.java:92) > at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:143) > at com.openshift.internal.client.APIResource$GetUserRequest.execute(APIResource.java:400) > at com.openshift.internal.client.APIResource.getUser(APIResource.java:101) > at org.jboss.tools.openshift.express.internal.core.connection.ExpressConnection.doCreateUser(ExpressConnection.java:221) > at org.jboss.tools.openshift.express.internal.core.connection.ExpressConnection.createUser(ExpressConnection.java:206) > at org.jboss.tools.openshift.express.internal.core.connection.ExpressConnection.connect(ExpressConnection.java:183) > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:316) > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage$ConnectJob.doRun(ConnectionWizardPage.java:459) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: com.openshift.internal.client.httpclient.UnauthorizedException: HTTP Basic: Access denied. > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:196) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:165) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:144) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:103) > at com.openshift.internal.client.RestService.request(RestService.java:160) > at com.openshift.internal.client.RestService.request(RestService.java:107) > ... 11 more > Caused by: java.io.IOException: Server returned HTTP response code: 401 for URL: https://openshift.redhat.com/broker/rest/user > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1627) > at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:161) > ... 15 more{code} > and then NPE: > {code}java.lang.NullPointerException > at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPageModel.loadDomains(SelectApplicationWizardPageModel.java:71) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPageModel.loadOpenShiftResources(SelectApplicationWizardPageModel.java:67) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPage.onPageActivated(SelectApplicationWizardPage.java:135) > at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage$1.pageChanged(AbstractOpenShiftWizardPage.java:87) > at org.eclipse.jface.wizard.WizardDialog$9.run(WizardDialog.java:1505) > 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.firePageChanged(WizardDialog.java:1502) > at org.eclipse.jface.wizard.WizardDialog.update(WizardDialog.java:1308) > at org.eclipse.jface.wizard.WizardDialog.showStartingPage(WizardDialog.java:1258) > at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:599) > at org.eclipse.jface.window.Window.create(Window.java:430) > at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096) > at org.eclipse.jface.window.Window.open(Window.java:792) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.ApplicationTemplateWizardPage$2.widgetSelected(ApplicationTemplateWizardPage.java:237) > 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:4477) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > 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(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229) > 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:499) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343) > at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:160) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4477) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > 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:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) > {code} > and then one more NPE: > {code}java.lang.NullPointerException > at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPageModel.refreshDomains(SelectApplicationWizardPageModel.java:49) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPageModel.refresh(SelectApplicationWizardPageModel.java:44) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPage$2$1.run(SelectApplicationWizardPage.java:148) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){code} > Then I pushed Back and Next and was able to see cartridges and browse my old applications. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19630) v3 connections: store to default url based persistence vs custom json format

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19630?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-19630: ----------------------------------- Assignee: Andre Dietisheim > v3 connections: store to default url based persistence vs custom json format > ---------------------------------------------------------------------------- > > Key: JBIDE-19630 > URL: https://issues.jboss.org/browse/JBIDE-19630 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > In JBIDE-19374 loading/saving was implemented using a custom json based format. We should drop this and use what we use for v2 connections. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19630) v3 connections: store to default url based persistence vs custom json format

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19630?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19630: ------------------------------------- Description: In JBIDE-19374 loading/saving was implemented using a custom json based format. We should drop this and use what we use for v2 connections. > v3 connections: store to default url based persistence vs custom json format > ---------------------------------------------------------------------------- > > Key: JBIDE-19630 > URL: https://issues.jboss.org/browse/JBIDE-19630 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > In JBIDE-19374 loading/saving was implemented using a custom json based format. We should drop this and use what we use for v2 connections. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19630) v3 connections: store to default url based persistence vs custom json format

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-19630: ---------------------------------------- Summary: v3 connections: store to default url based persistence vs custom json format Key: JBIDE-19630 URL: https://issues.jboss.org/browse/JBIDE-19630 Project: Tools (JBoss Tools) Issue Type: Enhancement Reporter: Andre Dietisheim -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 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 2015