You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Angela Fowler (JIRA)" <ji...@apache.org> on 2013/05/30 05:25:19 UTC

[jira] [Created] (CB-3549) windows create.js building from distro is missing config.xml

Angela Fowler created CB-3549:
---------------------------------

             Summary: windows create.js building from distro is missing config.xml
                 Key: CB-3549
                 URL: https://issues.apache.org/jira/browse/CB-3549
             Project: Apache Cordova
          Issue Type: Bug
    Affects Versions: 2.7.0
         Environment: Windows 7
            Reporter: Angela Fowler
            Priority: Minor


If building from "distro" the create.js script expects to copy the config.xml from a folder called xml in the root directory which doesn't exist.
    exec('%comspec% /c copy "'+ROOT+'\\xml\\config.xml" "' + PROJECT_PATH + '\\res\\xml\\config.xml" /Y');

The project builds but with an empty \res\xml folder. Running the application causes the PluginManager to fail with an outdated message
       LOG.e(TAG, "=====================================================================================");
        LOG.e(TAG, "ERROR: plugin.xml is missing.  Add res/xml/plugins.xml to your project.");
        LOG.e(TAG, "https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-android.git;a=blob;f=framework/res/xml/plugins.xml");
        LOG.e(TAG, "=====================================================================================");


Would the script be improved by a variable set at the beginning of the script to determine if running from source or distro? In one place this is determined by the presence of the jar and js files. In another by the presence of the framework directory.

Should there be a strings.xml and main.xml for the distro as there is for the framework or are the copies created by Android sufficient?

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