atlassian/amps (com.atlassian.maven.plugins:jira-maven-plugin)
### [`v8.17.2`](https://bitbucket.org/atlassian/amps/blob/HEAD/CHANGELOG.md#8172)
##### Added
- [AMPS-1683](https://ecosystem.atlassian.net/browse/AMPS-1683): Added `skipCopyFeModuleManifests` and
`skipReportFeManifestAssociations` to allow skipping goals from command line even if configured in pom.xml
### [`v8.17.1`](https://bitbucket.org/atlassian/amps/blob/HEAD/CHANGELOG.md#8171)
##### Fixed
- [AMPS-1682](https://ecosystem.atlassian.net/browse/AMPS-1682): Run `copy-fe-bundled-metadata` extraction only when
`copy-bundled-dependencies` does.
### [`v8.17.0`](https://bitbucket.org/atlassian/amps/blob/HEAD/CHANGELOG.md#8170)
##### Added
- [AMPS-1679](https://ecosystem.atlassian.net/browse/AMPS-1679): Added new maven mojo `verify-fe-manifest-associations`
that verifies that all javascript files have a manifest association in a given artifact.
### [`v8.16.2`](https://bitbucket.org/atlassian/amps/blob/HEAD/CHANGELOG.md#8162)
##### Fixed
- [AMPS-1681](https://ecosystem.atlassian.net/browse/AMPS-1681): the mojo `report-fe-manifest-associations`
now doesn't fail when a module uses the `war` packaging; though in that case it cannot automatically verify
declared associations
### [`v8.16.1`](https://bitbucket.org/atlassian/amps/blob/HEAD/CHANGELOG.md#8161)
##### Fixed
- [AMPS-1680](https://ecosystem.atlassian.net/browse/AMPS-1680): Property plugin.resource.directories is no longer set when running integration-test goal
### [`v8.16.0`](https://bitbucket.org/atlassian/amps/blob/HEAD/CHANGELOG.md#8160)
##### Added
- [AMPS-1676](https://ecosystem.atlassian.net/browse/AMPS-1676): Added new maven mojo `copy-fe-bundled-metadata` that extracts
and copies frontend manifests from `META-INF/fe-module-manifests` and manifest associations from
`META-INF/fe-manifest-associations` and places them in `META-INF/fe-bundled-metadata`
##### Fixed
- [AMPS-1676](https://ecosystem.atlassian.net/browse/AMPS-1676): Excluded frontend manifests and associations from being
copied by `copy-bundled-dependencies` goal to avoid overrides. Those files are instead handled by `copy-fe-bundled-metadata`
### [`v8.15.4`](https://bitbucket.org/atlassian/amps/blob/HEAD/CHANGELOG.md#8154)
##### Added
- \[AMPS-1675] Added `legacyValidateBannedDependencies` to provide more time adapting platform driven `validate-banned-dependencies` behaviour
### [`v8.15.2`](https://bitbucket.org/atlassian/amps/blob/HEAD/CHANGELOG.md#8152)
##### Fixed
- [AMPS-1673](https://ecosystem.atlassian.net/browse/AMPS-1673): the mojo `report-fe-manifest-associations`
now accepts entries about all file types (instead of only JavaScript files) in the inputs.
### [`v8.15.1`](https://bitbucket.org/atlassian/amps/blob/HEAD/CHANGELOG.md#8151)
##### Fixed
- [AMPS-1672](https://ecosystem.atlassian.net/browse/AMPS-1672): the mojo `report-fe-manifest-associations`
now outputs paths in the `declarations` values relative to the project base dir in all cases
### [`v8.15.0`](https://bitbucket.org/atlassian/amps/blob/HEAD/CHANGELOG.md#8150)
##### Added
- [AMPS-1671](https://ecosystem.atlassian.net/browse/AMPS-1671): Added new maven mojo `report-fe-manifest-associations` that will be used to report all output js files have their dependencies declared in package.json
Configuration
š Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
š¦ Automerge: Enabled.
ā» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
š Ignore: Close this PR and you won't be reminded about these updates again.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
8.14.3
->8.17.2
8.14.3
->8.17.2
8.14.3
->8.17.2
Release Notes
atlassian/amps (com.atlassian.maven.plugins:jira-maven-plugin)
### [`v8.17.2`](https://bitbucket.org/atlassian/amps/blob/HEAD/CHANGELOG.md#8172) ##### Added - [AMPS-1683](https://ecosystem.atlassian.net/browse/AMPS-1683): Added `skipCopyFeModuleManifests` and `skipReportFeManifestAssociations` to allow skipping goals from command line even if configured in pom.xml ### [`v8.17.1`](https://bitbucket.org/atlassian/amps/blob/HEAD/CHANGELOG.md#8171) ##### Fixed - [AMPS-1682](https://ecosystem.atlassian.net/browse/AMPS-1682): Run `copy-fe-bundled-metadata` extraction only when `copy-bundled-dependencies` does. ### [`v8.17.0`](https://bitbucket.org/atlassian/amps/blob/HEAD/CHANGELOG.md#8170) ##### Added - [AMPS-1679](https://ecosystem.atlassian.net/browse/AMPS-1679): Added new maven mojo `verify-fe-manifest-associations` that verifies that all javascript files have a manifest association in a given artifact. ### [`v8.16.2`](https://bitbucket.org/atlassian/amps/blob/HEAD/CHANGELOG.md#8162) ##### Fixed - [AMPS-1681](https://ecosystem.atlassian.net/browse/AMPS-1681): the mojo `report-fe-manifest-associations` now doesn't fail when a module uses the `war` packaging; though in that case it cannot automatically verify declared associations ### [`v8.16.1`](https://bitbucket.org/atlassian/amps/blob/HEAD/CHANGELOG.md#8161) ##### Fixed - [AMPS-1680](https://ecosystem.atlassian.net/browse/AMPS-1680): Property plugin.resource.directories is no longer set when running integration-test goal ### [`v8.16.0`](https://bitbucket.org/atlassian/amps/blob/HEAD/CHANGELOG.md#8160) ##### Added - [AMPS-1676](https://ecosystem.atlassian.net/browse/AMPS-1676): Added new maven mojo `copy-fe-bundled-metadata` that extracts and copies frontend manifests from `META-INF/fe-module-manifests` and manifest associations from `META-INF/fe-manifest-associations` and places them in `META-INF/fe-bundled-metadata` ##### Fixed - [AMPS-1676](https://ecosystem.atlassian.net/browse/AMPS-1676): Excluded frontend manifests and associations from being copied by `copy-bundled-dependencies` goal to avoid overrides. Those files are instead handled by `copy-fe-bundled-metadata` ### [`v8.15.4`](https://bitbucket.org/atlassian/amps/blob/HEAD/CHANGELOG.md#8154) ##### Added - \[AMPS-1675] Added `legacyValidateBannedDependencies` to provide more time adapting platform driven `validate-banned-dependencies` behaviour ### [`v8.15.2`](https://bitbucket.org/atlassian/amps/blob/HEAD/CHANGELOG.md#8152) ##### Fixed - [AMPS-1673](https://ecosystem.atlassian.net/browse/AMPS-1673): the mojo `report-fe-manifest-associations` now accepts entries about all file types (instead of only JavaScript files) in the inputs. ### [`v8.15.1`](https://bitbucket.org/atlassian/amps/blob/HEAD/CHANGELOG.md#8151) ##### Fixed - [AMPS-1672](https://ecosystem.atlassian.net/browse/AMPS-1672): the mojo `report-fe-manifest-associations` now outputs paths in the `declarations` values relative to the project base dir in all cases ### [`v8.15.0`](https://bitbucket.org/atlassian/amps/blob/HEAD/CHANGELOG.md#8150) ##### Added - [AMPS-1671](https://ecosystem.atlassian.net/browse/AMPS-1671): Added new maven mojo `report-fe-manifest-associations` that will be used to report all output js files have their dependencies declared in package.jsonConfiguration
š Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
š¦ Automerge: Enabled.
ā» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
š Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate. View repository job log here.