Skip to content

build circularly dependent Scala modules with fresh, not stock compiler? #154

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
SethTisue opened this issue Oct 28, 2015 · 2 comments
Closed

Comments

@SethTisue
Copy link
Member

as previously detailed at #142, dbuild's "assemble" builds Scala first, but then doesn't use the Scala it just built to build circularly dependent modules like scala-xml. this is arguably a bug, or at least not ideal, given that the whole idea of dbuild is to build everything using a freshly-built Scala compiler

dbuild builds Scala and its modules using the "assemble" build system. the doc on that build system says "the nested projects are built independently, each in isolation", which can be read as describing the behavior in this ticket as intentional. it's not trying and failing to override the module's Scala version — it isn't even trying.

@adriaanm
Copy link
Contributor

Maybe we should just use our own release script to build scala and have dbuild to the rest?

@SethTisue
Copy link
Member Author

superseded by #274

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants