March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13799) Source Lookup enhancements

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13799?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13799: --------------------------------------------- Yes, I still think it is best to do these in seperate steps so they can be applied with proper tests and the bugfixes gets done without waiting for feature to be polished. Plus once you got them separated out we can follow up with design and implementation concerns on those specific PR/features instead of having a hard to follow jira with many crosscutting concerns. Ok ? > Source Lookup enhancements > -------------------------- > > Key: JBIDE-13799 > URL: https://issues.jboss.org/browse/JBIDE-13799 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 4.1.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > > The PR includes the following enhancements: > - AS 7.2/EAP 6.1 are now recognized correctly > - the fix for the issue caused by changing the editor ID for ClassFileEdtor in 3.8/4.2 > - the fix for the ConcurrentModificationException exception > - included libraries can be filtered - jsf 1.2 and hibernate 3 will be excluded by default for JBoss AS Container > - JBoss Runtimes now can be included in the Java Search (this feature has been implemented in a similar way to adding PDE plugins to the Java Search) > - JBoss Java Project Source Container > See http://screencast.com/t/39LHqYx5m > Screenshot shows debugging the WeldBootstrap class in JBoss AS 7.1 and JBoss AS 7.2. > Note: > You have to have some deployment on the servers in order the WeldBootstrap class to be created. > You can add more JBoss servers to the Java Search, but it is the best to use only one at a time because of the performance reason. > The "Automatically add the JBoss Maven source container to all JBoss AS launch configurations" and "Include the following JBoss Servers in the Java Search" checkboxes aren't related. The first checkbox adds the source container that enables finding a Java source file when debugging, the second enables finding a Java source file using the Java Search (using the "Open type" command, for instance). -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2498) Creating a new SOA runtime does not automatically create a Drools runtime

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2498?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2498: -------------------------------------- Issue Type: Feature Request (was: Bug) > Creating a new SOA runtime does not automatically create a Drools runtime > ------------------------------------------------------------------------- > > Key: JBDS-2498 > URL: https://issues.jboss.org/browse/JBDS-2498 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: drools, SOA Tooling / Platform > Affects Versions: 5.0.2.GA > Environment: Version: 5.0.2.GA > Build id: v20130119-0035-H249-GA > Build date: 20130119-0035 > Reporter: Len DiMaggio > Assignee: Kris Verlaenen > Fix For: 5.0.4.GA-SOA, 6.0.0.Alpha1-SOA > > > Related to: https://issues.jboss.org/browse/JBDS-2473 > The same problem exists for Drools - creating an SOA runtime does not automatically create a Drools runtime -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2473) Creating a new SOA runtime does not automatically create an ESB runtime

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2473?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2473: -------------------------------------- Issue Type: Feature Request (was: Bug) > Creating a new SOA runtime does not automatically create an ESB runtime > ----------------------------------------------------------------------- > > Key: JBDS-2473 > URL: https://issues.jboss.org/browse/JBDS-2473 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: SOA Tooling / Platform > Affects Versions: 5.0.2.GA > Environment: Version: 5.0.2.GA > Build id: v20130119-0035-H249-GA > Build date: 20130119-0035 > http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.3.GA.soa-to... > Reporter: Len DiMaggio > Assignee: Brian Fitzpatrick > Fix For: 5.0.4.GA-SOA, 6.0.0.Alpha1-SOA > > Attachments: Screenshot-2.png, Screenshot.png > > > See the attached screenshot - the user must create the ESB runtime manually. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2472) Creating a new SOA runtime does not automatically create a jBPM runtime

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2472?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2472: -------------------------------------- Issue Type: Feature Request (was: Bug) this is not a bug, the server creation does not know about runtime detection which is the one that normally does this "wiring". I agree it would make perfect sense to have "subruntimes" detected/configured but that is currently not how it works. > Creating a new SOA runtime does not automatically create a jBPM runtime > ----------------------------------------------------------------------- > > Key: JBDS-2472 > URL: https://issues.jboss.org/browse/JBDS-2472 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jBPM, SOA Tooling / Platform > Affects Versions: 5.0.2.GA-SOA > Environment: Version: 5.0.2.GA > Build id: v20130119-0035-H249-GA > Build date: 20130119-0035 > http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.3.GA.soa-to... > Reporter: Len DiMaggio > Assignee: Koen Aers > Fix For: 5.0.4.GA-SOA, 6.0.0.Alpha1-SOA > > Attachments: Screenshot-1.png, Screenshot.png > > > See attached screenshots - the user must manually create a jBPM runtime. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2473) Creating a new SOA runtime does not automatically create an ESB runtime

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2473?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2473: ------------------------------------------- server creation never ran runtime detection - its always been like this. > Creating a new SOA runtime does not automatically create an ESB runtime > ----------------------------------------------------------------------- > > Key: JBDS-2473 > URL: https://issues.jboss.org/browse/JBDS-2473 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: SOA Tooling / Platform > Affects Versions: 5.0.2.GA > Environment: Version: 5.0.2.GA > Build id: v20130119-0035-H249-GA > Build date: 20130119-0035 > http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.3.GA.soa-to... > Reporter: Len DiMaggio > Assignee: Brian Fitzpatrick > Fix For: 5.0.4.GA-SOA, 6.0.0.Alpha1-SOA > > Attachments: Screenshot-2.png, Screenshot.png > > > See the attached screenshot - the user must create the ESB runtime manually. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-29) Migrate runtime detection plugins for SOA Tooling to their respective projects

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-29?page=com.atlassian.jira.plugin.s... ] Max Rydahl Andersen commented on JBTIS-29: ------------------------------------------ note: I can apply the https://github.com/jbosstools/jbosstools-runtime-soa/pull/11 but would like to first do so when we got verification I won't break JBTIS build by doing so and prefereably also got verification that the runtime detection actually still exist after this. [~nickboldt] did you or someone in QE verify they work after this cleanup ? > Migrate runtime detection plugins for SOA Tooling to their respective projects > ------------------------------------------------------------------------------ > > Key: JBTIS-29 > URL: https://issues.jboss.org/browse/JBTIS-29 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution, drools/ jBPM5, ESB, jBPM3, releng, runtime-soa > Affects Versions: 4.0.0 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.0.0 > > > You'll no doubt want a new feature wrapper for each of these plugins, as they'll need to be installable from their respective projects' sites: > * org.jboss.tools.runtime.drools.detector > * org.jboss.tools.runtime.esb.detector > * org.jboss.tools.runtime.jbpm.detector -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13845) 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)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13845?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13845 at 3/23/13 2:33 AM: ------------------------------------------------------------- *1. Change to pull from 4.0.x branch of install-grinder after branching (to keep using org.junit4):* * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... *2. Clone jbosstools-install-grinder_master to new job, add to DevStudio_6.0.juno view:* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... *3. Broken, needs to use org.junit (after branching off 4.0.x):* * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... was (Author: nickboldt): *1. Change to pull from 4.0.x branch of install-grinder after branching (to keep using org.junit4):* * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... *2. *Clone jbosstools-install-grinder_master to new job, add to DevStudio_6.0.juno view:* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... *3. Broken, needs to use org.junit (after branching off 4.0.x):* * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > 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: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13845) 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)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13845?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13845 at 3/23/13 2:33 AM: ------------------------------------------------------------- *1. Change to pull from 4.0.x branch of install-grinder after branching (to keep using org.junit4):* * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... *2. Clone jbosstools-install-grinder_master to new job, add to DevStudio_6.0.juno view:* * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... *3. Broken, needs to use org.junit (after branching off 4.0.x):* * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... was (Author: nickboldt): *1. Change to pull from 4.0.x branch of install-grinder after branching (to keep using org.junit4):* * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... *2. Clone jbosstools-install-grinder_master to new job, add to DevStudio_6.0.juno view:* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... *3. Broken, needs to use org.junit (after branching off 4.0.x):* * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > 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: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13845) 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)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13845?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13845 at 3/23/13 2:32 AM: ------------------------------------------------------------- *1. Change to pull from 4.0.x branch of install-grinder after branching (to keep using org.junit4):* * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... *2. *Clone jbosstools-install-grinder_master to new job, add to DevStudio_6.0.juno view:* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... *3. Broken, needs to use org.junit (after branching off 4.0.x):* * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... was (Author: nickboldt): Broken, needs to use org.junit: * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... *NEW JOB REQUIRED (clone from jbosstools-install-grinder_master and add to view):* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... Will need to be changed to pull from 4.0.x branch of install-grinder after branching (to keep using org.junit4): * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > 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: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13845) 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)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13845?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13845 at 3/23/13 2:31 AM: ------------------------------------------------------------- Broken, needs to use org.junit: * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... *NEW JOB REQUIRED (clone from jbosstools-install-grinder_master and add to view):* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... Will need to be changed to pull from 4.0.x branch of install-grinder after branching (to keep using org.junit4): * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... was (Author: nickboldt): Broken, needs to use org.junit: * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... 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*: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > 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: http://www.atlassian.com/software/jira

13 years

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 March 2013