Andrey Breslav 882412ea06 Proper handling of compiler messages ...

We used to have a triple (errorStream, messageRenderer, verbose) to represent the error reporting strategy.
 Now we have a single MessageCollector abstraction for this.
 As the MessageCollector abstraction was extracted, the need to CompilerMessageLocation and CompilerMessageSeverity arose, too.

2012-04-13 19:38:23 +04:00

..

ant/src/org/jetbrains/jet/buildtools/ant

Copyrights set to Apache, reflecting it's now open source

2012-02-14 19:25:06 +04:00

core/src/org/jetbrains/jet/buildtools/core

Proper handling of compiler messages

2012-04-13 19:38:23 +04:00

lib

Ant task - CompileEnvironment is used + "buildToolsTest" verifies <java> output

2012-01-15 22:16:28 +02:00

test

KT-1529: Failing module compilation doesn't fail Maven build - test added.

2012-03-07 21:12:16 +01:00

build-tools.iml

CompilerDependencies

2012-04-09 03:04:50 +04:00

build.xml

refactored out the KDocLoader stuff from the KotlinCompiler; also introduced CompilerPluginContext to wrap up the Project, BindingContext and List<JetFiles> in case a plugin were to need any of those things (or we added extra stuff later like the environment)

2012-03-29 16:37:36 +01:00

ivy.xml

Ant task - longer examples update; Maze doesn't compile, HtmlBuilder doesn't run; Ivy configuration files updated to use public TeamCity; Wiki update

2012-02-15 20:45:46 +02:00

ivyconf.xml

Ant task - longer examples update; Maze doesn't compile, HtmlBuilder doesn't run; Ivy configuration files updated to use public TeamCity; Wiki update

2012-02-15 20:45:46 +02:00

Wiki.txt

Ant task - longer examples update; Maze doesn't compile, HtmlBuilder doesn't run; Ivy configuration files updated to use public TeamCity; Wiki update

2012-02-15 20:45:46 +02:00