[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-2044:
--------------------------------
Fix Version/s: 8.0.x
(was: 8.0.0.Beta2)
> .eclipseproduct file no longer refers to JBDS
> ---------------------------------------------
>
> Key: JBDS-2044
> URL: https://issues.jboss.org/browse/JBDS-2044
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 5.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 8.0.x
>
>
> Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read:
> {code}
> name=JBoss Developer Studio
> id=com.jboss.jbds.all
> version=5.0.0.v201202271832M-H79-Beta1
> {code}
> Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads:
> {code}
> name=Eclipse Platform
> id=org.eclipse.platform
> version=3.7.0
> {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
11 years, 11 months
[JBoss JIRA] (JBIDE-16883) Broken UI logic in Hybrid Mobile/ Engine properties
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16883?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-16883:
--------------------------------------
I am not happy about direct deletion too. I think that adding a prompt to warn about deletion from the file system would be sufficient.
> Broken UI logic in Hybrid Mobile/ Engine properties
> ---------------------------------------------------
>
> Key: JBIDE-16883
> URL: https://issues.jboss.org/browse/JBIDE-16883
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Beta1
> Environment: JBDS 8.0.0.Beta1-v20140323-1410-B78, Linux
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Priority: Critical
> Fix For: 4.2.0.Beta2
>
> Attachments: enginesearch.png
>
>
> Case 0:
> 1. Open Window > Preferences > Hybrid Mobile > Engines with no engines defined
> 2. Resize Preferences window
> ERROR: Engine table is not resized
> Case 1:
> 1. Open Window > Preferences > Hybrid Mobile > Engines with no engines defined
> 2. Click on another Preferences tree item
> ERROR: It's not possible to select another preferences. Error dialog is displayed saying: "The currently displayed page contains invalid values"
> Case 2:
> 1. Use this preferences dialog to download Hybrid Mobile engine
> ERROR: Displayed Progress Bar has only two values 0% and 100% there is no progress change during downloading
> ERROR: OK button within Download Hybrid Mobile Engine dialog should be enabled only when version and at least one platform is selected
> ERROR: When first engine is downloaded it should be marked as default automatically
> ERROR: While downloading OK button, Version Combo and Platform Table are is still enabled
> Case 3:
> 1. Remove all downloaded engines by clicking on button Remove
> ERROR: Engines are removed immediately after Remove button is clicked. They should be really removed when button OK is pushed
> ERROR: Once there is no engine in dialog error from Case 1 happens
> Case 4:
> 1. Remove all downloaded engines
> 2. Reopen preferences dialog
> 3. Download engine
> 4. Check downloaded engine as default
> ERROR: Button OK is still disabled.
> 5. Uncheck default button
> 6. Check default button
> 7. OK button is enabled and it's possible to click on it
> Case 5:
> 1. Download at least 1 engine
> 2. Search for engine on local file system more times using the same directory
> ERROR: Platform in table is "Android Android ..."
> 3. Click on i image in third column
> ERROR: It shows more than one line with engine location and shows incorrect location for files found on local file system not downloaded from repo
> !enginesearch.png!
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-17082) Error when downloading additional Mobile Engine
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17082?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-17082:
---------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
> Error when downloading additional Mobile Engine
> -----------------------------------------------
>
> Key: JBIDE-17082
> URL: https://issues.jboss.org/browse/JBIDE-17082
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Beta1
> Environment: JBT 4.2.0.Beta1-v20140408-2318-B105 MS Windows 7_64bit
> Reporter: Vlado Pakan
> Priority: Critical
> Fix For: 4.2.0.Beta2
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> 1. Create Hybrid Mobile App with 3.4.0. Mobile engine downloaded
> 2. Click on created project in Package explorer and open properties
> 3. Select Hybrid Mobile > Engines and choose dowlnoad Mobile engine 3.3.0. version
> ERROR: There are errors in Error log:
> Second message has switched 'Plugin' and 'Message' columns content
> {noformat}
> Unhandled event loop exception
> org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTException: Widget is disposed)
> at org.eclipse.swt.SWT.error(SWT.java:4441)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:139)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4147)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3764)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:158)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:588)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:505)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:415)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:146)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:615)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226)
> 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:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> Caused by: org.eclipse.swt.SWTException: Widget is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4441)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.SWT.error(SWT.java:4327)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:476)
> at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:348)
> at org.eclipse.swt.widgets.ProgressBar.getSelection(ProgressBar.java:190)
> at org.eclipse.jface.dialogs.ProgressIndicator.worked(ProgressIndicator.java:139)
> at org.eclipse.jface.wizard.ProgressMonitorPart.internalWorked(ProgressMonitorPart.java:298)
> at org.eclipse.jface.operation.AccumulatingProgressMonitor$Collector.run(AccumulatingProgressMonitor.java:97)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> ... 35 more
> {noformat}
> {noformat}
> Plugin: missing Android engine file C:\Users\jbossqa\.cordova\lib\android\cordova\3.3.0\framework\cordova-3.3.0.jar
> Message: org.jboss.tools.aerogear.hybrid.core
> Stack trace: An exception stack trace is not available.
> {noformat}
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-17082) Error when downloading additional Mobile Engine
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17082?page=com.atlassian.jira.plugi... ]
Gorkem Ercan resolved JBIDE-17082.
----------------------------------
Resolution: Cannot Reproduce Bug
> Error when downloading additional Mobile Engine
> -----------------------------------------------
>
> Key: JBIDE-17082
> URL: https://issues.jboss.org/browse/JBIDE-17082
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Beta1
> Environment: JBT 4.2.0.Beta1-v20140408-2318-B105 MS Windows 7_64bit
> Reporter: Vlado Pakan
> Priority: Critical
> Fix For: 4.2.0.Beta2
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> 1. Create Hybrid Mobile App with 3.4.0. Mobile engine downloaded
> 2. Click on created project in Package explorer and open properties
> 3. Select Hybrid Mobile > Engines and choose dowlnoad Mobile engine 3.3.0. version
> ERROR: There are errors in Error log:
> Second message has switched 'Plugin' and 'Message' columns content
> {noformat}
> Unhandled event loop exception
> org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTException: Widget is disposed)
> at org.eclipse.swt.SWT.error(SWT.java:4441)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:139)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4147)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3764)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:158)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:588)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:505)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:415)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:146)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:615)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226)
> 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:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> Caused by: org.eclipse.swt.SWTException: Widget is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4441)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.SWT.error(SWT.java:4327)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:476)
> at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:348)
> at org.eclipse.swt.widgets.ProgressBar.getSelection(ProgressBar.java:190)
> at org.eclipse.jface.dialogs.ProgressIndicator.worked(ProgressIndicator.java:139)
> at org.eclipse.jface.wizard.ProgressMonitorPart.internalWorked(ProgressMonitorPart.java:298)
> at org.eclipse.jface.operation.AccumulatingProgressMonitor$Collector.run(AccumulatingProgressMonitor.java:97)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> ... 35 more
> {noformat}
> {noformat}
> Plugin: missing Android engine file C:\Users\jbossqa\.cordova\lib\android\cordova\3.3.0\framework\cordova-3.3.0.jar
> Message: org.jboss.tools.aerogear.hybrid.core
> Stack trace: An exception stack trace is not available.
> {noformat}
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-17082) Error when downloading additional Mobile Engine
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17082?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-17082:
--------------------------------------
I am not able to repro this one on master. We had a few changes/fixes related to precompilation that occurs right after download. This may have been related to those.
> Error when downloading additional Mobile Engine
> -----------------------------------------------
>
> Key: JBIDE-17082
> URL: https://issues.jboss.org/browse/JBIDE-17082
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Beta1
> Environment: JBT 4.2.0.Beta1-v20140408-2318-B105 MS Windows 7_64bit
> Reporter: Vlado Pakan
> Priority: Critical
> Fix For: 4.2.0.Beta2
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> 1. Create Hybrid Mobile App with 3.4.0. Mobile engine downloaded
> 2. Click on created project in Package explorer and open properties
> 3. Select Hybrid Mobile > Engines and choose dowlnoad Mobile engine 3.3.0. version
> ERROR: There are errors in Error log:
> Second message has switched 'Plugin' and 'Message' columns content
> {noformat}
> Unhandled event loop exception
> org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTException: Widget is disposed)
> at org.eclipse.swt.SWT.error(SWT.java:4441)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:139)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4147)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3764)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:158)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:588)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:505)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:415)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:146)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:615)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226)
> 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:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> Caused by: org.eclipse.swt.SWTException: Widget is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4441)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.SWT.error(SWT.java:4327)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:476)
> at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:348)
> at org.eclipse.swt.widgets.ProgressBar.getSelection(ProgressBar.java:190)
> at org.eclipse.jface.dialogs.ProgressIndicator.worked(ProgressIndicator.java:139)
> at org.eclipse.jface.wizard.ProgressMonitorPart.internalWorked(ProgressMonitorPart.java:298)
> at org.eclipse.jface.operation.AccumulatingProgressMonitor$Collector.run(AccumulatingProgressMonitor.java:97)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> ... 35 more
> {noformat}
> {noformat}
> Plugin: missing Android engine file C:\Users\jbossqa\.cordova\lib\android\cordova\3.3.0\framework\cordova-3.3.0.jar
> Message: org.jboss.tools.aerogear.hybrid.core
> Stack trace: An exception stack trace is not available.
> {noformat}
--
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
11 years, 11 months
[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-2044:
-------------------------------------
.eclipseproduct file is a marker file and "this file is still used. The main use is for computing a writeable configuration location when the install directory is read-only. See the method computeDefaultUserAreaLocation in Main and LocationManager" as stated here https://bugs.eclipse.org/bugs/show_bug.cgi?id=274517#attach_167190.
This file is installed as a root file for org.eclipse.platform, I can add root file for com.jboss.devstudio.core.feature but it gets overwritten by one from eclipse platform during installation. To fix latter problem devstudio product should not include org.eclipse.platform.
> .eclipseproduct file no longer refers to JBDS
> ---------------------------------------------
>
> Key: JBDS-2044
> URL: https://issues.jboss.org/browse/JBDS-2044
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 5.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 8.0.0.Beta2
>
>
> Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read:
> {code}
> name=JBoss Developer Studio
> id=com.jboss.jbds.all
> version=5.0.0.v201202271832M-H79-Beta1
> {code}
> Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads:
> {code}
> name=Eclipse Platform
> id=org.eclipse.platform
> version=3.7.0
> {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
11 years, 11 months
[JBoss JIRA] (JBIDE-15897) Make all relevant OpenShift Explorer actions available from Server Adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15897?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15897:
-------------------------------------
Attachment: explorer-context-menu.png
> Make all relevant OpenShift Explorer actions available from Server Adapter
> --------------------------------------------------------------------------
>
> Key: JBIDE-15897
> URL: https://issues.jboss.org/browse/JBIDE-15897
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Max Rydahl Andersen
> Fix For: 4.2.0.Beta2
>
> Attachments: explorer-context-menu.png, explorer-context-menu.png, server-adapter-context-menu.png, server-adapter-context-menu.png
>
>
> JBIDE-11841 was done earlier but only added the missing actions - when new actions are added we tend to forget to add them.
> Explorer:
> !explorer-context-menu.png!
> Server adapter:
> !server-adapter-context-menu.png!
> We should make it so these actions (when relevant) gets added to both places (openshift explorer / server adapter) and optimally also available in an OpenShift context menu on a project.
> Meaning you don't have to navigate to explorer view constantly.
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-15897) Make all relevant OpenShift Explorer actions available from Server Adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15897?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15897:
-------------------------------------
Attachment: server-adapter-context-menu.png
> Make all relevant OpenShift Explorer actions available from Server Adapter
> --------------------------------------------------------------------------
>
> Key: JBIDE-15897
> URL: https://issues.jboss.org/browse/JBIDE-15897
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Max Rydahl Andersen
> Fix For: 4.2.0.Beta2
>
> Attachments: explorer-context-menu.png, server-adapter-context-menu.png, server-adapter-context-menu.png
>
>
> JBIDE-11841 was done earlier but only added the missing actions - when new actions are added we tend to forget to add them.
> Explorer:
> !explorer-context-menu.png!
> Server adapter:
> !server-adapter-context-menu.png!
> We should make it so these actions (when relevant) gets added to both places (openshift explorer / server adapter) and optimally also available in an OpenShift context menu on a project.
> Meaning you don't have to navigate to explorer view constantly.
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-16885) Embed wizard: Can provide "Code Anything" without url, should not be able to
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16885?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16885:
-------------------------------------
Steps to Reproduce:
# ASSERT: have an application running on OpenShift
# EXEC: OpenShift Explorer: select "Edit Embedded Cartridges" from the context menu
# EXEC: check "Code Anything"
# ASSERT: "Finish" is disabled, URL text field is decorated with a *(star) to show that the user has to provide an url
# EXEC: check another cartridge (ex. mysql-5.5)
Result:
*Finish* is enabled even though the *Code Anything* cartridge is missing the url
!wrong_button_accessibility2.png!
Also:
# ASSERT: have an application running on OpenShift
# EXEC: OpenShift Explorer: select "Edit Embedded Cartridges" from the context menu
# EXEC: check "Code Anything"
# ASSERT: "Finish" is disabled, URL text field is decorated with a *(star) to show that the user has to provide an url
# EXEC: uncheck *Code Anything*
Result:
*Finish* should get enabled since we're not adding the *Code Anything* cartridge
!wrong_button_accessibility.png!
was:
# ASSERT: have an application running on OpenShift
# EXEC: OpenShift Explorer: select "Edit Embedded Cartridges" from the context menu
# EXEC: check "Code Anything"
# ASSERT: "Finish" is disabled, URL text field is decorated with a *(star) to show that the user has to provide an url
!wrong_button_accessibility.png!
# EXEC: check another cartridge (ex. mysql-5.5)
Result:
*Finish* is enabled even though the *Code Anything* cartridge is missing the url
!wrong_button_accessibility2.png!
Also:
# ASSERT: have an application running on OpenShift
# EXEC: OpenShift Explorer: select "Edit Embedded Cartridges" from the context menu
# EXEC: check "Code Anything"
# ASSERT: "Finish" is disabled, URL text field is decorated with a *(star) to show that the user has to provide an url
# EXEC: uncheck *Code Anything*
Result:
*Finish* should get enabled since we're not adding the *Code Anything* cartridge
> Embed wizard: Can provide "Code Anything" without url, should not be able to
> ----------------------------------------------------------------------------
>
> Key: JBIDE-16885
> URL: https://issues.jboss.org/browse/JBIDE-16885
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: embed_wizard
> Fix For: 4.2.0.Beta2
>
> Attachments: wrong_button_accessibility.png, wrong_button_accessibility.png, wrong_button_accessibility2.png, wrong_button_accessibility2.png
>
>
> In the wizard to edit the embeddable cartridges there is "Code Anything" cartridge which requires URL of cartridge. If user just selects and does not check this cartridge, it is not possible to hit the OK button (see attached screen wrong_button_accessibility).
> Also if user check this cartridge but select another one without providing URL to the Code anything cartridge, it is possible to hit the OK button (it should not be - see attached screenshot wrong_button_accessibility2.)
--
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
11 years, 11 months