cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Bowser (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CB-6727) build.xml in Android SDK directory is not found when new SDK installed or project moved to another computer
Date Fri, 13 Jun 2014 20:45:03 GMT

     [ https://issues.apache.org/jira/browse/CB-6727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Joe Bowser updated CB-6727:
---------------------------

    Component/s: CLI
         Labels: build  (was: build easyfix)

This is actually not an easy fix, and goes back to how the platforms ideally need to be treated
as a build artifact.

> build.xml in Android SDK directory is not found when new SDK installed or project moved
to another computer
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: CB-6727
>                 URL: https://issues.apache.org/jira/browse/CB-6727
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: Android, CLI
>    Affects Versions: 3.4.0
>         Environment: Windows 8.1 (possibly other operating systems as well)
>            Reporter: Ceyhun Can √úLKER
>            Priority: Minor
>              Labels: build
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> When I moved my project to another computer my cordova project stopped building. Error
was due to the imported ant buildfile of Android SDK was not found. I saw that local.properties
file in platforms/android folder contains a fixed path, and thought that if I comment it out,
sdk.dir would be taken from environment; but it wasn't the case. After extensive searching
and looking through verbose output, I found out that platforms/android/CordovaLib contains
another properties file. After changing the path there problem solved.
> My suggestion to this problem would be that, since these are generated file and not really
meant to be changed, defaults should remain in those files but they should be overridden by
environment variables. I guess this would solve this portability issue with respect to development
environment.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message