October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22713) IOException in CentralHelper.extractIfNeeded

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22713?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22713: ------------------------------- Sprint: devex #120 September 2016, devex #122 October 2016 (was: devex #120 September 2016) > IOException in CentralHelper.extractIfNeeded > -------------------------------------------- > > Key: JBIDE-22713 > URL: https://issues.jboss.org/browse/JBIDE-22713 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Reporter: Automated Error Reporting Bot > Assignee: Jeff MAURY > Fix For: 4.4.2.AM3 > > > The following problem was reported via the automated error reporting: > Message: Unable to open C:\eclipse\plugins\org.jboss.tools.central_2.0.1.Final-v20160401-1059-B103\resources\jbosstools-central-webpage.zip > {noformat} > java.io.IOException: D:\OneDrive\TreinaWeb\Java Básico\JSE\.metadata\.plugins\org.jboss.tools.central\central\bc8a80b\index.html can not be found > at org.jboss.tools.central.internal.CentralHelper.extractIfNeeded(CentralHelper.java:203) > at org.jboss.tools.central.internal.CentralHelper.getCentralPageUrl(CentralHelper.java:122) > at org.jboss.tools.central.internal.CentralHelper.getCentralUrl(CentralHelper.java:60) > at org.jboss.tools.central.editors.GettingStartedHtmlPage$5.run(GettingStartedHtmlPage.java:252) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 | > | org.jboss.tools.central | 2.0.1.Final-v20160401-1059-B103 | 2.1.0.qualifier | > Operating Systems: > | Linux | 3.2.0 | 4.5.7.fc23 | > | MacOSX | 10.10.5 | 10.11.5 | > | Windows | 5.1.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571659e0e4b055563f...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4110) New project always created under default namespace Openshift v3 Eclipse Tooling

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4110?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4110: ----------------------------- Sprint: devex #122 October 2016 > New project always created under default namespace Openshift v3 Eclipse Tooling > ------------------------------------------------------------------------------- > > Key: JBDS-4110 > URL: https://issues.jboss.org/browse/JBDS-4110 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: openshift > Affects Versions: 10.1.0.GA > Environment: !Screen Shot 2016-10-12 at 4.17.54 PM.png|thumbnail! > !Screen Shot 2016-10-12 at 4.17.45 PM.png|thumbnail! > !Screen Shot 2016-10-12 at 4.17.18 PM.png|thumbnail! > Reporter: Zak Hassan > Assignee: Jeff MAURY > Attachments: Screen Shot 2016-10-12 at 4.16.11 PM.png, Screen Shot 2016-10-12 at 4.17.18 PM.png, Screen Shot 2016-10-12 at 4.17.45 PM.png, Screen Shot 2016-10-12 at 4.17.54 PM.png > > > When creating a new project using eclipse openshift plugin dev studio. I specifically request to create an application under namespace "fsoss2016" but get my application created under default namespace Openshift v3 Eclipse Tooling. > See image below: > !Screen Shot 2016-10-12 at 4.16.11 PM.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23356) Deploy Docker Wizard: Image Stream created for local images is not shown in resource summary

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23356?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23356: ------------------------------- Sprint: devex #122 October 2016 > Deploy Docker Wizard: Image Stream created for local images is not shown in resource summary > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23356 > URL: https://issues.jboss.org/browse/JBIDE-23356 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > > When deploying a local docker image to OpenShift and pushing it to OpenShift registry, ImageStream is also created but it is not listed in the table of Resource creation summary right after deployment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23362) Failed test because of JBIDE-22916

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23362?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23362: ------------------------------- Sprint: devex #122 October 2016 > Failed test because of JBIDE-22916 > ---------------------------------- > > Key: JBIDE-23362 > URL: https://issues.jboss.org/browse/JBIDE-23362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: openshift, openshift_v3, tests > Fix For: 4.4.2.AM3 > > > Some DeployImageWizardModelTest are failing because of JBIDE-22916 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23300) After installation with development suite installer, restarting the Studio, cannot connect anymore automatically to OpenShift instance

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23300?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23300: ------------------------------- Sprint: devex #122 October 2016 > After installation with development suite installer, restarting the Studio, cannot connect anymore automatically to OpenShift instance > -------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23300 > URL: https://issues.jboss.org/browse/JBIDE-23300 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Fix For: 4.4.2.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23363) Docker tooling source code not available in the TP

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-23363: ---------------------------------- Summary: Docker tooling source code not available in the TP Key: JBIDE-23363 URL: https://issues.jboss.org/browse/JBIDE-23363 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.4.2.AM2 Reporter: Jeff MAURY The 4.60 and 4.61 TP do not have the source artifacts for Docker Tooling. They are not in http://download.jboss.org/jbosstools/updates/requirements/neon/201609281000 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4077) Cannot run integration tests against Devstudio with latest target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4077?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4077: ---------------------------------- I'm not sure what to do here, since I can't reproduce the same problems you're seeing. And worse, the same tests all pass in Jenkins: http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integratio... ... but looking closer, it seems that the build is blue because it's simply compiling the tests with -DskipTests. So that's a pretty meaningless test. :( I've changed that in the job config and am running them now, but I expect they'll fail because they're missing all the arcane -D flags you need to pass into the job to properly run the tests. Could someone take some time to configure the job with all the requires parameters so that what you're running locally can be reproduced in Jenkins, with a log & all the artifacts produced too? > Cannot run integration tests against Devstudio with latest target platform > -------------------------------------------------------------------------- > > Key: JBDS-4077 > URL: https://issues.jboss.org/browse/JBDS-4077 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 10.2.0.AM1 > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.2.0.AM3 > > Attachments: .log, jbosstools-integration-tests.log.txt.zip, org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.txt, org.jboss.tools.deltaspike.ui.bot.test.log.txt, org.jboss.tools.deltaspike.ui.bot.test.log_0.txt, Screenshot_2016-10-05_10-00-03.png, Screenshot_2016-10-05_10-00-21.png, Screenshot_2016-10-05_10-00-28.png, Screenshot_2016-10-05_10-00-57.png, Screenshot_2016-10-05_10-01-14.png, Screenshot_2016-10-05_10-01-32.png, shell.png, TEST-org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.xml, tpfail.png > > > Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards. > A full devstudio should open when the tests are run. Instead it looks like this: > !tpfail.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4077) Cannot run integration tests against Devstudio with latest target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4077?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4077: ----------------------------- Fix Version/s: 10.2.0.AM3 > Cannot run integration tests against Devstudio with latest target platform > -------------------------------------------------------------------------- > > Key: JBDS-4077 > URL: https://issues.jboss.org/browse/JBDS-4077 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 10.2.0.AM1 > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.2.0.AM3 > > Attachments: .log, jbosstools-integration-tests.log.txt.zip, org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.txt, org.jboss.tools.deltaspike.ui.bot.test.log.txt, org.jboss.tools.deltaspike.ui.bot.test.log_0.txt, Screenshot_2016-10-05_10-00-03.png, Screenshot_2016-10-05_10-00-21.png, Screenshot_2016-10-05_10-00-28.png, Screenshot_2016-10-05_10-00-57.png, Screenshot_2016-10-05_10-01-14.png, Screenshot_2016-10-05_10-01-32.png, shell.png, TEST-org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.xml, tpfail.png > > > Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards. > A full devstudio should open when the tests are run. Instead it looks like this: > !tpfail.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4085) unresolved bundles, slow initial start up

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4085?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4085: -------------------------------- Assignee: Nick Boldt > unresolved bundles, slow initial start up > ----------------------------------------- > > Key: JBDS-4085 > URL: https://issues.jboss.org/browse/JBDS-4085 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Reporter: Václav Kadlčík > Assignee: Nick Boldt > Fix For: 10.2.0.AM3 > > Attachments: restart-after-installing-m2e-wtp-jsf-stuff-from-Central.txt, restart-after-installing-m2e-wtp-jsf-stuff-from-Central_full.txt, unresolved-max.out, unresolved-mid.out, unresolved-min.out, workspace-max.log, workspace-mid.log, workspace-min.log > > > Tested: > * rh-eclipse46-devstudio-10.2-0.20161004.2205.el7.x86_64.rpm > * rh-eclipse46 Beta (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-Beta-...) > rh-eclipse46 has its own unresolved bundles (https://bugzilla.redhat.com/show_bug.cgi?id=1381820). But when you add rh-eclipse46-devstudio, the number of unresolved symbols increases quite dramatically and initial start up times also get worse. (I guess that the two problems can be connected so I file them together but feel free to split them if I'm mistaken). > I'm attaching "ss -s INSTALLED" and workspace logs for several scenarios: > * "min" in the name means minimal install rh-eclipse46-devstudio > * "mid" is for "yum install rh-eclipse46 rh-eclipse46-devstudio" > * "max" is for "yum install 'rh-eclipse46*'" - all the available RPMs, including devstudio > As for start up times, it looks like devstudio adds ~80s for one particular machine (Xeon with 16 cores 2.40GHz, 16 GB RAM). For example: > initial start of rh-eclipse46: 40s > same as above with rh-eclipse46-devstudio: 120s > initial start of rh-eclipse46* except devstudio: 50s > same as above with rh-eclipse46-devstudio: 140s > Roland Grunberg managed to improve initial start up times in rh-eclise46 a few weeks ago (https://bugzilla.redhat.com/show_bug.cgi?id=1362178#c17). I don't know it it helps here but I'm linking it anyway... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4085) unresolved bundles, slow initial start up

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4085?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4085: ----------------------------- Fix Version/s: 10.2.0.AM3 > unresolved bundles, slow initial start up > ----------------------------------------- > > Key: JBDS-4085 > URL: https://issues.jboss.org/browse/JBDS-4085 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Reporter: Václav Kadlčík > Fix For: 10.2.0.AM3 > > Attachments: restart-after-installing-m2e-wtp-jsf-stuff-from-Central.txt, restart-after-installing-m2e-wtp-jsf-stuff-from-Central_full.txt, unresolved-max.out, unresolved-mid.out, unresolved-min.out, workspace-max.log, workspace-mid.log, workspace-min.log > > > Tested: > * rh-eclipse46-devstudio-10.2-0.20161004.2205.el7.x86_64.rpm > * rh-eclipse46 Beta (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-Beta-...) > rh-eclipse46 has its own unresolved bundles (https://bugzilla.redhat.com/show_bug.cgi?id=1381820). But when you add rh-eclipse46-devstudio, the number of unresolved symbols increases quite dramatically and initial start up times also get worse. (I guess that the two problems can be connected so I file them together but feel free to split them if I'm mistaken). > I'm attaching "ss -s INSTALLED" and workspace logs for several scenarios: > * "min" in the name means minimal install rh-eclipse46-devstudio > * "mid" is for "yum install rh-eclipse46 rh-eclipse46-devstudio" > * "max" is for "yum install 'rh-eclipse46*'" - all the available RPMs, including devstudio > As for start up times, it looks like devstudio adds ~80s for one particular machine (Xeon with 16 cores 2.40GHz, 16 GB RAM). For example: > initial start of rh-eclipse46: 40s > same as above with rh-eclipse46-devstudio: 120s > initial start of rh-eclipse46* except devstudio: 50s > same as above with rh-eclipse46-devstudio: 140s > Roland Grunberg managed to improve initial start up times in rh-eclise46 a few weeks ago (https://bugzilla.redhat.com/show_bug.cgi?id=1362178#c17). I don't know it it helps here but I'm linking it anyway... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 October 2016