September 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBDS-1341) JBDS 3.0.0.GA and AS6M5

by Burr Sutter (JIRA)

JBDS 3.0.0.GA and AS6M5 ----------------------- Key: JBDS-1341 URL: https://jira.jboss.org/browse/JBDS-1341 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: servers Affects Versions: 3.0.0.GA Environment: Win7 Java 1.6 32-bit Reporter: Burr Sutter JBDS 3 can add and start a AS6M5 server but it fails on stop. Exception in thread "main" java.net.MalformedURLException: Service URL must start with service:jmx: at javax.management.remote.JMXServiceURL.<init>(JMXServiceURL.java:143) at org.jboss.Shutdown.main(Shutdown.java:234) To stop the server, kill the javaw.exe process/shutdown the whole IDE -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBDS-1324) ModeShape plugin needs to have its modeshape client jar replaced from the SOA-P build

by Van Halbert (JIRA)

ModeShape plugin needs to have its modeshape client jar replaced from the SOA-P build ------------------------------------------------------------------------------------- Key: JBDS-1324 URL: https://jira.jboss.org/browse/JBDS-1324 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: Modeshape Reporter: Van Halbert Fix For: 4.0.0.Beta1 The current ModeShape rest client jar is out-of-date. It needs to be replaced by the modeshape-client.jar being built from SOA-P. Note, the rest client jar is being replace by a different client jar that contains both the rest client and jdbc client interfaces. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBDS-754) Externalize English strings in devstudio code

by Sean Flanigan (JIRA)

Externalize English strings in devstudio code --------------------------------------------- Key: JBDS-754 URL: https://jira.jboss.org/jira/browse/JBDS-754 Project: Developer Studio Issue Type: Feature Request Components: ui/branding Affects Versions: 2.0.0.GA Reporter: Sean Flanigan Assignee: Sean Flanigan As in JBIDE-3557, there are some unexternalized strings which need to be pulled out into .properties files, so that they can be translated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

4
9
0 / 0

[JBoss JIRA] Created: (JBDS-587) Need to translate Help/About text including copyright statement

by Sean Flanigan (JIRA)

Need to translate Help/About text including copyright statement --------------------------------------------------------------- Key: JBDS-587 URL: https://jira.jboss.org/jira/browse/JBDS-587 Project: Developer Studio Issue Type: Feature Request Components: Build Affects Versions: 2.0.0.cr1 Reporter: Sean Flanigan Help/About JBoss Developer Studio shows the version/copyright information for JBDS. This text looks similar to /com.jboss.jbds.product/plugin.properties but is actually overwritten/expanded from releng/org.jboss.ide.eclipse.releng/builders/product/product.properties during the build. The problem is, if we create a translation fragment plugin for com.jboss.jbds.product, the translators will translate the obsolete information in /com.jboss.jbds.product/plugin.properties, and when a langpack is installed, the up-to-date information will be replaced by obsolete information. We need to work out how to handle this better, preferably keeping the translatable text somewhere in com.jboss.jbds.product, not in releng. Perhaps we could do something with /com.jboss.jbds.product/about.mappings / about.ini? Ref: http://help.eclipse.org/stable/index.jsp?topic=/org.eclipse.platform.doc.... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

6
28
0 / 0

[JBoss JIRA] Created: (JBIDE-7138) BPEL Component N&N

by Max Andersen (JIRA)

BPEL Component N&N ------------------ Key: JBIDE-7138 URL: https://jira.jboss.org/browse/JBIDE-7138 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: bpel Affects Versions: 3.2.0.M2 Reporter: Brian Fitzpatrick Assignee: Robert (Bob) Brodt Fix For: 3.2.0.M2 Create a N&N for any BPEL N&N issues for the M2 release -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6927) Integrate Savara plugins into JBoss Tools

by Gary Brown (JIRA)

Integrate Savara plugins into JBoss Tools ----------------------------------------- Key: JBIDE-6927 URL: https://jira.jboss.org/browse/JBIDE-6927 Project: Tools (JBoss Tools) Issue Type: Task Reporter: Gary Brown Assignee: Nick Boldt The requested information is: a) where Savara's build job is located (URL) Savara-1.0.x is the currently released version, which was not built using Tycho - so this version should not be integrated. Savara-1.1.0 (which is currently trunk) hudson job is here: http://hudson.qa.jboss.com/hudson/job/savara/ The tools part is located in a 'tools' sub-folder, within trunk. b) where Savara's update site is published (URL) Originally was publishing using the publish.sh script as part of jboss tools, but a change was made that causes it to fail, I think due to the fact that the Eclipse plugins/features/site are within a sub-folder, and not at the root of the build job. So currently the hudson job just provides the link to the latest built artifacts, which include the update site zip. The hudson job also builds a runtime distribution for Savara. c) the category name / label / description for the aggregate update site (chunk of XML) Savara / Savara / Tooling support for the Savara "Testable Architecture" capabilities. d) any other categories in which the Savara stuff needs to be included (chunk(s) of XML) e) the full list of Savara feature names to be included (plain text, as pulled from your feature.xml's ID field(s)) org.jboss.savara.tools.feature org.jboss.savara.experimental.feature org.scribble.protocol.feature -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

3
19
0 / 0

[JBoss JIRA] Created: (JBIDE-7087) New Properties file created via Externalize String Dialog is not properly displayed.

by Vlado pakan (JIRA)

New Properties file created via Externalize String Dialog is not properly displayed. ------------------------------------------------------------------------------------ Key: JBIDE-7087 URL: https://jira.jboss.org/browse/JBIDE-7087 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.2.0.M2 Environment: Linux 32bit Java Sun JDK 1.6 JBDS 4.0.0.v201009142310R-H472-M2 Reporter: Vlado pakan Assignee: Alexey Kazakov When new Properties File created using Externalize String Dialog is opened empty Properties editor is displayed. Both tabs Properties and Source of this editor has no content. But file in file system has proper content. It displays empty editor also after calling Refresh F5 on this file, reopening file and also after build was cleaned. After JBDS was restarted Properties file displayed file content properly. Steps to reproduce: 1. Create new JSF project using JSFKickStartWithoutLibs template. 2. Open inputUserName.jsp file and select text 'Input' within '<title>Input User Name Page</title>' tag 3. Open Externalize Strings Dialog, Check check box 'Create a new properties file' and choose button 'Next' 4. Specify properties file name and location and choose button 'OK' 5. Open newly created Porperties File Opened file has displayed empty content but has proper content in file system -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-7134) JST/JSF Components N&N

by Max Andersen (JIRA)

JST/JSF Components N&N ---------------------- Key: JBIDE-7134 URL: https://jira.jboss.org/browse/JBIDE-7134 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: JSF, jsp/jsf/xml source editing Affects Versions: 3.2.0.M2 Reporter: Denis Golovin Assignee: Alexey Kazakov Fix For: 3.2.0.M2 https://jira.jboss.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=pro... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBDS-1276) In Hibernate Tools, template connection coordinates for Ingres DB are missing. Negative partner perception

by Ken Johnson (JIRA)

In Hibernate Tools, template connection coordinates for Ingres DB are missing. Negative partner perception ----------------------------------------------------------------------------------------------------------- Key: JBDS-1276 URL: https://jira.jboss.org/browse/JBDS-1276 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: hibernate Affects Versions: 3.0.0.GA Environment: RHEL 5.4 Version: 3.0.0.GA Build id: v201003100055R Build date: 201003100222 Reporter: Ken Johnson Hibernate tooling: New->Hibernate Configuration File New->Console Configuration When user selects Ingres from the list of databases or database dialects, the "Driver Name:" field is not auto-populated as it is for other DBs. Consequently, the Connection URL cannot be auto-populated either. This is causing some friction with Ingres as their customers have questioned them as to whether they are really compatible with JBoss EAP. True it's largely a cosmetic issue but causing customer uncertainty. Can the tooling populate the defaults for Ingres?: "com.ingres.jdbc.IngresDriver" "jdbc:ingres://${HOSTNAME}:${PORT}/${DB};UID=${USERNAME};PWD=${PASSWORD}" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

5
13
0 / 0

[JBoss JIRA] Created: (JBIDE-7130) Hibernate Component N&N

by Max Andersen (JIRA)

Hibernate Component N&N ----------------------- Key: JBIDE-7130 URL: https://jira.jboss.org/browse/JBIDE-7130 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Hibernate Affects Versions: 3.2.0.M2 Reporter: Denis Golovin Assignee: Dmitry Geraskov Fix For: 3.2.0.M2 https://jira.jboss.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=pro... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

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