diff options
author | Adriaan Moors <adriaan.moors@typesafe.com> | 2013-07-04 19:40:59 -0700 |
---|---|---|
committer | Adriaan Moors <adriaan.moors@typesafe.com> | 2013-07-05 16:00:29 -0700 |
commit | a0a60e709fa8041a482f2389104b8c17443c5526 (patch) | |
tree | bcd1cd247ee37e3d40fd712962fed118447ced58 /src/eclipse/interactive | |
parent | 1b0fa91aa3f4d469505e5a1ff5d9cb1db0bdf662 (diff) | |
download | scala-a0a60e709fa8041a482f2389104b8c17443c5526.tar.gz scala-a0a60e709fa8041a482f2389104b8c17443c5526.tar.bz2 scala-a0a60e709fa8041a482f2389104b8c17443c5526.zip |
Add meta-information for dbuild.
The next version of [dbuild](http://typesafehub.github.io/distributed-build/0.5.3/index.html)
will parse `dbuild-meta.json` to determine which jars are produced by a Scala build.
This way we can modularize without changing dbuild itself.
Yes, I know `dbuild-meta.json` should be generated during the build.
However, given the state of our build.xml, I think this is pointless.
My goal is to generate build.xml, dbuild-meta.json and Eclipse projects
from a higher-level description of our build. Baby steps...
Including improvements by @cunei:
- Removing outdated field "uri" from ExtractedBuildMeta
- Changed "partest" to "scala-partest" (the actual jar name)
Diffstat (limited to 'src/eclipse/interactive')
0 files changed, 0 insertions, 0 deletions