March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2486) Investigate use of GWT/GPE 3.2.0.v201302131858-rel-r42 in Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2486?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2486 at 3/23/13 9:57 AM: ----------------------------------------------------------- [~maxandersen] see Burr's comments: https://issues.jboss.org/browse/JBDS-2486?focusedCommentId=12761049&page=... Also, I thought the workflow we used was "dev resolves, QE verifies". Why do you keep reopening when you could simply wait for QE to verify? was (Author: nickboldt): [~maxandersen] see Burr's comments: https://issues.jboss.org/browse/JBDS-2486?focusedCommentId=12761049&page=... > Investigate use of GWT/GPE 3.2.0.v201302131858-rel-r42 in Central > ----------------------------------------------------------------- > > Key: JBDS-2486 > URL: https://issues.jboss.org/browse/JBDS-2486 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, central > Affects Versions: 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 7.0.0.Alpha2 > > > New 3.2.0 mirrors: > http://download.jboss.org/jbosstools/updates/requirements/gwt/3.2.0.v2013... > https://devstudio.jboss.com/updates/requirements/gwt/3.2.0.v201302131858-... > New composites: > http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.1/ > https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.1/ > Note that at least one IU had been renamed: > OLD: com.google.gwt.eclipse.sdkbundle.e42.feature > NEW: com.google.gwt.eclipse.sdkbundle.feature -- 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-13846) Target Platform does not include the source bundles

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13846?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-13846. ------------------------------ Closing. [~gercan] please use this site: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... (Kepler M6) > Target Platform does not include the source bundles > --------------------------------------------------- > > Key: JBIDE-13846 > URL: https://issues.jboss.org/browse/JBIDE-13846 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha2 > > > Just tried with http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... p2 site. When I use it as my target with PDE none of the source bundles are available. Also browsed the p2 site, I do not see any of the source bundles. I think target platforms should also include the source bundles to be used as PDE targets during development. -- 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 Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13845?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-13845: ----------------------------------- I simply updated the install-grinder job to use the latest version of SWTBot and stop depend on org.junit4. Those changes are totally backward compatible, org.junit 4.x bundles were introduced with Galileo IIRC (http://wiki.eclipse.org/Eclipse/Testing/JUnit4_Changes ). So no need for a specific branch, just need to update jobs to use the latest version of install-grinder. > 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-13846) Target Platform does not include the source bundles

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13846?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-13846: ----------------------------------- Yes, I did forget ;) https://github.com/jbosstools/jbosstools-target-platforms/wiki > Target Platform does not include the source bundles > --------------------------------------------------- > > Key: JBIDE-13846 > URL: https://issues.jboss.org/browse/JBIDE-13846 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha2 > > > Just tried with http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... p2 site. When I use it as my target with PDE none of the source bundles are available. Also browsed the p2 site, I do not see any of the source bundles. I think target platforms should also include the source bundles to be used as PDE targets during development. -- 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-13846) Target Platform does not include the source bundles

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13846?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-13846: -------------------------------------- Did you forget to add the link to the documentation ? > Target Platform does not include the source bundles > --------------------------------------------------- > > Key: JBIDE-13846 > URL: https://issues.jboss.org/browse/JBIDE-13846 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha2 > > > Just tried with http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... p2 site. When I use it as my target with PDE none of the source bundles are available. Also browsed the p2 site, I do not see any of the source bundles. I think target platforms should also include the source bundles to be used as PDE targets during development. -- 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-13846) Target Platform does not include the source bundles

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13846?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-13846. ------------------------------------ Resolution: Rejected This site is dedicated to production and not development, that's why it doesn't include sources. In order to get access to sources in your TP, you should start by using the multiple target platform, which references to individual repositories containing sources. Some documentation is available here. Feel free to suggest improvements based on your experience. > Target Platform does not include the source bundles > --------------------------------------------------- > > Key: JBIDE-13846 > URL: https://issues.jboss.org/browse/JBIDE-13846 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha2 > > > Just tried with http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... p2 site. When I use it as my target with PDE none of the source bundles are available. Also browsed the p2 site, I do not see any of the source bundles. I think target platforms should also include the source bundles to be used as PDE targets during development. -- 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-13846) Target Platform does not include the source bundles

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13846?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-13846: ----------------------------------- Fix Version/s: 4.1.0.Alpha2 Assignee: Mickael Istria (was: Nick Boldt) > Target Platform does not include the source bundles > --------------------------------------------------- > > Key: JBIDE-13846 > URL: https://issues.jboss.org/browse/JBIDE-13846 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha2 > > > Just tried with http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... p2 site. When I use it as my target with PDE none of the source bundles are available. Also browsed the p2 site, I do not see any of the source bundles. I think target platforms should also include the source bundles to be used as PDE targets during development. -- 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-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13599: --------------------------------------------- [~nickboldt] see the PR for current discussions. > externalize Central site URL into a commandline property so that testing or mirroring is easier > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-13599 > URL: https://issues.jboss.org/browse/JBIDE-13599 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha2 > > Attachments: JBDS7alpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png, JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt, JBTalpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png > > > As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE. > A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value. > This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE. -- 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-13846) Target Platform does not include the source bundles

by Gorkem Ercan (JIRA)

Gorkem Ercan created JBIDE-13846: ------------------------------------ Summary: Target Platform does not include the source bundles Key: JBIDE-13846 URL: https://issues.jboss.org/browse/JBIDE-13846 Project: Tools (JBoss Tools) Issue Type: Bug Components: target-platform Reporter: Gorkem Ercan Assignee: Nick Boldt Just tried with http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... p2 site. When I use it as my target with PDE none of the source bundles are available. Also browsed the p2 site, I do not see any of the source bundles. I think target platforms should also include the source bundles to be used as PDE targets during development. -- 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-2486) Investigate use of GWT/GPE 3.2.0.v201302131858-rel-r42 in Central

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2486?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen reopened JBDS-2486: --------------------------------------- reopen for clarification. I don't see any mention in here verifying that the GWT facet feature we got has been verified to work ? > Investigate use of GWT/GPE 3.2.0.v201302131858-rel-r42 in Central > ----------------------------------------------------------------- > > Key: JBDS-2486 > URL: https://issues.jboss.org/browse/JBDS-2486 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, central > Affects Versions: 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 7.0.0.Alpha2 > > > New 3.2.0 mirrors: > http://download.jboss.org/jbosstools/updates/requirements/gwt/3.2.0.v2013... > https://devstudio.jboss.com/updates/requirements/gwt/3.2.0.v201302131858-... > New composites: > http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.1/ > https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.1/ > Note that at least one IU had been renamed: > OLD: com.google.gwt.eclipse.sdkbundle.e42.feature > NEW: com.google.gwt.eclipse.sdkbundle.feature -- 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