I try to use the version 1.1.0-M8 (from https://oss.sonatype.org/content/repositories/releases/io/get-coursier/coursier-cli_2.12/1.1.0-M8/coursier-cli_2.12-1.1.0-M8-standalone.jar) of coursier instead of the default one (1.0) but I get some

ClassNotFoundException: coursier.cli.Coursier

. A diff between the 2 jar I have show me that they are pretty different in their structure, can you give me an hint from where come the one in the dropbox ?

i believe we have a slightly different version of coursier on the dropbox (built with the pants BUILD files in the coursier repo i think?) @wide-energy-11069 would know the specific difference

# 3rdparty/jvm/io/get-coursier/BUILD

jar_library(name='coursier-dep',
  jars=[
    jar(org='io.get-coursier', name='coursier-cli_2.12', rev='1.1.0-M8'),
  ],
)

jvm_binary(
    name='coursier-bin',
    main='coursier.cli.Coursier',
    dependencies=[
        ':coursier-dep',
    ])

jvm_app(
    name='coursier',
    binary=':coursier-bin',
)

./pants bundle 3rdparty/jvm/io/get-coursier:coursier

just for future reference @brief-engineer-67497 you can use

scala_jar(org='io.get-coursier', name='coursier-cli', rev='1.1.0-M8')

which avoids the

_2.12

(it uses the scala version you're using)

thx @aloof-angle-91616 for the tip, but in this precise case I did not want it to be bind to my scala version

pants is using an older version right now https://github.com/pantsbuild/pants/commit/33c85286fdc0c57045d264e50b6ecf555be118dd

we used it as the value for

bootstrap_jar_url

https://github.com/coursier/coursier/releases/download/pants_release_1.5.x/coursier-cli-1.1.0.cf365ea27a710d5f09db1f0a6feee129aa1fc417.jarshould be official enough right? @brief-engineer-67497

thx ^_^

ok. so are you unblocked?

we are ! thank you

are you saying

coursier-cli_2.12-1.1.0-M8-standalone.jar

works with subprocess but fails with nailgun?

well, messes the jar as far nailgun is concerned

thanks for the pointer, maybe we can remove that line upstream

you're welcome !

although you might not want to set

execution_strategy=subprocess

globally for perf reasons

yeah, I figured. but what I'm not sure is

[resolve.coursier]
execution_strategy=subprocess

will impact only coursier bootstrap or every coursier resolution ?

coursier invocation

ok, anyway still faster than ivy and the real deal is compilation & test so we will be ok ^_^

i also made https://github.com/pantsbuild/pants/pull/6857 for

scala_jar()

-- thanks for clarifying @brief-engineer-67497 that was not your situation though, that was a hasty assumption on my part (i have actually just done the same thing this morning for a jvm tool)

No problem! Thank you for the spontaneous tip ^_^

Thank you for all these tips

@wide-energy-11069 so, actually the

execution-strategy=subprocess

seems to be ignored by the intellij plugin because the problem reappear when refreshing the project (or on initial loading)