November 2008 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-2820) Add supports for new jsf 2.0 elements

by Maxim Areshkau (JIRA)

Add supports for new jsf 2.0 elements -------------------------------------- Key: JBIDE-2820 URL: https://jira.jboss.org/jira/browse/JBIDE-2820 Project: Tools (JBoss Tools) Issue Type: Sub-task Affects Versions: 3.0.0.alpha Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.0.0.beta1 Add supports for new jsf 2.0 elements h:head, h:body ... -- 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, 8 months

6
10
0 / 0

[JBoss JIRA] Created: (JBDS-366) Welcome screen: view of Create New is incorrectly, and there is strange behavior

by Tatyana Romanovich (JIRA)

Welcome screen: view of Create New is incorrectly, and there is strange behavior -------------------------------------------------------------------------------- Key: JBDS-366 URL: http://jira.jboss.com/jira/browse/JBDS-366 Project: Developer Studio Issue Type: Bug Affects Versions: 1.1.0.CR1 Environment: JBoss Developer Studio Version: 1.1.0 Build id: 200806161541-nightly Build date: 06/16/2008 15:46 Reporter: Tatyana Romanovich Assigned To: Maxim Areshkau Priority: Trivial EXECUTE: Open JBDS with empty workspace EXECUTE: select Getting Started on the Welcome screen EXECUTE: move mouse over the each links 1. FAILURE: green badge on the icon appears only for "Viewlets and Tutorials" point (see Welcome1.png) EXECUTE: select any item (click on the right of link) EXECUTE: move mouse over another items icon 2. FAILURE: both icons have green badge at the same time (see Welcome2.png) EXECUTE: Select "Create New..." 3. FAILURE: "Create jBPM Process Project" is subitem of "Create Seam Project". Is it right? (see Welcome3.png) EXECUTE: Select "Perspectives" EXECUTE: Select any item -> Welcome window gets smaller EXECUTE: Verify Welcome window 4. FAILURE: Welcome to JBDS appears (Is it right? ) EXECUTE: Try to select Perspectives link 5. FAILURE: Perspectives can't be displayed -- 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

15 years, 9 months

4
20
0 / 0

[JBoss JIRA] Created: (JBDS-340) Intro/Welcome screen cleanup

by Max Rydahl Andersen (JIRA)

Intro/Welcome screen cleanup ---------------------------- Key: JBDS-340 URL: http://jira.jboss.com/jira/browse/JBDS-340 Project: Developer Studio Issue Type: Task Components: ui/branding Reporter: Max Rydahl Andersen Assigned To: Max Rydahl Andersen Fix For: 2.0.0.alpha Splashscreen support has improved in Ganymede, same has the intro and welcome screen setup. SWT did some changes to allow xulrunner to be configured at startup - we should make sure we do what is needede there. If that happens we should be able to remove our big code duplication and just use the normal welcome screen mechanism and hopefully create a JBDS branded version. -- 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

15 years, 9 months

4
14
0 / 0

[JBoss JIRA] Created: (JBIDE-3290) sorting/filtering is not updating correctly in code completion of source page in VPE

by Max Rydahl Andersen (JIRA)

sorting/filtering is not updating correctly in code completion of source page in VPE ------------------------------------------------------------------------------------ Key: JBIDE-3290 URL: https://jira.jboss.org/jira/browse/JBIDE-3290 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.0.0.cr1 Reporter: Max Rydahl Andersen Assignee: Victor Rubezhny Priority: Critical Fix For: 3.0.0.cr1 The sorting seem to make all EL completion show above the more relevant properties of style attributes and when typing the EL completion stays there even though they do not match the filter. See attached video -- 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, 9 months

3
25
0 / 0

[JBoss JIRA] Created: (JBIDE-2763) Add plugin versioning check

by Max Rydahl Andersen (JIRA)

Add plugin versioning check --------------------------- Key: JBIDE-2763 URL: https://jira.jboss.org/jira/browse/JBIDE-2763 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Reporter: Max Rydahl Andersen Fix For: LATER Our build should validate that A) version numbers only increases B) only increases when there are a change eclipse.org has some of these in place - maybe take a look there ;) -- 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, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBDS-378) Improve requirements build process

by Denis Golovin (JIRA)

Improve requirements build process ---------------------------------- Key: JBDS-378 URL: https://jira.jboss.org/jira/browse/JBDS-378 Project: Developer Studio Issue Type: Task Components: Build Reporter: Denis Golovin Assignee: Denis Golovin 1. Downloaded file verification to avoid build errors related to zip/unzip (md5 check or at least downloaded file size) 2. Incremental update for dependencies. If one dependency has been changed it shouldn't trigger at least downloading unaffected dependencies. -- 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, 9 months

2
11
0 / 0

[JBoss JIRA] Created: (JBIDE-1066) JBoss Server don't remove unused war files from deploy folder.

by Aliaksey Nis (JIRA)

JBoss Server don't remove unused war files from deploy folder. -------------------------------------------------------------- Key: JBIDE-1066 URL: http://jira.jboss.com/jira/browse/JBIDE-1066 Project: JBoss Tools Issue Type: Bug Environment: WindowsXP SP2 rhds-win32-1.0.0.beta2.jar Red Hat Developer Studio Version: 1.0.0 BETA2 Build: beta2 JDK 1.5_08 Reporter: Aliaksey Nis Create, run, remove from server and delete different projects. Look into deploy folder of JBoos server. Large amount of old war files, ds files, project folders can be found here. Dunno, if this is an issue, but think server must make some cleaning in deploy folder sometimes. :) -- 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

15 years, 9 months

5
18
0 / 0

[JBoss JIRA] Created: (JBIDE-2687) Exception during configuratiob

by Aliaksey Nis (JIRA)

Exception during configuratiob ------------------------------ Key: JBIDE-2687 URL: https://jira.jboss.org/jira/browse/JBIDE-2687 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Aliaksey Nis -- 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, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-2700) Console view sometimes not showing AS console output

by Galder Zamarreno (JIRA)

Console view sometimes not showing AS console output ---------------------------------------------------- Key: JBIDE-2700 URL: https://jira.jboss.org/jira/browse/JBIDE-2700 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.alpha Reporter: Galder Zamarreno Attachments: Screenshot-JBoss AS - loadgenerator-LoadGenerator-config-ScenarioConfig.properties - JBoss Developer Studio .png If I open a JBDS workspace and I'm directly in the JBoss AS perspective with the console view opened and then, I start one of the servers, the console shows nothing as you can see from the screenshot. There's a bug somewhere there. -- 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, 10 months

7
24
0 / 0

[JBoss JIRA] Created: (JBIDE-2532) Defect in GUI. Task Node | Task | Controller Tab Mapped Name displays in the Required Check Box column.

by Steve Hall (JIRA)

Defect in GUI. Task Node | Task | Controller Tab Mapped Name displays in the Required Check Box column. -------------------------------------------------------------------------------------------------------- Key: JBIDE-2532 URL: https://jira.jboss.org/jira/browse/JBIDE-2532 Project: Tools (JBoss Tools) Issue Type: Bug Components: Ganymede Affects Versions: 3.0.0.GA Environment: Eclipse plugin 3.1.3SP2. Installed in Eclipse 3.4.0. Running on Windows XP SP2 Reporter: Steve Hall Priority: Minor Created a Task Node. Added a task. Provided Name in General field. Set Assignment to Swinlane. Filled in the Swimlane Name. On the controller tab I added 6 variables. For each variable, I entered the name and mapped name filed. When I display the data in the GRID, the Mapped Name data shows up under the Required column. This is the associated processdefinition.xml file: <?xml version="1.0" encoding="UTF-8"?> <process-definition xmlns="urn:jbpm.org:jpdl-3.2" name="ProductMusicProducts"> <swimlane name="Talent Scout"> <assignment expression="group(Talent Scout)"></assignment> </swimlane> <swimlane name="Legal Advisor"> <assignment expression="group(Legal Advisor)"></assignment> </swimlane> <swimlane name="Band Member"> <assignment expression="group(Band Member)"></assignment> </swimlane> <swimlane name="Record Producer"> <assignment expression="group(Record Producer)"></assignment> </swimlane> <swimlane name="Artist Development"> <assignment expression="group(Artist Development)"></assignment> </swimlane> <swimlane name="Songwriter"> <assignment expression="group(Songwriter)"></assignment> </swimlane> <swimlane name="Musician"> <assignment expression="group(Musician)"></assignment> </swimlane> <swimlane name="Video Production"> <assignment expression="group(Video Production)"></assignment> </swimlane> <swimlane name="Artist"> <assignment expression="group(Artist)"></assignment> </swimlane> <start-state name="Hold Auditions"> <task name="Hold Auditions" swimlane="Talent Scout"> <description> The hold auditions task </description> <controller> <variable access="read,write,required" name="audDate" mapped-name="Audition Date"></variable> <variable access="read,write,required" name="audLocation" mapped-name="Audition Location"></variable> </controller> </task> <transition to="Select Band Members"></transition> </start-state> <task-node name="Select Band Members"> <task name="Select Band Members" swimlane="Talent Scout"> <description> Assign Band Members </description> <controller> <variable access="read,write,required" name="bm1" mapped-name="Band Member 1"></variable> <variable access="read,write,required" name="bm2" mapped-name="Band Members 2"></variable> <variable access="read,write,required" name="bm3" mapped-name="Band Member 3"></variable> <variable access="read,write" name="bm4" mapped-name="Band Member 4"></variable> <variable access="read,write" name="bm5" mapped-name="Band Member 5"></variable> <variable access="read,write" name="bm6" mapped-name="Band Member 6"></variable> </controller> </task> </task-node> <task-node name="Contract Band Members"> <task name="Contract Band Members"> <controller> <variable access="read,write,required" name="bm1ContractSent" mapped-name="Band Member 1 Contract Sent"></variable> <variable access="read,write,required" name="bm2ContractSent" mapped-name="Band Member 2 Contract Sent"></variable> <variable access="read,write,required" name="bm3ContractSent" mapped-name="Band Member 3 Contract Sent"></variable> <variable access="read,write" name="bm4ContractSent" mapped-name="Band Member 4 Contract Sent"></variable> <variable access="read,write" name="bm5ContractSent" mapped-name="Band Member 5 Contract Sent"></variable> <variable access="read,write" name="bm6ContractSent" mapped-name="Band Member 6 Contract Sent"></variable> </controller> </task> </task-node> <task-node name="All Contracts Agreed"> <task name="All Contracts Agreed" swimlane="Legal Advisor"> <controller> <variable access="read,write,required" name="bm1Agreed" mapped-name="Band Member 1 Agreed"></variable> <variable access="read,write,required" name="bm2Agreed" mapped-name="Band Member 2 Agreed"></variable> <variable access="read,write,required" name="bm3Agreed" mapped-name="Band Member 3 Agreed"></variable> <variable access="read,write" name="bm4Agreed" mapped-name="Band Member 4 Agreed"></variable> <variable access="read,write" name="bm5Agreed" mapped-name="Band Member 5 Agreed"></variable> <variable access="read,write" name="bm6Agreed" mapped-name="Band Member 6 Agreed"></variable> </controller> </task> </task-node> <task-node name="Contract Response"> <task> <controller> <variable access="read,write,required" name="bm1Agreed" mapped-name="BandMember1Agreed"></variable> <variable access="read,write,required" name="bm2Agreed" mapped-name="Band Member 2 Agreed"></variable> <variable access="read,write,required" name="bm3Agreed" mapped-name="Band Member 3 Agreed"></variable> <variable access="read,write" name="bm4Agreed" mapped-name="Band Member 4 Agreed"></variable> <variable access="read,write" name="bm5Agreed" mapped-name="Band Member 5 Agreed"></variable> <variable access="read,write" name="bm6Agreed" mapped-name="Band Member 6 Agreed"></variable> </controller> </task> </task-node> <end-state name="end-state1"></end-state> </process-definition> -- 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, 10 months

3
8
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2008