Skip to content

About

Tool for inspecting Java resource bundles (i18n)

Topics

Resources

Code of conduct

Contributing

Stars

10 stars

Watchers

1 watching

Forks

Repository files navigation

Overview

Coverage Status Maven Central Javadocs MIT license Hits Of Code

The resourcebundle-core project can inspect projects and find unused properties keys or duplicate keys.

Please support this project by simply putting a Github Star ⭐

Share this library with friends on Twitter and everywhere else you can

If you love this project donation

License

The source code comes under the liberal MIT License, making resourcebundle-inspector great for all types of applications.

Import dependencies to your project

gradle (click to expand)

gradle dependency

Replace the variable ${latestVersion} with the current latest version: Maven Central

You can first define the version in the ext section and add than the following gradle dependency to your project build.gradle if you want to import the core functionality of resourcebundle-core:

define version in file gradle.properties

resourcebundleCoreVersion=${latestVersion}

or in build.gradle ext area

    resourcebundleCoreVersion = "${latestVersion}"

then add the dependency to the dependencies area

    implementation("io.github.astrapi69:resourcebundle-core:$resourcebundleCoreVersion")

with new libs.versions.toml file

If you use the new libs.versions.toml file for new automatic catalog versions update

[versions]
resourcebundle-core-version= "${latestVersion}"
[libraries]
resourcebundle-core = { module = "io.github.astrapi69:resourcebundle-core", version.ref = "resourcebundle-core-version" }

then add the dependency to the dependencies area

    implementation libs.resourcebundle.core
Maven (click to expand)

Maven dependency

The library is on Maven Central. Check out Maven Central for the latest release.

Add the following maven dependency to your project pom.xml if you want to import the core functionality of resourcebundle-core:

Then you can add the dependency to your dependencies:

<properties>
    ...
        <!-- resourcebundle-core version -->
        <resourcebundle-core.version>${latestVersion}</resourcebundle-core.version>
    ...
</properties>
    ...
    <dependencies>
    ...
            <!-- resourcebundle-core DEPENDENCY -->
            <dependency>
                <groupId>io.github.astrapi69</groupId>
                <artifactId>resourcebundle-core</artifactId>
                <version>${resourcebundle-core.version}</version>
            </dependency>
    ...
    </dependencies>
Snapshots (click to expand)

📸 Snapshots

Snapshot

This section describes how to import snapshot versions into your project. Add the following code snippet to your gradle file in the repositories section:

repositories {
   //...
    maven {
        name "Central Portal Snapshots"
        url "https://central.sonatype.com/repository/maven-snapshots/"
        mavenContent {
            snapshotsOnly()
        }
    }
}

Semantic Versioning

The versions of resourcebundle-core are maintained with the Semantic Versioning guidelines.

Release version numbers will be incremented in the following format:

<major>.<minor>.<patch>

For detailed information on versioning for this project you can visit this wiki page.

Verifying the release signatures

The releases on Maven Central are signed with the OpenPGP key

5B2F A6B1 1E29 8BC0 9287  F423 D8C4 0351 8C49 CA75

Releases after 6.1 are signed by its signing subkey

6D67 F844 2A6F CC96 BD7C  1B5E 9FCF 7C97 10E2 BD8D

valid until 2028-10-09; 6.1 and earlier were signed by the primary key itself. The key, with the subkey, is on keyserver.ubuntu.com and keys.openpgp.org.

To check a download, fetch the key once, then verify the signature that lies next to each file on Maven Central:

gpg --keyserver hkps://keys.openpgp.org --recv-keys 5B2FA6B11E298BC09287F423D8C403518C49CA75
gpg --verify resourcebundle-core-6.1.jar.asc resourcebundle-core-6.1.jar

gpg answers Good signature and prints the Primary key fingerprint, for a release signed by the subkey also the Subkey fingerprint. Both have to be the ones above. The warning that the key "is not certified with a trusted signature" only says that you have not marked the key as trusted in your own keyring; the fingerprints are what to compare.

Want to Help and improve it?

The source code for resourcebundle-core are on GitHub. Please feel free to fork and send pull requests!

Create your own fork of astrapi69/resourcebundle-core/fork

To share your changes, submit a pull request.

Don't forget to add new units tests on your changes.

Contacting the Developers

Do not hesitate to contact the resourcebundle-core developers with your questions, concerns, comments, bug reports, or feature requests.

  • Feature requests, questions and bug reports can be reported at the issues page.

Note

No animals were harmed in the making of this library.

Support this project

If resourcebundle-core is useful to you, a star on GitHub helps others find it. Sharing it or reporting a bug helps just as much.

If you would like to contribute financially, the channels are on the repository's Sponsor button, which reads .github/FUNDING.yml: GitHub Sponsors, Liberapay, Ko-fi and PayPal.

Similar projects

Here is a list of awesome projects for resource bundles:

Git hooks

The repository's git hooks live in .githooks: commit-msg where present, and pre-commit, which refuses a commit whose files Spotless would format. Activate them once per clone or worktree:

git config core.hooksPath .githooks

About

Tool for inspecting Java resource bundles (i18n)

Topics

Resources

Code of conduct

Contributing

Stars

10 stars

Watchers

1 watching

Forks

Releases

Sponsor this project

Packages

Used by

Contributors

Languages