Clone Tools
  • last updated a few seconds ago
Constraints: committers
Constraints: files
Constraints: dates
Moved `ComponentSpecIdentifier` into an internal package.

  1. … 6 more files in changeset.
Fixed unit test for changes to descriptors of `BinarySpec` children.

Rework extensible type fixtures to simplify code

+review REVIEW-5695

  1. … 14 more files in changeset.
Merged `BinaryNamingSchemeBuilder` into `BinaryNamingScheme`.

  1. … 13 more files in changeset.
Do not use the legacy decoration on the delegate objects created for `ComponentSpec`, `BinarySpec` and `LanguageSourceSet` elements.

+review REVIEW-5708

  1. … 27 more files in changeset.
Move ModelRegistryHelper functionality to Groovy extension module

+review REVIEW-5715

  1. … 19 more files in changeset.
Fixed some unit tests for change to test fixture.

+review REVIEW-5708

  1. … 8 more files in changeset.
Remove the need for `ComponentSpecInternal` to expose a `FunctionalSourceSet`

- Rejigged CUnit plugin so that source sets are created via ModelMap API

- Don't use FunctionalSourceSet.baseDir to configure source directories for ComponentSpec.sources

- Removed `FunctionalSourceSet.baseDir`

Issue: gradle/langos#40 +review REVIEW-5681

  1. … 7 more files in changeset.
Merge branch 'release'

  1. … 4 more files in changeset.
Remove unused ProjectSourceSet

+review REVIEW-5669

  1. … 16 more files in changeset.
Pass a baseDir to the fixture for JvmLibrarySpec's

Changed the JVM and native component plugins to use names for binaries that reflect the role they play.

Now that more than one component may have a binary with a given name, use:

- `jar` as the name for a Jar binary that belongs to a JVM library

- `executable` as the name for an executable that belongs to a native application

- `sharedLibrary` and `staticLibrary` as the name for the binaries of a native library.

These can later turn into static properties of the appropriate `ComponentSpec` types.

There is a breaking change in this commit: the lifecycle task name and output directory name of the binaries of components with multiple variants now include the component name at the start of the name, rather than somewhere in the middle.

  1. … 26 more files in changeset.
Refactor JvmComponentPlugin

The following stylistic changes are made here in preparation for

substantive changes to this class in subsequent commits:

- Format Javadoc for readability

- Use public visibility consistently on rule-annotated methods

- Refactor #createBinaries and its related private methods for

readability and elimination of unused parameters

  1. … 1 more file in changeset.
Pushed construction of a component's main source set down into the constructor or `BaseComponentSpec`.

  1. … 13 more files in changeset.
Make it easier to reference an instance of the current JavaPlatform

  1. … 10 more files in changeset.
No need for these parameters anymore

+review REVIEW-5551

Custom plugin can add custom component built from Java source

+review REVIEW-5551

  1. … 4 more files in changeset.
Renamed `ComponentSpecInternal.sources` to `functionalSourceSet`

+review REVIEW-5541

  1. … 5 more files in changeset.
Removed `JvmComponentExtension` now that model DSL is improved

- Updated test for configuring jar binary of jvm library to use model DSL

  1. … 5 more files in changeset.
Reverted the unfinished attempt to move away from ToolChain and ToolProvider to ToolResolver and ResolvedTool

- This work needs a lot more thought and speccing: reverting for now seems like the best option

+review REVIEW-5398

  1. … 40 more files in changeset.
Expose ComponentSpec.source() as a node backed model map, instead of a domain object collection wrapped model map.

+review REVIEW-5498

  1. … 39 more files in changeset.
Back component.binaries with the model graph.

This is required, as opposed to simply wrap the previous DomainObjectSet with a ModelMap, in order to properly honour the configuration ordering semantics promised by ModelMap.

+review REVIEW-5498

  1. … 30 more files in changeset.
Introduce ModelMap extends CollectionBuilder and allow to use them interchangeably in rules

+review REVIEW-5491

  1. … 117 more files in changeset.
Make DirectInstantiator a singleton.

  1. … 89 more files in changeset.
Fixing CI breakages

+review REVIEW-5398

  1. … 3 more files in changeset.
Converting platform-jvm to use ToolResolver

+review REVIEW-5398

  1. … 9 more files in changeset.
Use a domain specific PlatformResolver plugin for resolving JavaPlatform instances

- Domain plugins can register a PlatformResolver for a Platform subtype

- JvmComponentPlugin registers a resolver for JavaPlatform

- JavaPlatform instances are no longer registered in the PlatformContainer

  1. … 11 more files in changeset.
PlatformResolver resolves each platform separately

  1. … 6 more files in changeset.
Merge branch 'release' into 'master'

  1. … 10 more files in changeset.
Moved PlatformResolver into internal package (temporarily) to resolve dependency cycle

  1. … 8 more files in changeset.