[
https://issues.apache.org/jira/browse/CB-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Clelland updated CB-4154:
-----------------------------
Description:
Because of [this bug|https://code.google.com/p/android/issues/detail?id=54828],
the project.properties file gets overwritten, poorly, when importing a new
Android project into eclipse.
The solution appears to be simple: Changing the {{target=Google Inc.:Google
APIs:17}} in project.properties to {{target=android-17}}.
We don't use any of the APIs in Cordova, so changing to bare API 17 shouldn't
have any affect. (This also affects new projects only; if a developer wants to
use the Google APIs, it's a trivial -- and obvious -- step to switch it, and it
won't ever revert.)
was:
Because of [this
bug]{https://code.google.com/p/android/issues/detail?id=54828}, the
project.properties file gets overwritten, poorly, when importing a new Android
project into eclipse.
The solution appears to be simple: Changing the {{target=Google Inc.:Google
APIs:17}} in project.properties to {{target=android-17}}.
We don't use any of the APIs in Cordova, so changing to bare API 17 shouldn't
have any affect. (This also affects new projects only; if a developer wants to
use the Google APIs, it's a trivial -- and obvious -- step to switch it, and it
won't ever revert.)
> Eclipse project properties overwritten when importing new project
> -----------------------------------------------------------------
>
> Key: CB-4154
> URL: https://issues.apache.org/jira/browse/CB-4154
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Reporter: Ian Clelland
> Assignee: Ian Clelland
>
> Because of [this
> bug|https://code.google.com/p/android/issues/detail?id=54828], the
> project.properties file gets overwritten, poorly, when importing a new
> Android project into eclipse.
> The solution appears to be simple: Changing the {{target=Google Inc.:Google
> APIs:17}} in project.properties to {{target=android-17}}.
> We don't use any of the APIs in Cordova, so changing to bare API 17 shouldn't
> have any affect. (This also affects new projects only; if a developer wants
> to use the Google APIs, it's a trivial -- and obvious -- step to switch it,
> and it won't ever revert.)
--
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
