Skip to content
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

Closed
5 tasks done
aloubyansky opened this issue Jul 25, 2019 · 8 comments
Closed
5 tasks done

Quarkus Platform Repository #3329

aloubyansky opened this issue Jul 25, 2019 · 8 comments
Assignees
Labels
area/platform Issues related to definition and interaction with Quarkus Platform
Milestone

Comments

@aloubyansky
Copy link
Member

aloubyansky commented Jul 25, 2019

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)

  • create a separate git repo in quarkusio
  • release a handdrafted platform bom referencing camel with quarkus bom that is known to work
  • create a separate quarkus-platform-tools - move project create/manipulation tools away from core and keep build/dev-mode/native-image where they are
  • release quarkus platform tools
  • make quarkus platform tools capable of reading online metadata to get latest versions to default to (if offline we'll fallback to what was there when platform tools release)
@aloubyansky aloubyansky self-assigned this Jul 25, 2019
@emmanuelbernard
Copy link
Member

Other todos:

  • define a extensions.yml or otherwise to be consumed by code.quarkus.io and our maven tooling to know the list of extensions
    • for example override a label as needed, set a category etc
  • create a process to generate and manually add the settings specific to extensions.yml
  • define the notion of beta or experimental for an extension (label?)
  • define the notion of a preferred extension (label). I think we had a better name but we need that

@aloubyansky
Copy link
Member Author

aloubyansky commented Sep 25, 2019

Here is an example how the extensions.json (in its current format) can be generated from a BOM aloubyansky@c80e58e

@emmanuelbernard
Copy link
Member

Right but this one is the per extension.json file. I'm also thinking of the extensions aggregating file.

@emmanuelbernard
Copy link
Member

And generally how people will enlist their extension for the platform

@aloubyansky
Copy link
Member Author

No, that's actually aggregating all the extensions from the bom.

@maxandersen maxandersen added the area/platform Issues related to definition and interaction with Quarkus Platform label Sep 30, 2019
@paulrobinson paulrobinson mentioned this issue Oct 15, 2019
18 tasks
@gastaldi
Copy link
Contributor

Looks like this issue can be closed now?

@aloubyansky
Copy link
Member Author

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.

@aloubyansky
Copy link
Member Author

Ok, I created #4771 and #4772

@gsmet gsmet added this to the 0.27.0 milestone Oct 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/platform Issues related to definition and interaction with Quarkus Platform
Projects
None yet
Development

No branches or pull requests

5 participants