避免多个Android项目之间布局文件命名冲突的方法

Che*_*eng 5 android

目前,我有一个 Android 项目,由 1 个主项目和多个库项目组成。

就在最近,我意识到如果主项目和库项目之间有相同的布局文件名,可能会发生不好的事情。

third-party-library-project
    - res
        - layout
            - actionbar_custom_view_done_discard.xml
main-project
    - res
        - layout
            - actionbar_custom_view_done_discard.xml
Run Code Online (Sandbox Code Playgroud)

因此,如果在 中third-party-library-project,如果您在其活动中有一行代码,

final View customActionBarView = inflater.inflate(
                R.layout.actionbar_custom_view_done_discard, null);
Run Code Online (Sandbox Code Playgroud)

布局文件命名冲突导致的错误堆栈跟踪

FATAL EXCEPTION: main
java.lang.RuntimeException: Unable to start activity ComponentInfo{org.yccheok.jstock.gui/group.pals.android.lib.ui.lockpattern.LockPatternActivity}: android.view.InflateException: Binary XML file line #24: Error inflating class <unknown>
    at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2059)
    at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2084)
    at android.app.ActivityThread.access$600(ActivityThread.java:130)
    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1195)
    at android.os.Handler.dispatchMessage(Handler.java:99)
    at android.os.Looper.loop(Looper.java:137)
    at android.app.ActivityThread.main(ActivityThread.java:4745)
    at java.lang.reflect.Method.invokeNative(Native Method)
    at java.lang.reflect.Method.invoke(Method.java:511)
    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
    at dalvik.system.NativeStart.main(Native Method)
Caused by: android.view.InflateException: Binary XML file line #24: Error inflating class <unknown>
    at android.view.LayoutInflater.createView(LayoutInflater.java:613)
    at com.android.internal.policy.impl.PhoneLayoutInflater.onCreateView(PhoneLayoutInflater.java:56)
    at android.view.LayoutInflater.onCreateView(LayoutInflater.java:660)
    at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:685)
    at android.view.LayoutInflater.rInflate(LayoutInflater.java:746)
    at android.view.LayoutInflater.parseInclude(LayoutInflater.java:830)
    at android.view.LayoutInflater.rInflate(LayoutInflater.java:736)
    at android.view.LayoutInflater.inflate(LayoutInflater.java:489)
    at android.view.LayoutInflater.inflate(LayoutInflater.java:396)
    at android.view.LayoutInflater.inflate(LayoutInflater.java:352)
    at group.pals.android.lib.ui.lockpattern.LockPatternActivity.initActionBar(LockPatternActivity.java:356)
    at group.pals.android.lib.ui.lockpattern.LockPatternActivity.onCreate(LockPatternActivity.java:347)
    at android.app.Activity.performCreate(Activity.java:5008)
    at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1079)
    at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2023)
    ... 11 more
Caused by: java.lang.reflect.InvocationTargetException
    at java.lang.reflect.Constructor.constructNative(Native Method)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:417)
    at android.view.LayoutInflater.createView(LayoutInflater.java:587)
    ... 25 more
Caused by: android.content.res.Resources$NotFoundException: Resource is not a Drawable (color or path): TypedValue{t=0x2/d=0x7f010137 a=-1}
    at android.content.res.Resources.loadDrawable(Resources.java:1892)
    at android.content.res.TypedArray.getDrawable(TypedArray.java:601)
    at android.widget.TextView.<init>(TextView.java:614)
    at android.widget.TextView.<init>(TextView.java:442)
    ... 28 more
Run Code Online (Sandbox Code Playgroud)

如果我将布局 XML 文件更改third-party-library-project为actionbar_custom_view_done_discard1.xml,则运行时错误将消失。

如果库项目的数量很少,这不是问题。冲突可以通过简单的重命名轻松解决。然而,当遇到大量的图书馆项目时,有什么有效的方法或策略来克服这个问题?

Com*_*are 4

Library projects need to ensure that their resource names will be distinctive and not collide with other library projects, such as by applying a prefix to those resource names.

请注意,显然新的基于 Gradle 的构建系统支持资源子目录。我还没有尝试过这一点,但如果子目录名称构成资源 ID 的一部分,那么将资源放在一个独特的子目录中将有助于保持资源 ID 的不同(至少对于非values资源而言)。