tasks

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Use public services in native plugins to construct `FileCollection` instances, rather than using internal `FileOperations`.

  1. … 32 more files in changeset.
Use public services in native plugins to construct `FileCollection` instances, rather than using internal `FileOperations`.

  1. … 32 more files in changeset.
Dogfood ImmutableFileCollection on production code (#4988)

This reverts commit 13eaebc2b1244511dcbff4c59cd41253e3b69642.

  1. … 88 more files in changeset.
Revert "Dogfood ImmutableFileCollection on production code (#4988)"

This reverts commit 834632674ca29b6fd190857947338b2b54a9bb62.

The commit caused a bug in incremental compilation, causing changes

to go undetected.

  1. … 88 more files in changeset.
Dogfood ImmutableFileCollection on production code (#4988)

Use ImmutableFileCollection in production code

  1. … 88 more files in changeset.
Delegate artifact creation to Publication

Issue: #4943

  1. … 35 more files in changeset.
Fix ignored tests, take 2

  1. … 2 more files in changeset.
Revert "Fix ignored tests"

  1. … 2 more files in changeset.
Fix ignored tests

  1. … 2 more files in changeset.
Ignore failing tests temporarily

  1. … 1 more file in changeset.
Re-use `TaskDependencyResolveContext` during task graph building (#3807)

All dependency resolution in Gradle should happen via TaskDependencyResolveContext during when building the task graph. Calling `DefaultTaskDependency.getDependencies(task)` should be avoided since it creates a new `TaskDependencyResolveContext` and needs to calculate the dependencies again.

`SkipTaskWithNoActionsExecuter` now re-uses the `TaskExecutionGraph` to determine the dependencies of a task instead of re-evaluating them.

After this commit, the task properties are resolved at three places:

- When building the task graph for walking the input files

- When checking if there a task can be executed in parallel with the currently running tasks based on on the declared outputs, destroyables and task local state

- For using the task properties during task execution

The last two places could still be unified into one, but that seems to be a little bit more complicated.

  1. … 23 more files in changeset.
Remove deprecated methods on TestUtil (#672)

In order to use project builder correctly without having

leaking files on windows it is necessary to initialize

the test fixture for NativeServices and clean up

the test directory after building.

AbstractProjectBuilderSpec provides a nice base class

for Groovy tests.

I removed the deprecated methods since using them leads

to files lying around. Migrating all the usages to the "new"

way ensures it is used correctly.

  1. … 97 more files in changeset.
renamed HelperUtil to TestUtil (REVIEW-1626)

  1. … 145 more files in changeset.
Changed DefaultTaskContainer, DefaultSourceSetContainer and DefaultConfigurationContainer to nag about the use of deprecated add() methods.

  1. … 38 more files in changeset.
REVIEW-1522, REVIEW-1544: Move classes and tests to better packages

    • -89
    • +0
    ./internal/IvyPublicationDynamicDescriptorGenerationTaskCreatorTest.groovy
    • -106
    • +0
    ./internal/IvyPublishDynamicTaskCreatorTest.groovy
  1. … 8 more files in changeset.
Reworked package structure to remove package cycle (both ivy & maven)

    • -2
    • +2
    ./internal/IvyPublicationDynamicDescriptorGenerationTaskCreatorTest.groovy
    • -1
    • +1
    ./internal/IvyPublishDynamicTaskCreatorTest.groovy
  1. … 53 more files in changeset.
Some tweaks to the output of `gradle tasks` when using the publishing plugins.

    • -2
    • +1
    ./internal/IvyPublicationDynamicDescriptorGenerationTaskCreatorTest.groovy
  1. … 7 more files in changeset.
Reorganised the package structure of ivy.publish - Moved IvyPublisher and related service classes into internal.publisher - Moved tasks.internal -> internal.plugins to be more consistent

    • -0
    • +1
    ./internal/IvyPublicationDynamicDescriptorGenerationTaskCreatorTest.groovy
    • -0
    • +1
    ./internal/IvyPublishDynamicTaskCreatorTest.groovy
  1. … 13 more files in changeset.
Started adding custom artifact support to ivy-publish plugin (based on maven-publish support) - Added IvyArtifact and IvyArtifactSet - Replaced use of PublishArtifact with IvyArtifact - Added IvyPublication.artifact(source) and IvyPublication.artifact(source, config) - Added IvyArtifactNotationParser and various implementations of IvyArtifact for file/archive/publishArtifact

    • -1
    • +1
    ./internal/IvyPublicationDynamicDescriptorGenerationTaskCreatorTest.groovy
  1. … 32 more files in changeset.
Cleaned up configuration of descriptorFile on IvyPublication - Can no longer specify descriptorFile directly on publication, this is done by setting destination on GenerateIvyDescriptor task - Default destination is configured directly on GenerateIvyDescriptor task - GenerateIvyDescriptor task supplies ivy descriptor to IvyPublication as a PublishArtifact

    • -5
    • +5
    ./internal/IvyPublicationDynamicDescriptorGenerationTaskCreatorTest.groovy
  1. … 7 more files in changeset.
Codenarc fix

DefaultIvyModuleDescriptor is no longer Buildable - Wire generator task directly into DefaultIvyPublication - All dependencies of PublishToIvyRepository are managed via IvyPublication.getPublishableFiles()

    • -12
    • +1
    ./PublishToIvyRepositoryTest.groovy
    • -12
    • +6
    ./internal/IvyPublicationDynamicDescriptorGenerationTaskCreatorTest.groovy
  1. … 8 more files in changeset.
Change the ivy module descriptor task name pattern to “generate«Publication-name»IvyModuleDescriptor”, using "" if the publication name is “ivy”.

    • -4
    • +4
    ./internal/IvyPublicationDynamicDescriptorGenerationTaskCreatorTest.groovy
  1. … 1 more file in changeset.
Don't have the IvyArtifactRepository create the IvyPublisher, use the DependencyResolver from it instead to create it.

This removes any trace of the new publishing stuff from core/coreImpl and allows some simplification.

We may find over time that this leads to some awkward duplication, but for the time being I'm favouring touching as little as possible in existing code.

    • -56
    • +1
    ./PublishToIvyRepositoryTest.groovy
  1. … 15 more files in changeset.
Some minor improvements too the thing that creates descriptor generation tasks for ivy publications.

    • -0
    • +95
    ./internal/IvyPublicationDynamicDescriptorGenerationTaskCreatorTest.groovy
  1. … 1 more file in changeset.
Rename “IvyRepositoryPublish” task to “PublishToIvyRepository”.

    • -143
    • +0
    ./IvyRepositoryPublishTest.groovy
    • -0
    • +143
    ./PublishToIvyRepositoryTest.groovy
    • -3
    • +3
    ./internal/IvyPublishDynamicTaskCreatorTest.groovy
  1. … 4 more files in changeset.
Change ivy-publish plugin to not create “main” things, and to use a different task naming strategy.

Changes:

1. The implicit publication is named “ivy” (reversion)

2. No repository is created by default (reversion)

3. Dynamically created tasks are named “publish«PUBLICATION NAME»PublicationTo«REPOSITORY NAME»Repository.

The task name leaves something to be desired.

    • -36
    • +0
    ./internal/DefaultIvyPublishTaskNamerTest.groovy
    • -6
    • +6
    ./internal/IvyPublishDynamicTaskCreatorTest.groovy
  1. … 19 more files in changeset.
Add “publish” lifecycle task in “publishing” plugin for concrete publish tasks to hang off.

    • -1
    • +12
    ./internal/IvyPublishDynamicTaskCreatorTest.groovy
  1. … 8 more files in changeset.
Cleaned up the new ivypublish sample and test.

Also cleaned up some of the ivy test fixtures.

    • -0
    • +143
    ./IvyRepositoryPublishTest.groovy
    • -3
    • +3
    ./internal/IvyPublishDynamicTaskCreatorTest.groovy
  1. … 18 more files in changeset.
Rename “IvyPublish#to” -> “IvyPublish#repo”.

  1. … 2 more files in changeset.