PropertiesFileContentMerger - Gradle DSL Version 4.10.2

# PropertiesFileContentMerger

API Documentation: | `PropertiesFileContentMerger`

Models the generation/parsing/merging capabilities. Adds properties-related hooks.

For examples see docs for `EclipseJdt` and others.

### Properties

No properties

### Methods

Method | Description
`beforeMerged(closure)` | Adds a closure to be called after content is loaded from existing file but before gradle build information is merged.
`beforeMerged(action)` | Adds an action to be called after content is loaded from existing file but before gradle build information is merged.
`whenMerged(closure)` | Adds a closure to be called after content is loaded from existing file and after gradle build information is merged.
`whenMerged(action)` | Adds an action to be called after content is loaded from existing file and after gradle build information is merged.
`withProperties(closure)` | Adds a closure to be called when the file has been created. The `Properties` are passed to the closure as a parameter. The closure can modify the Properties before they are written to the output file.
`withProperties(action)` | Incubating Adds an action to be called when the file has been created. The `Properties` are passed to the action as a parameter. The action can modify the Properties before they are written to the output file.

### Script blocks

No script blocks

### Method details

#### `void` `beforeMerged`(`Closure` closure)

Adds a closure to be called after content is loaded from existing file but before gradle build information is merged.

This is advanced api that gives access to internal implementation. It might be useful if you want to alter the way gradle build information is merged into existing file content.

For examples see docs for `EclipseProject` or `IdeaProject` and others.

#### `void` `beforeMerged`(``Action`<?>` action)

Adds an action to be called after content is loaded from existing file but before gradle build information is merged.

This is advanced api that gives access to internal implementation. It might be useful if you want to alter the way gradle build information is merged into existing file content.

For examples see docs for `EclipseProject` or `IdeaProject` and others.

#### `void` `whenMerged`(`Closure` closure)

Adds a closure to be called after content is loaded from existing file and after gradle build information is merged.

This is advanced api that gives access to internal implementation of idea plugin. Use it only to tackle some tricky edge cases.

For examples see docs for `EclipseProject` or `IdeaProject` and others.

#### `void` `whenMerged`(``Action`<?>` action)

Adds an action to be called after content is loaded from existing file and after gradle build information is merged.

This is advanced api that gives access to internal implementation of idea plugin. Use it only to tackle some tricky edge cases.

For examples see docs for `EclipseProject` or `IdeaProject` and others.

#### `void` `withProperties`(`Closure` closure)

Adds a closure to be called when the file has been created. The `Properties` are passed to the closure as a parameter. The closure can modify the Properties before they are written to the output file.

For examples see docs for `EclipseJdt` and others.

#### `void` `withProperties`(``Action`<`Properties`>` action)

Note: This method is incubating and may change in a future version of Gradle.

Adds an action to be called when the file has been created. The `Properties` are passed to the action as a parameter. The action can modify the Properties before they are written to the output file.

For examples see docs for `EclipseJdt` and others.