Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Simplify ScriptCompiler.compile() contract

Not requiring the ClassLoader anymore but only the ClassLoaderScope

as all implementations now use the export loader from the given scope.

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

Simplify ScriptCompiler.compile() contract

Not requiring the ClassLoader anymore but only the ClassLoaderScope

as all implementations now use the export loader from the given scope.

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

Fix mocks returning mocks based test

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

Fix mocks returning mocks based test

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

Fix mocks returning mocks based test

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

Fix mocks returning mocks based test

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

Fix mocks returning mocks based test

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

Add test for new snapshotting operations

Fix tests for existing build operations around execution

Rename TransformerInvoker to TransformerInvocationFactory

As this is what it does. Also moved a method only used in tests to the relevant test class.

Simplify code

It's a bit easier to read now I think, though it's still pretty complex.

Prefer scope export loader for 2nd stage of Groovy scripts compilation

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

Prefer scope export loader for 2nd stage of Groovy scripts compilation

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

Prefer scope export loader for 2nd stage of Groovy scripts compilation

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

Prefer scope export loader for 2nd stage of Groovy scripts compilation

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

Prefer scope export loader for 2nd stage of Groovy scripts compilation

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

Fix wrong scope used for first stage of Groovy scripts compilation

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

Fix wrong scope used for first stage of Groovy scripts compilation

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

Fix wrong scope used for first stage of Groovy scripts compilation

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

Fix wrong scope used for first stage of Groovy scripts compilation

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

Fix wrong scope used for first stage of Groovy scripts compilation

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

Add TODO:instant-execution to use a scope for Groovy script classes

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

Add TODO:instant-execution to use a scope for Groovy script classes

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

Add TODO:instant-execution to use a scope for Groovy script classes

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

Add TODO:instant-execution to use a scope for Groovy script classes

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

Add TODO:instant-execution to use a scope for Groovy script classes

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

Only test relevant build operations

Now that the execution engine is also emitting build operations we need to track only the ones that are relevant here. All of these operatins will be removed eventually in favor of the new operations. Until then we need to test them though.

Use a new line for each property type

so it's easy to see what gets added/removed later.

Fix resolved versions of substituted dependencies

This commit fixes an inconsistency when publishing resolved

versions of a component. If that component happens to be

substituted, which would be strange for a first level dependency

but nevertheless possible, then we wouldn't find the target

module in the resolution result, and the outcome would be that

POM/IVY/Gradle Module metadata files would all have an empty

version for a substituted dependency.

With the change, we will now also look for dependencies in

the resolution result, and if one matches the original dependency

coordinates, then we use its resolved component as the result.

This allows us to _substitute_ the result with complete coordinates

in the metadata files.

Fixes nebula-plugins/gradle-nebula-integration#62

Fix resolved versions of substituted dependencies

This commit fixes an inconsistency when publishing resolved

versions of a component. If that component happens to be

substituted, which would be strange for a first level dependency

but nevertheless possible, then we wouldn't find the target

module in the resolution result, and the outcome would be that

POM/IVY/Gradle Module metadata files would all have an empty

version for a substituted dependency.

With the change, we will now also look for dependencies in

the resolution result, and if one matches the original dependency

coordinates, then we use its resolved component as the result.

This allows us to _substitute_ the result with complete coordinates

in the metadata files.

Fixes nebula-plugins/gradle-nebula-integration#62