JvmProjectGeneratorTask.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Refactored buildSrc into modules to improve feedback cycles

- Created module boundaries around different languages and slow tests

    • -130
    • +0
    ./JvmProjectGeneratorTask.groovy
  1. … 528 more files in changeset.
Fix buildSrc/AbstractProjectGeneratorTask task properties

  1. … 3 more files in changeset.
Add native project generator that uses project dependencies

  1. … 44 more files in changeset.
Split integration and performance tests

So far, performance tests were just 'integration tests in the performance project'.

This required some special handling to make sure that:

- performance tests are not run during integration test invocations

- integration tests are not run during performance test invocations

It also lead to performance tests being monolithic instead of close to the code they are testing.

This change makes performance tests a first class citizen in every project.

The common infrastructure for testing a full distribution (including daemon cleanup etc.) is now

separate from the integration tests and can be reused by other test types.

The performance tests live in their own source set called 'performanceTest'. They can define their own

dependencies and can be used independently from integration tests.

    • -0
    • +124
    ./JvmProjectGeneratorTask.groovy
  1. … 111 more files in changeset.