You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 1, 2023. It is now read-only.
You can set the lifecyclemappingmetadata to ignore this plugin (see below) which (correct me if I'm wrong), will prevent for example that if you bind the jasper goal to "compile", Eclipse will run the plugin's jasper goal when compiling the project.
I was wondering if other users have managed to create lifecycleMappingMetadata to bind the plugin to m2e's execution. If so, it might be useful to add to the plugin's documentation!
Example m2e mapping configuration that ignores this plugin:
I was wondering if other users have managed to create lifecycleMappingMetadata to bind the plugin to m2e's execution. If so, it might be useful to add to the plugin's documentation!
If I get it right: you want the Eclipse build to compile .jrxml into .jasper, right?
You practically posted the answer, just change the xml snippet a bit, as well as talk about the M2E link you put here.
I tested it and it worked! Thank you for your post because it helped me.
When this plugin in in a project in Eclipse with m2e, Eclipse will complain that "Plugin Execution not covered by lifecycle configuration".
Reason for this is here - https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html
You can set the lifecyclemappingmetadata to ignore this plugin (see below) which (correct me if I'm wrong), will prevent for example that if you bind the jasper goal to "compile", Eclipse will run the plugin's jasper goal when compiling the project.
I was wondering if other users have managed to create lifecycleMappingMetadata to bind the plugin to m2e's execution. If so, it might be useful to add to the plugin's documentation!
Example m2e mapping configuration that ignores this plugin:
The text was updated successfully, but these errors were encountered: