[JBoss JIRA] (JBIDE-13857) JBoss EAP developer studio - Issue while adding custom capability
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13857?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration updated JBIDE-13857:
--------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=927147
> JBoss EAP developer studio - Issue while adding custom capability
> -----------------------------------------------------------------
>
> Key: JBIDE-13857
> URL: https://issues.jboss.org/browse/JBIDE-13857
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Reporter: Brian Leathem
>
> From the linked bugzilla:
> {quote}
> Description of problem:
> I am evaluating JBoss EAP and developer studio. Created an enterprise application and wanted to add richface capability to the web app.
> Via context menu clicked on add custom capabilities and selected richfaces 3.3 (no jars only file filters). Since I did not have web.xml it prompted em to add one and I canceled the operation. There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid".
> This happened to me twice and I had to create a new workspace and reconfigure everything from scratch.
> Version-Release number of selected component (if applicable):6.0.0
> How reproducible:
> Create an enterprise application and wanted to add richface capability to the web app.
> Via context menu clicked on add custom capabilities and selected richfaces 3.3 (no jars only file filters). Since I did not have web.xml it prompted em to add one and I canceled the operation. There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid".
> Steps to Reproduce:
> Created an enterprise application and wanted to add richface capability to the web app.
> Via context menu clicked on add custom capabilities and selected richfaces 3.3 (no jars only file filters). Since I did not have web.xml it prompted em to add one and I canceled the operation. There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid".
>
> Actual results:
> There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid".
> {quote}
--
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
13 years, 3 months
[JBoss JIRA] (JBIDE-13857) JBoss EAP developer studio - Issue while adding custom capability
by Brian Leathem (JIRA)
Brian Leathem created JBIDE-13857:
-------------------------------------
Summary: JBoss EAP developer studio - Issue while adding custom capability
Key: JBIDE-13857
URL: https://issues.jboss.org/browse/JBIDE-13857
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Brian Leathem
>From the linked bugzilla:
{quote}
Description of problem:
I am evaluating JBoss EAP and developer studio. Created an enterprise application and wanted to add richface capability to the web app.
Via context menu clicked on add custom capabilities and selected richfaces 3.3 (no jars only file filters). Since I did not have web.xml it prompted em to add one and I canceled the operation. There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid".
This happened to me twice and I had to create a new workspace and reconfigure everything from scratch.
Version-Release number of selected component (if applicable):6.0.0
How reproducible:
Create an enterprise application and wanted to add richface capability to the web app.
Via context menu clicked on add custom capabilities and selected richfaces 3.3 (no jars only file filters). Since I did not have web.xml it prompted em to add one and I canceled the operation. There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid".
Steps to Reproduce:
Created an enterprise application and wanted to add richface capability to the web app.
Via context menu clicked on add custom capabilities and selected richfaces 3.3 (no jars only file filters). Since I did not have web.xml it prompted em to add one and I canceled the operation. There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid".
Actual results:
There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid".
{quote}
--
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
13 years, 3 months
[JBoss JIRA] (JBIDE-13821) CI runs tests against minimum instead of maximum
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13821?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-13821.
------------------------------
Resolution: Done
> CI runs tests against minimum instead of maximum
> ------------------------------------------------
>
> Key: JBIDE-13821
> URL: https://issues.jboss.org/browse/JBIDE-13821
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.0.x, 4.1.0.Alpha2
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.0.1.Final, 4.1.0.Alpha2
>
>
> As Maven executions set a value for the TARGET_PLATFORM_VERSION value, this property is not overriden by the maximum profile.
> Maven order to set properties is
> # look a -D... to set property, if not found
> # look at active profiles to set property, if not found
> # look at default value of property to set it
> This makes that in mvn execution for tests, the TARGET_PLATFORM_VERSION is set to minimal is CI jobs, whereas with using the -Pmaximun profile, we expect maximum.
> This is a critical issue since it caused hours of confusions to debug on 4.0.x branch.
--
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
13 years, 3 months
[JBoss JIRA] (JBIDE-13821) CI runs tests against minimum instead of maximum
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13821?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13821 at 3/25/13 7:56 PM:
-------------------------------------------------------------
The 4.0.x jobs were updated to use
{code} clean install ${MAVEN_FLAGS} -gs /home/hudson/.m2/settings.xml -s ${WORKSPACE}/settings/hudson-settings.xml
-DTARGET_PLATFORM_VERSION=4.20.6.Final-SNAPSHOT -DTARGET_PLATFORM_VERSION_MAXIMUM=4.22.2.Final-SNAPSHOT {code}
instead of
{code} clean install ${MAVEN_FLAGS} -gs /home/hudson/.m2/settings.xml -s ${WORKSPACE}/settings/hudson-settings.xml
-DTARGET_PLATFORM_VERSION=4.20.6.Final-SNAPSHOT -DTARGET_PLATFORM_VERSION-maximum=4.22.2.Final-SNAPSHOT {code}
so there are no longer any references to the old variable, which means this issue can be closed.
was (Author: nickboldt):
4.0.x jobs were updated to use clean install ${MAVEN_FLAGS} -gs /home/hudson/.m2/settings.xml -s ${WORKSPACE}/settings/hudson-settings.xml -DTARGET_PLATFORM_VERSION=4.20.6.Final-SNAPSHOT -DTARGET_PLATFORM_VERSION_MAXIMUM=4.22.2.Final-SNAPSHOT
instead of
clean install ${MAVEN_FLAGS} -gs /home/hudson/.m2/settings.xml -s ${WORKSPACE}/settings/hudson-settings.xml -DTARGET_PLATFORM_VERSION=4.20.6.Final-SNAPSHOT -DTARGET_PLATFORM_VERSION-maximum=4.22.2.Final-SNAPSHOT
so...
nothing to do here.
/me takes a deep breath
Closing.
> CI runs tests against minimum instead of maximum
> ------------------------------------------------
>
> Key: JBIDE-13821
> URL: https://issues.jboss.org/browse/JBIDE-13821
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.0.x, 4.1.0.Alpha2
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.0.1.Final, 4.1.0.Alpha2
>
>
> As Maven executions set a value for the TARGET_PLATFORM_VERSION value, this property is not overriden by the maximum profile.
> Maven order to set properties is
> # look a -D... to set property, if not found
> # look at active profiles to set property, if not found
> # look at default value of property to set it
> This makes that in mvn execution for tests, the TARGET_PLATFORM_VERSION is set to minimal is CI jobs, whereas with using the -Pmaximun profile, we expect maximum.
> This is a critical issue since it caused hours of confusions to debug on 4.0.x branch.
--
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
13 years, 3 months
[JBoss JIRA] (JBIDE-13856) Test jQuery Mobile Palette Wizards on different platforms
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13856?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-13856:
----------------------------------
Description:
If system font size is set to large, wizard should take it into account.
For instance:
!ubuntu_64_large_font_toggle.png!
Windows 8 64:
{code}
org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser])
at org.eclipse.swt.SWT.error(SWT.java:4373)
at org.eclipse.swt.SWT.error(SWT.java:4288)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4144)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1057)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:941)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:79)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
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(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
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.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser]
at org.eclipse.swt.SWT.error(SWT.java:4399)
at org.eclipse.swt.browser.WebKit.create(WebKit.java:542)
at org.eclipse.swt.browser.Browser.<init>(Browser.java:99)
at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizardPage.createControl(AbstractNewHTMLWidgetWizardPage.java:139)
at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174)
at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736)
at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608)
at org.eclipse.jface.window.Window.create(Window.java:431)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
at org.jboss.tools.common.model.ui.editors.dnd.DropWizardDialog.create(DropWizardDialog.java:95)
at org.eclipse.jface.window.Window.open(Window.java:790)
at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:110)
at org.jboss.tools.jst.jsp.jspeditor.JSPTextEditor$4.run(JSPTextEditor.java:757)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
... 24 more
{code}
was:
If system font size is set to large, wizard should take it into account.
For instance:
!ubuntu_64_large_font_toggle.png!
> Test jQuery Mobile Palette Wizards on different platforms
> ---------------------------------------------------------
>
> Key: JBIDE-13856
> URL: https://issues.jboss.org/browse/JBIDE-13856
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: jsp/jsf/xml/html source editing
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Fix For: 4.1.0.Alpha2
>
> Attachments: ubuntu_64_button.png, ubuntu_64_checkboxes.png, ubuntu_64_cjeckbox.png, ubuntu_64_collapsible.png, ubuntu_64_dialog.png, ubuntu_64_footerbar.png, ubuntu_64_grid.png, ubuntu_64_headerbar.png, ubuntu_64_large_font_toggle.png, ubuntu_64_link.png, ubuntu_64_listview.png, ubuntu_64_navbar.png, ubuntu_64_page.png, ubuntu_64_radio.png, ubuntu_64_slider.png, ubuntu_64_textinput.png, ubuntu_64_toggle.png
>
>
> If system font size is set to large, wizard should take it into account.
> For instance:
> !ubuntu_64_large_font_toggle.png!
> Windows 8 64:
> {code}
> org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser])
> at org.eclipse.swt.SWT.error(SWT.java:4373)
> at org.eclipse.swt.SWT.error(SWT.java:4288)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4144)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1057)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:941)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:79)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> 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(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> 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.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser]
> at org.eclipse.swt.SWT.error(SWT.java:4399)
> at org.eclipse.swt.browser.WebKit.create(WebKit.java:542)
> at org.eclipse.swt.browser.Browser.<init>(Browser.java:99)
> at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizardPage.createControl(AbstractNewHTMLWidgetWizardPage.java:139)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608)
> at org.eclipse.jface.window.Window.create(Window.java:431)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
> at org.jboss.tools.common.model.ui.editors.dnd.DropWizardDialog.create(DropWizardDialog.java:95)
> at org.eclipse.jface.window.Window.open(Window.java:790)
> at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:110)
> at org.jboss.tools.jst.jsp.jspeditor.JSPTextEditor$4.run(JSPTextEditor.java:757)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 24 more
> {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
13 years, 3 months
[JBoss JIRA] (JBIDE-13856) Test jQuery Mobile Palette Wizards on different platforms
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13856?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-13856:
----------------------------------
Description:
If system font size is set to large, wizard should take it into account.
For instance:
!ubuntu_64_large_font_toggle.png!
> Test jQuery Mobile Palette Wizards on different platforms
> ---------------------------------------------------------
>
> Key: JBIDE-13856
> URL: https://issues.jboss.org/browse/JBIDE-13856
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: jsp/jsf/xml/html source editing
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Fix For: 4.1.0.Alpha2
>
> Attachments: ubuntu_64_button.png, ubuntu_64_checkboxes.png, ubuntu_64_cjeckbox.png, ubuntu_64_collapsible.png, ubuntu_64_dialog.png, ubuntu_64_footerbar.png, ubuntu_64_grid.png, ubuntu_64_headerbar.png, ubuntu_64_large_font_toggle.png, ubuntu_64_link.png, ubuntu_64_listview.png, ubuntu_64_navbar.png, ubuntu_64_page.png, ubuntu_64_radio.png, ubuntu_64_slider.png, ubuntu_64_textinput.png, ubuntu_64_toggle.png
>
>
> If system font size is set to large, wizard should take it into account.
> For instance:
> !ubuntu_64_large_font_toggle.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
13 years, 3 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:
-----------------------------------------
VJet has an issue on parsing the Regular Expressions [Bug 401250: regular expression causes false comment color|https://bugs.eclipse.org/bugs/show_bug.cgi?id=401250]
Because of this issue VJet cannot correctly parse RequireJS (and as such it cannot show its methods in content assist as well).
Moreover, I suppose that even if the RegEx issue will be fixed, there will be a difficulties on resolving the objects from the modules that are loaded/defined by require() or define() functions in desing-time.
> 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
> Labels: jsdt, vjet
> Fix For: 4.1.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
13 years, 3 months
[JBoss JIRA] (JBIDE-13821) CI runs tests against minimum instead of maximum
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13821?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-13821.
------------------------------
Resolution: Done
4.0.x jobs were updated to use clean install ${MAVEN_FLAGS} -gs /home/hudson/.m2/settings.xml -s ${WORKSPACE}/settings/hudson-settings.xml -DTARGET_PLATFORM_VERSION=4.20.6.Final-SNAPSHOT -DTARGET_PLATFORM_VERSION_MAXIMUM=4.22.2.Final-SNAPSHOT
instead of
clean install ${MAVEN_FLAGS} -gs /home/hudson/.m2/settings.xml -s ${WORKSPACE}/settings/hudson-settings.xml -DTARGET_PLATFORM_VERSION=4.20.6.Final-SNAPSHOT -DTARGET_PLATFORM_VERSION-maximum=4.22.2.Final-SNAPSHOT
so...
nothing to do here.
/me takes a deep breath
Closing.
> CI runs tests against minimum instead of maximum
> ------------------------------------------------
>
> Key: JBIDE-13821
> URL: https://issues.jboss.org/browse/JBIDE-13821
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.0.x, 4.1.0.Alpha2
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.0.1.Final, 4.1.0.Alpha2
>
>
> As Maven executions set a value for the TARGET_PLATFORM_VERSION value, this property is not overriden by the maximum profile.
> Maven order to set properties is
> # look a -D... to set property, if not found
> # look at active profiles to set property, if not found
> # look at default value of property to set it
> This makes that in mvn execution for tests, the TARGET_PLATFORM_VERSION is set to minimal is CI jobs, whereas with using the -Pmaximun profile, we expect maximum.
> This is a critical issue since it caused hours of confusions to debug on 4.0.x branch.
--
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
13 years, 3 months
[JBoss JIRA] (JBIDE-13856) Test jQuery Mobile Palette Wizards on different platforms
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13856?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-13856:
----------------------------------
Attachment: ubuntu_64_large_font_toggle.png
> Test jQuery Mobile Palette Wizards on different platforms
> ---------------------------------------------------------
>
> Key: JBIDE-13856
> URL: https://issues.jboss.org/browse/JBIDE-13856
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: jsp/jsf/xml/html source editing
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Fix For: 4.1.0.Alpha2
>
> Attachments: ubuntu_64_button.png, ubuntu_64_checkboxes.png, ubuntu_64_cjeckbox.png, ubuntu_64_collapsible.png, ubuntu_64_dialog.png, ubuntu_64_footerbar.png, ubuntu_64_grid.png, ubuntu_64_headerbar.png, ubuntu_64_large_font_toggle.png, ubuntu_64_link.png, ubuntu_64_listview.png, ubuntu_64_navbar.png, ubuntu_64_page.png, ubuntu_64_radio.png, ubuntu_64_slider.png, ubuntu_64_textinput.png, ubuntu_64_toggle.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
13 years, 3 months