[JBoss JIRA] (JBIDE-15788) Download runtime wizard shouldn't complain if install folder doesn't exist
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15788?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-15788:
-------------------------------------
The attached PR changes this from an error (stopping forward progress) into a warning (which does not prevent forward progress). The message has also been changed to inform the user that the directory will be created.
> Download runtime wizard shouldn't complain if install folder doesn't exist
> --------------------------------------------------------------------------
>
> Key: JBIDE-15788
> URL: https://issues.jboss.org/browse/JBIDE-15788
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: runtime-detection, server
> Affects Versions: 4.1.1.Alpha2
> Reporter: Fred Bricon
> Labels: respin-b
> Fix For: 4.1.1.Beta1
>
> Attachments: install_folder_must_exist.png
>
>
> If the install folder is missing, the download runtime wizard should cope with it, instead of displaying an error (i.e. create the missing folders when necessary)
> - assert no EAP/AS7 are installed
> - create a new html5 project from central
> - click download and install for the server requirement
> - enter a non-existing location for the install folder
> !install_folder_must_exist.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
12 years, 9 months
[JBoss JIRA] (JBIDE-15788) Download runtime wizard shouldn't complain if install folder doesn't exist
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15788?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-15788:
--------------------------------
Labels: respin-b (was: )
> Download runtime wizard shouldn't complain if install folder doesn't exist
> --------------------------------------------------------------------------
>
> Key: JBIDE-15788
> URL: https://issues.jboss.org/browse/JBIDE-15788
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: runtime-detection, server
> Affects Versions: 4.1.1.Alpha2
> Reporter: Fred Bricon
> Labels: respin-b
> Fix For: 4.1.1.Beta1
>
> Attachments: install_folder_must_exist.png
>
>
> If the install folder is missing, the download runtime wizard should cope with it, instead of displaying an error (i.e. create the missing folders when necessary)
> - assert no EAP/AS7 are installed
> - create a new html5 project from central
> - click download and install for the server requirement
> - enter a non-existing location for the install folder
> !install_folder_must_exist.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
12 years, 9 months
[JBoss JIRA] (JBIDE-15788) Download runtime wizard shouldn't complain if install folder doesn't exist
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15788?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-15788:
--------------------------------
Fix Version/s: 4.1.1.Beta1
(was: 4.1.1.CR1)
> Download runtime wizard shouldn't complain if install folder doesn't exist
> --------------------------------------------------------------------------
>
> Key: JBIDE-15788
> URL: https://issues.jboss.org/browse/JBIDE-15788
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: runtime-detection, server
> Affects Versions: 4.1.1.Alpha2
> Reporter: Fred Bricon
> Fix For: 4.1.1.Beta1
>
> Attachments: install_folder_must_exist.png
>
>
> If the install folder is missing, the download runtime wizard should cope with it, instead of displaying an error (i.e. create the missing folders when necessary)
> - assert no EAP/AS7 are installed
> - create a new html5 project from central
> - click download and install for the server requirement
> - enter a non-existing location for the install folder
> !install_folder_must_exist.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
12 years, 9 months
[JBoss JIRA] (JBIDE-11602) Provide first class support for client side development
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11602?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-11602:
-----------------------------------------
The patch is proposed for the issue [Bug 420533 - ClassCastException when getting validation participants|https://bugs.eclipse.org/bugs/show_bug.cgi?id=420533]
Patch fixes the ClassCastException by adding an additional object type check. No other changes were made because the only objects of type ValidationParticipant are acceptable here, so all other objects will be ignored.
> Provide first class support for client side development
> -------------------------------------------------------
>
> Key: JBIDE-11602
> URL: https://issues.jboss.org/browse/JBIDE-11602
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Sebastien Deleuze
> Assignee: Victor Rubezhny
> Priority: Critical
> Labels: jsdt, vjet
> Fix For: 4.2.x
>
> Attachments: jbosstools-add-vjet-dependencies-patch.patch, jquery-1.5.1.min.js.jpg, jquery.tagcanvas.min.js.jpg, nexj-JS-Content-Assist-On-a-JS-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-a-JS-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-an-HTML-1-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-an-HTML-1-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-an-HTML-2-1-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-an-HTML-2-1-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-an-HTML-2-2-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-an-HTML-2-2-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-Any-JS-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-a-JS-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-a-JS-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-HTML-1-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-HTML-1-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project.jpg
>
>
> Web application development is currently moving in many projects from end to end server side technologies to HTML5 RIA developed with REST Webservices/ Webscoket on serverside + pure client side technologies GUI (Backbone.js for example).
> Eclipse has been always been quite bad in the field of advanced Javascript development. JSDT was a good start, but its development has been stopped for a few years, and in its current status, it is not really a good tool for real HTML5/JS dev. From what I know, there is no roadmap for strong move on this field in the WTP team. The only real Eclipse initiative for client side development is Orion (http://www.eclipse.org/orion/) outside of the IDE.
> The only other alternative is Aptana Studio 3, acquired last year by AppAccelerator.
> My question is : is there any plan to consider client side development as a first class citizen in JBoss Studio, even if this question apply to the whole Eclipse Ecosystem ? Other IDE like Netbeans or IntelliJ Idea have a strong support for these technologies, and my guess is this lack may be a significant blocking point in the following years.
> Thanks in advance for your feedback.
--
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, 9 months
[JBoss JIRA] (JBIDE-15499) Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15499?page=com.atlassian.jira.plugi... ]
Radim Hopp commented on JBIDE-15499:
------------------------------------
Hi [~snjeza],
I'm trying to verify this issue. I tried to Drag&Drop that link from [comment|https://issues.jboss.org/browse/JBIDE-15499?focusedCommentId=1280...] into JBDS 7.1.0.Beta1a, but all I get is unhandled event loop exception
{noformat}
org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.core.runtime.AssertionFailedException: assertion failed: )
at org.eclipse.swt.SWT.error(SWT.java:4397)
at org.eclipse.swt.SWT.error(SWT.java:4312)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
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: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)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
Caused by: org.eclipse.core.runtime.AssertionFailedException: assertion failed:
at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96)
at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.asyncDrop(EditorAreaDropAdapter.java:131)
at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.access$0(EditorAreaDropAdapter.java:87)
at org.eclipse.ui.internal.ide.EditorAreaDropAdapter$1.run(EditorAreaDropAdapter.java:81)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
... 24 more
{noformat}
> Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-15499
> URL: https://issues.jboss.org/browse/JBIDE-15499
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Snjezana Peco
> Priority: Blocker
> Fix For: 4.1.1.Beta1
>
>
> usecase is that you can have a link to a connector, such as JBDS-IS could be installed by drag'n'drop to jboss tools or jbds.
> Similar to eclipse marketplace for marketplace urls something like:
> * https://devstudio.jboss.com/central/install?connector=com.jbds.integratio... or
> * http://download.jboss.org/jbosstools/central/install?CID=com.jbds.integra...
> would install the two connectors named "com.jbds.integration-stack.bpel" and "org.eclipse.m2e"
> This would allow drag'n'drop install from html docs.
> Consider also supporting this from any clipboard object (eg., dragged from an Acrobat Reader PDF or Microsoft Office doc). Would need to ensure we do lots of platform testing.
--
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, 9 months
[JBoss JIRA] (JBIDE-14388) Running "run in Android emulator" a second time fails
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14388?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-14388:
-------------------------------------
Please provide steps to verify
> Running "run in Android emulator" a second time fails
> -----------------------------------------------------
>
> Key: JBIDE-14388
> URL: https://issues.jboss.org/browse/JBIDE-14388
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Reporter: Sebastien Blanc
> Assignee: Gorkem Ercan
> Labels: respin-a
> Fix For: 4.1.1.Beta1
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> If a Android emulator is already running and that we run again from the project "run on Android Emulator" a second Emulator attempts to start and fails because some data is already in use.
> I'm not sure but when running again the project on the emulator, the plugin should check if there is already an instance of the emulator running and redeploy on this one instead of trying to start a new one.
--
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, 9 months