10 Commits

Author	SHA1	Message	Date
Mark Harrah	e47a357ab7	Resolve Scala version for projects in the normal `update` task. ... 1. Scala jars won't be copied to the boot directory, except for those needed to run sbt. 2. Scala SNAPSHOTs behave like normal SNAPSHOTs. In particular, running `update` will properly re-resolve the dynamic revision. 3. Scala jars are resolved using the same repositories and configuration as other dependencies. 4. Classloaders (currently, Scala classloaders) are cached by the timestamps of entries instead of Scala class loaders being cached by version. TODO: Support external dependency configuration	2012-11-17 20:23:06 -05:00
Peter Vlugter	7b7716953f	Use system classloader when finding root classloader	2012-04-13 11:51:15 +12:00
Mark Harrah	3ce7c0411d	search java.library.path for default run/test loader	2011-08-05 21:56:32 -04:00
Mark Harrah	7ea35daec2	class loader extension to handle native libraries loaded in multiple class loaders	2011-08-05 21:56:32 -04:00
Mark Harrah	2343a55bb9	replace Path with RichFile	2011-05-14 18:21:41 -04:00
Mark Harrah	d09aab03be	better location for class loaders (ClassLoaders.scala)	2011-04-15 18:22:57 -04:00
Mark Harrah	72261548ef	use java.util.Linked* instead of scala's	2011-01-22 16:21:22 -05:00
Mark Harrah	de3ad8c860	eliminate temporary directory for injecting resources into a class loader	2010-11-13 20:16:44 -05:00
Mark Harrah	d0fa1eb461	* move Environment classes to util/env module ... * move TrapExit, SelectMainClass to run module * rearrange some compilation-related code * Jetty-related code moved to web module	2010-07-14 19:24:50 -04:00
Mark Harrah	6f3c699435	- Stuart's improvements to triggered execution ... - continue splitting original sbt module * separated process, testing modules * various IO, logging, classpath migration * split out javac interface	2010-07-05 12:53:37 -04:00