-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add to m2e discovery catalog #30
Comments
I agree that it would be great to automatically discover and install this, but I don't know enough about this ecosystem to make it happen. Any chance you can help, @kwin ? |
A prerequisite for this is a p2 update site from where the extension could be installed (#1). Once that is in place I can help creating a PR for the discovery catalog. |
@kwin Do you know if the Takari discovery catalog is the only way to get automatically discovered? Is there any way for the formatter plugin itself to define enough metadata for discovery on its own? |
This is not called discovery then, but sure you can integrate m2e support in the plugin as well: https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html |
I think we want to
Based on this conversation and my previous investigations into this, I think the first option is the only way this can work, but since the link is broken, I don't know where to look for the full syntax of the configurator in the metadata: https://github.com/revelc/formatter-maven-plugin/blob/main/src/main/resources/META-INF/m2e/lifecycle-mapping-metadata.xml#L26-L34 |
This m2e extension should be added to https://github.com/takari/m2e-discovery-catalog to be able to automatically install this once the formatter-maven-plugin is detected.
The text was updated successfully, but these errors were encountered: