let me explain in SBT terms, because that's the only way I know how
the dependencies work that way:
core:test <- laws:main <- core:main
where
<- means depends on
so there's a bit of a circular dependency thing going on, if you consider that 1 module in 2 different configurations is not 2 modules
woah. Ok. I might have actually found a bug.
here's one of the errors I'm running into: I have a package called
It appears that scalac and bloop interpret the following differently:
kantan.codecs.shapeless. In a test file, I need to import shapeless.HNil.It appears that scalac and bloop interpret the following differently:
package kantan.codecs.shapeless
import shapeless.HNil
scalac things
shapeless is _root_.shapeless, bloop that it's kantan.codecs.shapeless
if I rewrite that explicitly to:
package kantan.codecs.shapeless
import _root_.shapeless.HNilThen bloop has no issue compiling it
how do i install the "launcher" referenced here: https://scalacenter.github.io/bloop/docs/launcher-reference
thanks, that should work. Another issue i'm having: when I run bloop server on my jenkins host, the output just hangs on this:
$ bloop server
Unable to load nailgun-version.properties.
NGServer [UNKNOWN] started on address localhost/127.0.0.1 port 8212.no further output is produced and the script doesn't terminate.
Which might fail due to network issues, or might just take a very long time
If you have full control over your environment, you'd be better off installing the Bloop server beforehand
IIRC, the launcher would look for a Bloop executable in your
$PATH, and also in some default location
i manually installed bloop using the curl method
The server is actually running and ready for requests
back to the launcher: it fails for me with
Exception in thread "main" java.lang.NoClassDefFoundError: scala/collection/immutable/List
Well, I guess you have to provide Scala JARs in the classpath
that makes sense, kind of a bummer though
If you're going to compile Scala code, you must have Scala JARs somewhere in the system
anyway, I can manage the launcher thing, there are lots of ways to get the scala jar
from inside the docker container though. The ~/.sbt folders maps to a different path on the host
Do I understand correctly that you generate the configs not on the same machine on which you're trying to run Bloop?
If so, I see two ways to solve that problem
Either edit these configs manually so that paths to JARs point to the correct locations
Or make sure that
~/.sbt exists on your host and contains all the artifacts that are referenced in the configs
i'll move any further questions there, i didn't realize the gitter was deprecated. Thanks for sticking around and helping out