March 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10947) Auto-detect and format JSON & XML in WS tester

by Jonathan Fuerth (JIRA)

Jonathan Fuerth created JBIDE-10947: --------------------------------------- Summary: Auto-detect and format JSON & XML in WS tester Key: JBIDE-10947 URL: https://issues.jboss.org/browse/JBIDE-10947 Project: Tools (JBoss Tools) Issue Type: Enhancement Reporter: Jonathan Fuerth When testing a web service, often the response data will be in JSON or XML format. It would be great if these could be auto-detected, syntax coloured, and (optionally?) reformatted and indented. Otherwise, I'm always going to have to copy the response data and paste it into jsonlint.com. :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
24
0 / 0

[JBoss JIRA] (JBIDE-10838) Unable to install BPEL editor from nightly JBT SOA update site

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-10838: ------------------------------------ Summary: Unable to install BPEL editor from nightly JBT SOA update site Key: JBIDE-10838 URL: https://issues.jboss.org/browse/JBIDE-10838 Project: Tools (JBoss Tools) Issue Type: Bug Environment: L64, JBT 3.3.Nightly Reporter: Jiri Peterka Cannot complete the install because one or more required items could not be found. Software being installed: JBoss BPEL Editor 1.1.0.v20120209-0947-H670-Beta1 (org.jboss.tools.bpel.feature.feature.group 1.1.0.v20120209-0947-H670-Beta1) Missing requirement: BPEL Editor (Incubation) 0.8.0.v20120202-0453-H135-CI (org.eclipse.bpel.ui 0.8.0.v20120202-0453-H135-CI) requires 'bundle org.eclipse.bpel.common.wsdl 0.0.0' but it could not be found Cannot satisfy dependency: From: BPEL Visual Designer 0.8.0.v20120202-0453-H135-CI (org.eclipse.bpel.feature.feature.group 0.8.0.v20120202-0453-H135-CI) To: org.eclipse.bpel.ui [0.8.0.v20120202-0453-H135-CI] Cannot satisfy dependency: From: JBoss BPEL Editor 1.1.0.v20120209-0947-H670-Beta1 (org.jboss.tools.bpel.feature.feature.group 1.1.0.v20120209-0947-H670-Beta1) To: org.eclipse.bpel.feature.feature.group [0.8.0.v20120202-0453-H135-CI] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-9464) test failures in org.jboss.tools.esb.ui.bot.test

by Nick Boldt (JIRA)

test failures in org.jboss.tools.esb.ui.bot.test ------------------------------------------------ Key: JBIDE-9464 URL: https://issues.jboss.org/browse/JBIDE-9464 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: esb Affects Versions: 3.3.0.M3 Reporter: Nick Boldt Assignee: Brian Fitzpatrick Fix For: 3.3.0.M4 svn co http://svn.jboss.org/repos/jbosstools/trunk/ cd trunk; mvn clean install [INFO] org.jboss.tools.esb.ui.bot.test ................... FAILURE [19.709s] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

9
28
0 / 0

[JBoss JIRA] Created: (JBDS-1778) JBDS50_0430: [COMMIT] (Dev) Document/QA Maven Archetypes

by mark yarborough (JIRA)

JBDS50_0430: [COMMIT] (Dev) Document/QA Maven Archetypes -------------------------------------------------------- Key: JBDS-1778 URL: https://issues.jboss.org/browse/JBDS-1778 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: Requirements Reporter: mark yarborough Fix For: 5.0.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
7
0 / 0

[JBoss JIRA] Created: (JBDS-1769) JBDS50_0425: [COMMIT] (Dev) Modular Delivery (eg. SOA plug-ins)

by mark yarborough (JIRA)

JBDS50_0425: [COMMIT] (Dev) Modular Delivery (eg. SOA plug-ins) --------------------------------------------------------------- Key: JBDS-1769 URL: https://issues.jboss.org/browse/JBDS-1769 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: Requirements Reporter: mark yarborough -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
7
0 / 0

[JBoss JIRA] (JBIDE-10588) Installing JBoss Maven Seam Integration plugin breaks Maven integration for WTP

by Rafal Krzewski (Created) (JIRA)

