The following docs from AutoValue and Immutables seem to indicate that both libraries do not recommend using the JavaBeans-style property accessors (getProperty(), isBoolean(), etc)
https://github.com/google/auto/blob/master/value/userguide/index.md
https://immutables.github.io/
Both libraries do support JavaBeans-style accessors to some degree however
https://github.com/google/auto/blob/master/value/userguide/howto.md#beans
https://immutables.github.io/style.html
In Mapstruct 1.3.0.Beta1 only JavaBeans-style properties are supported.
To support this new convention, Mapstruct will need an option to treat all methods as potential properties.
With no differentiation between standard methods and property getters, it seems that Mapstruct either needs:
- Mapped classes to only have property getters as methods.
- An annotation to allow Mapstruct to ignore certain methods when not using JavaBeans-style conventions.
Option 1 is up to the developer, and for Option 2, there is already an annotation that can do this, @Mapping(target = "somemethod", ignore = true)
The following docs from AutoValue and Immutables seem to indicate that both libraries do not recommend using the JavaBeans-style property accessors (
getProperty(),isBoolean(), etc)https://github.com/google/auto/blob/master/value/userguide/index.md
https://immutables.github.io/
Both libraries do support JavaBeans-style accessors to some degree however
https://github.com/google/auto/blob/master/value/userguide/howto.md#beans
https://immutables.github.io/style.html
In Mapstruct 1.3.0.Beta1 only JavaBeans-style properties are supported.
To support this new convention, Mapstruct will need an option to treat all methods as potential properties.
With no differentiation between standard methods and property getters, it seems that Mapstruct either needs:
Option 1 is up to the developer, and for Option 2, there is already an annotation that can do this,
@Mapping(target = "somemethod", ignore = true)