April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-625) JBDS-IS 8.0.1: Create an article about upgrading from previous to current version of JBDS-IS

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-625?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-625: ------------------------------------ [~supriya.bharadwaj], could you get this into an article on the CSP and paste the link here please? We need to provide the B*MS team with the links for their splash page earlier than the release date. You can implement any further changes directly in the article. > JBDS-IS 8.0.1: Create an article about upgrading from previous to current version of JBDS-IS > -------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-625 > URL: https://issues.jboss.org/browse/TOOLSDOC-625 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > > From Petr's feedback: > c) instructions on upgrading and uninstalling the IS are missing altogether, compared to the Fuse Tooling installation guide > JBDS-IS docs team has committed to this in time for GA. > * Create and populate the upgrading article > * Send link to Gemma for B*MS splash page -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-631) JBDS-IS 8.0.2: Update the upgrading article

by Misha Ali (JIRA)

Misha Ali created TOOLSDOC-631: ---------------------------------- Summary: JBDS-IS 8.0.2: Update the upgrading article Key: TOOLSDOC-631 URL: https://issues.jboss.org/browse/TOOLSDOC-631 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Reporter: Misha Ali Assignee: Misha Ali -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-632) JBDS-IS 8.0.2: Update the Installation Document & add uninstall instructions

by Misha Ali (JIRA)

Misha Ali created TOOLSDOC-632: ---------------------------------- Summary: JBDS-IS 8.0.2: Update the Installation Document & add uninstall instructions Key: TOOLSDOC-632 URL: https://issues.jboss.org/browse/TOOLSDOC-632 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Reporter: Misha Ali Assignee: Misha Ali -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-630) JBDS-IS 8.0.2: Generate Release Notes

by Misha Ali (JIRA)

Misha Ali created TOOLSDOC-630: ---------------------------------- Summary: JBDS-IS 8.0.2: Generate Release Notes Key: TOOLSDOC-630 URL: https://issues.jboss.org/browse/TOOLSDOC-630 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Reporter: Misha Ali Assignee: Misha Ali -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18515) Cordova Plugin discovery wizard has broken layout

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18515?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-18515: --------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Cordova Plugin discovery wizard has broken layout > ------------------------------------------------- > > Key: JBIDE-18515 > URL: https://issues.jboss.org/browse/JBIDE-18515 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.CR1 > Environment: JBT 4.2.0.CR2-v20141005-0541-B267 Fedora 19 KDE 64 bit Java Oracle 8 > Reporter: Vlado Pakan > Priority: Minor > Fix For: 4.3.0.Beta1 > > Attachments: brokenlayoutdirectory.png, brokenlayoutgit.png > > > 1. Create Hybrid Mobile Project > 2. Open Cordova Configuration Editor > 3. Open dialog to add plugin from Git > !brokenlayoutgit.png! > 4. Open dialog to add plugin from Directory and select some directory > ERROR: Selected directory is not displayed in dialog > !brokenlayoutdirectory.png! > Once dialog is resized all looks correct in both cases. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19472) Switch to use the new plugin syntax on config.xml

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19472?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-19472: --------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Switch to use the new plugin syntax on config.xml > ------------------------------------------------- > > Key: JBIDE-19472 > URL: https://issues.jboss.org/browse/JBIDE-19472 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 4.3.0.Beta1 > > > Cordova CLI started using <plugin> to persist plugin that needs to be restored. We need to switch to use <plugin> instead of <feature> -- 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 closed JBDS-3394. ------------------------------ Resolution: Done > 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-3271) Cordova App Splash Screen Support

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBDS-3271?page=com.atlassian.jira.plugin.... ] Gorkem Ercan resolved JBDS-3271. -------------------------------- Resolution: Done Thym 0.3, which fixes this issue, is delivered to builds > Cordova App Splash Screen Support > --------------------------------- > > Key: JBDS-3271 > URL: https://issues.jboss.org/browse/JBDS-3271 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid, requirements > Reporter: Burr Sutter > Assignee: Gorkem Ercan > Fix For: 9.0.0.Alpha2 > > > As a HTML5+Cordova mobile app developer, I need to change the splash screen associated with the application launch. -- 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 updated JBDS-3394: ------------------------------- CDW devel_ack: + (was: ?) Status: New (was: 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 > 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] (JBIDE-19471) Cordova platform targeting

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19471?page=com.atlassian.jira.plugi... ] Gorkem Ercan resolved JBIDE-19471. ---------------------------------- Resolution: Done Thym 0.3, which fixes this issue, is delivered to builds > Cordova platform targeting > -------------------------- > > Key: JBIDE-19471 > URL: https://issues.jboss.org/browse/JBIDE-19471 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 4.3.0.Alpha2 > > > Since cordova ceased to do cadence releases and started doing individual platform releases, it is harder for us to be compatible with Cordova CLI. > Also it is making it confusing for users since there is no concept of Cordova release anymore. > We need to support targeting individual cordova platform and version combinations instead of the single cordova version that we use today. -- 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