[
https://issues.jboss.org/browse/WFLY-9007?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on WFLY-9007:
----------------------------------------
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:<xxx> module
should come in via an FP
---------------------------------------------------------------------------------------
Key: WFLY-9007
URL:
https://issues.jboss.org/browse/WFLY-9007
Project: WildFly
Issue Type: Task
Components: Server
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 12.0.0.Alpha1
For WFLY-4692 we moved the "product" stuff out of [servlet-]feature-pack and
into [servlet-]dist. But this means it doesn't end up in the skinny dist produced by
the "[servlet-]build" module. Plus it makes the "dist" a kind of FP of
its own.
The stuff in [servlet-]dist/src/distribution should be its own FP. That one *perhaps*
depends on the related normal feature-pack. Then build and dist use the new FP in addition
to or instead of the regular feature-pack.
So, the regular 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 the regular 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 besides the official one.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)