October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13165) Forge Launches are not Correctly Removed

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13165?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-13165: ----------------------------------- This was fixed earlier. > Forge Launches are not Correctly Removed > ---------------------------------------- > > Key: JBIDE-13165 > URL: https://issues.jboss.org/browse/JBIDE-13165 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.0.0.CR1 > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Minor > > * Start Forge in a new workspace > * Stop Forge > * Start Forge again > => 2 errors in Error View > This is the stack trace: > java.lang.NullPointerException > at org.jboss.tools.forge.core.process.ForgeLaunchHelper$ForgeLaunchListener.launchRemoved(ForgeLaunchHelper.java:184) > at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.run(LaunchManager.java:443) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.notify(LaunchManager.java:428) > at org.eclipse.debug.internal.core.LaunchManager.fireUpdate(LaunchManager.java:1017) > at org.eclipse.debug.internal.core.LaunchManager.removeLaunch(LaunchManager.java:2224) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationManager.removeTerminatedLaunches(LaunchConfigurationManager.java:329) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationManager.launchAdded(LaunchConfigurationManager.java:315) > at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.run(LaunchManager.java:440) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.notify(LaunchManager.java:428) > at org.eclipse.debug.internal.core.LaunchManager.fireUpdate(LaunchManager.java:1017) > at org.eclipse.debug.internal.core.LaunchManager.addLaunch(LaunchManager.java:688) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:844) > at org.jboss.tools.forge.core.process.ForgeLaunchHelper.doLaunch(ForgeLaunchHelper.java:69) > at org.jboss.tools.forge.core.process.ForgeLaunchHelper.launch(ForgeLaunchHelper.java:53) > at org.jboss.tools.forge.core.process.ForgeAbstractRuntime.start(ForgeAbstractRuntime.java:50) > at org.jboss.tools.forge.ui.util.ForgeHelper$1.run(ForgeHelper.java:41) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) -- 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-13165) Forge Launches are not Correctly Removed

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13165?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-13165: ------------------------------ Fix Version/s: (was: 4.0.x) (was: 4.1.x) > Forge Launches are not Correctly Removed > ---------------------------------------- > > Key: JBIDE-13165 > URL: https://issues.jboss.org/browse/JBIDE-13165 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.0.0.CR1 > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Minor > > * Start Forge in a new workspace > * Stop Forge > * Start Forge again > => 2 errors in Error View > This is the stack trace: > java.lang.NullPointerException > at org.jboss.tools.forge.core.process.ForgeLaunchHelper$ForgeLaunchListener.launchRemoved(ForgeLaunchHelper.java:184) > at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.run(LaunchManager.java:443) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.notify(LaunchManager.java:428) > at org.eclipse.debug.internal.core.LaunchManager.fireUpdate(LaunchManager.java:1017) > at org.eclipse.debug.internal.core.LaunchManager.removeLaunch(LaunchManager.java:2224) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationManager.removeTerminatedLaunches(LaunchConfigurationManager.java:329) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationManager.launchAdded(LaunchConfigurationManager.java:315) > at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.run(LaunchManager.java:440) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.notify(LaunchManager.java:428) > at org.eclipse.debug.internal.core.LaunchManager.fireUpdate(LaunchManager.java:1017) > at org.eclipse.debug.internal.core.LaunchManager.addLaunch(LaunchManager.java:688) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:844) > at org.jboss.tools.forge.core.process.ForgeLaunchHelper.doLaunch(ForgeLaunchHelper.java:69) > at org.jboss.tools.forge.core.process.ForgeLaunchHelper.launch(ForgeLaunchHelper.java:53) > at org.jboss.tools.forge.core.process.ForgeAbstractRuntime.start(ForgeAbstractRuntime.java:50) > at org.jboss.tools.forge.ui.util.ForgeHelper$1.run(ForgeHelper.java:41) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) -- 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-15645) Revisit archetype switching based on runtime (community/product) and runtime level (ee6 vs ee7)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15645?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-15645: -------------------------------- Description: Enterprise/Community versions of archetypes will no longer be switchable through the -Denterprise switch. Different GAV coordinates will need to be used instead. We need to come up with changes in both stacks.yaml format and JBDS to cope with this Some discussion on etherpad : http://ether-man.rhcloud.com/p/funkyarchetype was: Enterprise/Community versions of archetypes will no longer be switchable through the -Denterprise switch. Different GAV coordinates will need to be used instead. We need to come up with changes in both stacks.yaml format and JBDS to cope with this > Revisit archetype switching based on runtime (community/product) and runtime level (ee6 vs ee7) > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-15645 > URL: https://issues.jboss.org/browse/JBIDE-15645 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: project-examples > Affects Versions: 4.1.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.1.1.Beta1 > > > Enterprise/Community versions of archetypes will no longer be switchable through the -Denterprise switch. Different GAV coordinates will need to be used instead. > We need to come up with changes in both stacks.yaml format and JBDS to cope with this > Some discussion on etherpad : http://ether-man.rhcloud.com/p/funkyarchetype -- 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-13573) Add "Forge Preferences" action to Forge Console

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13573?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-13573. ------------------------------- Resolution: Won't Fix > Add "Forge Preferences" action to Forge Console > ----------------------------------------------- > > Key: JBIDE-13573 > URL: https://issues.jboss.org/browse/JBIDE-13573 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.1.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Koen Aers > > It would be good to have this action or, at least, the Debug/Run toggle button in the Forge Console view. -- 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-13573) Add "Forge Preferences" action to Forge Console

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13573?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-13573: ------------------------------ Fix Version/s: (was: 4.1.x) > Add "Forge Preferences" action to Forge Console > ----------------------------------------------- > > Key: JBIDE-13573 > URL: https://issues.jboss.org/browse/JBIDE-13573 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.1.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Koen Aers > > It would be good to have this action or, at least, the Debug/Run toggle button in the Forge Console view. -- 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-13573) Add "Forge Preferences" action to Forge Console

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13573?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-13573: ----------------------------------- With Forge 2 around the corner it's probably not needed to add this on the Forge 1 console anymore. I'm going to resolve as 'Won't Fix' but feel free to reopen if you think it should be reconsidered. > Add "Forge Preferences" action to Forge Console > ----------------------------------------------- > > Key: JBIDE-13573 > URL: https://issues.jboss.org/browse/JBIDE-13573 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.1.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Koen Aers > > It would be good to have this action or, at least, the Debug/Run toggle button in the Forge Console view. -- 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-15597) Environmental Variables UI

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-15597 at 10/9/13 11:18 AM: -------------------------------------------------------------------- [~mwigglesworth-redhat] As discussed having the button in the 2nd page is IMHO not a good idea. The 2nd page is all about the local workspace "project" as opposed to the remote "application" in OpenShift. The env vars are only concerning the remote OpenShift "application", thus the widgets should make it to the 1st page (or an additional page that is concerning the OpenShift "application"). The 2nd thing that we discussed, the label/text input that shows you if there are env vars set or not: you were completely convinced that this was only additional clutter and that you would have to hit the button and look at the actual values anyway. I get this but after discussing things with [~maxandersen] we still thought that this label could make sense. Env variables would change the way an application is created. The actual request will differ with or without them. Having a brief information in the UI that shows if the app is created with or without env vars ("yes the app is created WITH env vars" or "no it'll get created without any env vars") is a valuable information that matters for the user. was (Author: adietish): [~mwigglesworth-redhat] As discussed having the button in the 2nd page is IMHO not a good idea. The 2nd page is all about the local workspace "project" as opposed to the remote "application" in OpenShift. The env vars are only concerning the remote OpenShift "application", thus the widgets should make it to the 1st page (or an additional page that is concerning the OpenShift "application"). The 2nd thing that we discussed, the label/text input that shows you if there are env vars set or not: you were completely convinced that this was only additional clutter and that you would have to hit the button and look at the actual values anyway. I get this but after discussing things with [~maxandersen] we still thought that this label could make sense. Env variables would change the way an application is created. The actual request will differ with or without them. Having a brief information in the UI that shows if the app is created with or without env vars ("yes the app is created WITH env vars" or "no it'll get created without any env vars") is a valuable information for the user. > Environmental Variables UI > -------------------------- > > Key: JBIDE-15597 > URL: https://issues.jboss.org/browse/JBIDE-15597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Martes Wigglesworth > Priority: Blocker > Attachments: Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.png, jira-JBIDE-15597-newapplication-variables-screenshot.jpeg, jira-JBIDE-15597-setupprojectview-variablesbutton-screenshot.jpeg, jira-JBIDE-15597-setupprojectview-variablesbutton-twochoices-screenshot.jpeg, manage-keys.png, openshift-newappwizard-config_and_server_settings.jpeg > > > GUI development tasking for creating the workflow for inserting environmental variable artifacts into the application being created via the JBDT OpenShift plugin. -- 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-15597) Environmental Variables UI

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-15597 at 10/9/13 11:16 AM: -------------------------------------------------------------------- [~mwigglesworth-redhat]: having double expansion like you suggest seems not a good idea imho. This is very uncommon for Eclipse. I suggest you put it into the "Advanced" section. Having the table in the page makes the page grow beyond acceptable size (it's already very very crowded). I therefore added a shortened label that tells one that there are env variables set. You can edit them and get to the table UI by hitting "Edit..." (see !Environmental Variables UI WorkFlow.png|thumbnail!) was (Author: adietish): [~mwigglesworth-redhat]: having double expansion like you suggest seems not a good idea imho. This is very uncommon for Eclipse. I suggest you put it into the "Advanced" section. Having the table in the page makes the page grow beyond acceptable size (it's already very very crowded). I therefore added a shortened label that tells one that there are env variables set. You can edit them and get to the table UI by hitting "Edit..." (see !Environmental Variables UI WorkFlow.png!) > Environmental Variables UI > -------------------------- > > Key: JBIDE-15597 > URL: https://issues.jboss.org/browse/JBIDE-15597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Martes Wigglesworth > Priority: Blocker > Attachments: Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.png, jira-JBIDE-15597-newapplication-variables-screenshot.jpeg, jira-JBIDE-15597-setupprojectview-variablesbutton-screenshot.jpeg, jira-JBIDE-15597-setupprojectview-variablesbutton-twochoices-screenshot.jpeg, manage-keys.png, openshift-newappwizard-config_and_server_settings.jpeg > > > GUI development tasking for creating the workflow for inserting environmental variable artifacts into the application being created via the JBDT OpenShift plugin. -- 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-15597) Environmental Variables UI

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15597: ------------------------------------------ [~mwigglesworth-redhat] As discussed having the button in the 2nd page is IMHO not a good idea. The 2nd page is all about the local workspace "project" as opposed to the remote "application" in OpenShift. The env vars are only concerning the remote OpenShift "application", thus the widgets should make it to the 1st page (or an additional page that is concerning the OpenShift "application"). The 2nd thing that we discussed, the label/text input that shows you if there are env vars set or not: you were completely convinced that this was only additional clutter and that you would have to hit the button and look at the actual values anyway. I get this but after discussing things with [~maxandersen] we still thought that this label could make sense. Env variables would change the way an application is created. The actual request will differ with or without them. Having a brief information in the UI that shows if the app is created with or without env vars ("yes the app is created WITH env vars" or "no it'll get created without any env vars") is a valuable information for the user. > Environmental Variables UI > -------------------------- > > Key: JBIDE-15597 > URL: https://issues.jboss.org/browse/JBIDE-15597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Martes Wigglesworth > Priority: Blocker > Attachments: Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.png, jira-JBIDE-15597-newapplication-variables-screenshot.jpeg, jira-JBIDE-15597-setupprojectview-variablesbutton-screenshot.jpeg, jira-JBIDE-15597-setupprojectview-variablesbutton-twochoices-screenshot.jpeg, manage-keys.png, openshift-newappwizard-config_and_server_settings.jpeg > > > GUI development tasking for creating the workflow for inserting environmental variable artifacts into the application being created via the JBDT OpenShift plugin. -- 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-14615) Forge set VERBOSE true command automatically opens Error Log tab

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14615?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-14615: ------------------------------ Fix Version/s: 4.2.x (was: 4.1.x) > Forge set VERBOSE true command automatically opens Error Log tab > ---------------------------------------------------------------- > > Key: JBIDE-14615 > URL: https://issues.jboss.org/browse/JBIDE-14615 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.1.0.Beta1 > Reporter: Michelle Murray > Assignee: Koen Aers > Fix For: 4.2.x > > > Related to JBIDE-11217, the Forge 'set VERBOSE true' command interacts with the IDE by recording exceptions in the error log. Would it be useful to users to automatically open (but not necessarily bring to the foreground) the Error Log tab when users issue the 'set VERBOSE true' command? -- 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