BuildInitPluginIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Rename @FailsWithInstantExecution to @ToBeFixedForInstantExecution

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -3
    • +3
    ./BuildInitPluginIntegrationTest.groovy
  1. … 872 more files in changeset.
Append .gitignore file on `gradle init` if it exists

Especially when using other scaffolding mechanisms (e.g. new

GitHub repository or gitignore.io), a `.gitignore` may already

exist before invoking `gradle init`. Just append gradle specific

ignore patterns in those cases.

Signed-off-by: Benjamin Muskalla <benjamin.muskalla@tasktop.com>

    • -3
    • +1
    ./BuildInitPluginIntegrationTest.groovy
  1. … 3 more files in changeset.
Annotate integ tests failing with instant execution in :buildInit

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -0
    • +3
    ./BuildInitPluginIntegrationTest.groovy
  1. … 14 more files in changeset.
gradle init creates .gitattributes #9583

Signed-off-by: Tom Eyckmans <teyckmans@gmail.com>

    • -0
    • +1
    ./BuildInitPluginIntegrationTest.groovy
  1. … 3 more files in changeset.
Replace 'Matchers' with 'CoreMatchers'

So we do not require 'org.hamcrest:hamcrest-library' as additional

dependency anymore. Which was only available for most of the tests

because it leaked onto the test compile classpath.

    • -3
    • +3
    ./BuildInitPluginIntegrationTest.groovy
  1. … 162 more files in changeset.
Emit links to documentation when generating a project with init

    • -0
    • +1
    ./BuildInitPluginIntegrationTest.groovy
  1. … 18 more files in changeset.
Split the interactive question used by the build init plugin to select a build init template into 2 separate, simpler, questions. The first asks the user to select what kind of component they want to produce, the second asks the user to select which source language they want to use to implement it.

    • -6
    • +6
    ./BuildInitPluginIntegrationTest.groovy
  1. … 44 more files in changeset.
Add build init templates for a basic Gradle plugin implemented in Groovy and in Kotlin.

    • -0
    • +4
    ./BuildInitPluginIntegrationTest.groovy
  1. … 29 more files in changeset.
Add a build init template for a Gradle plugin implemented in Java. This is intended to be a very, very minimal template that we can improve later.

    • -0
    • +2
    ./BuildInitPluginIntegrationTest.groovy
  1. … 17 more files in changeset.
Build Init plugin: add possibility to use JUnit Jupiter for Java project types

Signed-off-by: epeee <epeee@users.noreply.github.com>

    • -0
    • +1
    ./BuildInitPluginIntegrationTest.groovy
  1. … 10 more files in changeset.
Derive namespace from project name rather than package

    • -1
    • +1
    ./BuildInitPluginIntegrationTest.groovy
  1. … 13 more files in changeset.
Add build-init support for C++ libraries

    • -1
    • +5
    ./BuildInitPluginIntegrationTest.groovy
  1. … 8 more files in changeset.
Tweak the output produced by `TreeFormatter`.

    • -2
    • +4
    ./BuildInitPluginIntegrationTest.groovy
  1. … 36 more files in changeset.
Gradle init will not use parent `gradle.properties`

Running `gradle init` has always ignored a settings file in a parent

directory, instead creating an isolated, nested build with it's own

settings file. However, if a settings.gradle file was found in a

parent directory, a `gradle.properties` file found in the same directory

was used to determine daemon compatibility. This causes issues with our

NoDaemon integration tests, since the `init` task was finding the

properties file in the root Gradle directory, and starting a new daemon

with those parameters.

    • -1
    • +15
    ./BuildInitPluginIntegrationTest.groovy
  1. … 1 more file in changeset.
Do not generate a settings file for :build-init integration tests

    • -0
    • +3
    ./BuildInitPluginIntegrationTest.groovy
  1. … 4 more files in changeset.
Change `init` task so that it uses a default source package name that is derived from the project name, rather than an empty package name.

    • -1
    • +1
    ./BuildInitPluginIntegrationTest.groovy
  1. … 12 more files in changeset.
Change the `init` task to generate a simple `.gitignore` file in the build's root directory.

    • -0
    • +1
    ./BuildInitPluginIntegrationTest.groovy
  1. … 3 more files in changeset.
Change the `init` task to default to Kotlin DSL when generating Kotlin builds.

    • -8
    • +0
    ./BuildInitPluginIntegrationTest.groovy
  1. … 15 more files in changeset.
Change the `init` task to improve the interactive experience when converting a Maven build.

- Do not suggest `pom` as a build type when there is no `pom.xml` present, as the conversion makes no sense in this case.

- Do not prompt for a DSL or project name when converting a Maven build, as these are not supported or ignored by the Maven build conversion.

- When the `--project` or `--package` options are used with the `init` task, fail when the selected build type does not support these options, e.g. when converting to Maven build.

    • -13
    • +8
    ./BuildInitPluginIntegrationTest.groovy
  1. … 22 more files in changeset.
Tweak prompts and messages for the `init` task.

    • -2
    • +2
    ./BuildInitPluginIntegrationTest.groovy
  1. … 4 more files in changeset.
Add a `--package` command line option to the `init` task to allow the package used for generated source files to be specified.

    • -0
    • +10
    ./BuildInitPluginIntegrationTest.groovy
  1. … 52 more files in changeset.
Some tweaks to javadocs and command line option description in the build init plugin.

    • -4
    • +4
    ./BuildInitPluginIntegrationTest.groovy
  1. … 1 more file in changeset.
Add a `--project-name` command line option to the `init` task to allow the name of the generated project to be specified.

    • -0
    • +2
    ./BuildInitPluginIntegrationTest.groovy
  1. … 16 more files in changeset.
Improve the error messages reported by the build init plugin for unknown options or unsupported combinations of options.

    • -4
    • +18
    ./BuildInitPluginIntegrationTest.groovy
  1. … 20 more files in changeset.
Add a kotlin application build init plugin type.

    • -0
    • +1
    ./BuildInitPluginIntegrationTest.groovy
  1. … 8 more files in changeset.
Add a kotlin library build init plugin type.

    • -0
    • +1
    ./BuildInitPluginIntegrationTest.groovy
  1. … 20 more files in changeset.
Allow initializing nested builds

We deprecated nested builds without a settings file.

However, when calling `gradle init` there is no settings

file yet, so users would get a warning (and it would fail

in 5.0). We now detect this special case and treat it just

as if the user had specified `--no-search-upwards`.

    • -0
    • +13
    ./BuildInitPluginIntegrationTest.groovy
  1. … 1 more file in changeset.
Let init task use -bin distribution when --dsl kotlin

    • -1
    • +1
    ./BuildInitPluginIntegrationTest.groovy
  1. … 4 more files in changeset.
Fix build init usages of ouput test fixtures

    • -6
    • +6
    ./BuildInitPluginIntegrationTest.groovy
Polish new command line options functionality (#4052)

    • -11
    • +11
    ./BuildInitPluginIntegrationTest.groovy
  1. … 15 more files in changeset.