February 2010 - jbosstools-issues

[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

14 years, 8 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

14 years, 8 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

14 years, 8 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

14 years, 8 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

14 years, 8 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

14 years, 8 months

4
6
0 / 0

[JBoss JIRA] Created: (RHDS-276) Clicking on compile failure hyperlinks in Console view opens up redundant Java editor tabs

by Neil Griffin (JIRA)

Clicking on compile failure hyperlinks in Console view opens up redundant Java editor tabs ------------------------------------------------------------------------------------------ Key: RHDS-276 URL: http://jira.jboss.com/jira/browse/RHDS-276 Project: Red Hat Developer Studio Issue Type: Bug Affects Versions: 1.0.0.beta2 Reporter: Neil Griffin If I associate an Ant Builder with my JSF Web Project, and have a compile failure in my Java code, then the Console provides a handy mechanism whereby I can click on each failure as a hyperlink. When I click on the link, and the offending Java source file is already open in my editor, it will open up ANOTHER java source editor for the file, which is redundant. This might be because my Java "src" folder is in the WEB-INF folder. I don't know. -- 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

14 years, 8 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-4543) Create categories for properties

by Krasimir Goutcev (JIRA)

Create categories for properties -------------------------------- Key: JBIDE-4543 URL: https://jira.jboss.org/jira/browse/JBIDE-4543 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF, Visual Page Editor core Reporter: Krasimir Goutcev Attachments: properties1.png, properties2.png Open your page file and place the cursor in a place where you'd like to add a tag and then click that tag in the palette. In the Insert Tag window, that appears, you can set the value of GENERAL and ADVANCED attributes of the tag that you chose.(see pic1) Why to not have same categories when select inserted tag on page( see pic2) in properties view? -- 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

14 years, 8 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-1792) CA: In xhtml files with facelets: no [xmlns:*=""] attribute in content assist .

by Andrei Scherbovich (JIRA)

CA: In xhtml files with facelets: no [xmlns:*=""] attribute in content assist . ------------------------------------------------------------------------------- Key: JBIDE-1792 URL: http://jira.jboss.com/jira/browse/JBIDE-1792 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 2.0.1 Reporter: Andrei Scherbovich Assigned To: Maxim Areshkau CA: In xhtml files with facelets: 1. no [xmlns:*=""] attribute in content assist 2. CA when cursor at position [xmlns:*=" | "] not available for not <html> tags. I mean: a) <html xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html" xmlns:j=" | "> -- HERE CONTENT ASSIST AVAILABLE b) <h:form id="helloForm" xmlns:j=" | "> -- HERE CONTENT ASSIST NOT AVAILABLE -- 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

14 years, 8 months

8
15
0 / 0

[JBoss JIRA] Created: (JBIDE-5673) CA for jsf2 resource declaration

by Maxim Areshkau (JIRA)

CA for jsf2 resource declaration -------------------------------- Key: JBIDE-5673 URL: https://jira.jboss.org/jira/browse/JBIDE-5673 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.CR1 Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.1.1 Resources can be specified in project in following way <h:graphicImage value="#{resource['ru/img/1.0/img.gif']}" /> or <link rel="stylesheet" type="text/css" href="#{resource['css:hska.css']}"/>. It will be good if such proposals shows in CA. -- 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

14 years, 8 months

3
4
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 2010