Martin Panzer

Hi @neo7BF, sorry for the late response. I am not able to reproduce this issue yet. Here is my sample project. Simply run `mvn clean process-sources` to execute the plugin....

I figured something out. When the outputdirectory already contains an empty jasper file, it is not overwritten with new content.

Currently, the default is to use the `org.codehaus.plexus.compiler.util.scan.StaleSourceScanner` to check if a report needs to be recompiled. Only reports are compiled, where either the .jasper does not exists, or where...

@neo7BF Can you confirm if my observations (see previous comment) are correct? Can you give any more details how this is happening for you?

@RainerGanss I want to do some more sanity checks. Most likely I will build the release early next morning. anway, closing this issue. All points done.

@RainerGanss done

sorry for not getting back to you earlier. It looks to me like net/sf/dynamicreports was compiled using java 17 without the --release 11 switch set. I never used dynamicreports however,...

With the `--release 11` flag I meant the jdk compiler flag. https://openjdk.org/jeps/247 I was previously just looking at the dynamicreports website https://dynamicreports.org/, which did not point to any update of...

Try jasperreports-plugin as artefactid