August 2009 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-1036) MySQL connection profile

by Gavin King (JIRA)

MySQL connection profile ------------------------ Key: JBIDE-1036 URL: http://jira.jboss.com/jira/browse/JBIDE-1036 Project: JBoss Tools Issue Type: Feature Request Reporter: Gavin King Currently, Eclipse ships with a limited number of "Connection Profiles", we should at least have one for MySQL. This may be due to license incompatibilities, but we should at least investigate whether it is possible for us to dist the MySQL driver. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4160) Add option in JBoss ESB Editor to disable an ESB action

by Joao Paulo Viragine (JIRA)

Add option in JBoss ESB Editor to disable an ESB action ------------------------------------------------------- Key: JBIDE-4160 URL: https://jira.jboss.org/jira/browse/JBIDE-4160 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Affects Versions: 3.0.0.GA Environment: JBDS 2.0.0.GA Reporter: Joao Paulo Viragine Priority: Optional It would be great if we could disable an specific action in ESB. E.g. <action class="org.jboss.soa.esb.actions.SystemPrintln" name="Println" enabled="false"> <property name="message" value="JBoss ESB Rulez"/> </action> -- 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

12 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-1965) display links from tiles definitions on stuts diagram (like from jsp pages)

by Alex Titov (JIRA)

display links from tiles definitions on stuts diagram (like from jsp pages) --------------------------------------------------------------------------- Key: JBIDE-1965 URL: http://jira.jboss.com/jira/browse/JBIDE-1965 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: struts/shale Affects Versions: 2.0.1 Reporter: Alex Titov Priority: Minor Stuts plugin can display links from jsp page to actions and other jsp pages on diagram. That is grate! But if you use tiles plugin you don't work with jsp pages directly. Instead you work with tiles definition. For example <definition name="..." path="/WEB-INF/jsp/template.jsp"> <put name="content" value="/WEB-INF/graph.jsp"></put> </definition> Both template.jsp and graph.jsp are jsp pages and have links but struts plugin does not understand this. So links from these pages are not displayed in struts diagram. Also it would be nice if there were way to select jsp page for "value" attribute in "put" element in tiles editor (like for "path" attribute in "definition" element). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4601) JBoss Profiler throws NPE when Profile > Profile Configurations... dialog is launched for a Main class

by Nick Boldt (JIRA)

JBoss Profiler throws NPE when Profile > Profile Configurations... dialog is launched for a Main class ------------------------------------------------------------------------------------------------------ Key: JBIDE-4601 URL: https://jira.jboss.org/jira/browse/JBIDE-4601 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M2 Reporter: Nick Boldt Assignee: Max Rydahl Andersen Steps to repro: a) install Eclipse 3.5 b) install JBoss Profiler feature from update site http://download.jboss.org/jbosstools/updates/nightly/3.1.0.M2/ c) restart Eclipse d) create a Java project, eg., foobar e) create a Main class in that project, eg., foo.bar.Main f) put this in Main.java: package foo.bar; public class Main { /** * @param args */ public static void main(String[] args) { System.out.println("Hello, Foo!"); } } f) debug the class: right-click in the file and Debug As > Java Application g) add a breakpoint on the println() line h) debug again, this time switching to the Debug perspective when prompted i) right-click in class file, Debug As > Debug Configurations... j) note the new JBoss Profiler tab for your Java Application > Main launch configuration. Close the dialog. k) right-click in class file, Profile As > Profile Configurations... l) note three error dialogs. -- 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

12 years, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-3557) Externalise English strings (move them from source code into .properties)

by Sean Flanigan (JIRA)

Externalise English strings (move them from source code into .properties) ------------------------------------------------------------------------- Key: JBIDE-3557 URL: https://jira.jboss.org/jira/browse/JBIDE-3557 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Cleanup Reporter: Sean Flanigan Assignee: Sean Flanigan Much of the English text in JBoss Tools is already externalised into .properties files, but my pseudolocalisation testing [1] shows that there is still some hard-coded English text, particularly in files like plugin.xml and feature.xml, but also in parts of the Java source. Any such English text needs to be moved out of the source code into .properties files, and replaced by ResourceBundle lookups. - In the case of plugin.xml or Java source, Eclipse's "Externalize Strings" wizard can help. In most cases, if a plugin already has a ResourceBundle, for instance org.jboss.tools.{plugin}.Messages, it is best to reuse this bundle, rather than creating another one for each package in the bundle. (More bundles create more work for translators.) - In the case of feature.xml, there doesn't seem to be an Eclipse wizard, so externalisation has to be done by hand. [1] Running JBoss Tools together with Eclipse's Babel langpacks, plus the JBoss Tools langpacks. http://www.jboss.org/community/docs/DOC-13256 -- 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

