September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15451) For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Webservices]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15451?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15451: ------------------------------------ Have reconfigured the webservices_41 job [1] to run from my fork against the branch which includes PR 81, so that we can include 1.5.1.Alpha1 bits instead of 1.5.1.Final bits. [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Webservices] > ---------------------------------------------------------- > > Key: JBIDE-15451 > URL: https://issues.jboss.org/browse/JBIDE-15451 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.1.1.Alpha1 > > > For JBIDE 4.1.1.Alpha1: Please perform the following tasks: > 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. > Otherwise: > 1. Update your root pom to use parent pom version 4.1.1.Alpha1-SNAPSHOT; > 2. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha1; > 3. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha1x branch; > 4. Close (not resolve) this JIRA when done. [Webservices] > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15312) Update all AS versions AND manifest.mf dependency version ranges

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15312?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-15312. ------------------------------ No worries. http://download.jboss.org/jbosstools/updates/nightly/core/4.1.kepler/ now contains org.jboss.ide.eclipse.archives.feature version 3.4.101.Alpha1-v20130908-1628-B113. So, closing. Thanks for working on the weekend! > Update all AS versions AND manifest.mf dependency version ranges > ----------------------------------------------------------------- > > Key: JBIDE-15312 > URL: https://issues.jboss.org/browse/JBIDE-15312 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.1.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > API has been added in both branch and master. THis requires an update of version ranges. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14407) Manage different Cordova versions

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14407?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-14407: --------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Description: Ability to target different supported cordova versions... Tools at least should offer the ability to migrate to the latest supported Cordova version. Also all the cordova templates and files should be able to update independent of the rest of the plugins. This requires a UI for switching targeted cordova runtimes. .cordova/config.json can be populated with the engine information. Phonegap uses the following format. {"lib":{"www":{"id":"phonegap","version":"3.0.0","uri":"https://github.com/phonegap/phonegap-app-hello-world/archive/3.0.0.tar.gz"}},"id":"AAA","name":"HelloWorld"} was: Ability to target different supported cordova versions... Tools at least should offer the ability to migrate to the latest supported Cordova version. Also all the cordova templates and files should be able to update independent of the rest of the plugins. > Manage different Cordova versions > --------------------------------- > > Key: JBIDE-14407 > URL: https://issues.jboss.org/browse/JBIDE-14407 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: LATER > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Ability to target different supported cordova versions... Tools at least should offer the ability to migrate to the latest supported Cordova version. > Also all the cordova templates and files should be able to update independent of the rest of the plugins. > This requires a UI for switching targeted cordova runtimes. > .cordova/config.json can be populated with the engine information. Phonegap uses the following format. > {"lib":{"www":{"id":"phonegap","version":"3.0.0","uri":"https://github.com/phonegap/phonegap-app-hello-world/archive/3.0.0.tar.gz"}},"id":"AAA","name":"HelloWorld"} -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15412) Arquillian New and Noteworthy for 4.1.1.Alpha1

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15412?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-15412: ------------------------------------- Assignee: Max Rydahl Andersen (was: Snjezana Peco) > Arquillian New and Noteworthy for 4.1.1.Alpha1 > ---------------------------------------------- > > Key: JBIDE-15412 > URL: https://issues.jboss.org/browse/JBIDE-15412 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.1.1.Alpha1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Arquillian is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Arquillian by adding to [whatsnew|https://github.com/jbosstools/jbosstools-documentation/tree/mast...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15468) Ensure versioning errors (eg., maintenance branch at 3.5.1 while master at 3.5.0) are correctly shown in vwatch results table

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15468?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15468: ------------------------------- Attachment: jbide15432_missing_table_cell_tooltip_shows_actual_blocker_problem.png > Ensure versioning errors (eg., maintenance branch at 3.5.1 while master at 3.5.0) are correctly shown in vwatch results table > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15468 > URL: https://issues.jboss.org/browse/JBIDE-15468 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Affects Versions: 4.1.1.Alpha1 > Reporter: Nick Boldt > Fix For: 4.1.1.Alpha1 > > Attachments: jbide15432_missing_table_cell_tooltip_shows_actual_blocker_problem.png > > > This screenshot taken from http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... shows that in some cases the table cell is blank when there's a real problem that should be reported. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15468) Ensure versioning errors (eg., maintenance branch at 3.5.1 while master at 3.5.0) are correctly shown in vwatch results table

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15468?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15468: ------------------------------- Description: This screenshot taken from http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... shows that in some cases the table cell is blank when there's a real problem that should be reported. !jbide15432_missing_table_cell_tooltip_shows_actual_blocker_problem.png! was:This screenshot taken from http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... shows that in some cases the table cell is blank when there's a real problem that should be reported. > Ensure versioning errors (eg., maintenance branch at 3.5.1 while master at 3.5.0) are correctly shown in vwatch results table > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15468 > URL: https://issues.jboss.org/browse/JBIDE-15468 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Affects Versions: 4.1.1.Alpha1 > Reporter: Nick Boldt > Fix For: 4.1.1.Alpha1 > > Attachments: jbide15432_missing_table_cell_tooltip_shows_actual_blocker_problem.png > > > This screenshot taken from http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... shows that in some cases the table cell is blank when there's a real problem that should be reported. > !jbide15432_missing_table_cell_tooltip_shows_actual_blocker_problem.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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15468) Ensure versioning errors (eg., maintenance branch at 3.5.1 while master at 3.5.0) are correctly shown in vwatch results table

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15468?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15468: ------------------------------- Description: This screenshot taken from http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... shows that in some cases the table cell is blank when there's a real problem that should be reported, and that the reported problem in the tool tip doesn't match the information shown. !jbide15432_missing_table_cell_tooltip_shows_actual_blocker_problem.png! was: This screenshot taken from http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... shows that in some cases the table cell is blank when there's a real problem that should be reported. !jbide15432_missing_table_cell_tooltip_shows_actual_blocker_problem.png! > Ensure versioning errors (eg., maintenance branch at 3.5.1 while master at 3.5.0) are correctly shown in vwatch results table > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15468 > URL: https://issues.jboss.org/browse/JBIDE-15468 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Affects Versions: 4.1.1.Alpha1 > Reporter: Nick Boldt > Fix For: 4.1.1.Alpha1 > > Attachments: jbide15432_missing_table_cell_tooltip_shows_actual_blocker_problem.png > > > This screenshot taken from http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... shows that in some cases the table cell is blank when there's a real problem that should be reported, and that the reported problem in the tool tip doesn't match the information shown. > !jbide15432_missing_table_cell_tooltip_shows_actual_blocker_problem.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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15468) Ensure versioning errors (eg., maintenance branch at 3.5.1 while master at 3.5.0) are correctly shown in vwatch results table

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15468?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15468: ------------------------------- Priority: Blocker (was: Major) > Ensure versioning errors (eg., maintenance branch at 3.5.1 while master at 3.5.0) are correctly shown in vwatch results table > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15468 > URL: https://issues.jboss.org/browse/JBIDE-15468 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Affects Versions: 4.1.1.Alpha1 > Reporter: Nick Boldt > Priority: Blocker > Fix For: 4.1.1.Alpha1 > > Attachments: jbide15432_missing_table_cell_tooltip_shows_actual_blocker_problem.png > > > This screenshot taken from http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... shows that in some cases the table cell is blank when there's a real problem that should be reported, and that the reported problem in the tool tip doesn't match the information shown. > !jbide15432_missing_table_cell_tooltip_shows_actual_blocker_problem.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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15468) Ensure versioning errors (eg., maintenance branch at 3.5.1 while master at 3.5.0) are correctly shown in vwatch results table

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-15468: ---------------------------------- Summary: Ensure versioning errors (eg., maintenance branch at 3.5.1 while master at 3.5.0) are correctly shown in vwatch results table Key: JBIDE-15468 URL: https://issues.jboss.org/browse/JBIDE-15468 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: build, qa Affects Versions: 4.1.1.Alpha1 Reporter: Nick Boldt This screenshot taken from http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... shows that in some cases the table cell is blank when there's a real problem that should be reported. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15467) should JBT have a category for "stuff not in Abridged" ?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15467?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15467: ------------------------------------ They can be in more than one category. Are they not already in a Mobile-related category? > should JBT have a category for "stuff not in Abridged" ? > -------------------------------------------------------- > > Key: JBIDE-15467 > URL: https://issues.jboss.org/browse/JBIDE-15467 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.1.1.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.1.Alpha2 > > > The Marketplace entry for JBT includes all the features in the "Abridged JBoss Tools" category, but there are a number of features not included therein. > So for those users installing from the update site itself, not the Marketplace, should these be grouped into a single category, perhaps called "Additional JBoss Tools"? > {code} > org.jboss.tools.arquillian.feature > org.jboss.tools.common.mylyn.feature > org.jboss.tools.gwt.feature > org.jboss.tools.maven.gwt.feature > org.jboss.tools.aerogear.hybrid.feature > org.jboss.tools.vpe.cordovasim.feature > org.jboss.tools.central.themes.feature > org.jboss.tools.birt.feature > org.jboss.tools.forge.ext.feature > {code} > Added bonus (from a releng P.O.V., not an end user one) is that having such a category would make it easier to maintain the full list of features to be included in these job configs, to ensure we're properly doing full JBT co-installation testing: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... > [~burrsutter] [~maxandersen] [~koen.aers] [~gercan] WDYT? -- 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, 7 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 September 2013