[
https://issues.jboss.org/browse/WFCORE-3019?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-3019:
------------------------------------------
This is going to require more thought, as doing this via a FP means that users who neglect
to add this not-obviously-useful FP will end up without this stuff. So this needs to be a
package in a low-level FP, and probably quite a lot of the use for it should be rethought
in the context of the new provisioning system.
The bin/product.conf and the org.jboss.as.product:wildfly-core module
should come in via an FP
----------------------------------------------------------------------------------------------
Key: WFCORE-3019
URL:
https://issues.jboss.org/browse/WFCORE-3019
Project: WildFly Core
Issue Type: Task
Components: Server
Reporter: Brian Stansberry
Assignee: Brian Stansberry
For WFLY-4692 we moved the "product" stuff out of core-feature-pack and into
dist. But this means it doesn't end up in the skinny dist produced by the
"build" module. Plus it makes the "dist" a kind of FP of its own.
The stuff in dist/src/distribution should be its own FP. That one *perhaps* depends on
core-feature-pack. Then build and dist use the new FP in addition to or instead of
core-feature-pack.
So, core-feature-pack is independently usable, in other dists, but our offiical
build/dist, which has our official product module, picks up the new FP.
Whether the new "product" FP depends on core-feature-pack depends on how we
want to use it; i.e. can this bin/product.conf and module be used in some other flavor of
dist.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)