onslip/gradle-one-jar

The gradle-one-jar project is a Gradle plugin that uses One-JAR, a specialised Class-Loader written by Simon Tuffs (http://one-jar.sourceforge.net/), for building self-contained executable jars that include all dependencies.

gradle-one-jar's Issues

Does not include dependencies configured as "implementation"

Dependencies are not included into the one-jar, if they are configured in implementation scope. However, it works correctly with compile scope, which is now deprecated in Gradle.

I can provide an example if required, but it's very much straight-forward to reproduce this issue.

Gradle 4 support

Transfering this here because it's biting me. Maybe I'll look into it, but anyone else feel free of course... As it stands this version of the plugin is relatively happy in gradle 3, but I and evidently some others have hit this problem in gradle 4+

rholder#34

It looks like something is relying on a toString() somewhere and an object has changed to an object without a useful toString() implementation in 4.

Gradle 7+ compatibility

gradle-one-jar with Gradle 7+ results in

   > Could not create task of type 'OneJar'.
      > Could not get unknown property 'runtime' for configuration container of type org.gradle.api.internal.artifacts.configurations.DefaultConfigurationContainer.

because Gradle [removed the 'runtime' configuration] after 6.x

It would be nice to have a version that works with current Gradle versions.

MR Jar issues

Not actually an issue for this plugin, but perhaps a useful note/discussion/warning until (if) the underlying one-jar issue can be dealt with.

Multi-release artifacts are not finding their MR components. The specific case of primary interest is the newer versions of Log4J which output the following:

WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance.

Adding Multi-Release: true to the Manifest does not solve the problem as it should (see https://stackoverflow.com/a/54713830)

As I said, this is not the plugin's fault, but I suspect users will want to be aware, and if a solution becomes available it can be documented here.

Switch to Gradle 7.0 causes "unknown property 'runtime'"

When I switch to Gradle 7.0 https://github.com/ytai/ioio/pull/250/files I run into a build error

Current Behavior

I run into

> Could not create task ':HelloIOIOConsole:distJar'.
   > Could not create task of type 'OneJar'.
      > Could not get unknown property 'runtime' for configuration container of type org.gradle.api.internal.artifacts.configurations.DefaultConfigurationContainer.

This is the causing block

plugins {
    id "com.github.onslip.gradle-one-jar" version "1.0.6"
}

task distJar(type: OneJar) {                              <--- This is the error line !
    mainClass = 'ioio.examples.hello_console.HelloIOIOConsole'
}

Steps to Reproduce

https://github.com/ytai/ioio/pull/250/files

Environment

Here you see the error https://github.com/ytai/ioio/pull/250/checks?check_run_id=2340438978