viswaramamoorthy / gradle-util-plugins Goto Github PK

Fix for windows gradle long classpath issue. Fixes JavaExec tasks that error out with message "CreateProcess error=206, The filename or extension is too long"

License: MIT License

Groovy 100.00%

windows classpath issue manifest jar plugin gradle windows-gradle-long-classpath manifestclasspath-plugin javaexec-task

gradle-util-plugins's Introduction

gradle-util-plugins

When classpath for a Gradle JavaExec task is long, Windows command executions give error because of limitation to command line length greater than 32K.

With a number of classpath dependencies in a large project, typically JavaExec Gradle task fails with error "The filename or extension is too long" and this would be a stopping error. To solve this issue, use ManifestClasspath plugin.

ManifestClasspath plugin creates a manifest jar for jar files in the classpath of JavaExec task and sets the classpath with manifest jar.

Usage

To use the plugin, define a dependency in build script and have plugin entry in Gradle project.

build.gradle snippet to use ManifestClasspath plugin

Build script snippet for plugins DSL for Gradle 2.1 and later

plugins {
  id "com.github.ManifestClasspath" version "0.1.0-RELEASE"
}

Build script snippet for use in older Gradle versions or where dynamic configuration is required

buildscript {
  repositories {
    maven {
      url "https://plugins.gradle.org/m2/"
    }
  }
  dependencies {
    classpath "gradle.plugin.com.github.viswaramamoorthy:gradle-util-plugins:0.1.0-RELEASE"
  }
}

apply plugin: "com.github.ManifestClasspath"

Build

./gradlew build

gradle-util-plugins's People

Contributors

Stargazers

Watchers

Forkers

romanbjit johnjqc amrendranarayanmishra tresat sometxdude madhusudhan-srinivas tianyijushi rivancic emmanuel-irabor

gradle-util-plugins's Issues

Support manifest based classpath for tasks extending JavaForkOptions

Currently manifest classpath is used only for JavaExec tasks.

Since on windows gradle test also may fail because of long classpath, the plugin should support Test tasks and in fact all tasks extending JavaForkOptions

@viswaramamoorthy i'm ready to pick it up and provide a PR if you're currently busy.

Still having the issue with longClassPath

I am still having issue with Long Classpath after applying the plugin
java.io.IOException: Cannot run program "java": CreateProcess error=206, The filename or extension is too long
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
at com.ford.auto.parallel.runtime.ParallelFeatureRunner.run(ParallelFeatureRunner.java:27)
at com.ford.auto.parallel.runtime.ParallelRunner.runFeature(ParallelRunner.java:143)
at com.ford.auto.parallel.runtime.ParallelRunner.lambda$0(ParallelRunner.java:47)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

InvalidUserDataException using this plugin in Gradle 5.1.1

When I apply this plugin to my project, I get the following exception:

Caused by: org.gradle.api.InvalidUserDataException: Main class name has not been configured and it could not be resolved
        at org.springframework.boot.gradle.plugin.MainClassConvention.lambda$resolveMainClass$0(MainClassConvention.java:67)
        at org.springframework.boot.gradle.plugin.MainClassConvention.resolveMainClass(MainClassConvention.java:67)
        at org.springframework.boot.gradle.plugin.MainClassConvention.call(MainClassConvention.java:62)
        at org.gradle.util.GUtil.uncheckedCall(GUtil.java:459)
        at org.gradle.api.internal.ConventionAwareHelper$2.doGetValue(ConventionAwareHelper.java:82)
        at org.gradle.api.internal.ConventionAwareHelper$MappedPropertyImpl.getValue(ConventionAwareHelper.java:126)
        at org.gradle.api.internal.ConventionAwareHelper.getConventionValue(ConventionAwareHelper.java:109)
        at org.springframework.boot.gradle.tasks.run.BootRun_Decorated.getMain(Unknown Source)
        at org.gradle.api.tasks.JavaExec.exec(JavaExec.java:77)
        at org.springframework.boot.gradle.tasks.run.BootRun.exec(BootRun.java:50)

I'll try to post a minimal test case tomorrow.

I have a multi-module project, so it could be(?) related to:
#8

If plugin is applied to more than one project in a multi-build project, the resulting manifest jars are incorrect

The listener is applied at a global scope => it receives notifications from all tasks in the multi-build. If two separate build.gradle files apply the plugin, two listeners are created and they both transform each JavaExec task => the second and later end up writing a manifest jar the points to itself:

Manifest-Version: 1.0
Class-Path: file:/C:/repos/.../build/mfjars/taskName_ManifestJar.jar

Add the plugin to Gradle Plugin repository

If you add your plugin to the Gradle Plugin Repository then applying the plugin would be even easier:

plugins {
  id "gradle-util-plugins" version "0.1.0-RELEASE"
}

and that's it - no need for additional classpath entries!

Support for transformClassesWithDesugarFor

Could you add support for transformClassesWithDesugarFor.* tasks as well?

Based on this issue #1 a assume, the task is not handled by your plugin

Can't get it working

Hi there! We've been trying to apply this plugin in the project FastHub, but it still throws CreateProcess error=206.
We have also tried to manipulate with apply location without any success.

Here are commits and build results:

Commit	AppVeyor CI Build
k0shk0sh/FastHub@`5e84f79`	https://ci.appveyor.com/project/k0shk0sh/fasthub/build/342
k0shk0sh/FastHub@`c1bc5b1`	https://ci.appveyor.com/project/k0shk0sh/fasthub/build/345
k0shk0sh/FastHub@`bc787c2`	https://ci.appveyor.com/project/k0shk0sh/fasthub/build/347

Can you help us, please?

README.md

typo in ./gradelw build

must be ./gradlew build