Configuration properties ignored when using Plugin v4, old artifact id and Maven 3.8.4

[DManstrator]

After updating this plugin to v4, the build is failing due to not finding the configured source folder.

[ERROR] Failed to execute goal com.pro-crafting.tools:jasperreports-maven-plugin:4.0.0:jasper (default) on project <redacted>: Execution default of goal com.pro-crafting.tools:jasperreports-maven-plugin:4.0.0:jasper failed: Configured source directory C:\<redacted>\report\src\main\jasperreports is not a directory

The source folder mentioned in the exception message does in fact not exist but this is also not the configured source folder. It seems that the configured values are ignored now.

There are multiple ways to fix this issue:

• Using a higher Maven version (e.g. Maven 3.9.0) (Currently I use Maven 3.8.4).
• Using the new artifact id (jasperreports-maven-plugin).

Doing one of those options fixes the issue and I'm certainly not sure how this is possible to be honest. I can provide the full debug logs if needed.

Kind regards,

Daniel

[Postremus]

Thanks for reporting this @DManstrator
This is caused by https://issues.apache.org/jira/browse/MNG-5561, which is fixed in maven 3.8.5.

I will add a note about this in the migration section of the README.

[DManstrator]

Wow, this is really fascinating. At first I thought it was an IntelliJ-related caching problem or something similar due to the ways I was able to work around it. The fact I was also just one patch update away from a fixed version is also insane.

Thank you very much for researching and confirming the bug!

If you want I could also create a PR for that change.