ProjectLayoutIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Upgrade Groovy version to customized 1.0-2.5.7

x

  1. … 39 more files in changeset.
Unify Groovy versions to 2.5.4

  1. … 35 more files in changeset.
Unify Groovy versions to 2.5.4

  1. … 35 more files in changeset.
Unify Groovy versions to 2.5.4

  1. … 35 more files in changeset.
Unify Groovy versions to 2.5.4

  1. … 35 more files in changeset.
Upgrade Groovy to 2.5.7

  1. … 39 more files in changeset.
Unify Groovy versions to 2.5.4

  1. … 35 more files in changeset.
Merge pull request #6395 from gradle/wolfs/deprecations/classesDir

Another try at removing the classes dir.

This reverts commit 76e359df

  1. … 25 more files in changeset.
Revert "Merge pull request #6395 from gradle/wolfs/deprecations/classesDir"

Reverting since it breaks some cross version checks.

This reverts commit adaf86371e3d58d929030184bfc1c11b60ade1bf, reversing

changes made to 37df84902151344db627d6ea7c67461413ad55c9.

  1. … 25 more files in changeset.
Use global init script to set mirrors for buildSrc (#6627)

  1. … 50 more files in changeset.
Remove SourceSetOutput.classesDir

and `configureForSourceSet`.

  1. … 19 more files in changeset.
Use external repository mirrors in build (#6094)

We've been bitten by external repository fluctuation for a long time.

This PR makes most of tests use repository mirrors set up by ourselves

via init script and system property.

There're still some tests not switching to mirrors, which would be fixed

in follow-up commits.

  1. … 99 more files in changeset.
Re-enable Play/Scala tests on Java 9+ (#5593)

Almost all Play/Scala tests were ignored on Java 9/10, which makes it lack coverage. This PR does:

- Update Scala version to Java9-compatible version according to [JDK compatibility](https://docs.scala-lang.org/overviews/jdk-compatibility/overview.html).

- Update default Play version to latest 2.6.15, which supports Java 9/10

- Adjust corresponding samples. Previous default Play version 2.3.10 was too old (release at 2014).

- Ignored the tests which can't work on Java 9+.

- Separate Play test resources with different versions. For example, Play 2.6 uses `build.gradle` and `Play 2.4/2.5` uses `build.gradle.old`.

- Previously `AbstractMultiVersionPlayContinuousBuildIntegrationTest` didn't have `targetPlatform` configuration, which made multi-version tests meaningless

- Fix `play-logback` configuration for `2.5.18`.

  1. … 170 more files in changeset.
Use mavenCentral() and jcenter() mirrors in tests where possible

    • -13
    • +11
    ./ProjectLayoutIntegrationTest.groovy
  1. … 51 more files in changeset.
Fix failing tests

  1. … 4 more files in changeset.
On CI redirect maven central queries to local repo for integration tests

  1. … 108 more files in changeset.
Remove redundant deprecation warning expectations

  1. … 24 more files in changeset.
Use separate output directories for all JVM languages

- Introduce an outputDir on SourceDirectorySet

- Default output directory is now `build/classes/<source directory set name>/<source set name>`

- Example: Java compilation goes to build/classes/java/main instead of build/classes/main

- Adapt JDepend, FindBugs, Test and ValidateTaskProperties tasks to handle multiple class directories

- Deprecate setClassesDir/getClassesDir on SourceSetOutput

- Calling setClassesDir restores old behavior (shared output directory)

- Introduce addClassesDir and getClassesDirs on SourceSetOutput

- OSGi plugin needs a single classes directory, so introduce 'osgiClasses' task that syncs all classes to a single directory

Most of the changes to integration tests are find classes in their new location. Helper methods in AbstractIntegrationSpec

can locate class files vs hardcoding a path.

Squashed commit of sg-split-jvm-classes branch for REVIEW-6502

    • -17
    • +25
    ./ProjectLayoutIntegrationTest.groovy
  1. … 119 more files in changeset.
Upgrade to Groovy 2.4.10

Especially because binary incompatibility between Groovy 2.4.7 and 2.4.9 - https://issues.apache.org/jira/browse/GROOVY-8107

+review REVIEW-6487

  1. … 35 more files in changeset.
Bumped Groovy to 2.4.9

  1. … 28 more files in changeset.
Bring back Upgrade to Groovy 2.4.7.

This reverts commit fe58a375a0c5a962751db9b675c6ba4a2ff1a1ba.

  1. … 32 more files in changeset.
Revert "Upgrade to Groovy 2.4.7."

This reverts commit 5959b63d38dc7adcc7651ce2c4c5003bc699b1b4.

  1. … 32 more files in changeset.
Upgrade to Groovy 2.4.7.

+ review REVIEW-5995

  1. … 32 more files in changeset.
Upgrade to Apache Groovy 2.4.6

+review REVIEW-5995

  1. … 27 more files in changeset.
Remove the deprecated useAnt option form ProjectLayoutIntegrationTest.

+review REVIEW-5829

Changing Scala samples integration tests to always use Zinc compiler

+review REVIEW-5802

  1. … 10 more files in changeset.
Revert "Changing Groovydoc integration tests to run in their own daemon and own gradle user home."

Reverting this for now since there are other issues with this beyond just failed windows CI build.

This reverts commit 94848d9fd76c17517c2104dc86452dd94d330a10.

  1. … 4 more files in changeset.
Changing Groovydoc integration tests to run in their own daemon and own gradle user home.

+review REVIEW-5677

  1. … 4 more files in changeset.
Upgrade to Groovy 2.4.4

+review REVIEW-5598

  1. … 38 more files in changeset.
specify -XX:MaxPermSize=512m for ScalaCompile tasks in integtest - add forking option - also specify option in ForkScalaCompileInDaemonModeFixture - another attempt to fix PermGen failures in coverage builds

  1. … 1 more file in changeset.