October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15251) Cancel button doesn't work in Forge 'installing..' dialogs

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15251?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-15251: ----------------------------------- The Forge 1 wizards were implemented while awaiting Forge 2. Adding the option to cancel the installation is never going to work completely because there is no way to cancel the already issued Forge command. So rather then losing cycles trying to fix something that cannot be fixed properly, I would resolve this issue as "Won't Fix" and concentrate on the upcoming Forge 2 wizards. > Cancel button doesn't work in Forge 'installing..' dialogs > ---------------------------------------------------------- > > Key: JBIDE-15251 > URL: https://issues.jboss.org/browse/JBIDE-15251 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.CR1 > Reporter: Pavol Srna > Priority: Critical > > ASSERT ~/.forge is deleted > EXEC run Forge generate entities wizard > EXEC hit cancel button on 'installing hibernate-tools' dialog > Dialog doesn't terminate and hibernate-tools plugin is installed anyway. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15251) Cancel button doesn't work in Forge 'installing..' dialogs

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15251?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-15251: ------------------------------ Assignee: Koen Aers > Cancel button doesn't work in Forge 'installing..' dialogs > ---------------------------------------------------------- > > Key: JBIDE-15251 > URL: https://issues.jboss.org/browse/JBIDE-15251 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.CR1 > Reporter: Pavol Srna > Assignee: Koen Aers > Priority: Critical > > ASSERT ~/.forge is deleted > EXEC run Forge generate entities wizard > EXEC hit cancel button on 'installing hibernate-tools' dialog > Dialog doesn't terminate and hibernate-tools plugin is installed anyway. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15251) Cancel button doesn't work in Forge 'installing..' dialogs

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15251?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-15251. ------------------------------- Resolution: Won't Fix > Cancel button doesn't work in Forge 'installing..' dialogs > ---------------------------------------------------------- > > Key: JBIDE-15251 > URL: https://issues.jboss.org/browse/JBIDE-15251 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.CR1 > Reporter: Pavol Srna > Assignee: Koen Aers > Priority: Critical > > ASSERT ~/.forge is deleted > EXEC run Forge generate entities wizard > EXEC hit cancel button on 'installing hibernate-tools' dialog > Dialog doesn't terminate and hibernate-tools plugin is installed anyway. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10949) Drag and Drop to the Forge Console

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10949?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-10949: ------------------------------ Fix Version/s: 4.2.x (was: 3.3.x) > Drag and Drop to the Forge Console > ---------------------------------- > > Key: JBIDE-10949 > URL: https://issues.jboss.org/browse/JBIDE-10949 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Reporter: Jim Tyrrell > Assignee: Koen Aers > Fix For: 4.2.x > > > It would be great to be able to drag and drop artifacts from the project explorer into the Forge Console. ie instead of having to cd a large path, just drag the component in. Easier then maybe a right click and open... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10949) Drag and Drop to the Forge Console

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10949?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-10949: ----------------------------------- This will definitely not be done anymore for the old Forge 1 shell but probably a good idea to keep for the Forge 2 shell integration if it comes around > Drag and Drop to the Forge Console > ---------------------------------- > > Key: JBIDE-10949 > URL: https://issues.jboss.org/browse/JBIDE-10949 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Reporter: Jim Tyrrell > Assignee: Koen Aers > Fix For: 4.2.x > > > It would be great to be able to drag and drop artifacts from the project explorer into the Forge Console. ie instead of having to cd a large path, just drag the component in. Easier then maybe a right click and open... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9660) Cmd+4/Forge menu should be possible to activate without having the forge shell active

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9660?page=com.atlassian.jira.plugin... ] Koen Aers resolved JBIDE-9660. ------------------------------ Resolution: Done > Cmd+4/Forge menu should be possible to activate without having the forge shell active > ------------------------------------------------------------------------------------- > > Key: JBIDE-9660 > URL: https://issues.jboss.org/browse/JBIDE-9660 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > if the forge shell only is possible to show when the forge shell is in focus then its just a fancy ctrl+space thing. > Should be able to call it from outside of the forge UI so it becomes easily accessible. > Challenge is though to ensure forge is in the right directory - but taking the current selection as the directory to ensure forge is operating in should be enough. > Maybe the shell command should show the path for current selection so possible to know what context it will be executed in ? > Possibly even provide a "breadcrumb" style ui allowing users to click on a path segment to choose at what level it will operate. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9660) Cmd+4/Forge menu should be possible to activate without having the forge shell active

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9660?page=com.atlassian.jira.plugin... ] Koen Aers updated JBIDE-9660: ----------------------------- Fix Version/s: 4.2.0.Alpha1 4.1.1.Alpha1 (was: 3.3.x) > Cmd+4/Forge menu should be possible to activate without having the forge shell active > ------------------------------------------------------------------------------------- > > Key: JBIDE-9660 > URL: https://issues.jboss.org/browse/JBIDE-9660 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > if the forge shell only is possible to show when the forge shell is in focus then its just a fancy ctrl+space thing. > Should be able to call it from outside of the forge UI so it becomes easily accessible. > Challenge is though to ensure forge is in the right directory - but taking the current selection as the directory to ensure forge is operating in should be enough. > Maybe the shell command should show the path for current selection so possible to know what context it will be executed in ? > Possibly even provide a "breadcrumb" style ui allowing users to click on a path segment to choose at what level it will operate. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9660) Cmd+4/Forge menu should be possible to activate without having the forge shell active

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9660?page=com.atlassian.jira.plugin... ] Koen Aers commented on JBIDE-9660: ---------------------------------- This issue is completely solved by the inclusion of F2. Forge commands are now full fledged wizards, no need to have a shell active or in focus. > Cmd+4/Forge menu should be possible to activate without having the forge shell active > ------------------------------------------------------------------------------------- > > Key: JBIDE-9660 > URL: https://issues.jboss.org/browse/JBIDE-9660 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > if the forge shell only is possible to show when the forge shell is in focus then its just a fancy ctrl+space thing. > Should be able to call it from outside of the forge UI so it becomes easily accessible. > Challenge is though to ensure forge is in the right directory - but taking the current selection as the directory to ensure forge is operating in should be enough. > Maybe the shell command should show the path for current selection so possible to know what context it will be executed in ? > Possibly even provide a "breadcrumb" style ui allowing users to click on a path segment to choose at what level it will operate. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11998) Add a 'debug' option when running Forge

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11998?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-11998: ------------------------------ Fix Version/s: (was: 3.3.x) > Add a 'debug' option when running Forge > --------------------------------------- > > Key: JBIDE-11998 > URL: https://issues.jboss.org/browse/JBIDE-11998 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Reporter: Koen Aers > Assignee: Koen Aers > > This should be controlled by a preference setting. If this preference is set, Forge will be launched in debug mode and the Eclipse debugger will be automatically attached so that execution halts on the breakpoints that are set. This is especially useful when developing and testing Forge plugins but of course also when working on the Forge runtime code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11998) Add a 'debug' option when running Forge

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11998?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-11998. ------------------------------- Resolution: Out of Date > Add a 'debug' option when running Forge > --------------------------------------- > > Key: JBIDE-11998 > URL: https://issues.jboss.org/browse/JBIDE-11998 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Reporter: Koen Aers > Assignee: Koen Aers > > This should be controlled by a preference setting. If this preference is set, Forge will be launched in debug mode and the Eclipse debugger will be automatically attached so that execution halts on the breakpoints that are set. This is especially useful when developing and testing Forge plugins but of course also when working on the Forge runtime code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 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 October 2013