February 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-16659) Create 'platforms' and 'merges' sub-directories in the Hybrid Mobile project structure

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16659?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-16659: -------------------------------------- We used to create the platforms directory. I have removed it later because it just created an empty directory that was never used. platforms directory on the CLI is not a great idea for the CLI itself because it is basically hosting generated stuff the dependence to its existence is actually making it hard for CLI to share projects or easily update them to new versions. I agree with the sub directories of the merges for supported platforms. > Create 'platforms' and 'merges' sub-directories in the Hybrid Mobile project structure > -------------------------------------------------------------------------------------- > > Key: JBIDE-16659 > URL: https://issues.jboss.org/browse/JBIDE-16659 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: aerogear-hybrid > Affects Versions: 4.1.1.Final > Reporter: Vineet Reynolds > Fix For: 4.2.x > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Currently the Hybrid Mobile project structure is very nearly similar to the project structure created by the Cordova CLI. It simply lacks the {{platforms}} and {{merges}} sub-directories. > When attempting to use the Cordova CLI, the {{platforms}} directory needs to be created at the very least, followed by execution of the {{cordova platform add android}} or {{cordova platform add ios}} CLI commands. This eventually sets up the native SDK projects that can be built with ADT or XCode. > We should attempt to create a {{platforms}} sub-dir so that the hybrid mobile project is compatible with Cordova CLI. Additionally, if possible (due to the presence of a nested ADT sub-project), we should try and use the {{platforms}} directory as the default export location of the created native projects. This would ensure that exporting of the project in Eclipse is more or less equivalent to the {{cordova platform add android}} + {{cordova prepare android}} or {{cordova platform add ios}} + {{cordova prepare ios}} group of commands that create the native SDK projects and update their contents. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16644) Cordova Plugins are not loaded when they are not supported on certain platforms

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16644?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-16644: --------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Fix Version/s: 4.2.x > Cordova Plugins are not loaded when they are not supported on certain platforms > ------------------------------------------------------------------------------- > > Key: JBIDE-16644 > URL: https://issues.jboss.org/browse/JBIDE-16644 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.1.Final > Reporter: Vineet Reynolds > Fix For: 4.2.x > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > I added the [Cordova StatusBar plugin|https://github.com/apache/cordova-plugins/tree/master/statusbar] (supported on iOS and not on Android) to my HMT project. When run this project on an Android emulator, the statusbar plugin is not loaded by the tooling, even though a reference to the plugin is added to the starting page of the app - index.html. > See the [referenced screenshot|http://www.screencast.com/t/Jq5wZWLI8Ho] as an example. > This is not the case when using the Cordova CLI. The CLI commands ensure that the JS file for the StatusBar plugin is loaded on Android. While a 404 is not harmful in this case, it is certainly not recommended. > As a note, we must try and match the Cordova CLI behavior as much as possible, and this is a slight deviation from it - the iOS-specific plugin is referenced in {{android/assets/www/cordova_plugins.js}} in the Android project but is not copied to the {{android/assets/www/plugins}} directory in the project. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16388) Cordovasim does not use the Hybrid Mobile project's start page

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16388?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-16388: --------------------------------- Fix Version/s: 4.2.x > Cordovasim does not use the Hybrid Mobile project's start page > -------------------------------------------------------------- > > Key: JBIDE-16388 > URL: https://issues.jboss.org/browse/JBIDE-16388 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Affects Versions: 4.1.1.Final > Reporter: Vineet Reynolds > Assignee: Ilya Buziuk > Fix For: 4.2.x > > Attachments: startPage.png > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > When I run a Hybrid Mobile project under CordovaSim, it does not use the start page defined in {{config.xml}}. > If the application were to use a different application start page, say {{mobileapp.html}} in {{config.xml}}, CordovaSim reports the following error: http://www.screencast.com/t/8odNCS5FWK > I'm forced to create a new runtime configuration that explicitly defines the start page again. This is not necessary for running under the Android emulator or device, and is a problem only under CordovaSim. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16389) Query parameters are not allowed in the runtime configuration for CordovaSim

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16389?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-16389: --------------------------------- Fix Version/s: 4.2.x > Query parameters are not allowed in the runtime configuration for CordovaSim > ---------------------------------------------------------------------------- > > Key: JBIDE-16389 > URL: https://issues.jboss.org/browse/JBIDE-16389 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Affects Versions: 4.1.1.Final > Reporter: Vineet Reynolds > Assignee: Ilya Buziuk > Fix For: 4.2.x > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Related to JBIDE-16388, I'm creating a page: {{mobileapp.html}} that employs a query parameter ({{?target=cordova}}) to trigger the condition relevant to hybrid applications. The Hybrid Mobile application uses the REST APIs hosted on OpenShift via absolute URLs instead of relative URLs. The logic makes use of the presence/absence of the query parameter to use absolute (cloud) URLs instead of relative URLs. > When I create a runtime configuration to bypass JBIDE-16388 (to specify {{mobileapp.html}} as the start page), I cannot specify '?' in the path : http://www.screencast.com/t/ZYVMPtUWjq2 > This fails only in CordovaSim, and the app works when run in emulators/devices. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16275) [Android] Export/Import Hybrid/Native Project

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16275?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-16275: --------------------------------- Fix Version/s: 4.2.x > [Android] Export/Import Hybrid/Native Project > --------------------------------------------- > > Key: JBIDE-16275 > URL: https://issues.jboss.org/browse/JBIDE-16275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Reporter: Burr Sutter > Fix For: 4.2.x > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > The Export feature creates a project that is not easily importable back into JBDS - my guess is due to project naming. > http://www.screencast.com/t/BVHrka4e > Switching workspaces seems to do the trick -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16352) [iOS] iOS bundle identifier not escaped when exporting project

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16352?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-16352: --------------------------------- Fix Version/s: 4.2.x > [iOS] iOS bundle identifier not escaped when exporting project > -------------------------------------------------------------- > > Key: JBIDE-16352 > URL: https://issues.jboss.org/browse/JBIDE-16352 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Reporter: Tadeas Kriz > Assignee: Gorkem Ercan > Fix For: 4.2.x > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > When the project is exported as native xcode project, and the application name contains for example a space, this space is then exported in the bundle identifier, which then makes the compilation of the project fail. For example, if the name is "My Application", the bundle ID becomes "My Application" as well, even though it should be for example "MyApplication" (underscore is illegal character as well). -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16312) Support importing of Hybrid Mobile projects into workspace

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16312?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-16312: --------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Fix Version/s: LATER > Support importing of Hybrid Mobile projects into workspace > ---------------------------------------------------------- > > Key: JBIDE-16312 > URL: https://issues.jboss.org/browse/JBIDE-16312 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Affects Versions: 4.1.1.Final > Reporter: Vineet Reynolds > Fix For: LATER > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Currently, to import a Hybrid Mobile project, I need to import it as a plain Eclipse project, while ensuring that the original Eclipse project file (.project) is present that contains the desired project natures. > If the .project file is disallowed in version control, then this becomes a bit tricky since the .project file needs to be recreated. > It would be better to allow support for importing an existing directory into the workspace as a Hybrid Mobile project (like importing existing android project, existing maven projects etc.) via the Eclipse Import menu. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16212) [Android] Retain the Android project builder log in the Console view for the "Run as ..." tasks

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16212?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-16212: --------------------------------- Fix Version/s: 4.2.x > [Android] Retain the Android project builder log in the Console view for the "Run as ..." tasks > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-16212 > URL: https://issues.jboss.org/browse/JBIDE-16212 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Affects Versions: 4.1.1.CR1 > Reporter: Vineet Reynolds > Fix For: 4.2.x > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > When attempting to run a newly created hybrid mobile project (with no changes) on an Android emulator, the deployment to the emulator failed. > The Eclipse workspace log contained no information but the following entry: > {noformat} > !ENTRY org.jboss.tools.aerogear.hybrid.android.core 4 0 2013-12-04 14:50:34.841 > !MESSAGE APK installation did not succeed > {noformat} > The error dialog displayed the same message. The Ant build log was not available in the Console view, thus providing no info about whether the build failed or why it failed in a subsequent step. It would be useful to retain this build log in the Console View for debugging purposes or log the build output to a file on disk. > Note - I worked around the reported deployment failure by explicitly choosing the AVD to deploy to. For some reason, the hybrid tools was starting an AVD with API level 7. But the feature request is still valid since build or deployment failure could occur due to any reason (like an expired Debug certificate) and I had to rule out a build failure first. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-15769) Only Android parameters added to parameters table

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15769?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-15769: --------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Fix Version/s: 4.2.x > Only Android parameters added to parameters table > ------------------------------------------------- > > Key: JBIDE-15769 > URL: https://issues.jboss.org/browse/JBIDE-15769 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.1.Beta1 > Reporter: Michelle Murray > Assignee: Gorkem Ercan > Fix For: 4.2.x > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > In Cordova Configuration Editor, Platform Properties mode: > 1. Click Add for first features table (opens Cordova Plugin Discovery window) > 2. Select check box for cordova item (e.g., org.apache.cordova.camera) > 3. Click Next > 4. Click Finish > Outcomes: > * "Camera" is added to feature table > * "android-package" is added to parameter table > * Following is added to file in config.xml mode > {noformat} > <feature name="Camera"> > <param name="android-package" value="org.apache.cordova.camera.CameraLauncher" /> > <param name="ios-package" value="CDVCamera" /> > </feature> > {noformat} > So looks like only the Android parameter is being added to the parameter table. Should the iOS parameter be automatically added to the parameter table too? -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-15837) Improve the CordovaJS library provider

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15837?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-15837: --------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Fix Version/s: 4.2.x > Improve the CordovaJS library provider > -------------------------------------- > > Key: JBIDE-15837 > URL: https://issues.jboss.org/browse/JBIDE-15837 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Affects Versions: 4.1.1.Beta1 > Reporter: Gorkem Ercan > Assignee: Denis Golovin > Fix For: 4.2.x > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > The default inference engine fails to infer cordova types properly therefore most of them are not available for code assist. > JS library provider is not scanning for changes to runtime or the added/removed plugins. It should adjust to those changes. -- 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, 1 month

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 February 2014