-
-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
Plugin does not work from inside Eclipse #509
Comments
@javadch I could be wrong but I don't think the issue is with the OpenAPI Generator plugin. Would the following article help? http://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html |
@wing328 : yes and no. Our maven plugin could be a little bit more eclipse IDE friendly by integrating some additional metadata. This way no error would be displayed in Eclipse IDE. |
@jmini 👌 please share more so that the community can help add the metadata. |
I guess it is described here how to make the plugin compatible. I will give it a try http://www.eclipse.org/m2e/documentation/m2e-making-maven-plugins-compat.html edit: for me the full builds work after adding the lifecycle-mapping, but the source-code-generation also happens in incremental builds even when the openapi-definition has not changed. To prevent unneccessary builds, the plugin needs to be modified. Before doing smthing it needs to check if the json defintion has changed by using the BuildContext (see https://github.com/sonatype/sisu-build-api/blob/master/src/main/java/org/sonatype/plexus/build/incremental/BuildContext.java). |
@andreas-eternach thanks! Let me know if you need help with the PR. |
probably in that source we can see how to use it: https://github.com/highsource/maven-jaxb2-plugin/blob/79b7af0736c5967876cf89ff7967cafe62367bc7/plugin-core/src/main/java/org/jvnet/jaxb2/maven2/RawXJC2Mojo.java |
probably the file |
@javadch after pulling the repo as described by @wing328 you need to
|
* feat: OpenApi-generation from within eclipse (#509) * Added life-cycle-mapping for recognition by M2E * Make BuildContext injectable by M2E in oder to detect if json-source has been modified and a regeneration is required. * core: fix indentation problems, remove commented code
@javadch the fix by @andreas-eternach has been merged into master. Please give it a try to see if it works for you. Thanks @andreas-eternach for contributing the fix. |
…APITools#1332) * feat: OpenApi-generation from within eclipse (OpenAPITools#509) * Added life-cycle-mapping for recognition by M2E * Make BuildContext injectable by M2E in oder to detect if json-source has been modified and a regeneration is required. * core: fix indentation problems, remove commented code
…typescript-eslint-monorepo chore(deps): update typescript-eslint monorepo to v5 (major)
I have the following plugin spec in my eClipse POM:
It generates the output artifacts using the
mvn clean package
command, but does not generate the code form inside Eclipse! The IDE complains about the node saying:Description Resource Path Location Type Plugin execution not covered by lifecycle configuration: org.openapitools:openapi-generator-maven-plugin:3.1.0:generate (execution: default, phase: generate-resources) pom.xml /timex-backend-api line 34 Maven Project Build Lifecycle Mapping Problem
How can I fix this?
The text was updated successfully, but these errors were encountered: