[JBoss JIRA] (JBIDE-15913) Export dialogs should check the Android SDK
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15913?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-15913:
----------------------------------------
Assignee: Gorkem Ercan
> Export dialogs should check the Android SDK
> -------------------------------------------
>
> Key: JBIDE-15913
> URL: https://issues.jboss.org/browse/JBIDE-15913
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Reporter: Gorkem Ercan
> Assignee: Gorkem Ercan
> Priority: Minor
> Fix For: 4.1.1.CR1
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> If a project is exported for Android without setting the Android SDK preferences. An error occurs. Export wizards should check the availability of the preferences.
> Steps:
> 1. Create a project
> 2. Export Native Platform Project
> 3. Select Android and Click finish.
--
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, 7 months
[JBoss JIRA] (JBIDE-15934) Run on Android Device does not work on OS X
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15934?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-15934:
----------------------------------------
Assignee: Gorkem Ercan
> Run on Android Device does not work on OS X
> -------------------------------------------
>
> Key: JBIDE-15934
> URL: https://issues.jboss.org/browse/JBIDE-15934
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Environment: OS X Mavericks
> Latest Android SDK
> JBDS 7.1.0.Beta1
> Nexus 7
> Reporter: Martin Malina
> Assignee: Gorkem Ercan
> Fix For: 4.1.1.CR1
>
>
> Following the instructions in JBIDE-15904 I am trying to run an app on an Android Device.
> This fails for me - I get: No developer enabled android device is attached to this computer please attach your device and try again. (Punctuation is missing, btw.)
> When I try to run adb devices, I can see the device is not there. Development mode is enabled on the device and it works for Vlado on Linux.
> I found out that using Run on Android Device somehow breaks the connection with the device - before I run that, "adb devices" shows the device just fine. After I run that, the device is no longer displayed.
> We even tried to deploy the app using adb install and it worked (while the device was still connected)
--
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, 7 months
[JBoss JIRA] (JBIDE-15843) Unable to add Cordova Plugins to a cordova project
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15843?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen reassigned JBIDE-15843:
-------------------------------------------
Assignee: Gorkem Ercan
> Unable to add Cordova Plugins to a cordova project
> --------------------------------------------------
>
> Key: JBIDE-15843
> URL: https://issues.jboss.org/browse/JBIDE-15843
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Environment: JBDS7.1.0.Beta1b Beta1-v20131102-1529-B493
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Priority: Critical
> Fix For: 4.1.1.CR1
>
>
> 1. Create Hybrid Mobile project
> 2. Open config.xml in Corodova Configuration editor
> 3. Click on button Add.. to add Feature
> 4. Select more features and click Finish
> 5. Click Yest to All in Overwrite Files dialog (many times)
> ASSERT: Plugins are added to project and to config.xml file
> 6. Remove added plugins from config.xml file and from project/plugins directory
> 7. Repeat steps 3. and 4. selecting the same plugins as before
> ERROR: No plugins added neither to project/plugins dir or config.xml file
> 8. Refresh project
> ERROR: Only first selected plugin is added to project/plugins directory and still no plugins added to config.xml file
--
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, 7 months
[JBoss JIRA] (JBIDE-15894) EAP 6.1 (instead of 6.1+) string in final stage of new server wizard
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15894?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-15894:
----------------------------------------
Assignee: Rob Stryker
> EAP 6.1 (instead of 6.1+) string in final stage of new server wizard
> --------------------------------------------------------------------
>
> Key: JBIDE-15894
> URL: https://issues.jboss.org/browse/JBIDE-15894
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.1.Beta1
> Environment: JBDS 7.1.0.Beta1b B493
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.1.1.CR1
>
> Attachments: eap-6.1.png
>
>
> There is still one place where the string wasn't properly updated from EAP 6.1 to 6.1+.
> (See JBIDE-15774 and JBIDE-15751 for reference of other jiras dealing with this.)
> When you create a server, on the last page where you choose either local or remote server, at the top there is JBoss Enterprise Application Platform 6.1 even though I'm creating EAP 6.2, so it's a bit confusing.
> !eap-6.1.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
12 years, 7 months
[JBoss JIRA] (JBIDE-15935) Android SDK not installed automatically on OS X
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15935?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-15935:
----------------------------------------
Assignee: Vlado Pakan
> Android SDK not installed automatically on OS X
> -----------------------------------------------
>
> Key: JBIDE-15935
> URL: https://issues.jboss.org/browse/JBIDE-15935
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.1.Beta1
> Environment: JBDS 7.1.0.Beta1
> OS X Mavericks
> Reporter: Martin Malina
> Assignee: Vlado Pakan
> Fix For: 4.1.1.CR1
>
> Attachments: Central_AndTools.png
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> When I install android tools from central and then I restart the IDE as requested, I should be asked to automatically download and install Android SDK (I got word it works this way on Linux). I got nothing like that on OS X.
> So I had to download and setup SDK manually.
--
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, 7 months
[JBoss JIRA] (JBIDE-15843) Unable to add Cordova Plugins to a cordova project
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15843?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-15843:
----------------------------------------
Summary: Unable to add Cordova Plugins to a cordova project (was: Unable to add Cordova Feature)
> Unable to add Cordova Plugins to a cordova project
> --------------------------------------------------
>
> Key: JBIDE-15843
> URL: https://issues.jboss.org/browse/JBIDE-15843
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Environment: JBDS7.1.0.Beta1b Beta1-v20131102-1529-B493
> Reporter: Vlado Pakan
> Priority: Critical
> Fix For: 4.1.1.CR1
>
>
> 1. Create Hybrid Mobile project
> 2. Open config.xml in Corodova Configuration editor
> 3. Click on button Add.. to add Feature
> 4. Select more features and click Finish
> 5. Click Yest to All in Overwrite Files dialog (many times)
> ASSERT: Plugins are added to project and to config.xml file
> 6. Remove added plugins from config.xml file and from project/plugins directory
> 7. Repeat steps 3. and 4. selecting the same plugins as before
> ERROR: No plugins added neither to project/plugins dir or config.xml file
> 8. Refresh project
> ERROR: Only first selected plugin is added to project/plugins directory and still no plugins added to config.xml file
--
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, 7 months
[JBoss JIRA] (JBIDE-15788) Download runtime wizard shouldn't complain if install folder doesn't exist
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15788?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-15788:
----------------------------------------
Assignee: Rob Stryker
> Download runtime wizard shouldn't complain if install folder doesn't exist
> --------------------------------------------------------------------------
>
> Key: JBIDE-15788
> URL: https://issues.jboss.org/browse/JBIDE-15788
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: runtime-detection, server
> Affects Versions: 4.1.1.Alpha2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Fix For: 4.1.1.CR1
>
> Attachments: install_folder_must_exist.png
>
>
> If the install folder is missing, the download runtime wizard should cope with it, instead of displaying an error (i.e. create the missing folders when necessary)
> - assert no EAP/AS7 are installed
> - create a new html5 project from central
> - click download and install for the server requirement
> - enter a non-existing location for the install folder
> !install_folder_must_exist.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
12 years, 7 months