September 2008 - jbosstools-issues

[JBoss JIRA] Created: (JBDS-237) JBDS 1.0 - creating a new jBPM process project - creates processdefinition.xml in old format

by Len DiMaggio (JIRA)

JBDS 1.0 - creating a new jBPM process project - creates processdefinition.xml in old format -------------------------------------------------------------------------------------------- Key: JBDS-237 URL: http://jira.jboss.com/jira/browse/JBDS-237 Project: Developer Studio Issue Type: Bug Affects Versions: 1.0.0.GA Environment: JBoss Developer Studio Build id: 1.0.0.GA Reporter: Len DiMaggio Assigned To: Max Andersen Priority: Minor When a user creates a new jBPM process project, the first time that the processdefinition.xml file is edited, a dialog box is displayed telling the user that the file was created with an older version of the GPD and giving the user the option to convert the file to the current version. There's no functional impact, but it's awkward for the user. See attached screen shot. -- 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

17 years, 3 months

4
4
0 / 0

[JBoss JIRA] Created: (JBDS-347) JBDevstudio crashes from time to time (in a bleeding edge environment)

by David Tonhofer (JIRA)

JBDevstudio crashes from time to time (in a bleeding edge environment) ---------------------------------------------------------------------- Key: JBDS-347 URL: http://jira.jboss.com/jira/browse/JBDS-347 Project: Developer Studio Issue Type: Bug Components: visualeditor Affects Versions: 1.1.0.CR1 Environment: Fedora 9 + KDE: 2.6.25.3-18.fc9.x86_64 Additional plugins: antlr, sourceforge.metrics, subversive, subversive providers Reporter: David Tonhofer Assigned To: Max Rydahl Andersen JBDevstudio crashes from time to time, leaving only a dialog showing the JVM invocation command line in its wake. The last message in the .log file is: !ENTRY org.eclipse.jface 2 0 2008-05-28 21:18:31.564 !MESSAGE Keybinding conflicts occurred. They may interfere with normal accelerator operation. !SUBENTRY 1 org.eclipse.jface 2 0 2008-05-28 21:18:31.564 !MESSAGE A conflict occurred for CTRL+SHIFT+G: Binding(CTRL+SHIFT+G, ParameterizedCommand(Command(org.springframework.ide.eclipse.beans.ui.editor.commands.searchBeanReferences,Spring Beans References Search, , Category(org.eclipse.search.ui.category.search,Search,Search command category,true), , ,,true),null), org.eclipse.ui.defaultAcceleratorConfiguration, org.eclipse.wst.sse.ui.structuredTextEditorScope,,,system) Binding(CTRL+SHIFT+G, ParameterizedCommand(Command(org.jboss.tools.seam.ui.find.references,Find Seam References, Find Seam References, Category(org.eclipse.search.ui.category.search,Search,Search command category,true), ActionDelegateHandlerProxy(null,org.jboss.tools.seam.ui.actions.FindSeamReferencesAction), ,,true),null), org.eclipse.ui.defaultAcceleratorConfiguration, org.eclipse.wst.sse.ui.structuredTextEditorScope,,,system) Binding(CTRL+SHIFT+G, ParameterizedCommand(Command(org.eclipse.jdt.ui.edit.text.java.search.references.in.workspace,References in Workspace, Search for references to the selected element in the workspace, Category(org.eclipse.search.ui.category.search,Search,Search command category,true), , ,,true),null), org.eclipse.ui.defaultAcceleratorConfiguration, org.eclipse.ui.contexts.window,,,system) I the log shows more on the next crash, I will append more info here. -- 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

17 years, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (RHDS-302) Change default workspace for rhds to a non-space version

by Max Andersen (JIRA)

Change default workspace for rhds to a non-space version --------------------------------------------------------- Key: RHDS-302 URL: http://jira.jboss.com/jira/browse/RHDS-302 Project: Red Hat Developer Studio Issue Type: Feature Request Components: Build Affects Versions: 1.0.0.CR1 Reporter: Max Andersen Priority: Critical Fix For: 1.0.0.GA Because of the issues with spaces in names for both jboss AS and hibernate annotation used in hibernate tools we should see if we could change the default from ${user.home}/workspace to ${rhdshome}/workspace -- 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

17 years, 3 months

3
12
0 / 0

[JBoss JIRA] Created: (JBDS-240) Forum monitoring

by Anatoly Fedosik (JIRA)

Forum monitoring ---------------- Key: JBDS-240 URL: http://jira.jboss.com/jira/browse/JBDS-240 Project: Developer Studio Issue Type: Task Components: documentation Affects Versions: 1.0.0.GA Reporter: Anatoly Fedosik Assigned To: Catherine Luts Fix For: 1.0.1 Read the JBoss Developer Studio Users forum everyday in order to find the missing info in documentation. -- 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

17 years, 3 months

