From daa26379ceae60b441f49dab49f367ebea027529 Mon Sep 17 00:00:00 2001 From: Paul Phillips Date: Mon, 1 Aug 2011 17:46:48 +0000 Subject: Working on jar creation infrastructure. output generation (but only then, since otherwise we're not creating the jar): 1) -Xmain-class foo.Bar will give the jar a Main-Class of foo.Bar 2) Alternatively, if there is only one runnable program, that will be the Main-Class 3) Always, the jar's manifest will have an entry for Scala-Compiler-Version. Not very relatedly, a warning is now issued when a module has a main method but a runnable program will not be generated. Closes SI-4861. This represents an opening step toward automatically recognizing mismatched bytecode situations: coarse, but useful and safe. Review by mirco. --- test/pending/run/jar-version.scala | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 test/pending/run/jar-version.scala (limited to 'test/pending') diff --git a/test/pending/run/jar-version.scala b/test/pending/run/jar-version.scala new file mode 100644 index 0000000000..b79dfe733d --- /dev/null +++ b/test/pending/run/jar-version.scala @@ -0,0 +1,11 @@ +import scala.util.Properties._ +import scala.tools.nsc.util.ClassPath._ + +object Test { + def main(args: Array[String]): Unit = { + infoFor(this).jarManifestMainAttrs get ScalaCompilerVersion match { + case Some(v) => println("I was built by scala compiler version " + v) + case _ => println("I was not apprised of which scala compiler version built me.") + } + } +} -- cgit v1.2.3