[JBoss JIRA] (JBIDE-15840) CLONE - Can't restart application through server adapter
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15840?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-15840:
----------------------------------
Labels: (was: respin-b)
> CLONE - Can't restart application through server adapter
> --------------------------------------------------------
>
> Key: JBIDE-15840
> URL: https://issues.jboss.org/browse/JBIDE-15840
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Marián Labuda
> Assignee: Max Rydahl Andersen
> Fix For: 4.2.0.Alpha1
>
>
> ASSERT: have created OpenShift application
> EXEC: restart through OpenShift explorer
> ASSERT: application is restarting
> EXEC: restart through created server adapter (context menu -> OpenShift -> Restart Aplication)
> ASSERT: nothing happens
> In the Eclipse log you'll spot the following:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.express.internal.ui.job.RestartApplicationJob.<init>(RestartApplicationJob.java:33)
> at org.jboss.tools.openshift.express.internal.ui.serverviewer.actionDelegate.RestartApplicationActionProvider$RestartApplicationAction.restartApplication(RestartApplicationActionProvider.java:48)
> at org.jboss.tools.openshift.express.internal.ui.serverviewer.actionDelegate.RestartApplicationActionProvider$RestartApplicationAction.run(RestartApplicationActionProvider.java:42)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {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, 7 months
[JBoss JIRA] (JBIDE-15812) Can't restart application through server adapter
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15812?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-15812:
----------------------------------
Affects Version/s: (was: 4.2.0.Alpha1)
> Can't restart application through server adapter
> ------------------------------------------------
>
> Key: JBIDE-15812
> URL: https://issues.jboss.org/browse/JBIDE-15812
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Marián Labuda
> Assignee: Max Rydahl Andersen
> Labels: respin-b
> Fix For: 4.1.1.Beta1
>
>
> ASSERT: have created OpenShift application
> EXEC: restart through OpenShift explorer
> ASSERT: application is restarting
> EXEC: restart through created server adapter (context menu -> OpenShift -> Restart Aplication)
> ASSERT: nothing happens
> In the Eclipse log you'll spot the following:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.express.internal.ui.job.RestartApplicationJob.<init>(RestartApplicationJob.java:33)
> at org.jboss.tools.openshift.express.internal.ui.serverviewer.actionDelegate.RestartApplicationActionProvider$RestartApplicationAction.restartApplication(RestartApplicationActionProvider.java:48)
> at org.jboss.tools.openshift.express.internal.ui.serverviewer.actionDelegate.RestartApplicationActionProvider$RestartApplicationAction.run(RestartApplicationActionProvider.java:42)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {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, 7 months
[JBoss JIRA] (JBIDE-15840) CLONE - Can't restart application through server adapter
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15840?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-15840:
----------------------------------
Fix Version/s: (was: 4.1.1.Beta1)
> CLONE - Can't restart application through server adapter
> --------------------------------------------------------
>
> Key: JBIDE-15840
> URL: https://issues.jboss.org/browse/JBIDE-15840
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1
> Reporter: Marián Labuda
> Assignee: Max Rydahl Andersen
> Labels: respin-b
> Fix For: 4.2.0.Alpha1
>
>
> ASSERT: have created OpenShift application
> EXEC: restart through OpenShift explorer
> ASSERT: application is restarting
> EXEC: restart through created server adapter (context menu -> OpenShift -> Restart Aplication)
> ASSERT: nothing happens
> In the Eclipse log you'll spot the following:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.express.internal.ui.job.RestartApplicationJob.<init>(RestartApplicationJob.java:33)
> at org.jboss.tools.openshift.express.internal.ui.serverviewer.actionDelegate.RestartApplicationActionProvider$RestartApplicationAction.restartApplication(RestartApplicationActionProvider.java:48)
> at org.jboss.tools.openshift.express.internal.ui.serverviewer.actionDelegate.RestartApplicationActionProvider$RestartApplicationAction.run(RestartApplicationActionProvider.java:42)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {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, 7 months
[JBoss JIRA] (JBIDE-15840) CLONE - Can't restart application through server adapter
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-15840:
-------------------------------------
Summary: CLONE - Can't restart application through server adapter
Key: JBIDE-15840
URL: https://issues.jboss.org/browse/JBIDE-15840
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1
Reporter: Marián Labuda
Assignee: Max Rydahl Andersen
Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
ASSERT: have created OpenShift application
EXEC: restart through OpenShift explorer
ASSERT: application is restarting
EXEC: restart through created server adapter (context menu -> OpenShift -> Restart Aplication)
ASSERT: nothing happens
In the Eclipse log you'll spot the following:
{code}
java.lang.NullPointerException
at org.jboss.tools.openshift.express.internal.ui.job.RestartApplicationJob.<init>(RestartApplicationJob.java:33)
at org.jboss.tools.openshift.express.internal.ui.serverviewer.actionDelegate.RestartApplicationActionProvider$RestartApplicationAction.restartApplication(RestartApplicationActionProvider.java:48)
at org.jboss.tools.openshift.express.internal.ui.serverviewer.actionDelegate.RestartApplicationActionProvider$RestartApplicationAction.run(RestartApplicationActionProvider.java:42)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
{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, 7 months
[JBoss JIRA] (TOOLSDOC-414) Update screen captures in docs that explicitly reference JBDS 7.0
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-414?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-414:
-------------------------------------
Description:
Screen captures that will need updating for 7.1 docs
*Installation Guide*
* Figure 3.1. JBoss Developer Studio Downloads Listed on the Customer Portal [removed as refs specific JBDS version]
* Figure 3.2. Installation Step 3: Select Target Folder [done]
* Figure 3.3. Installation Step 4: Select Java VM [done]
* Figure 3.5. Installation Step 7: Installation Progress in Finished State [done]
* Figure 3.6. Install JBoss Developer Studio BYOE via Eclipse Marketplace
* Figure 3.7. Confirm Selected Features Window
* Figure 3.10. Work from an Online Website
* Figure 3.11. work from a Local Copy of the Update .zip File
* Figure 3.12. Available Software Window Listing JBoss Developer Studio 7.0 - Bring Your Own Eclipse
* Figure 6.2. Uninstall JBoss Developer Studio via Eclipse Marketplace
* Figure 6.3. Confirm Selected Features Window
*Migration Guide*
* Figure 3.1. jbdevstudio.ini File Open in a Text Editor
*Getting Started Guide* (all Fig. shared with Installation Guide)
* Figure 3.1. JBoss Developer Studio Downloads Listed on the Customer Portal [removed as refs specific JBDS version]
* Figure 3.2. Installation Step 3: Select Target Folder [done]
* Figure 3.3. Installation Step 4: Select Java VM [done]
* Figure 3.5. Installation Step 7: Installation Progress in Finished State [done]
*User Guide*
* Figure 2.4. JBoss Buzz
* Figure 2.22. Set Cheat Sheet Behavior in Project Examples Pane of Preferences Window
was:
Screen captures that will need updating for 7.1 docs
*Installation Guide*
* Figure 3.1. JBoss Developer Studio Downloads Listed on the Customer Portal
* Figure 3.2. Installation Step 3: Select Target Folder [done]
* Figure 3.3. Installation Step 4: Select Java VM [done]
* Figure 3.5. Installation Step 7: Installation Progress in Finished State [done]
* Figure 3.6. Install JBoss Developer Studio BYOE via Eclipse Marketplace
* Figure 3.7. Confirm Selected Features Window
* Figure 3.10. Work from an Online Website
* Figure 3.11. work from a Local Copy of the Update .zip File
* Figure 3.12. Available Software Window Listing JBoss Developer Studio 7.0 - Bring Your Own Eclipse
* Figure 6.2. Uninstall JBoss Developer Studio via Eclipse Marketplace
* Figure 6.3. Confirm Selected Features Window
*Migration Guide*
* Figure 3.1. jbdevstudio.ini File Open in a Text Editor
*Getting Started Guide* (all Fig. shared with Installation Guide)
* Figure 3.1. JBoss Developer Studio Downloads Listed on the Customer Portal
* Figure 3.2. Installation Step 3: Select Target Folder [done]
* Figure 3.3. Installation Step 4: Select Java VM [done]
* Figure 3.5. Installation Step 7: Installation Progress in Finished State [done]
*User Guide*
* Figure 2.4. JBoss Buzz
* Figure 2.22. Set Cheat Sheet Behavior in Project Examples Pane of Preferences Window
> Update screen captures in docs that explicitly reference JBDS 7.0
> -----------------------------------------------------------------
>
> Key: TOOLSDOC-414
> URL: https://issues.jboss.org/browse/TOOLSDOC-414
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Getting Started Guide, Installation Guide, Migration Guide, User Guide
> Affects Versions: 4.1.1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.1
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Screen captures that will need updating for 7.1 docs
> *Installation Guide*
> * Figure 3.1. JBoss Developer Studio Downloads Listed on the Customer Portal [removed as refs specific JBDS version]
> * Figure 3.2. Installation Step 3: Select Target Folder [done]
> * Figure 3.3. Installation Step 4: Select Java VM [done]
> * Figure 3.5. Installation Step 7: Installation Progress in Finished State [done]
> * Figure 3.6. Install JBoss Developer Studio BYOE via Eclipse Marketplace
> * Figure 3.7. Confirm Selected Features Window
> * Figure 3.10. Work from an Online Website
> * Figure 3.11. work from a Local Copy of the Update .zip File
> * Figure 3.12. Available Software Window Listing JBoss Developer Studio 7.0 - Bring Your Own Eclipse
> * Figure 6.2. Uninstall JBoss Developer Studio via Eclipse Marketplace
> * Figure 6.3. Confirm Selected Features Window
> *Migration Guide*
> * Figure 3.1. jbdevstudio.ini File Open in a Text Editor
> *Getting Started Guide* (all Fig. shared with Installation Guide)
> * Figure 3.1. JBoss Developer Studio Downloads Listed on the Customer Portal [removed as refs specific JBDS version]
> * Figure 3.2. Installation Step 3: Select Target Folder [done]
> * Figure 3.3. Installation Step 4: Select Java VM [done]
> * Figure 3.5. Installation Step 7: Installation Progress in Finished State [done]
> *User Guide*
> * Figure 2.4. JBoss Buzz
> * Figure 2.22. Set Cheat Sheet Behavior in Project Examples Pane of Preferences Window
--
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, 7 months
[JBoss JIRA] (TOOLSDOC-414) Update screen captures in docs that explicitly reference JBDS 7.0
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-414?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-414:
-------------------------------------
Description:
Screen captures that will need updating for 7.1 docs
*Installation Guide*
* Figure 3.1. JBoss Developer Studio Downloads Listed on the Customer Portal
* Figure 3.2. Installation Step 3: Select Target Folder [done]
* Figure 3.3. Installation Step 4: Select Java VM [done]
* Figure 3.5. Installation Step 7: Installation Progress in Finished State [done]
* Figure 3.6. Install JBoss Developer Studio BYOE via Eclipse Marketplace
* Figure 3.7. Confirm Selected Features Window
* Figure 3.10. Work from an Online Website
* Figure 3.11. work from a Local Copy of the Update .zip File
* Figure 3.12. Available Software Window Listing JBoss Developer Studio 7.0 - Bring Your Own Eclipse
* Figure 6.2. Uninstall JBoss Developer Studio via Eclipse Marketplace
* Figure 6.3. Confirm Selected Features Window
*Migration Guide*
* Figure 3.1. jbdevstudio.ini File Open in a Text Editor
*Getting Started Guide* (all Fig. shared with Installation Guide)
* Figure 3.1. JBoss Developer Studio Downloads Listed on the Customer Portal
* Figure 3.2. Installation Step 3: Select Target Folder [done]
* Figure 3.3. Installation Step 4: Select Java VM [done]
* Figure 3.5. Installation Step 7: Installation Progress in Finished State [done]
*User Guide*
* Figure 2.4. JBoss Buzz
* Figure 2.22. Set Cheat Sheet Behavior in Project Examples Pane of Preferences Window
was:
Screen captures that will need updating for 7.1 docs
*Installation Guide*
* Figure 3.1. JBoss Developer Studio Downloads Listed on the Customer Portal
* Figure 3.2. Installation Step 3: Select Target Folder
* Figure 3.3. Installation Step 4: Select Java VM
* Figure 3.5. Installation Step 7: Installation Progress in Finished State
* Figure 3.6. Install JBoss Developer Studio BYOE via Eclipse Marketplace
* Figure 3.7. Confirm Selected Features Window
* Figure 3.10. Work from an Online Website
* Figure 3.11. work from a Local Copy of the Update .zip File
* Figure 3.12. Available Software Window Listing JBoss Developer Studio 7.0 - Bring Your Own Eclipse
* Figure 6.2. Uninstall JBoss Developer Studio via Eclipse Marketplace
* Figure 6.3. Confirm Selected Features Window
*Migration Guide*
* Figure 3.1. jbdevstudio.ini File Open in a Text Editor
*Getting Started Guide* (all Fig. shared with Installation Guide)
* Figure 3.1. JBoss Developer Studio Downloads Listed on the Customer Portal
* Figure 3.2. Installation Step 3: Select Target Folder
* Figure 3.3. Installation Step 4: Select Java VM
* Figure 3.5. Installation Step 7: Installation Progress in Finished State
*User Guide*
* Figure 2.4. JBoss Buzz
* Figure 2.22. Set Cheat Sheet Behavior in Project Examples Pane of Preferences Window
> Update screen captures in docs that explicitly reference JBDS 7.0
> -----------------------------------------------------------------
>
> Key: TOOLSDOC-414
> URL: https://issues.jboss.org/browse/TOOLSDOC-414
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Getting Started Guide, Installation Guide, Migration Guide, User Guide
> Affects Versions: 4.1.1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.1
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Screen captures that will need updating for 7.1 docs
> *Installation Guide*
> * Figure 3.1. JBoss Developer Studio Downloads Listed on the Customer Portal
> * Figure 3.2. Installation Step 3: Select Target Folder [done]
> * Figure 3.3. Installation Step 4: Select Java VM [done]
> * Figure 3.5. Installation Step 7: Installation Progress in Finished State [done]
> * Figure 3.6. Install JBoss Developer Studio BYOE via Eclipse Marketplace
> * Figure 3.7. Confirm Selected Features Window
> * Figure 3.10. Work from an Online Website
> * Figure 3.11. work from a Local Copy of the Update .zip File
> * Figure 3.12. Available Software Window Listing JBoss Developer Studio 7.0 - Bring Your Own Eclipse
> * Figure 6.2. Uninstall JBoss Developer Studio via Eclipse Marketplace
> * Figure 6.3. Confirm Selected Features Window
> *Migration Guide*
> * Figure 3.1. jbdevstudio.ini File Open in a Text Editor
> *Getting Started Guide* (all Fig. shared with Installation Guide)
> * Figure 3.1. JBoss Developer Studio Downloads Listed on the Customer Portal
> * Figure 3.2. Installation Step 3: Select Target Folder [done]
> * Figure 3.3. Installation Step 4: Select Java VM [done]
> * Figure 3.5. Installation Step 7: Installation Progress in Finished State [done]
> *User Guide*
> * Figure 2.4. JBoss Buzz
> * Figure 2.22. Set Cheat Sheet Behavior in Project Examples Pane of Preferences Window
--
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, 7 months
[JBoss JIRA] (JBIDE-15495) OpenShift server adapter: publish locks the whole workspace
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15495?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-15495:
-------------------------------------
[~xcoulon] If you want to open a bug against egit for this, to not lock the entire worspace during a git commit, that'd be good.
> OpenShift server adapter: publish locks the whole workspace
> -----------------------------------------------------------
>
> Key: JBIDE-15495
> URL: https://issues.jboss.org/browse/JBIDE-15495
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift, server
> Affects Versions: 4.1.0.Final
> Reporter: Xavier Coulon
> Assignee: Rob Stryker
> Labels: openshift_server_adapter
> Fix For: LATER
>
> Attachments: Screen Shot 2013-09-17 at 10.42.43 AM.png
>
>
> Have 2 projects in a workspace, one of them is an OpenShift application
> Deploy some changes on OpenShift, and while the publication is performed (git push, then OS restarts the server), go to the second (unrelated) project and try to move a file from a package to another package in the same project.
> The 'Publish' operation locked the whoel workspace, which means that the move operation needs to wait.
--
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, 7 months
[JBoss JIRA] (TOOLSDOC-416) Update screen captures in Installation Guide for 7.1.0 UI changes
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-416?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-416:
-------------------------------------
Original Estimate: 45 minutes
Remaining Estimate: 45 minutes
> Update screen captures in Installation Guide for 7.1.0 UI changes
> -----------------------------------------------------------------
>
> Key: TOOLSDOC-416
> URL: https://issues.jboss.org/browse/TOOLSDOC-416
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Getting Started Guide, Installation Guide
> Affects Versions: 4.1.1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.1
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> *Installation Guide*
> * Figure 3.4. Installation Step 4: Select Java VM (JBDS-2757) [also in Getting Started Guide]
> * Figure 3.5. Add Location Window for Runtime Detection (JBDS-2712)
> * Figure 3.13. Available Software Window Listing JBoss Developer Studio 7.0 - Bring Your Own Eclipse (JBDS-2714)
--
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, 7 months
[JBoss JIRA] (TOOLSDOC-417) Update screen captures in User Guide for 7.1.0 UI changes
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-417?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-417:
-------------------------------------
Parent: TOOLSDOC-415
Issue Type: Sub-task (was: Feature Request)
> Update screen captures in User Guide for 7.1.0 UI changes
> ---------------------------------------------------------
>
> Key: TOOLSDOC-417
> URL: https://issues.jboss.org/browse/TOOLSDOC-417
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: User Guide
> Affects Versions: 4.1.1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.1
>
> Original Estimate: 1 hour, 30 minutes
> Remaining Estimate: 1 hour, 30 minutes
>
> *User Guide*
> * Figure 2.7. Show Installed Check Box Selected and Installed Plug-ins Listed as Disabled (JBDS-2710)
> * Figure 2.8. Find and Install Software in Software/Update Page of JBoss Central Tab (JBDS-2710)
> * Figure 2.9. Install Window (JBDS-2710)
> * Figure 2.13. Cheat Sheet Open in Cheat Sheets Tab (JBDS-2727)
> * Figure 2.14. Open In Cheat Sheets View Menu Option (JBDS-2727)
> * Figure 2.2. Start from Sample Wizards; update when new projects added (JBDS-2729)
--
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, 7 months