cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Grieve (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CB-6892) Cordova Android unable to resolve org.apache.cordova (Mac)
Date Sun, 08 Jun 2014 00:44:01 GMT

    [ https://issues.apache.org/jira/browse/CB-6892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14021038#comment-14021038
] 

Andrew Grieve commented on CB-6892:
-----------------------------------

Not sure I fully followed what the problem is. Would be really helpful to have a copy &
paste of your terminal to see what commands were typed and what error messages came out. e.g.
{quote}
cordova create foo a.b.c foo
cd foo
cordova platform add android
cordova build android
{quote}

As for the .jar, Cordova switched from using a .jar to using an Android Library dependency.
Basically, what used to be cordova-x.x.x.jar is now CordovaLib. Using a sub-library allows
the framework to include assets and makes it so that by default you can step into Cordova
native framework methods using a debugger and actually see the source.

> Cordova Android unable to resolve org.apache.cordova (Mac)
> ----------------------------------------------------------
>
>                 Key: CB-6892
>                 URL: https://issues.apache.org/jira/browse/CB-6892
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android
>    Affects Versions: 3.5.0
>            Reporter: Bruno Braga
>
> After update from 3.2 to 3.5 my android project stopped to compile.
> I think something broke in a recent update with Cordova.
> My problem is the same reported at http://forum.ionicframework.com/t/unable-to-resolve-org-apache-cordova-mac/4445
> Another guy tested each Cordova version (android + mac + eclipse) and that is the results:
> ------------------------------------------------
> 3.4.1-0.1.0 - After my success in the previous post,I deleted CordovaLib from the platfiorms/Android
directory. Cordova was unable to rebuild it - works if it already exists (which may be why
they didn't catch this bug - it affects brand new projects).
> 3.2.0-0.4.0 - does not build (note - seemed to have alot of plugins included)
> 3.3.1-0.4.2 - works if you start with a fresh new folder - you can't just ugrade, you
have to start fresh and copy your app files back in
> 3.5.0-0.2.4 (latest) - fails on a clean build
> 3.5.0-0.2.1 - fails on clean build
> 3.4.1-0.1.0 - fails on clean build
> 3.4.0-0.1.3 - fails on clean build
> 3.4.0-0.1.0 - fails on clean build
> 3.4.0-rc.2 - could not install via npm - its gone...
> 3.3.1-0.4.23.3.1-0.4.2 - SUCCESS! WORKS
> now to jump ahead and upgrade cordova to latest and try rebuilding on top of old project
with CordovaLib already built:
> 3.5.0-0.2.4 - the latest!
> Rebuilds, but output different - no line breaks in the output, but it works. There seems
to be alot of operations different than the early version - like a degug.apk being created.
> To recap I did this to fix it [ATTENTION: BAND-AID SOLUTION FOLLOWS]:
> Install old version of cordova from February, 2014
> sudo npm -g uninstall cordova
> sudo npm -g install cordova@3.3.1-0.4.23.3.1-0.4.2
> delete previous project
> rm -Rf wishthisworked
> cordova create wishthisworked
> cordova platform add android
> cordova build android
> DONE with old version, now to install the latest version
> sudo npm -g uninstall cordova
> sudo npm -g install cordova@3.5.0-0.2.4
> within directory, build again - WORKS
> Going forward :
> Cordova needs to fix this bug. I'll report my findings to them.
> The bad thing is every new project won't build for Android, without first uninstalling
the new version of Cordova and going back to the old version from Feb, 2014, or try copying
the CordovaLib directory to the platform/android directory - but that is stupid ... We shouldn't
have to do this... (I have not tested this by the way)
> So there's definitely a bug, it shouldn't be this hard. And even if its an issue with
my environment when all is said and done, it would be REAL NICE to have some code in the setup
that checks for that and tells the user/installer. Otherwise, I have to dig into this more
to find out why Ant is broke, and I don't have time for that. I can just do my app in native
Android and Xcode faster than fixing this issue.
> ------------------------------------------------



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

Mime
View raw message