July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4488) Very slow initial startup for Eclipse

by Martin Coufal (JIRA)

Martin Coufal created JBDS-4488: ----------------------------------- Summary: Very slow initial startup for Eclipse Key: JBDS-4488 URL: https://issues.jboss.org/browse/JBDS-4488 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: rpm Affects Versions: 11.0.0.AM2 Environment: * rh-eclipse47 (http://download.eng.bos.redhat.com/rel-eng/DevTools-1.0-RHEL-7-Beta-1.0/c...) * devstudio (https://devstudio.jboss.com/11/snapshots/builds/devstudio.rpm_master/2017...) Reporter: Martin Coufal Priority: Minor Launching Eclipse after installation of any plugins from Devstudio (Red Hat Central) takes VERY long time (around 180s). This is regression bug, for more details, see [1]. Note: Also, launching rh-eclipse47 with Devstudio takes about 90s. [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1392095 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1153) Missing Fuse category in Devstudio IS standalone installer

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1153?page=com.atlassian.jira.plugin... ] Paul Leacu resolved JBTIS-1153. ------------------------------- Fix Version/s: 11.0.0.CR2 Resolution: Done Hey [~apodhrad] - please verify the stand-alone installer here: https://devstudio.redhat.com/11/staging/updates/integration-stack/11.0.0.... > Missing Fuse category in Devstudio IS standalone installer > ---------------------------------------------------------- > > Key: JBTIS-1153 > URL: https://issues.jboss.org/browse/JBTIS-1153 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 11.0.0.CR2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 11.0.0.CR2 > > Attachments: devstudio_vs_devstudiois.png > > > The Devstudio installer contains a category for installing Fuse tooling but Devstudio IS installer doesn't. IMHO the Devstudio IS installer should contain everything from Devstudio, wdyt? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

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

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24594?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24594. --------------------------------- > $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 > Fix For: 4.5.0.AM2 > > > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24769) Determine how to harmonize (or not) test structure between Fuse Tooling and JBoss Tools

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24769?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24769: ---------------------------------- Assignee: Aurélien Pupier > Determine how to harmonize (or not) test structure between Fuse Tooling and JBoss Tools > --------------------------------------------------------------------------------------- > > Key: JBIDE-24769 > URL: https://issues.jboss.org/browse/JBIDE-24769 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools, fusetools-extras > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Aurélien Pupier > Fix For: 4.5.x > > > as reported in initial document here https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > The differences are explained in this old thread http://lists.jboss.org/pipermail/jbosstools-dev/2016-January/010908.html > I gave a talk @EclipseCon on the subject: https://www.youtube.com/watch?v=IGkFy2H-d60 > To make it short: > Fuse Tooling: > - "unit test" are at class level --> plugin named *.tests, test named *Test > - "integration test" are at osgi level --> plugin named *.tests.integration, test named *IT > Jboss Tools: > - "unit test" are at osgi level --> plugin named *.tests; test named *Test > - "integration test" are also at osgi level but with more complex requirements on environment -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24769) Determine how to harmonize (or not) test structure between Fuse Tooling and JBoss Tools

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24769?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24769: ------------------------------- Fix Version/s: 4.5.x > Determine how to harmonize (or not) test structure between Fuse Tooling and JBoss Tools > --------------------------------------------------------------------------------------- > > Key: JBIDE-24769 > URL: https://issues.jboss.org/browse/JBIDE-24769 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools, fusetools-extras > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Aurélien Pupier > Fix For: 4.5.x > > > as reported in initial document here https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > The differences are explained in this old thread http://lists.jboss.org/pipermail/jbosstools-dev/2016-January/010908.html > I gave a talk @EclipseCon on the subject: https://www.youtube.com/watch?v=IGkFy2H-d60 > To make it short: > Fuse Tooling: > - "unit test" are at class level --> plugin named *.tests, test named *Test > - "integration test" are at osgi level --> plugin named *.tests.integration, test named *IT > Jboss Tools: > - "unit test" are at osgi level --> plugin named *.tests; test named *Test > - "integration test" are also at osgi level but with more complex requirements on environment -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24243) migrate Fuse Tools builds to JBT infrastructure/process

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24243?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24243 at 7/27/17 9:47 AM: ------------------------------------------------------------- Re: SAP Tools / Fuse Extras sources: https://github.com/jbosstools/jbosstools-fuse-extras/blob/master/jboss-fu... But I see the tests are not published. Do the Fuse Extras TESTS need to be published downstream into the JBT tests site for use in downstream integration tests, as we do for the Fuse Tooling tests? Re: Fuse Tooling having its own site (and async releases outside the release train), see JBIDE-24248. Re: API tooling - see https://github.com/jbosstools/jbosstools-devdoc/ and CTRL-F for "api" to find related docs. Maybe ping [~rob.stryker] too, as I believe he wrote those docs. Re: Dec 2017 release, see comment I left on that doc - there's no Dec 2017 planned release at this time. Maybe you mean Oct 31 or Jan 30? also cc:'d [~dgolovin] as that's probably a question for him re: the devsuite installer was (Author: nickboldt): Re: SAP Tools / Fuse Extras sources: https://github.com/jbosstools/jbosstools-fuse-extras/blob/master/jboss-fu... Do the Fuse Extras TESTS need to be published downstream into the JBT tests site for use in downstream integration tests? > migrate Fuse Tools builds to JBT infrastructure/process > ------------------------------------------------------- > > Key: JBIDE-24243 > URL: https://issues.jboss.org/browse/JBIDE-24243 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, fusetools, updatesite > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > > Fuse Tooling currently has jobs under this view: https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... > * https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... -> http://download.jboss.org/jbosstools/neon/staging/builds/integration-stac... > ** https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... -> http://download.jboss.org/jbosstools/neon/integration/updates/integration... > which publish integration, development or stable update sites. > As part of the migration of Fuse Tooling into JBoss Tools 4.5 for Oxygen, this path will change to something like: > * http://download.jboss.org/jbosstools/*oxygen*/snapshots/builds/fuse-tooling/ > * http://download.jboss.org/jbosstools/*oxygen*/staging/updates/fuse-tooling/ > We will also need to ensure that JBT composites/aggregates are configured to pick up these features/plugins. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24715) JST New and Noteworthy for 4.5.0.Final

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24715?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-24715. ------------------------------ Resolution: Rejected > JST New and Noteworthy for 4.5.0.Final > ----------------------------------------------------- > > Key: JBIDE-24715 > URL: https://issues.jboss.org/browse/JBIDE-24715 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jst > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.5.0.Final > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed JST 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 JST, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for JST 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-24706 #comment Create N&N for JST 4.5.0.Final #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 JST for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.5.0.Final since the AM3 release of JST, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.5.0.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.5.0.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24726) Error Reporting New and Noteworthy for 4.5.0.Final

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24726?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-24726. ------------------------------ Resolution: Rejected > Error Reporting New and Noteworthy for 4.5.0.Final > ----------------------------------------------------- > > Key: JBIDE-24726 > URL: https://issues.jboss.org/browse/JBIDE-24726 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aeri > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.5.0.Final > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Error Reporting 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 Error Reporting, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Error Reporting 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-24706 #comment Create N&N for Error Reporting 4.5.0.Final #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 Error Reporting for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.5.0.Final since the AM3 release of Error Reporting, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.5.0.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.5.0.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24710) Usage Analytics New and Noteworthy for 4.5.0.Final

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24710?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-24710. ------------------------------ Resolution: Rejected > Usage Analytics New and Noteworthy for 4.5.0.Final > ----------------------------------------------------- > > Key: JBIDE-24710 > URL: https://issues.jboss.org/browse/JBIDE-24710 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: usage > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.5.0.Final > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Usage Analytics 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 Usage Analytics, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Usage Analytics 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-24706 #comment Create N&N for Usage Analytics 4.5.0.Final #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 Usage Analytics for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.5.0.Final since the AM3 release of Usage Analytics, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.5.0.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.5.0.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24713) Maven New and Noteworthy for 4.5.0.Final

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24713?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-24713. ------------------------------ Resolution: Rejected > Maven New and Noteworthy for 4.5.0.Final > ----------------------------------------------------- > > Key: JBIDE-24713 > URL: https://issues.jboss.org/browse/JBIDE-24713 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven > Reporter: Jeff MAURY > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.5.0.Final > > > Fred Bricon, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Maven 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 Maven, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Maven 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-24706 #comment Create N&N for Maven 4.5.0.Final #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 Maven for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.5.0.Final since the AM3 release of Maven, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.5.0.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.5.0.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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