August 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-5166) Classes in hibernate xml editor should have different icons for different classes types

by Denis Golovin (JIRA)

Classes in hibernate xml editor should have different icons for different classes types --------------------------------------------------------------------------------------- Key: JBIDE-5166 URL: https://jira.jboss.org/jira/browse/JBIDE-5166 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.1.0.M4 Reporter: Denis Golovin Priority: Minor There are fore types: Class, Joined Subclass, Subclass, Union-Sublass and all those classes have the same icons now, it is really good to have different icon to distinguish different types of classes form each other. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6256) Cleanup old mechanizm of page templates

by Maxim Areshkau (JIRA)

Cleanup old mechanizm of page templates --------------------------------------- Key: JBIDE-6256 URL: https://jira.jboss.org/jira/browse/JBIDE-6256 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Affects Versions: 3.2.next Reporter: Maxim Areshkau Assignee: Alexey Kazakov Fix For: 3.2.next In scope of https://jira.jboss.org/jira/browse/JBIDE-6131 has been eclipse-style source code templates component. So our can be cleaned. -- 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

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-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: (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-6611) Seam project makes displaying of Add and Remove from/to server dialog very slow.

by Vlado Pakan (JIRA)

Seam project makes displaying of Add and Remove from/to server dialog very slow. -------------------------------------------------------------------------------- Key: JBIDE-6611 URL: https://jira.jboss.org/browse/JBIDE-6611 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.M1 Environment: JBDS Version: 4.0.0.M1 Build id: v201007091251N Build date: 201007091354 Linux 32bit Java Sun JDK 1.6 Reporter: Vlado Pakan Assignee: Rob Stryker Steps to reproduce: 1. Create seam ear project 2. Create seam war project 3. Define Server within Server view 4. Right-Click on defined server and choose "Add and Remove" popup menu It takes really a lot of time to display requested dialog which should not be there. There are these additional items displayed as available to be added to server: lib/<seamear-ear project name>/EarContent/lib/mvel2.jar lib/<seamear-ear project name>/EarContent/lib/jboss-seam.jar Also when trying to run seam project via menu Run > Run On Server it takes lot of time to display Run On Server Dialog and expand available servers tree view. -- 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
8
0 / 0

[JBoss JIRA] Created: (JBIDE-6404) Include org.jboss.tools.jsf.test plug-in in back in test suite

by Denis Golovin (JIRA)

Include org.jboss.tools.jsf.test plug-in in back in test suite -------------------------------------------------------------- Key: JBIDE-6404 URL: https://jira.jboss.org/browse/JBIDE-6404 Project: Tools (JBoss Tools) Issue Type: Task Components: testing Affects Versions: 3.2.0.M1 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.2.0.M1 It was disabled because it freeze workbench for unknown reason. This problem should be fixed before including it back in test suite -- 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
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6900) Remote start and stop for generic RSE / ssh / linux systems

by Rob Stryker (JIRA)

Remote start and stop for generic RSE / ssh / linux systems ----------------------------------------------------------- Key: JBIDE-6900 URL: https://jira.jboss.org/browse/JBIDE-6900 Project: Tools (JBoss Tools) Issue Type: Task Components: JBossAS Affects Versions: 3.2.0.M2 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.0.Beta -- 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

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6956) Restore structure of http://download.jboss.org/jbosstools

by Denis Golovin (JIRA)

Restore structure of http://download.jboss.org/jbosstools --------------------------------------------------------- Key: JBIDE-6956 URL: https://jira.jboss.org/browse/JBIDE-6956 Project: Tools (JBoss Tools) Issue Type: Task Components: Build/Releng Affects Versions: 3.2.0.M2 Reporter: Denis Golovin Assignee: Nick Boldt Priority: Critical Fix For: 3.2.0.Beta Before aggregation was introduced which is building final aggregated repo we used to have simple hierarchical stucture (see attached picture) jbosstools/builds/${type}/${branch/tag}/${timestamp} jbosstools/updates/${type}/${branch/tag} where ${type} is nightly, stable, development nightly for nightly builds stable for GA releases development for M's, betas and CR's releases ${branch/tag} was used to separate builds made from different branch tags ${timestamp} time stamp YYYYMMDDHHMMSS for example in jbosstools/builds/nightly jbosstools/builds/nightly/trunk would contains last three nightly builds from trunk jbosstools/builds/nightly/3.1.X would contains last three nightly builds from 3.1.X branch jbosstools/builds/nightly/3.1.1 would contains last several builds from 3.1.1 tag depends on what kind of problems was found in release candidate build for example jbosstools/updates/nightly would contains last update sites for tags/branches like jbosstools/updates/nightly/trunk - last update site built from trunk jbosstools/updates/nightly/3.1.X last update site built from 3.1.X branch jbosstools/updates/nightly/3.1.1 last update site built from 3.1.1 tag -- 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
21
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 August 2010