Skip to content

Commit

Permalink
build-result of maven builder
Browse files Browse the repository at this point in the history
  • Loading branch information
katunin-ng committed Jan 16, 2020
1 parent f316fcf commit 87a18e7
Show file tree
Hide file tree
Showing 2 changed files with 15 additions and 1 deletion.
2 changes: 1 addition & 1 deletion docs/docs/configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -185,7 +185,7 @@ You can configure the following build parameters to define artifacts to package

| Name | Default value | Description
| ------ | -------- | ----------
| `build-result` | The module folder | A folder containing the build results to package.
| `build-result` | For the `maven` builder: <module's folder>/target/\*.war <br><br> For the `fetcher` builder: <module's folder>/target/\*.\* <br><br> For other builders: <module's folder> | A path to the build results that should be packaged.
| `ignore` | None | Files and/or subfolders to exclude from the package.


Expand Down
14 changes: 14 additions & 0 deletions docs/docs/migration.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,20 @@ The following `build-parameters` are not supported by the Cloud MTA Build Tool:

If you need to change the default build behavior defined for the corresponding builder, see [configure `custom` builder](configuration.md#configuring-the-custom-builder). For a complete list of available builders and their default behaviors, see [Builders execution commands](https://github.com/SAP/cloud-mta-build-tool/blob/master/configs/builder_type_cfg.yaml).
&nbsp;
If you replace the `maven` builder with the `custom` builder, you also need to set the `build-result` parameter (if it was not configured explicitly) as follows:
&nbsp;
```yaml
- name: module1
type: java
build-parameters:
builder: custom
...
build-result: target/*.war
...
```
&nbsp;

</li>
<li>

Expand Down

0 comments on commit 87a18e7

Please sign in to comment.