[JBoss JIRA] (JBIDE-17423) BrowserSim is not opening source code of opened web page
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17423?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-17423:
------------------------------------------------
Attached PRs fixes this issue. But preview does not show anything when plain HTML text is opened in editor(without file). This is separate issue.
> BrowserSim is not opening source code of opened web page
> --------------------------------------------------------
>
> Key: JBIDE-17423
> URL: https://issues.jboss.org/browse/JBIDE-17423
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2-v20140525-2146-B104
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Priority: Blocker
> Fix For: 4.2.0.Beta3
>
>
> 1. Open BrowserSim
> 2. Open page www.github.com in BrowserSim
> 3. Choose View Page Source from BrowserSim context menu
> ERROR: No source code displayed in JBDS just error message in VPE and Error Log view
> {noformat}
> java.lang.ClassCastException: org.jboss.tools.vpe.browsersim.eclipse.callbacks.StringInput cannot be cast to org.eclipse.ui.IFileEditorInput
> at org.jboss.tools.vpe.preview.editor.VpeEditorPartFactory.createVisualEditor(VpeEditorPartFactory.java:35)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor.createPagesForVPE(JSPMultiPageEditor.java:589)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:506)
> at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:362)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:140)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:99)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:321)
> at sun.reflect.GeneratedMethodAccessor143.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:888)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:869)
> at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:120)
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:337)
> at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:258)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:104)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:73)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:55)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:127)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:984)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:663)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:767)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:738)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:732)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:716)
> at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1250)
> at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer$1.handleEvent(LazyStackRenderer.java:66)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:187)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:156)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4598)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:207)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:81)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:59)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:171)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:479)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:445)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:692)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1123)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3127)
> at org.eclipse.ui.internal.WorkbenchPage.access$23(WorkbenchPage.java:3049)
> at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:3031)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3026)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2990)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2971)
> at org.jboss.tools.vpe.browsersim.eclipse.callbacks.ViewSourceCallback.openInMemoryHtmlEditor(ViewSourceCallback.java:100)
> at org.jboss.tools.vpe.browsersim.eclipse.callbacks.ViewSourceCallback.access$0(ViewSourceCallback.java:83)
> at org.jboss.tools.vpe.browsersim.eclipse.callbacks.ViewSourceCallback$1.run(ViewSourceCallback.java:75)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3781)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3419)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1152)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1033)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:635)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:578)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:379)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:233)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17523) Filter runtime downloads to hide unsupported runtime types
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17523?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-17523.
---------------------------------
Resolution: Done
pushed to b3
> Filter runtime downloads to hide unsupported runtime types
> ----------------------------------------------------------
>
> Key: JBIDE-17523
> URL: https://issues.jboss.org/browse/JBIDE-17523
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection, server
> Affects Versions: 4.2.0.Beta2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.0.Beta3
>
>
> This concern arose while testing the new WildFly 8.1 runtime added to stacks.yaml (JDF-727). This itself is ok, but Rob pointed out another concern:
> If a new runtime requires a new runtime type in the future and we add this to stacks.yaml, older versions of JBDS/JBT will not recognize this runtime type, but will still gladly offer it to you for download through Preferences -> Runtime Detection -> Download. When you choose the path of Server -> New, the runtimes offered for download are restricted to the given server type, so we're safe there.
> So this is what we should do:
> The list of runtimes offered for download should always be restricted to only those runtimes that are defined in the given JBDS/JBT.
> E.g. if EAP 7 needs an eap7 runtime type in stacks.yaml, but this type is not available in JBDS 8, JBDS 8 should not offer EAP 7 for download.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17454) NPE when clicking on element in VPE visual part
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17454?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-17454:
------------------------------------------------
Not reproducible under Windows. Will take a look on fedora.
> NPE when clicking on element in VPE visual part
> -----------------------------------------------
>
> Key: JBIDE-17454
> URL: https://issues.jboss.org/browse/JBIDE-17454
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2-v20140525-2146-B104
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.2.0.Beta3
>
>
> 1. Import HTML 5 project from JBoss Central
> 2. Open index.html in VPE
> 3. Click on some UI element within visual pane (Preview)
> ERROR: Error in Error log with:
> Message: Unhandled event loop exception
> Stack Trace: java.lang.NullPointerException
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17523) Filter runtime downloads to hide unsupported runtime types
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17523?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-17523:
----------------------------------
Fix Version/s: 4.2.0.Beta3
> Filter runtime downloads to hide unsupported runtime types
> ----------------------------------------------------------
>
> Key: JBIDE-17523
> URL: https://issues.jboss.org/browse/JBIDE-17523
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection, server
> Affects Versions: 4.2.0.Beta2
> Reporter: Martin Malina
> Fix For: 4.2.0.Beta3
>
>
> This concern arose while testing the new WildFly 8.1 runtime added to stacks.yaml (JDF-727). This itself is ok, but Rob pointed out another concern:
> If a new runtime requires a new runtime type in the future and we add this to stacks.yaml, older versions of JBDS/JBT will not recognize this runtime type, but will still gladly offer it to you for download through Preferences -> Runtime Detection -> Download. When you choose the path of Server -> New, the runtimes offered for download are restricted to the given server type, so we're safe there.
> So this is what we should do:
> The list of runtimes offered for download should always be restricted to only those runtimes that are defined in the given JBDS/JBT.
> E.g. if EAP 7 needs an eap7 runtime type in stacks.yaml, but this type is not available in JBDS 8, JBDS 8 should not offer EAP 7 for download.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17523) Filter runtime downloads to hide unsupported runtime types
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17523?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-17523:
----------------------------------
Assignee: Rob Stryker
> Filter runtime downloads to hide unsupported runtime types
> ----------------------------------------------------------
>
> Key: JBIDE-17523
> URL: https://issues.jboss.org/browse/JBIDE-17523
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection, server
> Affects Versions: 4.2.0.Beta2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.0.Beta3
>
>
> This concern arose while testing the new WildFly 8.1 runtime added to stacks.yaml (JDF-727). This itself is ok, but Rob pointed out another concern:
> If a new runtime requires a new runtime type in the future and we add this to stacks.yaml, older versions of JBDS/JBT will not recognize this runtime type, but will still gladly offer it to you for download through Preferences -> Runtime Detection -> Download. When you choose the path of Server -> New, the runtimes offered for download are restricted to the given server type, so we're safe there.
> So this is what we should do:
> The list of runtimes offered for download should always be restricted to only those runtimes that are defined in the given JBDS/JBT.
> E.g. if EAP 7 needs an eap7 runtime type in stacks.yaml, but this type is not available in JBDS 8, JBDS 8 should not offer EAP 7 for download.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17523) Filter runtime downloads to hide unsupported runtime types
by Martin Malina (JIRA)
Martin Malina created JBIDE-17523:
-------------------------------------
Summary: Filter runtime downloads to hide unsupported runtime types
Key: JBIDE-17523
URL: https://issues.jboss.org/browse/JBIDE-17523
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtime-detection, server
Affects Versions: 4.2.0.Beta2
Reporter: Martin Malina
This concern arose while testing the new WildFly 8.1 runtime added to stacks.yaml (JDF-727). This itself is ok, but Rob pointed out another concern:
If a new runtime requires a new runtime type in the future and we add this to stacks.yaml, older versions of JBDS/JBT will not recognize this runtime type, but will still gladly offer it to you for download through Preferences -> Runtime Detection -> Download. When you choose the path of Server -> New, the runtimes offered for download are restricted to the given server type, so we're safe there.
So this is what we should do:
The list of runtimes offered for download should always be restricted to only those runtimes that are defined in the given JBDS/JBT.
E.g. if EAP 7 needs an eap7 runtime type in stacks.yaml, but this type is not available in JBDS 8, JBDS 8 should not offer EAP 7 for download.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17404) Cordova Sim cannot be launched on RHEL7
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17404?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-17404:
-------------------------------------------
Fix Version/s: 4.2.0.Beta3
(was: 4.2.0.Beta2)
> Cordova Sim cannot be launched on RHEL7
> ---------------------------------------
>
> Key: JBIDE-17404
> URL: https://issues.jboss.org/browse/JBIDE-17404
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim
> Environment: RHEL7 latest, 64bit
> Installed webkitgtk3-devel 0:2.0.4-6-el7
> TicketMonster Cordava example from latest WFK
> JBDS 8.0.0.Beta1
> OpenJDK 7
> Reporter: Karel Piwko
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.0.Beta3
>
>
> Launching BrowserSim fails with NPE, adding information from workspace log
> Before webkitgtk3-devel is installed
> {code}
> !ENTRY No engine information on the config.json, this is OK if using an old project. Falling back to default engine. 2 0 2014-05-23 13:03:54.128
> !MESSAGE org.jboss.tools.aerogear.hybrid.core
> !ENTRY org.jboss.tools.vpe.browsersim 4 0 2014-05-23 13:03:56.162
> !MESSAGE BrowserSim is failed to start with the following error:
> "No more handles"
> Please note that WebKitGTK 1.2.0 or newer must be installed and available in the library load path.
> If not, use your package manager to install libwebkitgtk.
> Also see <a href="https://community.jboss.org/docs/DOC-18100">BrowserSim FAQ</a>.
> Stack trace:
> org.eclipse.swt.SWTError: No more handles
> at org.eclipse.swt.SWT.error(SWT.java:4467)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.SWT.error(SWT.java:4327)
> at org.eclipse.swt.browser.Browser.<init>(Browser.java:103)
> at org.jboss.tools.vpe.browsersim.browser.BrowserSimBrowser.<init>(BrowserSimBrowser.java:36)
> at org.jboss.tools.vpe.browsersim.browser.AbstractWebKitBrowser.<init>(AbstractWebKitBrowser.java:25)
> at org.jboss.tools.vpe.browsersim.browser.internal.WebKitBrowser_gtk_linux_x86_64.<init>(WebKitBrowser_gtk_linux_x86_64.java:37)
> at org.jboss.tools.vpe.browsersim.browser.WebKitBrowserFactory.createBrowser(WebKitBrowserFactory.java:39)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.createCordovaSim(CordovaSimRunner.java:189)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.startCordovaSim(CordovaSimRunner.java:90)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:84)
> {code}
> After:
> {code}
> !ENTRY No engine information on the config.json, this is OK if using an old project. Falling back to default engine. 2 0 2014-05-23 14:03:57.380
> !MESSAGE org.jboss.tools.aerogear.hybrid.core
> !ENTRY No engine information on the config.json, this is OK if using an old project. Falling back to default engine. 2 0 2014-05-23 14:03:57.380
> !MESSAGE org.jboss.tools.aerogear.hybrid.core
> !ENTRY org.eclipse.core.jobs 4 2 2014-05-23 14:03:57.395
> !MESSAGE An internal error occurred during: "Launching TicketMonster-Cordova".
> !STACK 0
> java.lang.NullPointerException
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLauncher.launchCordovaSim(CordovaSimLauncher.java:157)
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLauncher.launchCordovaSim(CordovaSimLauncher.java:115)
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLaunchConfigurationDelegate.launch(CordovaSimLaunchConfigurationDelegate.java:24)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-16129) Environment Variables wizard: Refresh should warn that it'll undo all changes
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16129?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-16129:
------------------------------------------
merged and pushed to upstream/master
> Environment Variables wizard: Refresh should warn that it'll undo all changes
> -----------------------------------------------------------------------------
>
> Key: JBIDE-16129
> URL: https://issues.jboss.org/browse/JBIDE-16129
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: env_var_wizard
> Fix For: 4.2.0.Beta3
>
> Attachments: RefreshVariables.png
>
>
> In Edit Environment variables shell the Refresh button undo local changes - all changes upon local variables (removed/added/modified) are commited after click on Finish button. So if someone try to modify more environment variables and then "accidentally" click on Refresh button, then all local changes are disposed and variables are refreshed from server. There should be probably some warning before this action to let the user be sure about consequences of his action.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months