June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24540) Remove Openshift 2 tooling

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24540?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24540: ------------------------------------ >From [~rpdavis]: {quote}I thought we had decided on the 5x5 to remove OpenShift v2 tooling with the release of DevSuite 11 - it was in a comment, but I guess it didn't get pushed up.{quote} I'll therefore get this removed ASAP in AM2. [~rhopp] I've updated the fixversion for JBIDE-24580 to AM2 too. > Remove Openshift 2 tooling > -------------------------- > > Key: JBIDE-24540 > URL: https://issues.jboss.org/browse/JBIDE-24540 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Radim Hopp > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > End of support of Openshift 2 was in December 2016 [1] > There was a mail thread back in November/December 2016, where Todd stated, that Devstudio 11 would be the right release for dropping Openshift 2 support from Tools/Devstudio [2][3]. > Should we get PM/PgM approval once again just to be sure we are OK with removing Openshift 2 tooling from Tools/Devstudio? > [1] https://access.redhat.com/support/policy/updates/openshift/ > [2] http://post-office.corp.redhat.com/archives/devtools-program/2016-Novembe... > [3] http://post-office.corp.redhat.com/archives/devtools-program/2016-Decembe... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24289) Update JBoss Tools features page to better promote Fuse Tooling inside JBoss Tools

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24289?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24289: ------------------------------- Summary: Update JBoss Tools features page to better promote Fuse Tooling inside JBoss Tools (was: Update JBoss Tools features page) > Update JBoss Tools features page to better promote Fuse Tooling inside JBoss Tools > ---------------------------------------------------------------------------------- > > Key: JBIDE-24289 > URL: https://issues.jboss.org/browse/JBIDE-24289 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: website > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Lars Heinemann > Fix For: 4.5.0.AM2 > > > Once Fuse Tooling is in JBT, we'll have to update http://tools.jboss.org/features/index.html to reflect that fact. > See https://github.com/jbosstools/jbosstools-website/blob/master/features/apa... for source of the page to update. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24289) Update JBoss Tools features page to better promote Fuse Tooling (not in Integration Stack anymore)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24289?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24289: ------------------------------- Summary: Update JBoss Tools features page to better promote Fuse Tooling (not in Integration Stack anymore) (was: Update JBoss Tools features page to better promote Fuse Tooling inside JBoss Tools) > Update JBoss Tools features page to better promote Fuse Tooling (not in Integration Stack anymore) > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-24289 > URL: https://issues.jboss.org/browse/JBIDE-24289 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: website > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Lars Heinemann > Fix For: 4.5.0.AM2 > > > Once Fuse Tooling is in JBT, we'll have to update http://tools.jboss.org/features/index.html to reflect that fact. > See https://github.com/jbosstools/jbosstools-website/blob/master/features/apa... for source of the page to update. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24289) Update JBoss Tools features page

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24289?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24289: ------------------------------------ These pages are still used for JBoss Tools, afaik. Might want to check with [~jeffmaury] or [~tmancini] about how we plan to market Fuse in JBT/devstudio going forward. If you can find the equivalent documentation / marketing info on https://developers.redhat.com/products/devstudio/overview/ then yeah, maybe we don't need to talk about Fuse Tools much in the JBoss Tools context? cc: [~rkratky] At the very least, we should move the Camel stuff from being listed under Integration Stack up into the main feature list on http://tools.jboss.org/features/index.html ... but maybe we should wait on that until 4.5.0.Final is out, since TODAY the Fuse stuff *IS* in the Integration Stack. cc: [~pleacu] > Update JBoss Tools features page > -------------------------------- > > Key: JBIDE-24289 > URL: https://issues.jboss.org/browse/JBIDE-24289 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: website > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Lars Heinemann > Fix For: 4.5.0.AM2 > > > Once Fuse Tooling is in JBT, we'll have to update http://tools.jboss.org/features/index.html to reflect that fact. > See https://github.com/jbosstools/jbosstools-website/blob/master/features/apa... for source of the page to update. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24465) OpenShift New and Noteworthy for 4.5.0.AM1

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24465?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-24465. ------------------------------ Resolution: Rejected > OpenShift New and Noteworthy for 4.5.0.AM1 > --------------------------------------------------- > > Key: JBIDE-24465 > URL: https://issues.jboss.org/browse/JBIDE-24465 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdk, openshift > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.5.0.AM1 > > > Andre Dietisheim, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed OpenShift JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for OpenShift, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for OpenShift by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24455 #comment Create N&N for OpenShift 4.5.0.AM1 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for OpenShift for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24582) Runtime Environment appears twice in server editor for remote eap

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24582?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24582: --------------------------------------- I verified this and it seems alright. Yes, it's a bit strange that when you have no runtime for a remote server, the selection in Server Editor is empty and when you click to choose, you can only select to have a runtime. And once you do that, you cannot select and empty selection again. But you can always click Behavior Profile and uncheck runtime there and that will take you back to the no runtime mode. So while it's not ideal, I think it's good enough. > Runtime Environment appears twice in server editor for remote eap > ----------------------------------------------------------------- > > Key: JBIDE-24582 > URL: https://issues.jboss.org/browse/JBIDE-24582 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.0.AM2 > > Attachments: runtime-environment-twice.png > > > I just wanted to verify that remote servers are working and came across a situation where the Runtime Environment field was there twice: > !runtime-environment-twice.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24594) $0 subscription download doesn't work - Read timed out

by Martin Malina (JIRA)

