Skip to content
This repository was archived by the owner on Sep 30, 2020. It is now read-only.
This repository was archived by the owner on Sep 30, 2020. It is now read-only.

Gradle 5.1 > Cannot infer Scala class path because no Scala library Jar was found #81

Closed
Closed
Gradle 5.1 > Cannot infer Scala class path because no Scala library Jar was found#81
@ghilainm

Description

@ghilainm
ghilainm
opened on Jan 17, 2019

Hi guys,

I have used a simple setup following your conventions and got the following error:
Cannot infer Scala class path because no Scala library Jar was found

I have run gradle gatlingRun.

build.gradle:

plugins {
    id "com.github.lkishalmi.gatling" version "3.0.2"
}

gatling {
    toolVersion = '3.0.2'
    scalaVersion = '2.11.8'
    includeMainOutput = false
    includeTestOutput = false
    jvmArgs = [ '-server', '-Xms512M', '-Xmx512M' ]
}

Output of --dry-run

Configuration on demand is an incubating feature.
:system-tests:compileJava SKIPPED
:system-tests:compileScala SKIPPED
:system-tests:processResources SKIPPED
:system-tests:classes SKIPPED
:system-tests:compileTestJava SKIPPED
:system-tests:compileTestScala SKIPPED
:system-tests:processTestResources SKIPPED
:system-tests:testClasses SKIPPED
:system-tests:compileGatlingJava SKIPPED
:system-tests:compileGatlingScala SKIPPED
:system-tests:processGatlingResources SKIPPED
:system-tests:gatlingClasses SKIPPED
:system-tests:gatlingRun SKIPPED

I don't understand why the task :system-tests:compileTestScala is created as I have excluded mainOutput and testOutput .

It seems to be the culprit :).

Thx for your help.

Activity

eshepelyuk

eshepelyuk commented on Jan 17, 2019

@eshepelyuk
eshepelyuk
on Jan 17, 2019 · edited by eshepelyuk
Collaborator

Have you tried with Gradle 4.x ? If not - plz do and report. Also plz attach project archive to be able to reproduce the issue.

eshepelyuk
closed this as completedon Jan 30, 2019
ghilainm

ghilainm commented on Jan 30, 2019

@ghilainm
ghilainm
on Jan 30, 2019
Author

@eshepelyuk I didn't try with Gradle 4.X. My project was a minimal example, I can't unfortunately publish it. But I just applied the plugin as shown in your documentation and followed your conventions, nothing fancy. Did you find the issue?

eshepelyuk

eshepelyuk commented on Jan 30, 2019

@eshepelyuk
eshepelyuk
on Jan 30, 2019
Collaborator

Hello

  1. plz try in 4.x
  2. just obfuscate the code and send me a minimal project reproducing the bug, the project must contain gradle wrapper as well. Unfortunately this is a single way to debug the issues. Otherwise I won't be able to help.
zeburek

zeburek commented on Oct 25, 2019

@zeburek
zeburek
on Oct 25, 2019

@eshepelyuk

Made a little investigation. Configuration like this breaks gatlingRun.

Removing scalaVersion from configuration and cleaning project makes it run again.

It seems that scalaVersion works wrong way. Tested on Gradle 5.3 and 4.10

plugins {
    id "com.github.lkishalmi.gatling" version "3.2.9"
}

repositories {
    mavenCentral()
}

group 'test'
version '0.0.1'

apply plugin: 'scala'

dependencies {
    compile 'org.scala-lang:scala-library:2.13.1'
}

gatling {
    toolVersion = '3.2.1'
    scalaVersion = '2.13.1'
    includeMainOutput = false
    includeTestOutput = false
}

I will reopen this issue because I've found a cause.

zeburek
mentioned this on Oct 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @ghilainm@eshepelyuk@zeburek

        Issue actions
          Gradle 5.1 > Cannot infer Scala class path because no Scala library Jar was found · Issue #81 · lkishalmi/gradle-gatling-plugin