April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19550) Fully export the Proxy interface package from forge

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19550?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-19550: ------------------------------------ Issue Type: Bug (was: Feature Request) > Fully export the Proxy interface package from forge > --------------------------------------------------- > > Key: JBIDE-19550 > URL: https://issues.jboss.org/browse/JBIDE-19550 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.3.Final > Reporter: Jess Sightler > Assignee: George Gastaldi > Fix For: 4.3.0.Alpha2 > > > This is needed for https://issues.jboss.org/browse/WINDUP-547 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19550) Fully export the Proxy interface package from forge

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19550?page=com.atlassian.jira.plugi... ] George Gastaldi reassigned JBIDE-19550: --------------------------------------- Assignee: George Gastaldi > Fully export the Proxy interface package from forge > --------------------------------------------------- > > Key: JBIDE-19550 > URL: https://issues.jboss.org/browse/JBIDE-19550 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.2.3.Final > Reporter: Jess Sightler > Assignee: George Gastaldi > Fix For: 4.3.0.Alpha2 > > > This is needed for https://issues.jboss.org/browse/WINDUP-547 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19550) Fully export the Proxy interface package from forge

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19550?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-19550: ------------------------------------ Fix Version/s: 4.3.0.Alpha2 > Fully export the Proxy interface package from forge > --------------------------------------------------- > > Key: JBIDE-19550 > URL: https://issues.jboss.org/browse/JBIDE-19550 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.2.3.Final > Reporter: Jess Sightler > Fix For: 4.3.0.Alpha2 > > > This is needed for https://issues.jboss.org/browse/WINDUP-547 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19550) Fully export the Proxy interface package from forge

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19550?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-19550: ------------------------------------ Affects Version/s: 4.2.3.Final > Fully export the Proxy interface package from forge > --------------------------------------------------- > > Key: JBIDE-19550 > URL: https://issues.jboss.org/browse/JBIDE-19550 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.2.3.Final > Reporter: Jess Sightler > Fix For: 4.3.0.Alpha2 > > > This is needed for https://issues.jboss.org/browse/WINDUP-547 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19550) Fully export the Proxy interface package from forge

by Jess Sightler (JIRA)

Jess Sightler created JBIDE-19550: ------------------------------------- Summary: Fully export the Proxy interface package from forge Key: JBIDE-19550 URL: https://issues.jboss.org/browse/JBIDE-19550 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: forge Reporter: Jess Sightler This is needed for https://issues.jboss.org/browse/WINDUP-547 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

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: --------------------------------------------- Now i'm back I can give full stacktrace: java.lang.RuntimeException: Current Eclipse instance doesn't support software installation. at org.jboss.tools.central.installation.InstallationChecker.getUnits(InstallationChecker.java:101) at org.jboss.tools.central.installation.InstallationChecker.getEarlyAccessUnits(InstallationChecker.java:79) at org.jboss.tools.central.installation.InstallationChecker.hasEarlyAccess(InstallationChecker.java:72) at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText$3.runInUIThread(JBossCentralEditor.java:574) All looks like something that can just be gracefully logged to error log instead of having a full modal dialog popup to all developers using PDE. > 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)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3394) Use cordova platform downloads from npm

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBDS-3394?page=com.atlassian.jira.plugin.... ] Gorkem Ercan commented on JBDS-3394: ------------------------------------ a) I do not know about examples (not even sure what examples we are referring to ) but we are not dropping the support for building/running engines older than 3.5.0. We are basically synching the list of downloadable engines with Cordova CLI. Also Cordova CLI did not have engine pinning supported until a month ago and we handle our own pinning (see b for details) so I am not sure what would be updated. b) If the project is referring to an earlier than 3.5.0 engine and you have the engine available locally nothing will happen. We support running those engines. If the engine is not present locally, we will prompt that the selected engine is not present and ask users to select one. In this case user either needs to download manually and install or select a 3.5.0 or later platform. > Use cordova platform downloads from npm > --------------------------------------- > > Key: JBDS-3394 > URL: https://issues.jboss.org/browse/JBDS-3394 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 9.0.0.Alpha2 > > > 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)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3394) Use cordova platform downloads from npm

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3394?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3394: ------------------------------------------- moved from jbide to jbds to get it ack'ed. The two only concerns I have is: a) do we have any examples that uses pre-3.5.0 versions that we need to get updated ? b) what happens if importing old/existing projects referring to these "overall" versions, will we gracefully convert them to use individual versions or how will that work ? > Use cordova platform downloads from npm > --------------------------------------- > > Key: JBDS-3394 > URL: https://issues.jboss.org/browse/JBDS-3394 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 9.0.0.Alpha2 > > > 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)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3394) Use cordova platform downloads from npm

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3394?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3394: -------------------------------------- Fix Version/s: 9.0.0.Alpha2 > Use cordova platform downloads from npm > --------------------------------------- > > Key: JBDS-3394 > URL: https://issues.jboss.org/browse/JBDS-3394 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 9.0.0.Alpha2 > > > 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)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3394) Use cordova platform downloads from npm

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3394?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3394: -------------------------------------- Project: Developer Studio (JBoss Developer Studio) (was: Tools (JBoss Tools)) Key: JBDS-3394 (was: JBIDE-19547) Workflow: CDW v1 (was: GIT Pull Request workflow ) Affects Version/s: (was: 4.2.3.Final) Component/s: aerogear-hybrid (was: aerogear-hybrid) Docs QE Status: NEW > Use cordova platform downloads from npm > --------------------------------------- > > Key: JBDS-3394 > URL: https://issues.jboss.org/browse/JBDS-3394 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid > 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)

11 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2015