Installing JBoss Maven Seam Integration plugin breaks Maven integration for WTP ------------------------------------------------------------------------------- Key: JBIDE-10588 URL: https://issues.jboss.org/browse/JBIDE-10588 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.3.0.M5 Environment: Eclipse 3.7.1.20110916-0149, m2e 1.0.100.20110804-1717, m2e-wtp 0.14.0.20110928-2045 Reporter: Rafal Krzewski Assignee: Fred Bricon After installing istalling JBoss Maven Seam Integration plugin from http://download.jboss.org/jbosstools/updates/development/indigo/ m2e-wtp configurator stopped working. Running Maven > Update Configuration produces to following error on any project that is using war or ejb packaging (ear is OK): Project configurator "org.jboss.tools.maven.seam.configurator" is not available. To enable full functionality, install the project configurator and run Maven->Update Project Configuration. Additionally, maven-ejb-plugin and maven-war-plugin executions are reported as not covered by by lifecycle configuration. I've checked with OSGi host console and org.jboss.tools.maven.seam bundle is deployed: osgi> ss org.jboss.tools.maven.seam id State Bundle 774 ACTIVE org.jboss.tools.maven.seam_1.3.0.v20111209-0524-H40-M5 The configurator extension is also deployed: osgi> pt -v org.eclipse.m2e.core.projectConfigurators Extension(s): ------------------- null [from org.jboss.tools.maven.seam] <configurator> id = org.jboss.tools.maven.seam.configurator class = org.jboss.tools.maven.seam.configurators.SeamProjectConfigurator name = Seam secondaryTo = org.maven.ide.eclipse.configuration.wtp.configurator </configurator> Alas, the configurator class cannot be instantiated. Eclipse error log contains the following: Plug-in "org.jboss.tools.maven.seam" was unable to instantiate class "org.jboss.tools.maven.seam.configurators.SeamProjectConfigurator". An exception stack trace is not available. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

9
28
0 / 0

[JBoss JIRA] (JBIDE-10120) find a way to display a project example once when several versions targeted for different runtimes exist

by Fred Bricon (Created) (JIRA)

find a way to display a project example once when several versions targeted for different runtimes exist -------------------------------------------------------------------------------------------------------- Key: JBIDE-10120 URL: https://issues.jboss.org/browse/JBIDE-10120 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: project-examples Affects Versions: 3.3.0.M3 Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 3.3.0.Beta1 Given the upcoming (40+) new quickstart projects, we'll most likely have duplicates between the community and enterprise versions. In order to reduce the amount of quickstarts in the Project Examples UI, in addtion to adding a Runtime filter (JBIDE-10119), we could also regroup similar projects under one entry. So, for example, instead of seeing 2 entries for kitchensink (community) and kitchensink (eap6) We could display only one kitchensink entry in the UI, and upon selection, choose the actual version / target runtime we want to create. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-9239) Custom deploy folders should be added to AS7 setup like done for previous issues

by Max Rydahl Andersen (JIRA)

Custom deploy folders should be added to AS7 setup like done for previous issues -------------------------------------------------------------------------------- Key: JBIDE-9239 URL: https://issues.jboss.org/browse/JBIDE-9239 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Blocker Fix For: 3.3.0.M3 JBIDE-9085 allows targeting custom deploy folder but doesn't register the location at startup/deregister at shutdown like was done via jmx in old days. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

7
19
0 / 0

[JBoss JIRA] Created: (JBDS-1587) retro1

by mark yarborough (JIRA)

retro1 ------ Key: JBDS-1587 URL: https://issues.jboss.org/browse/JBDS-1587 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: Program Reporter: mark yarborough Assignee: mark yarborough -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
4
0 / 0

[JBoss JIRA] (JBIDE-11297) AS7 ability to add deployment folders on separate file systems

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-11297: ----------------------------------- Summary: AS7 ability to add deployment folders on separate file systems Key: JBIDE-11297 URL: https://issues.jboss.org/browse/JBIDE-11297 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Affects Versions: 3.3.0.Beta1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.0.Beta2 Servers earlier than as7 have a management task which can be called to add an arbitrary folder as one that the deployment scanner should scan. Ensure that jbosstools can make use of this for as7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
7
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 2012