-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
After discussing with jdenise@redhat.com, we determined the org.jboss.galleon:galleon-core artifact should be part of Wildfly manifests, currently it's not.
One side effect is that when listing upgradeable components via prospero or JBoss CLI, the galleon-core is always listed as "to be removed", because it's not resolveable by subscribed channels.
Notes from the conversation:
- Galleon adds galleon-core item into recorded manifest intentionally.
- Galleon looks at all the feature packs that are to be provisioned and determines latest version of galleon-core. Each feature pack manifest should state the galleon-core version.
- Similarly, "universe" artifacts are as well added explicitly to the Wildfly/EAP manifests, galleon-core should be added similarly. It can be achieved by adding galleon-core as a dependency in the galleon pack module, as the "universe" artifacts were added.
- The version of galleon-core to add to the manifest should be the version used for building the galleon pack.
- relates to
-
JBEAP-31872 Prospero generate galleon-core entry to server manifest, although galleon-core is not used in server nor channel
-
- Resolved
-