<commit_before>## New and noteworthy

Here are the new features introduced in Gradle 1.1-rc-1

### Test Logging

In previous versions, Gradle didn't show much information about what happened during test execution.
In Gradle 1.1-rc-1, the default output is more useful, and can be tuned to your preferences in many ways.
All features are supported both for JUnit and TestNG.

#### Show Exceptions

One of the most useful options is to show the exceptions thrown by failed tests. By default, Gradle will
log a succinct message for every test exception. To get more detailed output, configure the `exceptionFormat`:

<pre>
test {
    testLogging {
        exceptionFormat "full"
    }
}
</pre>

#### Stack Trace Filters

Stack traces of test exceptions are automatically truncated not to show anything below the entry point into
the test code. This filters out Gradle internals and internals of the test framework. A number of other
filters are available. For example, when dealing with Groovy code it makes sense to add the `groovy` filter:

<pre>
test {
    testLogging {
        stackTraceFilters "truncate", "groovy"
    }
}
</pre>

#### Show Other Test Events

Besides a test having failed, a number of other test events can be logged:

<pre>
test {
    testLogging {
        events "started", "passed", "skipped", "failed", "standardOut", "standardError"
        minGranularity 0
    }
}
</pre>

By setting `minGranularity`, these events aren't only shown for individual tests, but also for test classes and suites.

#### Individual Logging Per Log Level

Test logging can be configured separately per log level:

<pre>
test {
    testLogging {
        quiet {
            events "failed"
        }
    }
}
</pre>

On log levels `LIFECYCLE`, `INFO`, and `DEBUG`, some test events (most importantly failed tests) are already shown by default.
For detailed documentation about all test logging related options, see
[TestLogging](http://gradle.org/docs/nightly/javadoc/org/gradle/api/tasks/testing/logging/TestLogging.html)
and [TestLoggingContainer](http://gradle.org/docs/nightly/javadoc/org/gradle/api/tasks/testing/logging/TestLoggingContainer.html).

### Tooling API provides Gradle module information for external dependencies

The Tooling API can be used to obtain the model of the project which includes the information about the dependencies/libraries.
Now the Tooling API also provides Gradle module information, i.e. group, name, version of the dependency.
Please see the javadoc for [ExternalGradleModule](http://gradle.org/docs/nightly/javadoc/org/gradle/tooling/model/ExternalGradleModule.html).
You can obtain the Gradle module information iva [ExternalDependency.getExternalGradleModule()] (http://gradle.org/docs/nightly/javadoc/org/gradle/tooling/model/ExternalDependency.html#getExternalGradleModule()).

### Some feature

#### Some detail

Some details about the feature.

## Upgrading from Gradle 1.0

Please let us know if you encounter any issues during the upgrade to Gradle 1.1-rc-1, that are not listed below.

### Deprecations

#### Statement Labels<commit_msg>Removed the placeholder feature.<commit_after>## New and noteworthy

Here are the new features introduced in Gradle 1.1-rc-1

### Test Logging

In previous versions, Gradle didn't show much information about what happened during test execution.
In Gradle 1.1-rc-1, the default output is more useful, and can be tuned to your preferences in many ways.
All features are supported both for JUnit and TestNG.

#### Show Exceptions

One of the most useful options is to show the exceptions thrown by failed tests. By default, Gradle will
log a succinct message for every test exception. To get more detailed output, configure the `exceptionFormat`:

<pre>
test {
    testLogging {
        exceptionFormat "full"
    }
}
</pre>

#### Stack Trace Filters

Stack traces of test exceptions are automatically truncated not to show anything below the entry point into
the test code. This filters out Gradle internals and internals of the test framework. A number of other
filters are available. For example, when dealing with Groovy code it makes sense to add the `groovy` filter:

<pre>
test {
    testLogging {
        stackTraceFilters "truncate", "groovy"
    }
}
</pre>

#### Show Other Test Events

Besides a test having failed, a number of other test events can be logged:

<pre>
test {
    testLogging {
        events "started", "passed", "skipped", "failed", "standardOut", "standardError"
        minGranularity 0
    }
}
</pre>

By setting `minGranularity`, these events aren't only shown for individual tests, but also for test classes and suites.

#### Individual Logging Per Log Level

Test logging can be configured separately per log level:

<pre>
test {
    testLogging {
        quiet {
            events "failed"
        }
    }
}
</pre>

On log levels `LIFECYCLE`, `INFO`, and `DEBUG`, some test events (most importantly failed tests) are already shown by default.
For detailed documentation about all test logging related options, see
[TestLogging](http://gradle.org/docs/nightly/javadoc/org/gradle/api/tasks/testing/logging/TestLogging.html)
and [TestLoggingContainer](http://gradle.org/docs/nightly/javadoc/org/gradle/api/tasks/testing/logging/TestLoggingContainer.html).

### Tooling API provides Gradle module information for external dependencies

The Tooling API can be used to obtain the model of the project which includes the information about the dependencies/libraries.
Now the Tooling API also provides Gradle module information, i.e. group, name, version of the dependency.
Please see the javadoc for [ExternalGradleModule](http://gradle.org/docs/nightly/javadoc/org/gradle/tooling/model/ExternalGradleModule.html).
You can obtain the Gradle module information iva [ExternalDependency.getExternalGradleModule()] (http://gradle.org/docs/nightly/javadoc/org/gradle/tooling/model/ExternalDependency.html#getExternalGradleModule()).

## Upgrading from Gradle 1.0

Please let us know if you encounter any issues during the upgrade to Gradle 1.1-rc-1, that are not listed below.

### Deprecations

#### Statement Labels
{'fraction_non_alphanumeric': 0.0811296114920013, 'fraction_numerical': 0.0039177277179236044, 'mean_word_length': 4.192372881355932, 'pattern_counts': {'":': 0, '<': 19, '<?xml version=': 0, '>': 19, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5096863', 'n_tokens_mistral': 1707, 'n_tokens_neox': 1638, 'n_words': 717}