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

[DRAFT] Introduce channel manifest when resolving feature-packs #41

Draft
wants to merge 3 commits into
base: release
Choose a base branch
from

Conversation

jfdenise
Copy link
Contributor

@jfdenise jfdenise commented Jun 25, 2024

Split the provisioning.xml content into 2 pieces:

  • The provisioning.xml contains the list of known feature-packs, without versions. For backward compatibility with older Glow tooling, versions are actually kept in the file but overridden by the manifest.
  • A manifest per execution context and preview/not preview is introduced to resolve feature-pack versions from the manifest.
  • The manifest requires the WildFly manifest
  • The manifest contains streams for the other feature-packs that don't have published manifests.
  • When the other feature-packs will migrate to published manifests, streams will get removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant