October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15804) Repair failing tests in: http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15804?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-15804: -------------------------------------- It looks like the command to invoke the tests changed. From: /bin/sh -c cd /home/jbossqa/workspace/jbosstools.mylyn.bot.tests.poc/mylyn/tests/org.jboss.tools.mylyn.ui.bot.test && /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/bin/java -Dosgi.noShutdown=false -Dosgi.os=linux -Dosgi.ws=gtk -Dosgi.arch=x86_64 '-javaagent:/home/jbossqa/.m2/repository/org/jacoco/org.jacoco.agent/0.6.1.201212231917/org.jacoco.agent-0.6.1.201212231917-runtime.jar=destfile=/home/jbossqa/workspace/jbosstools.mylyn.bot.tests.poc/mylyn/target/jacoco.exec,append=true,includes=org.jboss.tools.*' -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m -Dswt.bot.test.record.screencast=false -Dorg.eclipse.swtbot.screenshots.dir=/home/jbossqa/workspace/jbosstools.mylyn.bot.tests.poc/mylyn/tests/org.jboss.tools.mylyn.ui.bot.test/target/screenshots -Dusage_reporting_enabled=false -Dorg.jboss.tools.tests.skipPrivateRequirements=false -Dorg.eclipse.ui.testsDisableWorkbenchAutoSave=true -jar /home/jbossqa/.m2/repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.3.0.v20130327-1440/org.eclipse.equinox.launcher-1.3.0.v20130327-1440.jar -data /home/jbossqa/workspace/jbosstools.mylyn.bot.tests.poc/mylyn/tests/org.jboss.tools.mylyn.ui.bot.test/target/work/data -install /home/jbossqa/workspace/jbosstools.mylyn.bot.tests.poc/mylyn/tests/org.jboss.tools.mylyn.ui.bot.test/target/work -configuration /home/jbossqa/workspace/jbosstools.mylyn.bot.tests.poc/mylyn/tests/org.jboss.tools.mylyn.ui.bot.test/target/work/configuration -application org.eclipse.tycho.surefire.osgibooter.uitest -testproperties /home/jbossqa/workspace/jbosstools.mylyn.bot.tests.poc/mylyn/tests/org.jboss.tools.mylyn.ui.bot.test/target/surefire.properties -testApplication org.eclipse.ui.ide.workbench -product org.eclipse.platform.ide -nouithread To: /bin/sh -c cd /home/jbossqa/workspace/jbosstools.mylyn.bot.tests.poc/mylyn/tests/org.jboss.tools.mylyn.ui.bot.test && /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/bin/java -Dosgi.noShutdown=false -Dosgi.os=linux -Dosgi.ws=gtk -Dosgi.arch=x86_64 '-javaagent:/home/jbossqa/.m2/repository/org/jacoco/org.jacoco.agent/0.6.1.201212231917/org.jacoco.agent-0.6.1.201212231917-runtime.jar=destfile=/home/jbossqa/workspace/jbosstools.mylyn.bot.tests.poc/mylyn/target/jacoco.exec,append=true,includes=org.jboss.tools.*' -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m -Dswt.bot.test.record.screencast=false -Dorg.eclipse.swtbot.screenshots.dir=/home/jbossqa/workspace/jbosstools.mylyn.bot.tests.poc/mylyn/tests/org.jboss.tools.mylyn.ui.bot.test/target/screenshots -Dusage_reporting_enabled=false -Dorg.jboss.tools.tests.skipPrivateRequirements=false -Dorg.eclipse.ui.testsDisableWorkbenchAutoSave=true -jar /home/jbossqa/.m2/repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.3.0.v20130327-1440/org.eclipse.equinox.launcher-1.3.0.v20130327-1440.jar -data /home/jbossqa/workspace/jbosstools.mylyn.bot.tests.poc/mylyn/tests/org.jboss.tools.mylyn.ui.bot.test/target/work/data -install /home/jbossqa/workspace/jbosstools.mylyn.bot.tests.poc/mylyn/tests/org.jboss.tools.mylyn.ui.bot.test/target/work -configuration /home/jbossqa/workspace/jbosstools.mylyn.bot.tests.poc/mylyn/tests/org.jboss.tools.mylyn.ui.bot.test/target/work/configuration -application org.eclipse.tycho.surefire.osgibooter.uitest -testproperties /home/jbossqa/workspace/jbosstools.mylyn.bot.tests.poc/mylyn/tests/org.jboss.tools.mylyn.ui.bot.test/target/surefire.properties -nouithread Where this was lost: -product org.eclipse.platform.ide > Repair failing tests in: http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/ > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-15804 > URL: https://issues.jboss.org/browse/JBIDE-15804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Len DiMaggio > Assignee: Len DiMaggio > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15804) Repair failing tests in: http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-15804: ------------------------------------ Summary: Repair failing tests in: http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/ Key: JBIDE-15804 URL: https://issues.jboss.org/browse/JBIDE-15804 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Len DiMaggio Assignee: Len DiMaggio -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15802) Unable to import Cordova Plugin from Git

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15802?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-15802: --------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Assignee: Gorkem Ercan > Unable to import Cordova Plugin from Git > ---------------------------------------- > > Key: JBIDE-15802 > URL: https://issues.jboss.org/browse/JBIDE-15802 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.1.Beta1 > Environment: JBT 4.1.1 Beta1-v20131020-0207-B454 > Reporter: Vlado Pakan > Assignee: Gorkem Ercan > Fix For: 4.1.1.CR1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > 1. Create Hybrid Mobile project > 2. Open config.xml in Corodova Configuration editor > 3. Click on button Add.. to add Feature > 4. Click on Git tab of Cordova Plugins Discovery dialog > 5. Write some Plugins git repo to URL text > ERROR: Finish button is always disabled so it's not possible to add Plugin from Git repo -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15802) Unable to import Cordova Plugin from Git

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15802?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-15802: -------------------------------------- fixed on master > Unable to import Cordova Plugin from Git > ---------------------------------------- > > Key: JBIDE-15802 > URL: https://issues.jboss.org/browse/JBIDE-15802 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.1.Beta1 > Environment: JBT 4.1.1 Beta1-v20131020-0207-B454 > Reporter: Vlado Pakan > Assignee: Gorkem Ercan > Fix For: 4.1.1.CR1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > 1. Create Hybrid Mobile project > 2. Open config.xml in Corodova Configuration editor > 3. Click on button Add.. to add Feature > 4. Click on Git tab of Cordova Plugins Discovery dialog > 5. Write some Plugins git repo to URL text > ERROR: Finish button is always disabled so it's not possible to add Plugin from Git repo -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15612) install-grinder gets stuck after installing JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15612?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15612: ------------------------------------ https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... and https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... are now all blue. What new timeout did you set? Could you link to the git change(s) ? > install-grinder gets stuck after installing JBDS > ------------------------------------------------ > > Key: JBIDE-15612 > URL: https://issues.jboss.org/browse/JBIDE-15612 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.1.1.Alpha2 > Reporter: Nick Boldt > Assignee: Pavol Srna > Fix For: 4.1.1.Beta1, 4.1.1.CR1 > > Attachments: install-grinder-gets-stuck.png > > > Seems that the prompt at the end of the installation of JBDS is not being caught and clicked by the install grinder, so the eclipse instance stays open forever (until the job times out). > Steps to reproduce locally: > {code} > # as root, install these if not already installed > yum install tigervnc.x86_64 tigervnc-server.x86_64 vinagre -y > exit > # in a terminal, run this: > vncserver > # then launch vinagre to connect to the VNC session: > vinagre localhost:1 > # within the VNC session, run this: > git clone https://github.com/jbosstools/jbosstools-install-grinder/ > cd jbosstools-install-grinder > mvn org.apache.maven.plugins:maven-dependency-plugin:2.7:unpack \ > -Dartifact=org.jboss.tools.installation-tests:scripts:4.1.0.Beta1-SNAPSHOT:zip:delivery > cd scripts/target/scripts-*-delivery/ > SCRIPTDIR=`pwd` > WORKSPACE=/tmp/jbtcentraltarget-verify > rm -fr ${WORKSPACE}; mkdir -p ${WORKSPACE}; cd ${WORKSPACE} > # must be lowercase kepler > eclipseBundleVersion=kepler.R > # or > eclipseBundleVersion=kepler.SR1 > # path to where you store eclipse tar.gz files > eclipseCacheDirectory=${HOME}/tmp/Eclipse_Bundles > groovy ${SCRIPTDIR}/getAndInstallEclipse.groovy \ > eclipseCacheDirectory=${eclipseCacheDirectory} \ > eclipseBundleVersion=${eclipseBundleVersion} > INSTALL_PLAN="http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/;http:/..." > # or > INSTALL_PLAN="http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/;http:..." > groovy ${SCRIPTDIR}/testInstall.groovy ${WORKSPACE}/eclipse/ $INSTALL_PLAN > {code} > Here's a screenshot: > !install-grinder-gets-stuck.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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15612) install-grinder gets stuck after installing JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15612?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15612: ------------------------------------ Log should show which URLs are used to install everything from Central. Bear in mind that most of that content is on devstudio.jboss.com (can be slow/bottlenecky), or download.jboss.org (generally fast but occasionally dead), but two connectors are linked to google.com and zeroturnaround.com. If those sites are slow, there's nothing we can do except to exclude those connectors from installation. But again, since this works for JBT Central, and JBDS installation is more or less the same size as JBT install, it seems like the bottleneck / network slowness is coming from devstudio.jboss.com. > install-grinder gets stuck after installing JBDS > ------------------------------------------------ > > Key: JBIDE-15612 > URL: https://issues.jboss.org/browse/JBIDE-15612 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.1.1.Alpha2 > Reporter: Nick Boldt > Assignee: Pavol Srna > Fix For: 4.1.1.Beta1, 4.1.1.CR1 > > Attachments: install-grinder-gets-stuck.png > > > Seems that the prompt at the end of the installation of JBDS is not being caught and clicked by the install grinder, so the eclipse instance stays open forever (until the job times out). > Steps to reproduce locally: > {code} > # as root, install these if not already installed > yum install tigervnc.x86_64 tigervnc-server.x86_64 vinagre -y > exit > # in a terminal, run this: > vncserver > # then launch vinagre to connect to the VNC session: > vinagre localhost:1 > # within the VNC session, run this: > git clone https://github.com/jbosstools/jbosstools-install-grinder/ > cd jbosstools-install-grinder > mvn org.apache.maven.plugins:maven-dependency-plugin:2.7:unpack \ > -Dartifact=org.jboss.tools.installation-tests:scripts:4.1.0.Beta1-SNAPSHOT:zip:delivery > cd scripts/target/scripts-*-delivery/ > SCRIPTDIR=`pwd` > WORKSPACE=/tmp/jbtcentraltarget-verify > rm -fr ${WORKSPACE}; mkdir -p ${WORKSPACE}; cd ${WORKSPACE} > # must be lowercase kepler > eclipseBundleVersion=kepler.R > # or > eclipseBundleVersion=kepler.SR1 > # path to where you store eclipse tar.gz files > eclipseCacheDirectory=${HOME}/tmp/Eclipse_Bundles > groovy ${SCRIPTDIR}/getAndInstallEclipse.groovy \ > eclipseCacheDirectory=${eclipseCacheDirectory} \ > eclipseBundleVersion=${eclipseBundleVersion} > INSTALL_PLAN="http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/;http:/..." > # or > INSTALL_PLAN="http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/;http:..." > groovy ${SCRIPTDIR}/testInstall.groovy ${WORKSPACE}/eclipse/ $INSTALL_PLAN > {code} > Here's a screenshot: > !install-grinder-gets-stuck.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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2797) .ini upgrade issue for 7.0.1 OSX users

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2797?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2797: ------------------------------------------- [~dgolovin] is this fixed or not ? > .ini upgrade issue for 7.0.1 OSX users > -------------------------------------- > > Key: JBDS-2797 > URL: https://issues.jboss.org/browse/JBDS-2797 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer > Affects Versions: 7.0.1.GA > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Labels: respin-a > Fix For: 7.1.0.Beta1 > > > User noticed issues with 7.0.0 to 7.0.1 updates at https://community.jboss.org/message/841477#841477 that needs investigation. > The post is about osx but I don't think this is limited to this OS, just that OSX has a different java behavior. > Worrisome issues are: > development url used in GA update: > -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml > startup/launcher directories are hardcoded in the .ini file: > -startup > ../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar > --launcher.library > ../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.200.v20130807-1835 > Have these been forgotten/set wrong in the update or is this some specific update path that is failing ? -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15749) Every archetype-based example project from central has possibility to create blank project

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15749?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15749: ---------------------------------------- Labels: (was: respin-a) > Every archetype-based example project from central has possibility to create blank project > ------------------------------------------------------------------------------------------ > > Key: JBIDE-15749 > URL: https://issues.jboss.org/browse/JBIDE-15749 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.1.Beta1 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Fix For: 4.1.1.Beta1 > > > "Create a blank project" checkbox button is present for every archetype based example (HTML5, Richfaces, Spring, Java EE6,GWT). It does nothing except for Java EE6 which really generates blank project. This button should be removed for other examples if it does nothing. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15749) Every archetype-based example project from central has possibility to create blank project

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15749?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15749: --------------------------------------------- this is not a blocker for beta1 imo. thus not relevant to put on respin-a > Every archetype-based example project from central has possibility to create blank project > ------------------------------------------------------------------------------------------ > > Key: JBIDE-15749 > URL: https://issues.jboss.org/browse/JBIDE-15749 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.1.Beta1 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Fix For: 4.1.1.Beta1 > > > "Create a blank project" checkbox button is present for every archetype based example (HTML5, Richfaces, Spring, Java EE6,GWT). It does nothing except for Java EE6 which really generates blank project. This button should be removed for other examples if it does nothing. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15792) JPP 6.1 project does not contain JBoss Portlet Libraries

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15792?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-15792: --------------------------------------- The issue is caused by the change of the structure in JPP 6.1. Fixed by https://github.com/jbosstools/jbosstools-portlet/commit/28cf63877772d39a8... > JPP 6.1 project does not contain JBoss Portlet Libraries > -------------------------------------------------------- > > Key: JBIDE-15792 > URL: https://issues.jboss.org/browse/JBIDE-15792 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.1.1.Beta1 > Reporter: Radoslav Rábara > Assignee: Snjezana Peco > Priority: Blocker > Labels: respin-a > Fix For: 4.1.1.Beta1 > > Attachments: portlet.jpg > > > Portal project with target runtime JPP 6.1.Final does not contain file "JBoss Portlet Libraries", so Java Portlet contains errors. However, if you create portal project with JPP 6.1.Beta then the file exists and no error is present. -- 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, 6 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 2013