[
https://issues.apache.org/jira/browse/CB-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489714#comment-13489714
]
Joe Bowser commented on CB-1810:
--------------------------------
Hey
I just started fixing up our broken JUnit Tests, and I discovered that the
recent refactors broke the CordovaWebView standalone component. This means
that anyone who is using the CordovaWebView as a standalone component should
probably not upgrade to 2.2.0 and that we'll have to issue a 2.2.1 release to
address this issue.
It seems that for some reason deviceready is no longer firing. I think this
may have to do with the recent changes to plugins as well as the addition of a
thread pool. I'm going to commit the fixes to the tests today, but you can
recreate the issue by pulling down this debug repo, putting it in Eclipse and
making it use Cordova as a library.
https://github.com/infil00p/CordovaActionView/tree/debug_version
Also, you can debug this using the default activity on the test project,
although the test project still needs a lot of cleaning to be done.
It sucks that we missed this, but we really need to make sure we don't break
the tests when we do a refactor.
I'll add more details to the bug soon. This harsh sucks, because I don't think
this will be an easy fix. :(
> CordovaWebView does not work as a component
> -------------------------------------------
>
> Key: CB-1810
> URL: https://issues.apache.org/jira/browse/CB-1810
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Affects Versions: 2.2.0
> Reporter: Joe Bowser
> Assignee: Joe Bowser
> Priority: Blocker
> Fix For: 2.3.0
>
>
> Apparently CordovaWebView no longer works as a stand-alone component. We may
> have to release a 2.2.1 because of this issue.
--
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
