[
https://issues.jboss.org/browse/WFCORE-1609?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-1609:
------------------------------------------
A quick design note on this: instead of passing in the slot and still having ProductConfig
read a module to get the necessary data, I could have put in a mechanism to just directly
pass in the data. But I wanted to do the minimum quickly here, keep the overall mechanism
as much like the standard one as possible and try to avoid bugs, confusion or unintended
uses that arise from bigger differences. But the other approach can be considered in the
future if it makes sense.
Allow static definition of the product module slot
--------------------------------------------------
Key: WFCORE-1609
URL:
https://issues.jboss.org/browse/WFCORE-1609
Project: WildFly Core
Issue Type: Feature Request
Components: Server
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 2.2.0.CR4, 3.0.0.Alpha3
The way a WildFly Core based distribution is able to control metadata such as the
reported product name and version is by packaging an org.jboss.as.product:xxx module and
then including a bin/product.conf file with a properties file that includes property
slot=xxx. The ProductConfig class looks for bin/product.conf and reads it from the
filesystem.
This does not work for WildFly Swarm, which is not based on an expanded filesystem. There
is no bin/product.conf file, not even a bin dir.
This RFE is to have ProductConfig allow the slot name to be directly passed in, skipping
the property file reading, with SelfContainerContainer (used by swarm) passing in a static
value of "main". So swarm can package a org.jboss.as.product:main module and
use it to control the product settings.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)