summaryrefslogtreecommitdiff
path: root/test/files/presentation/parse-invariants/src
diff options
context:
space:
mode:
authorSeth Tisue <seth@tisue.net>2017-02-13 16:10:29 -0800
committerSeth Tisue <seth@tisue.net>2017-02-13 16:10:29 -0800
commit1371a216d81836b79d9b60afd5481c088bf5c438 (patch)
tree76250ebf207857405881f73d26529c894a8f8e0d /test/files/presentation/parse-invariants/src
parent7311a29a992db1d3d16a73a9c49c80b0a4383103 (diff)
downloadscala-1371a216d81836b79d9b60afd5481c088bf5c438.tar.gz
scala-1371a216d81836b79d9b60afd5481c088bf5c438.tar.bz2
scala-1371a216d81836b79d9b60afd5481c088bf5c438.zip
during bootstrap, don't build scala-parser-combinators or -swing
I see no further reason to include them in the bootstrap process. Adriaan agrees (in-person discussion). note that the community build makes sure the modules still compile as we make changes to Scala. as for actually publishing scala-parser-combinators and scala-swing when we make binary incompatible changes to Scala, I think it's fine to consider that properly the job of the module maintainers, rather than properly the job of this script. (if we want more automation on that, we could make some elsewhere, keeping that concern separate from actual bootstrapping concerns.) scala-xml, scala-partest, and scalacheck (commented out at the moment) remain in this script since they are all actually still part of the bootstrapping picture. fixes https://github.com/scala/scala-dev/issues/302 , so that integrate-bootstrap will pass again (currently it fails, since scala-parser-combinators merged Scala.js support)
Diffstat (limited to 'test/files/presentation/parse-invariants/src')
0 files changed, 0 insertions, 0 deletions