-
Notifications
You must be signed in to change notification settings - Fork 2.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
Quarkus Platform Repository #3329
Comments
Other todos:
|
Here is an example how the extensions.json (in its current format) can be generated from a BOM aloubyansky@c80e58e |
Right but this one is the per extension.json file. I'm also thinking of the extensions aggregating file. |
And generally how people will enlist their extension for the platform |
No, that's actually aggregating all the extensions from the bom. |
Looks like this issue can be closed now? |
There are a couple of points from Emmanuel's list we could use to create a couple of issues. Otherwise, yes, can be closed, imo. |
The Quarkus Platform will be aggregating extensions from Quarkus Core and extensions developed externally, including their testsuites. The platform build process will be generating the BOMs and parent POMs for applications as well as the catalog of extensions as a JSON file for Quarkus tooling (such as the starter).
proposed action-plan made on 2019-09-25 (made by @aloubyansky and @maxandersen)
quarkus-platform-tools
- move project create/manipulation tools away from core and keep build/dev-mode/native-image where they areThe text was updated successfully, but these errors were encountered: