sbt-proguard

KO | EN

gitlite — search

#llm #golang #machine-learning #linux #docker #java #windows #awesome #cli #kubernetes #security #mcp #ios #openai

(★ 99)

Proguard sbt plugin

파일 탐색기

최종 버전 다운로드 (.zip)

- - ci.yml
  - release.yml
- build.properties
- plugins.sbt
.gitignore
build.sbt
README.md

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

sbt-proguard
============

[sbt] plugin for running [ProGuard]. This plugin requires sbt 1.0.

[![Build Status](https://travis-ci.org/sbt/sbt-proguard.png?branch=master)](https://travis-ci.org/sbt/sbt-proguard)

Add plugin
----------

Add plugin to `project/plugins.sbt`. For example:

```scala
addSbtPlugin("com.github.sbt" % "sbt-proguard" % "{version}")
```

See [released versions][releases].

**Note**: earlier versions of sbt-proguard used the `"com.typesafe.sbt"` or `"com.lightbend.sbt"` organization.

Example
-------

A simple `build.sbt` with settings to configure sbt-proguard:

```scala
enablePlugins(SbtProguard)
Proguard/proguardOptions ++= Seq("-dontnote", "-dontwarn", "-ignorewarnings")
Proguard/proguardOptions += ProguardOptions.keepMain("some.MainClass")
Proguard/proguardOptions += ProguardOptions.mappingsFile("mappings.txt")`
```

Run proguard at the sbt shell with:

```shell
proguard
```

Specifying the proguard version
-------
In your `build.sbt`:
```scala
Proguard/proguardVersion := "7.6.1"
```

Available proguard versions: https://github.com/Guardsquare/proguard/releases

Filters
-------

Proguard supports file filtering for inputs, libraries, and outputs. In
sbt-proguard there are `File => Option[String]` settings for adding filters to
files.

For example, to add a `!META-INF/**` filter to just the scala-library jar:

```scala
Proguard/proguardInputFilter := { file =>
  file.name match {
    case "scala-library.jar" => Some("!META-INF/**")
    case _                   => None
  }
}
```

which will create the following proguard configuration:

```
-injars "/path/to/scala-library.jar"(!META-INF/**)
```

There are corresponding settings for libraries and outputs: `proguardLibraryFilter` and
`proguardOutputFilter`.

For more advanced usage the `proguardFilteredInputs`, `proguardFilteredLibraries`, and
`proguardFilteredOutputs` settings can be set directly.

Merging
-------

If the same path exists in multiple inputs then proguard will throw an error.
The conflicting paths can be resolved using file filters, as described above,
but this is not always the most useful approach. For example, `reference.conf`
files for the Typesafe Config library need to be retained and not discarded.

The sbt-proguard plugin supports pre-merging inputs, similar to creating an
assembly jar first. To enable this merging use:

```scala
Proguard/proguardMerge := true
```

Conflicting paths that are not identical will now fail at the merge stage. These
conflicting paths can have merge strategies applied, similar to the [sbt-assembly]
plugin.

Helper methods for creating common merges are available. These are:

- `discard` -- discard all matching entries
  - `first` -- only keep the first entry
  - `last` -- only keep the last entry
  - `rename` -- rename entries adding the name of the source
  - `append` -- append entries together into one file

The paths matched against in these helpers are normalised to be separated by `/`
regardless of platform. Paths can be matched exactly with a string or with a
regular expression.

The default strategy is to only discard `META-INF/MANIFEST.MF`. This same
strategy could be added with:

```scala
Proguard/proguardMergeStrategies += ProguardMerge.discard("META-INF/MANIFEST.MF")
```

Or all `META-INF` contents could be discarded with a regular expression:

```scala
Proguard/proguardMergeStrategies += ProguardMerge.discard("META-INF/.*".r)
```

To concatenate all `reference.conf` files together use:

```scala
Proguard/proguardMergeStrategies += ProguardMerge.append("reference.conf")
```

To discard all `.html` and `.txt` files you may use two strategies together:

```scala
Proguard/proguardMergeStrategies ++= Seq(
  ProguardMerge.discard("\\.html$".r),
  ProguardMerge.discard("\\.txt$".r) 
)
```

Completely custom merge strategies can also be created. See the plugin source
code for how this could be done.

Scala 3
---------------
ProGuard doesn't handle Scala 3's TASTy files, which contain much more information than Java's class files. Therefore, we need to post-process the ProGuard output JAR and remove all TASTy files for classes that have been obfuscated. To determine which classes have been obfuscated, you must configure the `-mappingsfile` option, e.g., via `Proguard/proguardOptions += ProguardOptions.mappingsFile("mappings.txt")`. See the [Scala 3 test project](src/sbt-test/proguard/scala3), which is included in the scripted tests.

Sample projects
---------------

There are some [runnable sample projects][samples] included as sbt scripted tests.

Contribution policy
-------------------

Contributions via GitHub pull requests are gladly accepted from their original
author. Before we can accept pull requests, you will need to agree to the
[Lightbend Contributor License Agreement][cla] online, using your GitHub account.

License
-------

[ProGuard] is licensed under the [GNU General Public License][gpl]. sbt and sbt scripts
are included in a [special exception][except] to the GPL licensing.

The code for this sbt plugin is licensed under the [Apache 2.0 License][apache].

[sbt]: https://github.com/sbt/sbt
[ProGuard]: https://www.guardsquare.com/en/proguard
[releases]: https://github.com/sbt/sbt-proguard/releases
[sbt-assembly]: https://github.com/sbt/sbt-assembly
[samples]: https://github.com/sbt/sbt-proguard/tree/master/src/sbt-test/proguard
[cla]: https://www.lightbend.com/contribute/cla
[gpl]: http://www.gnu.org/licenses/gpl.html
[except]: http://proguard.sourceforge.net/GPL_exception.html
[apache]: http://www.apache.org/licenses/LICENSE-2.0.html

sbt-proguard

파일 탐색기

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

sbt-proguard

파일 탐색기

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README