February 2014 - jbosstools-issues

[JBoss JIRA] (JBDS-2886) 7.1.1 Supported Operating Systems

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2886?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-2886: ------------------------------ Assignee: Len DiMaggio > 7.1.1 Supported Operating Systems > --------------------------------- > > Key: JBDS-2886 > URL: https://issues.jboss.org/browse/JBDS-2886 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Burr Sutter > Assignee: Len DiMaggio > Labels: jbds711 > Fix For: 7.1.1.CR1 > > > Current OS/JVM combinations as of JBDS 7.1.0 https://access.redhat.com/site/articles/427493 > add OSX 10.9 Mavericks > remove OSX 10.7 Lion > We target testing & support at the latest two OSX releases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16046) CLONE - allow users to set openshift-java-client specific timeout in JBoss Tools via Eclipse Preferences

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16046?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-16046. --------------------------------- Verified in JBT 4.2.0.Alpha1. > CLONE - allow users to set openshift-java-client specific timeout in JBoss Tools via Eclipse Preferences > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-16046 > URL: https://issues.jboss.org/browse/JBIDE-16046 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: new_and_noteworthy > Fix For: 4.2.0.Alpha1 > > Attachments: openshift-client-timeout.png > > > In JBIDE-15880 we provide a system property that allow JBoss Tools to set a timeout that affects only the http connections that the openshift-java-client is using. We We should allow users to set this value in JBoss tools via Eclipse preferences -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16047) CLONE - Timeout when add/remove postgresql cartridge to application (Openshift Enterprise)

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16047?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-16047. --------------------------------- Verified in JBT 4.2.0.Alpha1. > CLONE - Timeout when add/remove postgresql cartridge to application (Openshift Enterprise) > ------------------------------------------------------------------------------------------ > > Key: JBIDE-16047 > URL: https://issues.jboss.org/browse/JBIDE-16047 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Marián Labuda > Assignee: Max Rydahl Andersen > Fix For: 4.2.0.Alpha1 > > > Attempt to add to existing (or can be added when creating new) application PostgreSQL database cartridge cause connection time out. Dialog with text > {code}Could not request url https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati..., connection timed out {code} is shown. > Finally, cartridge seems to be added correctly (seems to be embedded well, environment variables are correctly set up for the given cartridge etc.) > This happens only on Openshift Enterprise (Openshift Online works fine) > Eclipse log: > {code} > !ENTRY org.jboss.tools.openshift.express.ui 4 0 2013-11-01 12:54:14.209 > !MESSAGE Could not embed cartridges for application dasda > !STACK 0 > com.openshift.client.OpenShiftTimeoutException: Could not request url https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati..., connection timed out > at com.openshift.internal.client.RestService.request(RestService.java:139) > at com.openshift.internal.client.RestService.request(RestService.java:109) > at com.openshift.internal.client.RestService.request(RestService.java:92) > at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:142) > at com.openshift.internal.client.ApplicationResource$AddEmbeddedCartridgeRequest.execute(ApplicationResource.java:1026) > at com.openshift.internal.client.ApplicationResource.addEmbeddableCartridge(ApplicationResource.java:353) > at com.openshift.internal.client.ApplicationResource.addEmbeddableCartridges(ApplicationResource.java:368) > at org.jboss.tools.openshift.express.internal.ui.job.EmbedCartridgesJob.addEmbeddedCartridges(EmbedCartridgesJob.java:94) > at org.jboss.tools.openshift.express.internal.ui.job.EmbedCartridgesJob.doRun(EmbedCartridgesJob.java:56) > at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > Caused by: java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.read(SocketInputStream.java:150) > at java.net.SocketInputStream.read(SocketInputStream.java:121) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:442) > at sun.security.ssl.InputRecord.read(InputRecord.java:480) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:927) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:884) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:102) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:235) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:275) > at java.io.BufferedInputStream.read(BufferedInputStream.java:334) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:633) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:579) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1322) > at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:146) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:125) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:101) > at com.openshift.internal.client.RestService.request(RestService.java:179) > at com.openshift.internal.client.RestService.request(RestService.java:123) > ... 10 more > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16343) "Materialize Libraries" is not obvious

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16343?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-16343: ------------------------------------- Yes, the 2nd statement is more clear - as I was interpreting that my pom.xml might disappear. :-) > "Materialize Libraries" is not obvious > -------------------------------------- > > Key: JBIDE-16343 > URL: https://issues.jboss.org/browse/JBIDE-16343 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven > Affects Versions: 4.2.0.Alpha1 > Reporter: Mickael Istria > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.2.0.Alpha2 > > > While looking at [~fbricon] doing a demo I (and [~FroMage] and [~xcoulon]) felt that "Materialize Libraries" is not a clear name for what it does. > Why not renaming it to "Copy libraries into Project..." or "Turn into Libraries inside project..." ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16048) CLONE - OpenShift Explorer: OpenShift Enterprise: Refreshing domain has no effect

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16048?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-16048. --------------------------------- Verified in JBT 4.2.0.Alpha1. > CLONE - OpenShift Explorer: OpenShift Enterprise: Refreshing domain has no effect > --------------------------------------------------------------------------------- > > Key: JBIDE-16048 > URL: https://issues.jboss.org/browse/JBIDE-16048 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16049) CLONE - Edit environment variables: Cannot edit env vars, erroneous warning "not supported"

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16049?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-16049. --------------------------------- Verified in JBT 4.2.0.Alpha1. > CLONE - Edit environment variables: Cannot edit env vars, erroneous warning "not supported" > ------------------------------------------------------------------------------------------- > > Key: JBIDE-16049 > URL: https://issues.jboss.org/browse/JBIDE-16049 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15840) CLONE - Can't restart application through server adapter

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15840?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-15840. --------------------------------- Verified in JBT 4.2.0.Alpha1. > CLONE - Can't restart application through server adapter > -------------------------------------------------------- > > Key: JBIDE-15840 > URL: https://issues.jboss.org/browse/JBIDE-15840 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Marián Labuda > Assignee: Max Rydahl Andersen > Fix For: 4.2.0.Alpha1 > > > ASSERT: have created OpenShift application > EXEC: restart through OpenShift explorer > ASSERT: application is restarting > EXEC: restart through created server adapter (context menu -> OpenShift -> Restart Aplication) > ASSERT: nothing happens > In the Eclipse log you'll spot the following: > {code} > java.lang.NullPointerException > at org.jboss.tools.openshift.express.internal.ui.job.RestartApplicationJob.<init>(RestartApplicationJob.java:33) > at org.jboss.tools.openshift.express.internal.ui.serverviewer.actionDelegate.RestartApplicationActionProvider$RestartApplicationAction.restartApplication(RestartApplicationActionProvider.java:48) > at org.jboss.tools.openshift.express.internal.ui.serverviewer.actionDelegate.RestartApplicationActionProvider$RestartApplicationAction.run(RestartApplicationActionProvider.java:42) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:499) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) > at org.eclipse.equinox.launcher.Main.run(Main.java:1450) > at org.eclipse.equinox.launcher.Main.main(Main.java:1426) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16343) "Materialize Libraries" is not obvious

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16343?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-16343 at 2/3/14 10:36 AM: -------------------------------------------------------------- No, the pom.xml is not deleted. Users can still decide to import their project as a Maven project and go back to the original situation. Strictly speaking, the warning should be "This will remove the Maven nature from this project" or "This will remove the Maven/Eclipse configuration from this project" was (Author: fbricon): No, the pom.xml is not deleted. Users can still decide to import their project as a Maven project and go back to the original situation. > "Materialize Libraries" is not obvious > -------------------------------------- > > Key: JBIDE-16343 > URL: https://issues.jboss.org/browse/JBIDE-16343 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven > Affects Versions: 4.2.0.Alpha1 > Reporter: Mickael Istria > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.2.0.Alpha2 > > > While looking at [~fbricon] doing a demo I (and [~FroMage] and [~xcoulon]) felt that "Materialize Libraries" is not a clear name for what it does. > Why not renaming it to "Copy libraries into Project..." or "Turn into Libraries inside project..." ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16381) Application wizard: wizard will create app and import, but wont create adapter and wont close

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16381?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-16381. --------------------------------- Verified in JBT 4.2.0.Alpha1. > Application wizard: wizard will create app and import, but wont create adapter and wont close > --------------------------------------------------------------------------------------------- > > Key: JBIDE-16381 > URL: https://issues.jboss.org/browse/JBIDE-16381 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.2.0.Alpha1 > > Attachments: stop-at-page2-and-wont-close.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16045) CLONE - Application wizard: Cannot create application with environment variables: button not viisible

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16045?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-16045. --------------------------------- Verified in JBT 4.2.0.Alpha1. > CLONE - Application wizard: Cannot create application with environment variables: button not viisible > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-16045 > URL: https://issues.jboss.org/browse/JBIDE-16045 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.2.0.Alpha1 > > Attachments: missing-env-vars-button.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 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 February 2014