Skip to content

Bump mapstruct.version from 1.4.1.Final to 1.4.2.Final#19

Open
dependabot-preview[bot] wants to merge 1 commit into
mainfrom
dependabot/maven/mapstruct.version-1.4.2.Final
Open

Bump mapstruct.version from 1.4.1.Final to 1.4.2.Final#19
dependabot-preview[bot] wants to merge 1 commit into
mainfrom
dependabot/maven/mapstruct.version-1.4.2.Final

Conversation

@dependabot-preview

Copy link
Copy Markdown
Contributor

Bumps mapstruct.version from 1.4.1.Final to 1.4.2.Final.
Updates mapstruct from 1.4.1.Final to 1.4.2.Final

Release notes

Sourced from mapstruct's releases.

1.4.2.Final

Enhancement

  • Relax strictness for Mapping#qualifiedByName and Mapping#qualifier for collection mappings (#2324, #2346)
  • Mark mapstruct-processor jar as Spring-Boot-Jar-Type: annotation-processor (#2244)

Bugs

  • Nested target properties uses same method for different mappings after upgrade from 1.3.1.Final to 1.4.1.Final (#2236)
  • MapStruct 1.3.0.Final version is generating wrong code for optional collection getter fields (#2233)
  • Problems with Optional<T> mapping (#2295)
  • Nested source null check calls method twice instead of using intermediate variable (#2245)
  • Mapper create invalid implementation - variable is already defined in method (#2251)
  • Stack Trace instead of Message on Missing Mapping (#2263)
  • Wrong reporting for unmapped source properties when source source is implicitly mapped (#2253)
  • Getting either "Unknown property" or "Unmapped target property" (#2301)
  • @InheritInverseConfiguration and @Mapping(target:"bean.childProperty", ignore=true) do not play together (#2278)
  • Mappings are ignored when @InheritConfiguration defines a mapping for a sub-field (#2318)

Documentation

  • Vague documentation and code samples of @Default annotation as of 1.4.X (#2258)
  • Example uses wrong maven plugin configuration (#2307)
  • Typo in @MapperConfig annotation in documentation (#2293)
Commits
  • 1ca7c7b [maven-release-plugin] prepare release 1.4.2.Final
  • 7d20cf2 #2346 Update documentation and readme about MapStruct and Gradle
  • bef3482 #2250, #2324 Do not throw error when qualifier is missing on iterable mapping
  • 0c51f7a #2278 inherited property ignored due to ignore on nested level (#2332)
  • 15b3469 #2301 Implicitly ignore forward inherited mappings from different method types
  • e6479dc #2293 Use MapperConfig instead of MappingConfig in the documentation
  • 24ac2f3 Update chapter-2-set-up.asciidoc
  • 164535e Add Lombok subsection in the documentation (#2266)
  • 628ff17 #2253 remove unmapped source properties when source parameter is directly mapped
  • 934d096 #2263 Fix IndexOutOfBoundsException when resolving TypeVar to a Type
  • Additional commits viewable in compare view

Updates mapstruct-processor from 1.4.1.Final to 1.4.2.Final

Release notes

Sourced from mapstruct-processor's releases.

1.4.2.Final

Enhancement

  • Relax strictness for Mapping#qualifiedByName and Mapping#qualifier for collection mappings (#2324, #2346)
  • Mark mapstruct-processor jar as Spring-Boot-Jar-Type: annotation-processor (#2244)

Bugs

  • Nested target properties uses same method for different mappings after upgrade from 1.3.1.Final to 1.4.1.Final (#2236)
  • MapStruct 1.3.0.Final version is generating wrong code for optional collection getter fields (#2233)
  • Problems with Optional<T> mapping (#2295)
  • Nested source null check calls method twice instead of using intermediate variable (#2245)
  • Mapper create invalid implementation - variable is already defined in method (#2251)
  • Stack Trace instead of Message on Missing Mapping (#2263)
  • Wrong reporting for unmapped source properties when source source is implicitly mapped (#2253)
  • Getting either "Unknown property" or "Unmapped target property" (#2301)
  • @InheritInverseConfiguration and @Mapping(target:"bean.childProperty", ignore=true) do not play together (#2278)
  • Mappings are ignored when @InheritConfiguration defines a mapping for a sub-field (#2318)

Documentation

  • Vague documentation and code samples of @Default annotation as of 1.4.X (#2258)
  • Example uses wrong maven plugin configuration (#2307)
  • Typo in @MapperConfig annotation in documentation (#2293)
Commits
  • 1ca7c7b [maven-release-plugin] prepare release 1.4.2.Final
  • 7d20cf2 #2346 Update documentation and readme about MapStruct and Gradle
  • bef3482 #2250, #2324 Do not throw error when qualifier is missing on iterable mapping
  • 0c51f7a #2278 inherited property ignored due to ignore on nested level (#2332)
  • 15b3469 #2301 Implicitly ignore forward inherited mappings from different method types
  • e6479dc #2293 Use MapperConfig instead of MappingConfig in the documentation
  • 24ac2f3 Update chapter-2-set-up.asciidoc
  • 164535e Add Lombok subsection in the documentation (#2266)
  • 628ff17 #2253 remove unmapped source properties when source parameter is directly mapped
  • 934d096 #2263 Fix IndexOutOfBoundsException when resolving TypeVar to a Type
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Bumps `mapstruct.version` from 1.4.1.Final to 1.4.2.Final.

Updates `mapstruct` from 1.4.1.Final to 1.4.2.Final
- [Release notes](https://github.com/mapstruct/mapstruct/releases)
- [Commits](mapstruct/mapstruct@1.4.1.Final...1.4.2.Final)

Updates `mapstruct-processor` from 1.4.1.Final to 1.4.2.Final
- [Release notes](https://github.com/mapstruct/mapstruct/releases)
- [Commits](mapstruct/mapstruct@1.4.1.Final...1.4.2.Final)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview Bot added the dependencies Pull requests that update a dependency file label Feb 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants