February 2013 - jbosstools-issues

[JBoss JIRA] (JBDS-2484) 3rd party certification for JBDS 7.x

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2484?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2484: ----------------------------- Description: The current list of Extras/Central connectors that we mirror are: {code} atlassian/3.0.6.v20120628 eclipsecs/5.6.0.201209221626 findbugs/2.0.2.20121210 gwt/3.1.0.v201208080121-rel-r42 pmd/3.2.6 springide/2.7.2.201109122348 subclipse/1.8.16_1.7.5.v1 testng/6.7.0.20120825_1316 {code} As per: http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.0/composi... https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.0/compositeAr... For JBDS 7, we need to bump these to newer versions. was: We should define what kind of certifications we want and then certify 3rd party plugins with JBDS Certifiaction could for example be for Groovy Plugin we know it installs, but beyond that there aren't any guarantees. For m2eclipse it would be the same with respect to installation but that we support the maven integration plugins and provide fixes for that - but not m2eclipse it self. Specific versions for JBDS 5 are listed here and in JBDS-1594: {code} jslint/1.5 m2eclipse/0.13.0.201103291237 (or later) springide/2.6.0.201103160035 testng/6.0.1.20110418_1444 {code} as well as everything listed in JBDS-1235 and JBDS-1593 > 3rd party certification for JBDS 7.x > ------------------------------------ > > Key: JBDS-2484 > URL: https://issues.jboss.org/browse/JBDS-2484 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements > Affects Versions: 5.0.0.M2 > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 5.0.0.CR1 > > > The current list of Extras/Central connectors that we mirror are: > {code} > atlassian/3.0.6.v20120628 > eclipsecs/5.6.0.201209221626 > findbugs/2.0.2.20121210 > gwt/3.1.0.v201208080121-rel-r42 > pmd/3.2.6 > springide/2.7.2.201109122348 > subclipse/1.8.16_1.7.5.v1 > testng/6.7.0.20120825_1316 > {code} > As per: > http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.0/composi... > https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.0/compositeAr... > For JBDS 7, we need to bump these to newer versions. -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2484) 3rd party certification for JBDS 7.x (JBDS70_1211)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2484?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2484: ----------------------------- Summary: 3rd party certification for JBDS 7.x (JBDS70_1211) (was: 3rd party certification for JBDS 7.x) > 3rd party certification for JBDS 7.x (JBDS70_1211) > -------------------------------------------------- > > Key: JBDS-2484 > URL: https://issues.jboss.org/browse/JBDS-2484 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements > Affects Versions: 5.0.0.M2 > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 5.0.0.CR1 > > > The current list of Extras/Central connectors that we mirror are: > {code} > atlassian/3.0.6.v20120628 > eclipsecs/5.6.0.201209221626 > findbugs/2.0.2.20121210 > gwt/3.1.0.v201208080121-rel-r42 > pmd/3.2.6 > springide/2.7.2.201109122348 > subclipse/1.8.16_1.7.5.v1 > testng/6.7.0.20120825_1316 > {code} > As per: > http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.0/composi... > https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.0/compositeAr... > For JBDS 7, we need to bump these to newer versions. -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2484) 3rd party certification for JBDS 7.x

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2484: -------------------------------- Summary: 3rd party certification for JBDS 7.x Key: JBDS-2484 URL: https://issues.jboss.org/browse/JBDS-2484 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements Affects Versions: 5.0.0.M2 Reporter: Max Rydahl Andersen Assignee: Len DiMaggio Priority: Blocker Fix For: 5.0.0.CR1 We should define what kind of certifications we want and then certify 3rd party plugins with JBDS Certifiaction could for example be for Groovy Plugin we know it installs, but beyond that there aren't any guarantees. For m2eclipse it would be the same with respect to installation but that we support the maven integration plugins and provide fixes for that - but not m2eclipse it self. Specific versions for JBDS 5 are listed here and in JBDS-1594: {code} jslint/1.5 m2eclipse/0.13.0.201103291237 (or later) springide/2.6.0.201103160035 testng/6.0.1.20110418_1444 {code} as well as everything listed in JBDS-1235 and JBDS-1593 -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13691) The feature 'org.jboss.tools.forge.ext.feature' should be included on the JBT update site (not JBDS)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13691?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-13691: ---------------------------------- Assignee: Koen Aers (was: Nick Boldt) Yes, can you give me a PR for these files? https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... > The feature 'org.jboss.tools.forge.ext.feature' should be included on the JBT update site (not JBDS) > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-13691 > URL: https://issues.jboss.org/browse/JBIDE-13691 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.1.0.Alpha2 > > -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-8530) Message Driven Bean (EJB3.x) wizard generates incorrect annotattions

by Libor Zoubek (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8530?page=com.atlassian.jira.plugin... ] Libor Zoubek commented on JBIDE-8530: ------------------------------------- Hi, it works for me correctly. I tried to deploy such MDB to EAP 6.0.1 bundled within JBoss Developer Studio 7.0.0.Alpha1 without any issues > Message Driven Bean (EJB3.x) wizard generates incorrect annotattions > -------------------------------------------------------------------- > > Key: JBIDE-8530 > URL: https://issues.jboss.org/browse/JBIDE-8530 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: ejb3 > Affects Versions: 3.2.0.Final > Reporter: Libor Zoubek > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.0.2.Final > > -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13687) Project wizard from central: requirements should be recommendations

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13687?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-13687: --------------------------------------- The Requirements section is related to runtimes and plugins. Plugins are always required. The maven projects (archetypes, quickstarts) don't require any runtime when they are being created or built, but require a runtime when they run. Non-maven projects require both of them : runtimes and plugins when building and running. I propose the following: - change the Requirements section to "Requirements and Recommendations". - add the "recommended" property to the project xml file. It would be added when a fix isn't required (as to the maven project examples, the default is true for runtimes, false for plugins; for non-maven project examples, the default value is always false) - add the "Required" checkbox to the requirements/recommendations list. It would be unchecked if there is the "recommended" property. > Project wizard from central: requirements should be recommendations > ------------------------------------------------------------------- > > Key: JBIDE-13687 > URL: https://issues.jboss.org/browse/JBIDE-13687 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha2 > > Attachments: no-server.png > > > In the new project wizard in Central, there is the table with required plugins and runtimes. In fact these are recommendations - even if you don't have the required server, the project can be created and if you have a compatible server, you can deploy the project to it. > So the table's title should be changed to Recommendations. -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13586) Empty/blank response header after POST request

by Juergen Zimmermann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13586?page=com.atlassian.jira.plugi... ] Juergen Zimmermann resolved JBIDE-13586. ---------------------------------------- Resolution: Out of Date The issue is gone when trying with 4.1.0.Alpha1b > Empty/blank response header after POST request > ---------------------------------------------- > > Key: JBIDE-13586 > URL: https://issues.jboss.org/browse/JBIDE-13586 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 4.1.0.Alpha1 > Reporter: Juergen Zimmermann > Assignee: Brian Fitzpatrick > > I tried 4.1.0.Alpha1 (see http://lists.jboss.org/pipermail/jbosstools-dev/2013-February/007053.html) on Kepler 5a. > When I use the Web Service Tester and send a POST request with request header content-type=application/json, then the response header is totally blank/empty although the server-side operation in JBossAS 7.2 was successful. -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13692) Update HTML5 jQuery Mobile Page Template

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13692?page=com.atlassian.jira.plugi... ] Burr Sutter updated JBIDE-13692: -------------------------------- Attachment: jquery_mobile_template.png > Update HTML5 jQuery Mobile Page Template > ---------------------------------------- > > Key: JBIDE-13692 > URL: https://issues.jboss.org/browse/JBIDE-13692 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Reporter: Burr Sutter > Attachments: jquery_mobile_template.png > > > I believe by the time we ship JBDS 7, the JDF/Aerogear teams will have selected some different versions of jquery/jquery mobile. -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13692) Update HTML5 jQuery Mobile Page Template

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-13692: ----------------------------------- Summary: Update HTML5 jQuery Mobile Page Template Key: JBIDE-13692 URL: https://issues.jboss.org/browse/JBIDE-13692 Project: Tools (JBoss Tools) Issue Type: Enhancement Reporter: Burr Sutter I believe by the time we ship JBDS 7, the JDF/Aerogear teams will have selected some different versions of jquery/jquery mobile. -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13691) The feature 'org.jboss.tools.forge.ext.feature' should be included on the JBT update site (not JBDS)

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13691?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-13691: ----------------------------------- Btw, isn't this just a matter of adding the right stuff to the category.xml file? <?xml version="1.0" encoding="UTF-8"?> <site> <description>To install these features, point Eclipse at this site.</description>  <category-def label="JBoss Tools Forge Nightly Build Update Site" name="JBoss Tools Forge Nightly Build Update Site"> <description>JBoss Tools Forge Nightly Build Update Site: contains all features in this build.</description> </category-def> <feature url="features/org.jboss.tools.forge.feature_0.0.0.jar" id="org.jboss.tools.forge.feature" version="0.0.0"> <category name="JBoss Tools Forge Nightly Build Update Site"/> </feature> <feature url="features/org.jboss.tools.forge.test.feature_0.0.0.jar" id="org.jboss.tools.forge.test.feature" version="0.0.0"> <category name="JBoss Tools Forge Nightly Build Update Site"/> </feature>  <feature url="features/org.jboss.tools.forge.feature.source_0.0.0.jar" id="org.jboss.tools.forge.feature.source" version="0.0.0"> <category name="JBoss Tools Forge Nightly Build Update Site"/> </feature> <feature url="features/org.jboss.tools.forge.test.feature.source_0.0.0.jar" id="org.jboss.tools.forge.test.feature.source" version="0.0.0"> <category name="JBoss Tools Forge Nightly Build Update Site"/> </feature> <feature url="features/org.jboss.tools.forge.feature_0.0.0.jar" id="org.jboss.tools.forge.ext.feature" version="0.0.0"> <category name="JBoss Tools Forge Nightly Build Update Site"/> </feature> <feature url="features/org.jboss.tools.forge.test.feature_0.0.0.jar" id="org.jboss.tools.forge.ext.test.feature" version="0.0.0"> <category name="JBoss Tools Forge Nightly Build Update Site"/> </feature>  <feature url="features/org.jboss.tools.forge.feature.source_0.0.0.jar" id="org.jboss.tools.forge.ext.feature.source" version="0.0.0"> <category name="JBoss Tools Forge Nightly Build Update Site"/> </feature> <feature url="features/org.jboss.tools.forge.test.feature.source_0.0.0.jar" id="org.jboss.tools.forge.ext.test.feature.source" version="0.0.0"> <category name="JBoss Tools Forge Nightly Build Update Site"/> </feature> </site> > The feature 'org.jboss.tools.forge.ext.feature' should be included on the JBT update site (not JBDS) > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-13691 > URL: https://issues.jboss.org/browse/JBIDE-13691 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Reporter: Koen Aers > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > -- 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 month

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