From 77bf3a09328709f702bc066fe93fc3e12cd64ba2 Mon Sep 17 00:00:00 2001 From: Paul Phillips Date: Thu, 13 Jun 2013 05:54:44 -0400 Subject: Removed sbt build. Difficult though it may be to accept, it must go. We couldn't keep it working with active maintenance; after eight months of neglect there is no chance. Nobody is working on it or using it. The code will remain in the history if anyone wants it. One of the most annoying experiences one can have when building a new project is finding out one has been fiddling with an abandoned build system which isn't even expected to work. Sometimes I check out a scala project and there is a build.xml, a pom.xml, and a project directory. We should not be among those who sow such build confusion. --- project/Release.scala | 30 ------------------------------ 1 file changed, 30 deletions(-) delete mode 100644 project/Release.scala (limited to 'project/Release.scala') diff --git a/project/Release.scala b/project/Release.scala deleted file mode 100644 index feab8bdc8c..0000000000 --- a/project/Release.scala +++ /dev/null @@ -1,30 +0,0 @@ -import sbt._ -import Keys._ - -object Release { - - // TODO - Just make the STARR artifacts and dump the sha1 files. - - val starrLibs = Seq("scala-library.jar", "scala-reflect.jar", "scala-compiler.jar", "jline.jar") - - val pushStarr = Command.command("new-starr") { (state: State) => - /*val extracted = Project.extract(state) - import extracted._ - // First run tests - val (s1, result) = runTask(test in Test, state) - // If successful, package artifacts - val (s2, distDir) = runTask(makeExplodedDist, s1) - // Then copy new libs in place - val bd = extracted get baseDirectory - for { - jarName <- starrLibs - jar = distDir / "lib" / jarName - if jar.exists - } IO.copyFile(jar, bd / "lib" / jarName) - // Invalidate SHA1 files. - ShaResolve.removeInvalidShaFiles(bd) - // Now run tests *again*? - s2*/ - state - } -} -- cgit v1.2.3