On 6月27日, 上午10时49分, bazookier <[email protected]> wrote:
> On 6月27日, 上午3时12分, fadden <[email protected]> wrote:
>
>
>
>
>
> > On Jun 26, 12:55 am, bazookier <[email protected]> wrote:
>
> > > I have two classes declared in one package.
> > > One accesses the other.
> > > Made a dex file contain this whole package.
> > > When running, it reported the following error:
>
> > > Class resolved by unexpected DEX: ......
> > > ......
>
> > The message means it expected the class to be resolved from one DEX,
> > but it actually came from another; i.e. you have two copies of the
> > same class available to the app.
>
> > The "dexopt" optimizations assume that, if class A refers to class B
> > in the same DEX file, that it will come from there when the app runs.
> > If the class loader pulls class B from somewhere else, the
> > optimizations are invalid and could cause the VM to crash. So it
> > refuses to load class B.
>
> Then does sdk1.5_r1 core lib include the package
> org.apache.felix.metatype.internal
OK.It turns out a class refered by B is coupled with another one.
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---