5
18
0 / 0

[JBoss JIRA] Created: (RHDS-157) Dev Jira taks review

by Svetlana mukhina (JIRA)

Dev Jira taks review --------------------- Key: RHDS-157 URL: http://jira.jboss.com/jira/browse/RHDS-157 Project: Red Hat Developer Studio Issue Type: Task Components: documentation Affects Versions: 1.0.0.beta2 Reporter: Svetlana mukhina Assigned To: Anatoly Fedosik Fix For: 1.0.0.beta2 Look through the tasks of the dev team, and check whether all the changes made in Studio were documented. -- 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

17 years, 3 months

4
21
0 / 0

[JBoss JIRA] Created: (JBIDE-2555) Moving Seam component yields persistent, incorrect validation error

by Tim Otten (JIRA)

Moving Seam component yields persistent, incorrect validation error ------------------------------------------------------------------- Key: JBIDE-2555 URL: https://jira.jboss.org/jira/browse/JBIDE-2555 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 2.1.0.CR1 Environment: JBoss Developer Studio 1.1.0.CR1 Seam 2.0.2.SP1 Ubuntu Feisty Reporter: Tim Otten When moving a Seam component from one Java package to another Java package, the Seam validator erroneously reports the error "Duplicate component name." Cleaning the project does not remove the error. Eclipse must be restarted. Steps to reproduce: 1. Create a new EAR-based project 2. Generate an entity, entityhome, etc. 3. Move one of the Seam components to a new Java package, e.g. 3.a. In the "Package Explorer" tab, locate the entity's home component. 3.b. Right-click -> Refactor -> Move 3.c. Designate a new package 3.d. Click "OK" 4. Clean/Rebuild project 4.a. In the Eclipse menu bar, choose Project -> Clean 4.b. Choose any/all applicable projects 4.c. Enable "Start a build immediately" 4.d. Click "OK" 5. In the "Problems" tab, an error appears twice: "Duplicate component name" After repeated attempts to clean/build the project(s), the error message persists. The error can be removed by: 6. Close Eclipse 7. Open Eclipse 8. Clean/Rebuild project At this point, the error message goes away. The project will now build and deploy, and the refactored component functions appropriately. (Note: I'm using the current stable release of JBoss Developer Studio 1.1.0.CR1 with JBoss Tools 2.1.0.CR1. I've checked the list of open tickets and the release notes for JBoss Tools 2.1.1 and 2.1.2 -- I couldn't identify any related issues.) -- 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

17 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-1670) structured xml editor for jboss-esb.xml

by Max Andersen (JIRA)

structured xml editor for jboss-esb.xml --------------------------------------- Key: JBIDE-1670 URL: http://jira.jboss.com/jira/browse/JBIDE-1670 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: XML Structured Editor Affects Versions: 2.0.0.GA Reporter: Max Andersen Fix For: 2.1 -- 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

17 years, 3 months

5
12
0 / 0

[JBoss JIRA] Created: (JBIDE-2386) ESB Project Structure

by John Graham (JIRA)

ESB Project Structure --------------------- Key: JBIDE-2386 URL: http://jira.jboss.com/jira/browse/JBIDE-2386 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Reporter: John Graham Assigned To: John Graham Need to determine (and, if necessary, implement components in support of) the structure in Eclipse for JBESB projects. Choices include (a) free style, (b) WTP style, (c) custom ESB style, (d) others... Also need to determine if JBESB archives can be built in other project types (such as Java or web app projects), or whether they are confined to JBESB projects. -- 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

17 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBDS-296) Dev what's new review

by Svetlana mukhina (JIRA)

Dev what's new review ---------------------- Key: JBDS-296 URL: http://jira.jboss.com/jira/browse/JBDS-296 Project: Developer Studio Issue Type: Task Components: documentation Affects Versions: 1.0.0.GA Reporter: Svetlana mukhina Assigned To: Anatoly Fedosik Fix For: 1.0.1 have a look at here http://docs.jboss.org/tools/whatsnew, it's a what's of the previous release, just run over it to be sure we didn't skip anything. -- 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

17 years, 3 months

4
31
0 / 0

[JBoss JIRA] Created: (JBIDE-2772) Problem with using link (tag <a)

by Andrei Scherbovich (JIRA)

Problem with using link (tag <a) -------------------------------- Key: JBIDE-2772 URL: https://jira.jboss.org/jira/browse/JBIDE-2772 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Affects Versions: 3.0.0.alpha Reporter: Andrei Scherbovich Assignee: Maxim Areshkau Priority: Minor In example "exposer" if we change tag <a, for example, with tag <b (see pic. VPEafterChanging.png) the result will be correct. But if we return previous tag <a the result will be the same (see pic. VPEafterReturningTag) but it must be as shown on figure VPEbeforeError -- 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

17 years, 3 months

5
14
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 2008