sbt/compile
Grzegorz Kossakowski a7fb54e4df Add debug logging in ClassfileManager
Add logging of various operations the transactional class file manager is
doing. You can pass logger to be used by the transactional class file
manager by using overloaded definition of `ClassfileManager.transactional`
method. The old overload has been deprecated.

The factory methods for class file manager in IncOptions companion object
has been deprecated in favor of using ClassfileManager companion object
directly. The code in Defaults.scala has been updated to use non-deprecated
methods. The logging is turned off by default.

The canonical way of enabling transactional class file manager in sbt
project is:

```
incOptions := incOptions.value.withNewClassfileManager(
  sbt.inc.ClassfileManager.transactional(
    crossTarget.value / "classes.bak",
    (streams in (compile, Compile)).value.log
  )
)
```

It's a bit verbose which shows that the api for this is not the best.
However, I don't expect sbt users to need this code very often.

This patch should help debug the problem described in #1184
2014-04-11 13:42:21 +02:00
..
api Classes that only inherit a macro don't have a macro 2014-04-03 18:27:17 +02:00
inc Add debug logging in ClassfileManager 2014-04-11 13:42:21 +02:00
integration/src/main/scala/sbt/compiler Include value of `nameHashing` flag in `CompileSetup`. 2014-02-17 17:00:19 +01:00
interface Add link to corresponding issue in Scala issue tracker 2014-04-08 23:18:48 +02:00
ivy/src/main/scala/sbt/compiler Follow source layout convention supported by Eclipse. 2012-12-07 10:27:08 -08:00
persist Include value of `nameHashing` flag in `CompileSetup`. 2014-02-17 17:00:19 +01:00
src/main/scala/sbt Merge ExtendedReporter into Reporter. 2013-05-27 19:12:39 -04:00
NOTICE - Stuart's improvements to triggered execution 2010-07-05 12:53:37 -04:00