12 years, 10 months

4
16
0 / 0

[JBoss JIRA] Created: (JBIDE-4044) Review unused strings from Messages classes as reported by UCDetector

by Sean Flanigan (JIRA)

Review unused strings from Messages classes as reported by UCDetector --------------------------------------------------------------------- Key: JBIDE-4044 URL: https://jira.jboss.org/jira/browse/JBIDE-4044 Project: Tools (JBoss Tools) Issue Type: Task Components: Cleanup Affects Versions: 3.1.0 Reporter: Sean Flanigan I've run UCDetector [1] against the codebase, and it has found 294 fields in *Messages classes which have 0 references. I've attached a list (views well in oocalc). I'd like to remove them, along with their corresponding resourcebundle properties, to reduce the number of translatable strings before localisation begins. I think it should be safe to remove these fields, since any direct usage will be caught by the compiler as soon as we try to remove it (and wouldn't have been listed by UCDetector anyway, unless it is completely broken), and it would be extremely unlikely for anyone to access a Messages field by reflection. If you want to run UCDetector yourself, select one or more plugin projects (not features, not non-Java projects), select UCDetector/Detect unnecessary code, and wait. I recommend configuring Eclipse's Problems view to show problems of type "UCDetector Marker (References)" whose description contains 'Field "'. The relevant problems are of the form 'Field SomethingMessages.SOME_KEY" has 0 references'. [1] http://ucdetector.sourceforge.net/ -- 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

12 years, 10 months

10
30
0 / 0

[JBoss JIRA] Created: (JBDS-706) Add option to create a JBoss Portal project

by Joao Paulo Viragine (JIRA)

Add option to create a JBoss Portal project ------------------------------------------- Key: JBDS-706 URL: https://jira.jboss.org/jira/browse/JBDS-706 Project: Developer Studio Issue Type: Feature Request Environment: JBDS 2.0.0.GA Reporter: Joao Paulo Viragine It would be nice if we could create a portal in JBoss Portal directly from JBDS/Tools. We could have an option named: 'Create JBoss Portal Project', which included facets like JBoss Portlet and Seam (among others) and created: portlet.xml, portlet-instances.xml and default-object.xml. This option could prompt for a portal name, so we don't need to even define/create the portal in JBoss Portal Admin console. Everything would be done directly from JBDS/Tools. Note that option would be slight different from an existing 'JBoss JSF/Seam Portlet' option that doesn't create a portal, only a portal page in an existing portal. -- 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

12 years, 10 months

5
11
0 / 0

[JBoss JIRA] Created: (JBIDE-1692) Documentation plugins with context sensitive help

by Max Andersen (JIRA)

Documentation plugins with context sensitive help ------------------------------------------------- Key: JBIDE-1692 URL: http://jira.jboss.com/jira/browse/JBIDE-1692 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 2.0.0.GA Reporter: Max Andersen Priority: Critical Fix For: 2.1 Get doc into eclipse format Have reference docs with context sensitive links -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

6
19
0 / 0

[JBoss JIRA] Created: (JBIDE-2110) Creation tests for Conversation and Entity in Seam-test project.

by Anton Klimkovich (JIRA)

Creation tests for Conversation and Entity in Seam-test project. ---------------------------------------------------------------- Key: JBIDE-2110 URL: http://jira.jboss.com/jira/browse/JBIDE-2110 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 2.1.0.beta1 Reporter: Anton Klimkovich Priority: Minor Create tests for Conversation and Entity in Seam-test project to run it with testNG -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBDS-699) Persistence unit not found in seam-gen application

by Jozef Hartinger (JIRA)

Persistence unit not found in seam-gen application -------------------------------------------------- Key: JBDS-699 URL: https://jira.jboss.org/jira/browse/JBDS-699 Project: Developer Studio Issue Type: Bug Components: seam Affects Versions: 2.0.0.GA Environment: JBoss Seam 2.1.2.CR1 JDK 5 update 16 Reporter: Jozef Hartinger Fix For: 2.0.1 Attachments: jbds-persistenceunit.jpg To reproduce, create an application with seam-gen and import it into JBDS. Open the hibernate configuration and expand the configuration node. After that, you should see an error window similar to the attached one. Persistence unit is not picked up, as it is stored in persistence-dev.xml file. -- 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

12 years, 11 months

4
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2009