Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jun 18 10:23
    scala-steward synchronize #1361
  • Jun 18 10:23
    scala-steward synchronize #1378
  • Jun 18 10:04

    github-actions[bot] on gh-pages

    Updated github pages from commi… (compare)

  • Jun 18 10:02

    lefou on main

    github release script: don't us… (compare)

  • Jun 18 07:40
    scala-steward synchronize #1361
  • Jun 18 07:40
    scala-steward synchronize #1378
  • Jun 18 07:27

    github-actions[bot] on gh-pages

    Updated github pages from commi… (compare)

  • Jun 18 07:19

    lefou on main

    maven release script: don't use… (compare)

  • Jun 17 16:23
    scala-steward synchronize #1361
  • Jun 17 16:23
    scala-steward synchronize #1378
  • Jun 17 15:04

    github-actions[bot] on gh-pages

    Updated github pages from commi… (compare)

  • Jun 17 14:55
    lefou closed #1366
  • Jun 17 14:55

    lefou on main

    Update scalajs-linker, ... to 1… (compare)

  • Jun 16 20:31
    forty closed #1381
  • Jun 16 20:02
    forty opened #1381
  • Jun 16 12:09
    scala-steward synchronize #1361
  • Jun 16 12:09
    scala-steward synchronize #1366
  • Jun 16 12:09
    scala-steward synchronize #1378
  • Jun 16 11:02

    github-actions[bot] on gh-pages

    Updated github pages from commi… (compare)

  • Jun 16 10:53

    lefou on main

    Adapted scalafmt config and ref… (compare)

Oliver
@xthemage:synapse.xthemage.net
[m]
cool. Thanks!
Tobias Roeser
@lefou
"*" -> "*" will exclude all
Aaron Schweiger
@aschweig
I am getting started with Mill. It looks to be a quite promising alternative to sbt. I am trying to set up a simple build.sc with Scala 3. I understand that mill foo.docJar generates the docJar, but when I run it I see my scalac compiler options coming through: e.g., "bad option '-feature' was ignored" -- what am I missing? (./mill foo.compile works as expected.)
Guillaume Martres
@smarter
try with 3.0.1-RC1
Tobias Roeser
@lefou
IIRC in scala 3 the scaladoc tool is based on the compiler and also accepts options. In mill we default to use the same options used for scalac, but you can override and/or customize via the scalaDocOptions target.
Aaron Schweiger
@aschweig
thx --
def scalaDocOptions = Seq("") // <-- works; super.scalaDocOptions() yields "bad option '-feature' was ignored"
Guillaume Martres
@smarter
there's a bug in 3.0.0 which is fixed in 3.0.1-RC1 where it warns about these options instead of ignoring them
setting def scalaDocOptions = Seq("") might lead to weird failures for example when using scala.js so I don't recommend it
@aschweig
Aaron Schweiger
@aschweig
@smarter Thanks!
heksesang
@heksenlied:matrix.org
[m]
I am getting a lot of errors like this in the Metals output when importing the build definition from mill:
2021.06.05 20:09:38 ERROR error processing file:///Users/heksesang/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/com/typesafe/config/1.3.3/config-1.3.3-sources.jar
Florian Schmaus
@Flowdalic
Can mill show me the dependency tree?
The only slightly related thing I found was mill mill.scalalib.Dependency/showUpdates
ahh ivyDepsTree
Brandon Stilson
@bbstilson

hey folks. i'm hitting this error attempting to compile my project. this is the full error:

```

build.sc:53: `T.command` definitions must have 1 parameter list
  implicit lazy val millDiscover: _root_.mill.define.Discover[this.type] = _root_.mill.define.Discover[this.type]
                                                                                                      ^
Compilation Failed
my build.sc file has 38 lines, so i'm not really sure where this is from
but since it's coming from the mill internals, i'm not sure how i can fix it in my build
Brandon Stilson
@bbstilson
i think it's my own module.

I had this:

def deployLambda = T.command

but I think it needs to be:

def deployLambda() = T.command
heksesang
@heksenlied:matrix.org
[m]
A T.command always need to be defined with a parameter clause.
Targets (i.e. T) should not have parameter clauses, while commands (i.e. T.command) should have them (including an empty one if the command has no parameters).
Florian Schmaus
@Flowdalic
Can I have a Scala 3 mill project using Scala 2.13 libs?
Tobias Roeser
@lefou
@Flowdalic Yes. Just add a .withDottyCompat(scalaVersion()) to your ivy"..." deps.
Florian Schmaus
@Flowdalic
@lefou whoot whoot, great, thanks :)
hmm, but as soon as I set scalaVersion to 3.0.0 mill fails to resolve a dependency that appears to be non existent:
Resolution failed for 1 modules:
--------------------------------------------
  org.scalameta:semanticdb-scalac_3.0.0:4.4.10
Florian Schmaus
@Flowdalic
ok, this is probably scalacenter/scalafix#1316
Ólafur Páll Geirsson
@olafurpg
@Flowdalic you can remove the semanticdb-scalac compiler plugin for Scala 3 projects. The Scala 3 compiler has built-in support for SemanticDB with the -Xsemanticdb compiler option
Florian Schmaus
@Flowdalic
Thanks, but this really appears to be related to scalafix not yet supporting Scala 3: joan38/mill-scalafix#46
Ólafur Páll Geirsson
@olafurpg
@Flowdalic the semanticdb-scalac dependency should not be declared in the build because this artifact doesn't exist for Scala 3. It's not a scalafix issue.
Florian Schmaus
@Flowdalic
Thanks for the help :)
Tobias Roeser
@lefou
Main branch now targets mill 0.10 and is binary incompatible: https://github.com/com-lihaoyi/mill/discussions/1376
heksesang
@heksenlied:matrix.org
[m]
Is the mill-scalafix plugin still binary compatible with mill versions that target 0.10?
Another thing, I noticed that mill occasionally copies the Java runtime jar to the project root folder when running the BSP server. I assume it is related to the fact that MillBuildServer sets val home: Path = evaluator.rootModule.millSourcePath in ctx and ClassLoader.makeUrls uses ctx.home.
heksesang
@heksenlied:matrix.org
[m]
@lefou: When is 0.10 planned to release? And is there a plan to start releasing the latest commits to Github again soon (so that they can be downloaded by tools)?
Tobias Roeser
@lefou
@heksenlied:matrix.org No planned date, but it will take some time I think.
But the snapshot process is still enabled, just use the latest one, and ignore the fact that its version starts with 0.9
As soon we have some binary compat check mechanism in place we will cut a 0.10 milestone release to get external plugins ready.
I'm working more or less alone on mill core atm, so there is no better answer to ETA questions, sorry.
Tobias Roeser
@lefou
About the java runtime jar, AFAIK Java 9 and above don't include it anymore, so we package it ourself on demand.
heksesang
@heksenlied:matrix.org
[m]
Yeah, but it usually puts it in the ammonite home, but there seem to be something that causes it to sometimes put it at the project root instead (seems to be when using the mill bsp).
heksesang
@heksenlied:matrix.org
[m]
Looks like it puts it there everytime I run the "Metals: Connect to build server" command in vscode.
Tobias Roeser
@lefou
@heksenlied:matrix.org We use Ctx.home as base location for rt.jar. It is overridable, so maybe this is what's happening.
Damian Reeves
@DamianReeves
How does one go about changing proxy settings for mill if you are behind a corporate proxy? It doesn’t seem like HTTP_PROXY and the like carry over
Tobias Roeser
@lefou
@DamianReeves Have you tried: mill -D http.proxyHost=server -D http.proxyPort=8080 ?
Adrien Piquerez
@adpi2

@heksenlied:matrix.org asked

@lefou: Is it currently possible to debug applications with breakpoints when using mill as BSP server?

There is the scala-debug-adapter project that can be integrated into any Scala BSP server to add the debug capability. It is already used by Bloop and sbt.
We intended to make the integration with Mill as a Google summer of code project (description here), but it has not been selected in the end. So, if anyone wants to take it on that would be great!