Martin Malina created JBIDE-24594: ------------------------------------- Summary: $0 subscription download doesn't work - Read timed out Key: JBIDE-24594 URL: https://issues.jboss.org/browse/JBIDE-24594 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime-detection Affects Versions: 4.5.0.AM1 Reporter: Martin Malina Assignee: Rob Stryker When I try to download EAP 7.0 using Preferences -> Runtime Detection and Download, I get an error when it validates my redhat.com credentials. {code} Read timed out java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) at java.net.SocketInputStream.read(SocketInputStream.java:171) at java.net.SocketInputStream.read(SocketInputStream.java:141) at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) at sun.security.ssl.InputRecord.read(InputRecord.java:503) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) at java.io.BufferedInputStream.read(BufferedInputStream.java:345) at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:735) at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1569) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerWorkflowUtility.headerOnlyStatusCode(DownloadManagerWorkflowUtility.java:65) at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerWorkflowUtility.getWorkflowStatus(DownloadManagerWorkflowUtility.java:47) at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment.validateCredentials(DownloadManagerCredentialsFragment.java:205) at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment.access$1(DownloadManagerCredentialsFragment.java:203) at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment$3.run(DownloadManagerCredentialsFragment.java:168) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) {code} What I did: I was trying to verify JBIDE-24582, so I installed Eclipse Oxygen. Then JBoss Tools abridged (4.5.0.AM1). And then built the PR from that JIRA and installed it. I doubt it could cause this. Then I went to Preferences -> Runtime Detection and Download, selected eap 7.0, then added my account, but selected "always ask for password". Then I entered password and clicked Next. Now it failed with the above error. I tried several times. I tried the same in devstudio 11.0.0.AM1 and it works fine for me there, so that's odd - I was suspecting some server-side outage. I tried again in Eclipse and it still fails. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24076) NullPointerException in JaxrsApplicationCreationWizardPage.getWebxmlResource

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24076?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-24076: ------------------------------------- Sprint: devex #132 May 2017, devex #134 Jun 2017 (was: devex #132 May 2017) > NullPointerException in JaxrsApplicationCreationWizardPage.getWebxmlResource > ---------------------------------------------------------------------------- > > Key: JBIDE-24076 > URL: https://issues.jboss.org/browse/JBIDE-24076 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Automated Error Reporting Bot > Assignee: Dmitrii Bocharov > Fix For: 4.5.0.AM2 > > > The following problem was reported via the automated error reporting: > Message: Unhandled event loop exception > java.lang.NullPointerException: null > at org.jboss.tools.ws.jaxrs.ui.wizards.JaxrsApplicationCreationWizardPage.getWebxmlResource(JaxrsApplicationCreationWizardPage.java:596) > at org.jboss.tools.ws.jaxrs.ui.wizards.JaxrsApplicationCreationWizard.performFinish(JaxrsApplicationCreationWizard.java:84) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:790) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:423) > 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) > Bundles: > | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 | > | org.eclipse.swt | 3.105.1.v20160907-0248 | 3.105.1.v20160907-0248 | > | org.jboss.tools.ws.jaxrs.ui | 1.9.1.v20160608-0648 | 1.9.2.v20160922-1835 | > Operating Systems: > | Linux | 3.13.0 | 3.13.0 | > | Windows | 10.0.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/581152c0e4b00cfabf9... for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4451) What is the official name of JBoss Fuse?

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4451?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-4451. ------------------------------ Assignee: Lukáš Valach Resolution: Done > What is the official name of JBoss Fuse? > ---------------------------------------- > > Key: JBDS-4451 > URL: https://issues.jboss.org/browse/JBDS-4451 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: fuse-tooling > Affects Versions: 11.0.0.AM2 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Priority: Minor > Fix For: 11.0.0.AM2 > > > Recently, the JBoss Fuse was migrated from IS to JBDS. [~apodhrad] said that there was a discusion about renaming Fuse during the migration. > I have noticed that we are using couple of different names for Fuse. > JBDS -> Help -> Install New Software: *Red Hat JBoss Fuse Tools* > Jar installer -> Select Additional Features: *JBoss Fuse Tools* > Jar installer -> Summary Information: *Red Hat JBoss Fuse Developement* > [www.redhat.com|https://www.redhat.com/en/technologies/jboss-middleware/fuse]: *Red Hat JBoss Fuse* > [Product page|https://pp.engineering.redhat.com/pp/product/jbds/release/jbds-10-0/...]: *Red Hat JBoss Fuse* > So, what is the official name of Fuse? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4451) What is the official name of JBoss Fuse?

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4451?page=com.atlassian.jira.plugin.... ] Lukáš Valach commented on JBDS-4451: ------------------------------------ The "Red Hat" prefix before product name is optional I guess and we don't have to remove or add it. So the only thing we have to do is to fix name in installer -> Summary Information, because "Red Hat JBoss Fuse Development" is incorrect. I will do it in JBDS-4447. > What is the official name of JBoss Fuse? > ---------------------------------------- > > Key: JBDS-4451 > URL: https://issues.jboss.org/browse/JBDS-4451 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: fuse-tooling > Affects Versions: 11.0.0.AM2 > Reporter: Lukáš Valach > Priority: Minor > Fix For: 11.0.0.AM2 > > > Recently, the JBoss Fuse was migrated from IS to JBDS. [~apodhrad] said that there was a discusion about renaming Fuse during the migration. > I have noticed that we are using couple of different names for Fuse. > JBDS -> Help -> Install New Software: *Red Hat JBoss Fuse Tools* > Jar installer -> Select Additional Features: *JBoss Fuse Tools* > Jar installer -> Summary Information: *Red Hat JBoss Fuse Developement* > [www.redhat.com|https://www.redhat.com/en/technologies/jboss-middleware/fuse]: *Red Hat JBoss Fuse* > [Product page|https://pp.engineering.redhat.com/pp/product/jbds/release/jbds-10-0/...]: *Red Hat JBoss Fuse* > So, what is the official name of Fuse? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 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 June 2017