[jboss-jira] [JBoss JIRA] (AS7-1807) Add support for rebranding jars
[
https://issues.jboss.org/browse/AS7-1807?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen commented on AS7-1807:
------------------------------------------
David - does your suggestion avoid the .bat/.sh scripts being the place this is defined ?
See above why we should not make .bat/.sh's the place to control product disto
settings.
basically any settings controlled by .bat/.sh is ignored by any launches done via
IDE's, arquillian and other "jboss launchers" because of the non-portability
of control over processes started via .bat/.sh.
Add support for rebranding jars
-------------------------------
Key: AS7-1807
URL: https://issues.jboss.org/browse/AS7-1807
Project: Application Server 7
Issue Type: Feature Request
Reporter: Jason Greene
Assignee: Paul Gier
Fix For: 7.1.0.CR1
In order to make it easier for multiple products (EAP/SOA-P/etc) to consume the same
common AS source code, we need to implement a plugability mechanism that allows version
numbers, branding skins/themes, logos, etc to be easily replaced (preferably using a
single jar).
The mechanism would involve supplying some kind of an argument to the bootstrap. For
example:
java -jar \"$JBOSS_HOME/jboss-modules.jar\" \
<snip>
org.jboss.as.standalone
-Djboss.brand.module=org.jboss.as.project-brand
We would then provide some API to get the module so that it can be used to launch
services and/or perform resource loading.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira