Followup #151: pom.xml in Reference Documentation, ch. 2.1. Apache Maven, is not working

[hayosc]

Follow-up to prematurely closed #151.

First, do not close issues, without giving the author the chance to reply, just because you do not get the point.

The documentation is crystal clear: There is nothing to be added to the example maven-plugiin annotationProcessorPaths section, otherwise there would be three dots ("...") in front or after the mapstruct-spring-extensions entry.

The screen shots you posted tell the reader indirectly to put the libraries of mapstruct into the project (pom.xml).

• Either just the libraries as dependencies.
• Or set up the complete mapstruct-processor as described in the MapStruct documentation. This means using a second maven-plugin section. And this setup leads to errors in the annotation processing.

It took me two days to find the correct setup, wasting your tax payers money by the way.

[Chessray]

The documentation is crystal clear: There is nothing to be added to the example maven-plugiin annotationProcessorPaths section, otherwise there would be three dots ("...") in front or after the mapstruct-spring-extensions entry.

This extension project has been "out there" for four years. The documentation section in question hasn't changed at all during this time (apart from adding a warning symbol to the reminder about requiring MapStruct itself after one request that ran across a similar oversight on the user end in a Gradle configuration). Not even once during these four years has anyone suggested this interpretation, so it doesn't seem "crystal clear".

Needless to say there are also examples in this project. Yes, they're Gradle-based; but the relevant sections aren't that difficult to understand. If you feel there could be a little more clarity here, I'm happy to receive a PR.

[filiphr]

@hayosc please be respectful. This is a project maintained by volunteers in their own free time. There is no corporation behind MapStruct. If you were having problems configuring something and you think something should be improved, you are more than welcome to provide a PR with the improvement. Being rude will most definitely not help.

First, do not close issues, without giving the author the chance to reply, just because you do not get the point.

You know that you can also write in a closed issue, not like it's closed forever.