]
Nick Boldt edited comment on JBIDE-13845 at 3/23/13 2:30 AM:
-------------------------------------------------------------
Broken, needs to use org.junit:
*
Will need to be changed/created to pull from 4.0.x branch of install-grinder after
branching (to keep using org.junit4):
* *NEW JOB*:
was (Author: nickboldt):
Broken, needs to use org.junit:
Will need to be changed/created to pull from 4.0.x branch of install-grinder after
branching (to keep using org.junit4):
Branch install-grinder for Juno (using
org.eclipse.swtbot.eclipse.test.junit4.feature.group 2.0.5 and org.junit4 4.8) and Kepler
(org.eclipse.swtbot.eclipse.test.junit.feature.group 2.1 and org.junit 4.11)
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13845
URL:
https://issues.jboss.org/browse/JBIDE-13845
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: testing-tools
Affects Versions: 4.1.0.Alpha2
Reporter: Nick Boldt
Assignee: Mickael Istria
Priority: Blocker
Fix For: 4.1.0.Alpha2
As noted in JBIDE-13843, Kepler M6 no longer includes the org.junit4_4.8 bundle; instead
it includes org.junit_4.11.
So, install-grinder fails to set up the install base with this error due to the missing
IU:
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-install-grinder.install-tests.matrix_master/INSTALL_PLAN=http%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fdiscovery%2Fnightly%2Fcore%2Ftrunk%2F%3Bhttp%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fdiscovery%2Fnightly%2Fcore%2Ftrunk%2Fdevstudio-directory.xml,eclipseBundleVersion=kepler.M6,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/102/console}
Framework arguments: -application org.eclipse.equinox.p2.director -repository
http://download.eclipse.org/technology/swtbot/helios/dev-build/update-sit...
-installIU org.jboss.tools.tests.installation -installIU
org.eclipse.swtbot.eclipse.test.junit4.feature.group
Command-line arguments: -application org.eclipse.equinox.p2.director -repository
http://download.eclipse.org/technology/swtbot/helios/dev-build/update-sit...
-installIU org.jboss.tools.tests.installation -installIU
org.eclipse.swtbot.eclipse.test.junit4.feature.group -consolelog
!ENTRY org.eclipse.equinox.p2.director 4 1 2013-03-23 02:15:09.053
!MESSAGE Cannot complete the install because one or more required items could not be
found.
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2013-03-23 02:15:09.054
!MESSAGE Software bCannot complete the install because one or more required items could
not be found.
Software being installed: SWTBot JUnit 4.x Headless launchers for Eclipse (incubation)
2.0.5.20111003_1754-3676ac8-dev-e36 (org.eclipse.swtbot.eclipse.test.junit4.feature.group
2.0.5.20111003_1754-3676ac8-dev-e36)
Missing requirement: SWTBot JUnit 4.x Headless launchers for Eclipse (incubation)
2.0eing installed: SWTBot JUnit 4.x Headless launchers for Eclipse (incubation)
2.0.5.20111003_1754-3676ac8-dev-e36 (org.eclipse.sw.5.20111003_1754-3676ac8-dev-e36
(org.eclipse.swtbot.eclipse.test.junit4.feature.group 2.0.5.20111003_1754-3676ac8-dev-e36)
requtbot.eclipse.test.junit4.feature.group 2.0.5.20111003_1754-3676ac8-dev-e36)
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2013-03-23 02:15:09.054
!MESSAGE Missing requirement: SWTBot JUnit 4.x Headless launchers for Eclipse
(incubation) 2.0.5.20111003_1754-3676ac8-dev-e36
(org.eclipse.swtbot.eclipse.test.junit4.feature.group 2.0.5.20111003_1754-3676ac8-dev-e36)
requires 'org.junit4 0.0.0' but it could not be found
ires 'org.junit4 0.0.0' but it could not be found
{code}
However, since the Juno tests still depend on SWTBot 2.0.5 and Juno (in which org.junit4
CAN be found) we need to create a jbosstools-4.0.x branch and configure all the 4.0.x jobs
that depend on install-grinder so that they will use this new org.junit4_4.8 / SWTBot
2.0.5 compatible branch, while master moves ahead with SWTBot 2.1 and org.junit_4.11.
--
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: