May 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8947) Move hibernatetools to Eclipse3.7M7

by Dmitry Geraskov (JIRA)

Move hibernatetools to Eclipse3.7M7 ----------------------------------- Key: JBIDE-8947 URL: https://issues.jboss.org/browse/JBIDE-8947 Project: Tools (JBoss Tools) Issue Type: Task Components: Hibernate Affects Versions: 3.3.0.M2 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.3.0.M2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8921) simplify inconsistencies w/ JBT and JBDS build/update site URLs

by Nick Boldt (JIRA)

simplify inconsistencies w/ JBT and JBDS build/update site URLs --------------------------------------------------------------- Key: JBIDE-8921 URL: https://issues.jboss.org/browse/JBIDE-8921 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, updatesite Affects Versions: 3.2.1.M1, 3.3.0.M1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.2.1.CR1, 3.3.0.M1 Spoke with Max today and we've decided to simplify the collection of URLs a little. Thus, here's the new structure for development milestones. -- == JBT development milestones (3.2.1.M1, 3.3.0.M1) == === Updates === http://download.jboss.org/jbosstools/updates/stable/helios/ (still 3.2.0.GA, as 3.2.1.M1 is an "unofficial release" at this point; UNCHANGED) http://download.jboss.org/jbosstools/updates/development/? (new landing page, does NOT redirect to /stable/helios/) http://download.jboss.org/jbosstools/updates/development/helios/ (3.2.1.M1, unofficial release) http://download.jboss.org/jbosstools/updates/development/indigo/ (3.3.0.M1 - once vetted, this will be linked from www.jboss.org/tools site & pushed to sourceforge later this week) === Builds === See subfolders of these: http://download.jboss.org/jbosstools/builds/stable/ (previous GAs; was /release/ but now renamed for consistency) http://download.jboss.org/jbosstools/builds/development/ (milestones) ---- == JBDS development milestones (4.1.0.M1) == === Updates === See subfolders of these: http://www.qa.jboss.com/binaries/RHDS/updates/stable/ (previous GAs; UNCHANGED) http://www.qa.jboss.com/binaries/RHDS/updates/development/ (milestones) === Builds === See subfolders of these: http://www.qa.jboss.com/binaries/RHDS/builds/stable/ (previous GAs; UNCHANGED) http://www.qa.jboss.com/binaries/RHDS/builds/development/ (milestones) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4082) Can't change starting state node from graphical editor

by Hedley Proctor (JIRA)

Can't change starting state node from graphical editor ------------------------------------------------------ Key: JBIDE-4082 URL: https://jira.jboss.org/jira/browse/JBIDE-4082 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.1.0 Environment: Windows xp Eclipse 3.3.2, build M20080221-1800 JBoss jBPM Eclipse plugin v3.1.3 SP2 Reporter: Hedley Proctor Fix For: 3.1.0 It doesn't seem possible to change the a starting state node to a normal state node, or vice versa. e.g. if you have a starting state with transitions to a number of states, but you want to insert a new starting state before it and convert the present node to a normal "State" node, it looks like you have to - delete your current starting state node - create a new state node with the same name, transitions, actions etc - add your new starting state node Since state and starting states are very similar, perhaps we could have an option to convert a starting state node to a normal state? e.g. in the properties tab at the bottom perhaps? Then you could just click this button or change the option to convert the node type, without any deleting and recreating. -- 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, 10 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8910) Unable to upgrade from 3.2.0 to 3.2.1.M1 - conflicting dependency of jBPM

by Libor Zoubek (JIRA)

