[jboss-jira] [JBoss JIRA] (AS7-1807) Add support for rebranding jars
[
https://issues.jboss.org/browse/AS7-1807?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on AS7-1807:
----------------------------------
This is a -1 to solving this problem by having a module which is designed to be different
in every distribution. This just adds one more obstacle in the path to simplifying the
productization process. Better to boot into a different module per distribution. The
module could even be an aggregate of the actual bootstrap module plus the branding bits
with one boot class to set up the branding environment.
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