-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jasper file created is empty #50
Comments
I had the same problem and I fixed it by deleting the configuraton parameter |
Hi @neo7BF, I am not able to reproduce this issue yet. Here is my sample project. Are you able to reproduce your issue with this sample project? |
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 If, by any chance, any other process now modifies the compiled .jasper file, then it still exist and is newer then the source file. Another supported source scanner is the SimpleSourceInclusionScanner. This one just searches what source files exists, and always recompiles all of them.
|
@neo7BF Can you confirm if my observations (see previous comment) are correct? Can you give any more details how this is happening for you? |
I'm using this plugin in a spring web application and it produces empty .jasper files while with the original official plugin (in beta) they are produced correctly.
Can you tell me what the problem is?
Thank you.
Java version:
Jasper Reports version used:
New plugin configuration (produces empty .jasper files):
Old plugin configuration (jasper files are produced correctly):
The text was updated successfully, but these errors were encountered: