Skip to content

sbt-dotty plugin fails to aggregate multiple projects #3172

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
allanrenucci opened this issue Sep 25, 2017 · 2 comments
Closed

sbt-dotty plugin fails to aggregate multiple projects #3172

allanrenucci opened this issue Sep 25, 2017 · 2 comments
Assignees

Comments

@allanrenucci
Copy link
Contributor

allanrenucci commented Sep 25, 2017

Consider the following scenario:

I have a project structure like this

.
├── bar
│   └── src
│       └── main
│           └── scala
│               └── Bar.scala
│
├── foo
│   └── src
│       └── main
│           └── scala
│               └── Foo.scala
│
├── build.sbt
│
└── project
    ├── build.properties
    └── plugins.sbt

and a build.sbt as follow:

lazy val foo = project
  .in(file("foo"))

lazy val bar = project
  .in(file("bar"))

lazy val root = project
  .in(file("."))
  .aggregate(foo, bar)

If plugin.sbt is empty, then I can type sbt compile and it will compile Foo.scala and Bar.scala. However, if plugin.sbt contains

addSbtPlugin("ch.epfl.lamp" % "sbt-dotty" % "0.1.5")

then when I type sbt compile, it will do nothing. I can still do sbt bar/compile or sbt foo/compile

@smarter
Copy link
Member

smarter commented Sep 25, 2017

This has something to do with the use of Def.derive in DottyIDEPlugin but I don't understand what. As a workaround you can add:

  .disablePlugins(dotty.tools.sbtplugin.DottyIDEPlugin)

to every sbt project in the build.

@smarter
Copy link
Member

smarter commented Sep 25, 2017

Opened an issue against sbt because I'm baffled: sbt/sbt#3580

smarter added a commit that referenced this issue Sep 27, 2017
Fix #3172: sbt-dotty breaks aggregrated tasks
ennru pushed a commit to ennru/dotty that referenced this issue Sep 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants