September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15008) Need to change all example descriptors suffixes to Beta2, as we're gonna break them in CR1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15008?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15008: ------------------------------------ [~fbricon] [~rhopp] [~maxandersen] https://github.com/jbdevstudio/jbdevstudio-product/pull/16 was never applied. Does it still need to be? > Need to change all example descriptors suffixes to Beta2, as we're gonna break them in CR1 > ------------------------------------------------------------------------------------------ > > Key: JBIDE-15008 > URL: https://issues.jboss.org/browse/JBIDE-15008 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.1.0.Beta1 > Reporter: Fred Bricon > Assignee: Max Rydahl Andersen > Labels: respin-b > Fix For: 4.1.0.Beta2 > > > We need to change all example descriptors to Beta2 (currently using GA suffixes), as Rob and I are gonna break them for CR1 -- 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, 8 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 updated JBIDE-15467: ------------------------------- Attachment: 15467_new.png OK, I've replaced the single-feature "Other Tools" category with the new "Additional JBoss Tools" category, which now includes 9 features. The "Abridged JBoss Tools" contains the other 37 features. And as you can see, aerogear.hybrid, vpe.cordovasim, and vpe.browsersim are also (still) listed in the Mobile category: !15467_new.png! > 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 > > Attachments: 15467.png, 15467_new.png > > > 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.aerogear.hybrid.feature > org.jboss.tools.arquillian.feature > org.jboss.tools.birt.feature > org.jboss.tools.central.themes.feature > org.jboss.tools.forge.ext.feature > org.jboss.tools.gwt.feature > org.jboss.tools.vpe.cordovasim.feature > org.jboss.tools.maven.gwt.feature > org.jboss.tools.common.mylyn.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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2734) Forge 2 in JBDS

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/JBDS-2734?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on JBDS-2734: ------------------------------------------ https://bugs.eclipse.org/bugs/show_bug.cgi?id=417524 > Forge 2 in JBDS > --------------- > > Key: JBDS-2734 > URL: https://issues.jboss.org/browse/JBDS-2734 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: forge, requirements > Reporter: Burr Sutter > > Is Forge 2 ready to be included in JBDS ? -- 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, 8 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 updated JBIDE-15467: ------------------------------- Description: 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.aerogear.hybrid.feature org.jboss.tools.arquillian.feature org.jboss.tools.birt.feature org.jboss.tools.central.themes.feature org.jboss.tools.forge.ext.feature org.jboss.tools.gwt.feature org.jboss.tools.vpe.cordovasim.feature org.jboss.tools.maven.gwt.feature org.jboss.tools.common.mylyn.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? was: 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? > 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 > > Attachments: 15467.png > > > 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.aerogear.hybrid.feature > org.jboss.tools.arquillian.feature > org.jboss.tools.birt.feature > org.jboss.tools.central.themes.feature > org.jboss.tools.forge.ext.feature > org.jboss.tools.gwt.feature > org.jboss.tools.vpe.cordovasim.feature > org.jboss.tools.maven.gwt.feature > org.jboss.tools.common.mylyn.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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15498) should JBDS 7.1 include org.jboss.tools.wtp.runtimes.tomcat.feature ?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15498?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15498: ------------------------------- Attachment: 15498.png > should JBDS 7.1 include org.jboss.tools.wtp.runtimes.tomcat.feature ? > --------------------------------------------------------------------- > > Key: JBIDE-15498 > URL: https://issues.jboss.org/browse/JBIDE-15498 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.1.1.Alpha1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Attachments: 15498.png > > > Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7. > Was it intentionally excluded from the update site, or forgotten? -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15498) should JBDS 7.1 include org.jboss.tools.wtp.runtimes.tomcat.feature ?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15498?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15498: ------------------------------- Description: Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7. Comparing the update sites for JBT 4.1.x and JBDS 7.1.x: !15498.png! Was it intentionally excluded from the update site, or forgotten? was: Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7. Was it intentionally excluded from the update site, or forgotten? > should JBDS 7.1 include org.jboss.tools.wtp.runtimes.tomcat.feature ? > --------------------------------------------------------------------- > > Key: JBIDE-15498 > URL: https://issues.jboss.org/browse/JBIDE-15498 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.1.1.Alpha1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Attachments: 15498.png > > > Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7. > Comparing the update sites for JBT 4.1.x and JBDS 7.1.x: > !15498.png! > Was it intentionally excluded from the update site, or forgotten? -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15498) should JBDS 7.1 include org.jboss.tools.wtp.runtimes.tomcat.feature ?

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-15498: ---------------------------------- Summary: should JBDS 7.1 include org.jboss.tools.wtp.runtimes.tomcat.feature ? Key: JBIDE-15498 URL: https://issues.jboss.org/browse/JBIDE-15498 Project: Tools (JBoss Tools) Issue Type: Bug Components: updatesite Affects Versions: 4.1.1.Alpha1 Reporter: Nick Boldt Assignee: Rob Stryker Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7. Was it intentionally excluded from the update site, or forgotten? -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2686) Investigate use of SpringSource's Quick Search in JBT/JBDS Central

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-2686?page=com.atlassian.jira.plugin.... ] Burr Sutter updated JBDS-2686: ------------------------------ CDW pm_ack: + (was: ?) Status: New (was: New) > Investigate use of SpringSource's Quick Search in JBT/JBDS Central > ------------------------------------------------------------------ > > Key: JBDS-2686 > URL: https://issues.jboss.org/browse/JBDS-2686 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central, discovery, requirements, updatesite > Reporter: Nick Boldt > Assignee: Len DiMaggio > Fix For: 7.1.x, 8.0.x > > > @fbricon wrote: > {quote} > This looks very interesting > http://blog.springsource.org/2013/07/11/eclipse-quick-search/ > And it -apparently- doesn't depend on other spring stuff, so I > think it's a good candidate for integration in JBT/JBDS. > {quote} > Update site: > http://dist.springsource.com/release/TOOLS/eclipse-integration-commons/ -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2686) Investigate use of SpringSource's Quick Search in JBT/JBDS Central

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2686?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2686: ----------------------------- CDW devel_ack: ? > Investigate use of SpringSource's Quick Search in JBT/JBDS Central > ------------------------------------------------------------------ > > Key: JBDS-2686 > URL: https://issues.jboss.org/browse/JBDS-2686 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central, discovery, requirements, updatesite > Reporter: Nick Boldt > Assignee: Len DiMaggio > Fix For: 7.1.x, 8.0.x > > > @fbricon wrote: > {quote} > This looks very interesting > http://blog.springsource.org/2013/07/11/eclipse-quick-search/ > And it -apparently- doesn't depend on other spring stuff, so I > think it's a good candidate for integration in JBT/JBDS. > {quote} > Update site: > http://dist.springsource.com/release/TOOLS/eclipse-integration-commons/ -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15457) CordovaSim and Hybrid tools interaction/source code sharing

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15457?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-15457: -------------------------------------- CordovaSim is really valuable when it is integrated with the project(s) in Eclipse. Otherwise developers would probably use Ripple as their standalone tool. I do not see many developers choosing our solution over Ripple. > CordovaSim and Hybrid tools interaction/source code sharing > ----------------------------------------------------------- > > Key: JBIDE-15457 > URL: https://issues.jboss.org/browse/JBIDE-15457 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: aerogear-hybrid, browsersim > Reporter: Yahor Radtsevich > Assignee: Yahor Radtsevich > Fix For: 4.2.x > > > Currently CordovaSim application consists of two parts: a Jetty-based server, and a BrowserSim-based client. The server part generates some content on the fly. For instance, the server may response with generated {{cordova_plugins.js}} content when it is requested by the client. Both parts of CordovaSim are executed in their own JVM, which means they do not have access to the Eclipse API. > Hybrid tools do very similar things, but in static way. For instance, while creating Android executables, they create {{cordova_plugins.js}} file on disk. Hybrid tools is a set of Eclipse plugins, so they have access to the Eclipse API. > Obviously CordovaSim and Hybrid tools have some code in their sources that could be shared. For the example above, both of them need a method to generate content of {{cordova_plugins.js}}. There are several approaches to implement it: > 1. Create two different implementations for CordovaSim and Hybrid tools and synchronize them when needed (currently we do this). This approach creates code duplication problems. > 2. Create an Eclipse API-independent plugin, so both CordovaSim and Hybrid tools could set it as a dependency. This approach imposes some restriction on the independent plugin (useful Eclipse API and libs cannot be used). > 3. Move the server part of CordovaSim to the Eclipse JVM, so it could use Eclipse API and any Hybrid tools API. With this approach we loose the ability to create standalone CordovaSim in the future. -- 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, 8 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