Unable to upgrade from 3.2.0 to 3.2.1.M1 - conflicting dependency of jBPM --------------------------------------------------------------------------- Key: JBIDE-8910 URL: https://issues.jboss.org/browse/JBIDE-8910 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.2.1.M1 Reporter: Libor Zoubek Assignee: Koen Aers Priority: Blocker Cannot complete the install because of a conflicting dependency. Software being installed: jBPM 4 Tools Runtime 4.0.0.v20110506-1208-H111-M1 (org.jboss.tools.jbpm4.feature.feature.group 4.0.0.v20110506-1208-H111-M1) Software currently installed: jBPM 4 Graphical Editor and Tools 4.0.0.v20110215-1501-H35-GA (org.jboss.tools.flow.jpdl4.feature.feature.group 4.0.0.v20110215-1501-H35-GA) Only one of the following can be installed at once: jBPM 4 Graphical Editor and Tools 4.0.0.v20110215-1501-H35-GA (org.jboss.tools.flow.jpdl4.feature.feature.jar 4.0.0.v20110215-1501-H35-GA) jBPM 4 Graphical Editor and Tools 4.0.0.v20110506-1208-H111-M1 (org.jboss.tools.flow.jpdl4.feature.feature.jar 4.0.0.v20110506-1208-H111-M1) Cannot satisfy dependency: From: jBPM 4 Graphical Editor and Tools 4.0.0.v20110215-1501-H35-GA (org.jboss.tools.flow.jpdl4.feature.feature.group 4.0.0.v20110215-1501-H35-GA) To: org.jboss.tools.flow.jpdl4.feature.feature.jar [4.0.0.v20110215-1501-H35-GA] Cannot satisfy dependency: From: jBPM 4 Graphical Editor and Tools 4.0.0.v20110506-1208-H111-M1 (org.jboss.tools.flow.jpdl4.feature.feature.group 4.0.0.v20110506-1208-H111-M1) To: org.jboss.tools.flow.jpdl4.feature.feature.jar [4.0.0.v20110506-1208-H111-M1] Cannot satisfy dependency: From: jBPM 4 Tools Runtime 4.0.0.v20110506-1208-H111-M1 (org.jboss.tools.jbpm4.feature.feature.group 4.0.0.v20110506-1208-H111-M1) To: org.jboss.tools.flow.jpdl4.feature.feature.group [4.0.0.v20110506-1208-H111-M1] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
4
0 / 0

[JBoss JIRA] Issue Comment Edited: (JBIDE-8453) Richfaces 4 new tag names not compatible with JBoss Tools

by Denis Maliarevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8453?page=com.atlassian.jira.plugin... ] Denis Maliarevich edited comment on JBIDE-8453 at 5/14/11 7:44 AM: ------------------------------------------------------------------- VPE is missing the following RF4 tags: rich:collapsibleSubTable rich:collapsibleSubTableToggler rich:dragSource rich:dropTarget rich:hashParam rich:treeModelAdaptor rich:treeModelRecursiveAdaptor rich:treeSelectionChangeListener rich:treeToggleListener rich:validator All the other tags' spelling is fine. was (Author: dmaliarevich): VPE is missing the followong RF4 tags: rich:collapsibleSubTable rich:collapsibleSubTableToggler rich:dragSource rich:dropTarget rich:hashParam rich:treeModelAdaptor rich:treeModelRecursiveAdaptor rich:treeSelectionChangeListener rich:treeToggleListener rich:validator All the other tags' spelling is fine. > Richfaces 4 new tag names not compatible with JBoss Tools > --------------------------------------------------------- > > Key: JBIDE-8453 > URL: https://issues.jboss.org/browse/JBIDE-8453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JSF, Visual Page Editor Templates > Affects Versions: 3.2.0.CR1 > Environment: Tomcat 7.0.8/ Mojarra 2.0.4 > Reporter: Flávio Henrique > Assignee: Denis Maliarevich > Priority: Minor > Fix For: 3.2.1.CR1, 3.3.0.M2 > > > This tag names has changed in Richfaces 4: > toolBar -> RF4: toolbar > toolBarGroup -> RF4: toolbarGroup > toolTip -> RF4: tooltip > Maybe more, so far I found only these. > The change is fine, but brought some problens in a IDE environment and in migration: > 1 - you can still use the old name in JBoss Tools, but the IDE can´t detected that this is wrong for RF4; > 2 - JBoss Tools can only render the preview for the old tag name not for the new tag name; > 3 - this can lead to mistakes for people migratin from 3.X branch like me. > Since JBoss Tools 3.2 CR1 is out, it would be nice that CR2 has the ability to handle this changes. I first post this here, because I don´t know if RF team will take another action to solve this problem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBIDE-8453) Richfaces 4 new tag names not compatible with JBoss Tools

by Denis Maliarevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8453?page=com.atlassian.jira.plugin... ] Denis Maliarevich commented on JBIDE-8453: ------------------------------------------ Committed to trunk and branches/jbosstools-3.2.x. > Richfaces 4 new tag names not compatible with JBoss Tools > --------------------------------------------------------- > > Key: JBIDE-8453 > URL: https://issues.jboss.org/browse/JBIDE-8453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JSF, Visual Page Editor Templates > Affects Versions: 3.2.0.CR1 > Environment: Tomcat 7.0.8/ Mojarra 2.0.4 > Reporter: Flávio Henrique > Assignee: Denis Maliarevich > Priority: Minor > Fix For: 3.2.1.CR1, 3.3.0.M2 > > > This tag names has changed in Richfaces 4: > toolBar -> RF4: toolbar > toolBarGroup -> RF4: toolbarGroup > toolTip -> RF4: tooltip > Maybe more, so far I found only these. > The change is fine, but brought some problens in a IDE environment and in migration: > 1 - you can still use the old name in JBoss Tools, but the IDE can´t detected that this is wrong for RF4; > 2 - JBoss Tools can only render the preview for the old tag name not for the new tag name; > 3 - this can lead to mistakes for people migratin from 3.X branch like me. > Since JBoss Tools 3.2 CR1 is out, it would be nice that CR2 has the ability to handle this changes. I first post this here, because I don´t know if RF team will take another action to solve this problem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBIDE-8453) Richfaces 4 new tag names not compatible with JBoss Tools

by Denis Maliarevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8453?page=com.atlassian.jira.plugin... ] Denis Maliarevich commented on JBIDE-8453: ------------------------------------------ JBIDE-8950 was created to add missing templates. > Richfaces 4 new tag names not compatible with JBoss Tools > --------------------------------------------------------- > > Key: JBIDE-8453 > URL: https://issues.jboss.org/browse/JBIDE-8453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JSF, Visual Page Editor Templates > Affects Versions: 3.2.0.CR1 > Environment: Tomcat 7.0.8/ Mojarra 2.0.4 > Reporter: Flávio Henrique > Assignee: Denis Maliarevich > Priority: Minor > Fix For: 3.2.1.CR1, 3.3.0.M2 > > > This tag names has changed in Richfaces 4: > toolBar -> RF4: toolbar > toolBarGroup -> RF4: toolbarGroup > toolTip -> RF4: tooltip > Maybe more, so far I found only these. > The change is fine, but brought some problens in a IDE environment and in migration: > 1 - you can still use the old name in JBoss Tools, but the IDE can´t detected that this is wrong for RF4; > 2 - JBoss Tools can only render the preview for the old tag name not for the new tag name; > 3 - this can lead to mistakes for people migratin from 3.X branch like me. > Since JBoss Tools 3.2 CR1 is out, it would be nice that CR2 has the ability to handle this changes. I first post this here, because I don´t know if RF team will take another action to solve this problem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBIDE-8453) Richfaces 4 new tag names not compatible with JBoss Tools

by Denis Maliarevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8453?page=com.atlassian.jira.plugin... ] Denis Maliarevich commented on JBIDE-8453: ------------------------------------------ VPE is missing the followong RF4 tags: rich:collapsibleSubTable rich:collapsibleSubTableToggler rich:dragSource rich:dropTarget rich:hashParam rich:treeModelAdaptor rich:treeModelRecursiveAdaptor rich:treeSelectionChangeListener rich:treeToggleListener rich:validator All the other tags' spelling is fine. > Richfaces 4 new tag names not compatible with JBoss Tools > --------------------------------------------------------- > > Key: JBIDE-8453 > URL: https://issues.jboss.org/browse/JBIDE-8453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JSF, Visual Page Editor Templates > Affects Versions: 3.2.0.CR1 > Environment: Tomcat 7.0.8/ Mojarra 2.0.4 > Reporter: Flávio Henrique > Assignee: Denis Maliarevich > Priority: Minor > Fix For: 3.2.1.CR1, 3.3.0.M2 > > > This tag names has changed in Richfaces 4: > toolBar -> RF4: toolbar > toolBarGroup -> RF4: toolbarGroup > toolTip -> RF4: tooltip > Maybe more, so far I found only these. > The change is fine, but brought some problens in a IDE environment and in migration: > 1 - you can still use the old name in JBoss Tools, but the IDE can´t detected that this is wrong for RF4; > 2 - JBoss Tools can only render the preview for the old tag name not for the new tag name; > 3 - this can lead to mistakes for people migratin from 3.X branch like me. > Since JBoss Tools 3.2 CR1 is out, it would be nice that CR2 has the ability to handle this changes. I first post this here, because I don´t know if RF team will take another action to solve this problem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBIDE-8453) Richfaces 4 new tag names not compatible with JBoss Tools

by Denis Maliarevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8453?page=com.atlassian.jira.plugin... ] Denis Maliarevich commented on JBIDE-8453: ------------------------------------------ rf4 templates were renamed and re-ordered. > Richfaces 4 new tag names not compatible with JBoss Tools > --------------------------------------------------------- > > Key: JBIDE-8453 > URL: https://issues.jboss.org/browse/JBIDE-8453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JSF, Visual Page Editor Templates > Affects Versions: 3.2.0.CR1 > Environment: Tomcat 7.0.8/ Mojarra 2.0.4 > Reporter: Flávio Henrique > Assignee: Denis Maliarevich > Priority: Minor > Fix For: 3.2.1.CR1, 3.3.0.M2 > > > This tag names has changed in Richfaces 4: > toolBar -> RF4: toolbar > toolBarGroup -> RF4: toolbarGroup > toolTip -> RF4: tooltip > Maybe more, so far I found only these. > The change is fine, but brought some problens in a IDE environment and in migration: > 1 - you can still use the old name in JBoss Tools, but the IDE can´t detected that this is wrong for RF4; > 2 - JBoss Tools can only render the preview for the old tag name not for the new tag name; > 3 - this can lead to mistakes for people migratin from 3.X branch like me. > Since JBoss Tools 3.2 CR1 is out, it would be nice that CR2 has the ability to handle this changes. I first post this here, because I don´t know if RF team will take another action to solve this problem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBIDE-8453) Richfaces 4 new tag names not compatible with JBoss Tools

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8453?page=com.atlassian.jira.plugin... ] Yahor Radtsevich updated JBIDE-8453: ------------------------------------ Fix Version/s: (was: 3.2.1.M1) > Richfaces 4 new tag names not compatible with JBoss Tools > --------------------------------------------------------- > > Key: JBIDE-8453 > URL: https://issues.jboss.org/browse/JBIDE-8453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JSF, Visual Page Editor Templates > Affects Versions: 3.2.0.CR1 > Environment: Tomcat 7.0.8/ Mojarra 2.0.4 > Reporter: Flávio Henrique > Assignee: Yahor Radtsevich > Priority: Minor > Fix For: 3.2.1.CR1, 3.3.0.M2 > > > This tag names has changed in Richfaces 4: > toolBar -> RF4: toolbar > toolBarGroup -> RF4: toolbarGroup > toolTip -> RF4: tooltip > Maybe more, so far I found only these. > The change is fine, but brought some problens in a IDE environment and in migration: > 1 - you can still use the old name in JBoss Tools, but the IDE can´t detected that this is wrong for RF4; > 2 - JBoss Tools can only render the preview for the old tag name not for the new tag name; > 3 - this can lead to mistakes for people migratin from 3.X branch like me. > Since JBoss Tools 3.2 CR1 is out, it would be nice that CR2 has the ability to handle this changes. I first post this here, because I don´t know if RF team will take another action to solve this problem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
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 May 2011