問題描述

我正在使用 gradle 構建的應用程序中導入一個 android 庫，如下所示:

I'm importing an android library in an application built with gradle, like that:

dependencies {
    compile 'com.example:great-lib:0.1-SNAPSHOT'
}

此庫僅包含要在 webview 中使用的資產、js、css 和圖像，布局如下:

This library contains only assets, js, css and images to be used in a webview, with a layout like that:

assets/
|-> great.css
|-> great.min.js
|-> great.min.js.map
|-> js/
|   |-> plop.js
|   |-> foo.js
|   ...
|-> img/
|   ...

js 文件夾包含源文件(用于源映射).我想在調試版本中包含它和 .map 文件，并且在發布版本中只有縮小的 js，但我找不到這樣做的方法.

The js folder contains source files (to be used with source maps). I would like to include it and the .map file for the debug builds, and have only the minified js in release builds, but I can't find a way to do that.

到目前為止，我已經嘗試過:

So far I've tried :?

android {
    // this doesn't exclude anything
    packageOptions {
        exclude 'assets/js'
    }
    buildTypes {
        release {
            // this does exclude the js folder, but in both release and debug
            aaptOptions {
                ignoreAssetsPattern "!js"
            }
        }
    }
}

知道我想要的是否可以實現，如果可以，如何實現?

Any idea if what I want is possible to achieve, and if so how?

(我也想過發布兩個版本的庫(great-lib和great-lib-debug)，并且在中有依賴debugCompile 和 releaseCompile，但我寧愿避免這種情況并發布單個版本)

(I've also thought of publishing two versions of the library (great-lib and great-lib-debug), and have the dependency in debugCompile and releaseCompile, but I'd prefer avoiding that and publishing a single version)

推薦答案

我最終做了以下事情:

android.applicationVariants.all { variant ->

  if (variant.name.contains('Release')) {
    // exclude source and sourcemap from release builds
    def noJsSourceTask = task("delete${variant.name}JsSource", type: Delete) {
      delete "${buildDir}/intermediates/assets/${variant.dirName}/js"
      delete "${buildDir}/intermediates/assets/${variant.dirName}/great.min.js.map"
    }
    variant.mergeAssets.finalizedBy noCeJsSourceTask
  }
}

它工作正常，但有幾件事我不太喜歡:

It works ok, but there are a few things I don't really like:

• 我正在處理任務完成后生成的文件(finalizedBy)，因此它不適用于最新"檢查.但這僅適用于發布版本，我更頻繁地進行調試
• 要刪除的文件的路徑是手動構建的.我不確定它是否足夠通用，可以按原樣在其他項目中重用
• 我根據它們的名稱選擇變體.我會喜歡更有條理的東西.

• I'm touching at the files produced by a task after it is done (the finalizedBy), so it doesn't work well with "up-to-date" checking. But it's only for release builds, I'm doing debug ones more often
• the path of the files to delete is manually built. I'm not sure if it's generic enough to be reused in other projects as-is
• I'm selecting the variants based on their name. I would have liked something more structured.

這篇關于排除發布構建類型的資產的文章就介紹到這了，希望我們推薦的答案對大家有所幫助，也希望大家多多支持html5模板網！