April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19547) Use cordova platform downloads from npm

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19547?page=com.atlassian.jira.plugi... ] Gorkem Ercan reassigned JBIDE-19547: ------------------------------------ Assignee: Gorkem Ercan > Use cordova platform downloads from npm > --------------------------------------- > > Key: JBIDE-19547 > URL: https://issues.jboss.org/browse/JBIDE-19547 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Affects Versions: 4.2.3.Final > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > > Switch to downloading the cordova platforms from npm and as a consequence limit the downloadable platform versions to what is available on npm. The plan is to continue to support building applications for Cordova version>3.0.0 but when a developer wants to download a cordova platform using JBDS/JBT, only versions 3.5.0 and later will be available. Configuring a manually downloaded cordova platforms on JBDS will still be available. > Around Cordova 3.5.0 time, Apache Cordova project switched to using npm for distributing cordova platforms. npm provides a much better infrastructure compared to the old way which is basically git archive mechanism. We already had cases where apache infrastructure was not available for maintenance. Also the lack of CDN does not help either. So I think JBDS should follow Apache Cordova and start using npm for downloading cordova platforms. Below are the list of relevant cordova platforms and version that are available today from npm. > cordova-ios > ['3.5.0', '3.6.0', '3.6.1', '3.6.3', '3.7.0', '3.8.0' ] > cordova-android > [ '3.5.0','3.5.1','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0','3.7.1' ] > cordova-wp8 > [ '3.5.0','3.6.0-dev','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0-dev','3.7.0','3.7.1' ] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19547) Use cordova platform downloads from npm

by Gorkem Ercan (JIRA)

Gorkem Ercan created JBIDE-19547: ------------------------------------ Summary: Use cordova platform downloads from npm Key: JBIDE-19547 URL: https://issues.jboss.org/browse/JBIDE-19547 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: aerogear-hybrid Affects Versions: 4.2.3.Final Reporter: Gorkem Ercan Switch to downloading the cordova platforms from npm and as a consequence limit the downloadable platform versions to what is available on npm. The plan is to continue to support building applications for Cordova version>3.0.0 but when a developer wants to download a cordova platform using JBDS/JBT, only versions 3.5.0 and later will be available. Configuring a manually downloaded cordova platforms on JBDS will still be available. Around Cordova 3.5.0 time, Apache Cordova project switched to using npm for distributing cordova platforms. npm provides a much better infrastructure compared to the old way which is basically git archive mechanism. We already had cases where apache infrastructure was not available for maintenance. Also the lack of CDN does not help either. So I think JBDS should follow Apache Cordova and start using npm for downloading cordova platforms. Below are the list of relevant cordova platforms and version that are available today from npm. cordova-ios ['3.5.0', '3.6.0', '3.6.1', '3.6.3', '3.7.0', '3.8.0' ] cordova-android [ '3.5.0','3.5.1','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0','3.7.1' ] cordova-wp8 [ '3.5.0','3.6.0-dev','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0-dev','3.7.0','3.7.1' ] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19410: --------------------------------------------- yes, so please just have central not try and load p2 metadata if it is not available. right now it just makes you not want to have central loaded when developing. > earlyaccess still not failing gracefully > ---------------------------------------- > > Key: JBIDE-19410 > URL: https://issues.jboss.org/browse/JBIDE-19410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE) > start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently. > but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19546) Unhandled event loop exception when downloading Android engine

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19546?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-19546: ------------------------------------------- Steps to Reproduce: 1. Go to Hybrid Mobile Engines Preferences/Project Properties 2. Click download button and select version which is not already installed 3. Click OK, and after that click Cancel ASAP 4. See Error log {quote} !MESSAGE Unhandled event loop exception during blocked modal context. !STACK 0 org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:4477) at org.eclipse.swt.SWT.error(SWT.java:4392) at org.eclipse.swt.SWT.error(SWT.java:4363) 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.Control.setEnabled(Control.java:3303) at org.eclipse.jface.wizard.ProgressMonitorPart$1.handleEvent(ProgressMonitorPart.java:81) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) 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.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:172) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:387) at org.eclipse.thym.ui.internal.engine.EngineDownloadDialog.run(EngineDownloadDialog.java:347) at org.eclipse.thym.ui.internal.engine.EngineDownloadDialog.okPressed(EngineDownloadDialog.java:324) at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:466) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) 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.jface.window.Window.runEventLoop(Window.java:827) at org.eclipse.jface.window.Window.open(Window.java:803) at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection$5.handleEvent(AvailableCordovaEnginesSection.java:338) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) 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.jface.window.Window.runEventLoop(Window.java:827) at org.eclipse.jface.window.Window.open(Window.java:803) at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211) at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:63) at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) 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.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:172) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:387) at org.eclipse.thym.ui.internal.engine.EngineDownloadDialog.run(EngineDownloadDialog.java:347) at org.eclipse.thym.ui.internal.engine.EngineDownloadDialog.okPressed(EngineDownloadDialog.java:324) {quote} was: Steps to reproduce: 1. Go to Hybrid Mobile Engines Preferences/Project Properties 2. Click download button and select version which is not already installed 3. Click OK, and after that click Cancel ASAP 4. See Error log {quote} !MESSAGE Unhandled event loop exception during blocked modal context. !STACK 0 org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:4477) at org.eclipse.swt.SWT.error(SWT.java:4392) at org.eclipse.swt.SWT.error(SWT.java:4363) 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.Control.setEnabled(Control.java:3303) at org.eclipse.jface.wizard.ProgressMonitorPart$1.handleEvent(ProgressMonitorPart.java:81) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) 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.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:172) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:387) at org.eclipse.thym.ui.internal.engine.EngineDownloadDialog.run(EngineDownloadDialog.java:347) at org.eclipse.thym.ui.internal.engine.EngineDownloadDialog.okPressed(EngineDownloadDialog.java:324) at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:466) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) 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.jface.window.Window.runEventLoop(Window.java:827) at org.eclipse.jface.window.Window.open(Window.java:803) at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection$5.handleEvent(AvailableCordovaEnginesSection.java:338) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) 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.jface.window.Window.runEventLoop(Window.java:827) at org.eclipse.jface.window.Window.open(Window.java:803) at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211) at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:63) at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) 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.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:172) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:387) at org.eclipse.thym.ui.internal.engine.EngineDownloadDialog.run(EngineDownloadDialog.java:347) at org.eclipse.thym.ui.internal.engine.EngineDownloadDialog.okPressed(EngineDownloadDialog.java:324) {quote} > Unhandled event loop exception when downloading Android engine > -------------------------------------------------------------- > > Key: JBIDE-19546 > URL: https://issues.jboss.org/browse/JBIDE-19546 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha1 > Environment: Win 7, thym 0.2.0 > Reporter: Konstantin Marmalyukov > Assignee: Gorkem Ercan > Priority: Minor > > It smells like jface bug, but anyway it will be good to handle this exception -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-420) Enable support for a remote SAP tooling update site URL

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-420?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-420. ------------------------------ Resolution: Done Modified the ide-config.properties to create a property that may be used to identify the IS extras URL: https://github.com/jbosstools/jbosstools-download.jboss.org/commit/71b629... https://github.com/jbosstools/jbosstools-download.jboss.org/commit/26c879... Also established IS composites to hold the "extras" URLs (currently only component is SAP tooling): http://download.jboss.org/jbosstools/updates/development/luna/integration... http://download.jboss.org/jbosstools/updates/development/luna/integration... http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac... http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac... > Enable support for a remote SAP tooling update site URL > ------------------------------------------------------- > > Key: JBTIS-420 > URL: https://issues.jboss.org/browse/JBTIS-420 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 8.0.1.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 8.0.2.GA > > > Update the ide-config properties to establish the following: > jboss.site.integration-stack-extras.url|jbosstools|4.2=http://download.jb... > jboss.site.integration-stack-extras.url|devstudio|8=https://devstudio.red... > Also update the SAP POM accordingly. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19546) Unhandled event loop exception when downloading Android engine

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19546?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-19546: ------------------------------------------- Description: It smells like jface bug, but anyway it will be good to handle this exception (was: This is jface bug, but please add catch block to handle this exception) > Unhandled event loop exception when downloading Android engine > -------------------------------------------------------------- > > Key: JBIDE-19546 > URL: https://issues.jboss.org/browse/JBIDE-19546 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha1 > Environment: Win 7, thym 0.2.0 > Reporter: Konstantin Marmalyukov > Assignee: Gorkem Ercan > Priority: Minor > > It smells like jface bug, but anyway it will be good to handle this exception -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3392) Arquillian icon is missing in JBDS 8.1.0 Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3392?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3392: ----------------------------------- This is the exact same problem that was fixed in master with JBIDE-19330 > Arquillian icon is missing in JBDS 8.1.0 Central > ------------------------------------------------ > > Key: JBDS-3392 > URL: https://issues.jboss.org/browse/JBDS-3392 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.1.0.GA > Reporter: Len DiMaggio > Assignee: Mickael Istria > Attachments: JBDS_810_GA.png > > > See attached screenshot -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19546) Unhandled event loop exception when downloading Android engine

by Konstantin Marmalyukov (JIRA)

Konstantin Marmalyukov created JBIDE-19546: ---------------------------------------------- Summary: Unhandled event loop exception when downloading Android engine Key: JBIDE-19546 URL: https://issues.jboss.org/browse/JBIDE-19546 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.3.0.Alpha1 Environment: Win 7, thym 0.2.0 Reporter: Konstantin Marmalyukov Assignee: Gorkem Ercan Priority: Minor This is jface bug, but please add catch block to handle this exception -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3392) Arquillian icon is missing in JBDS 8.1.0 Central

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3392?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3392: ------------------------------- Attachment: JBDS_810_GA.png > Arquillian icon is missing in JBDS 8.1.0 Central > ------------------------------------------------ > > Key: JBDS-3392 > URL: https://issues.jboss.org/browse/JBDS-3392 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.1.0.GA > Reporter: Len DiMaggio > Assignee: Mickael Istria > Attachments: JBDS_810_GA.png > > > See attached screenshot -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3392) Arquillian icon is missing in JBDS 8.1.0 Central

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-3392: ---------------------------------- Summary: Arquillian icon is missing in JBDS 8.1.0 Central Key: JBDS-3392 URL: https://issues.jboss.org/browse/JBDS-3392 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: central Affects Versions: 8.1.0.GA Reporter: Len DiMaggio Assignee: Mickael Istria See attached screenshot -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2015