[jboss-jira] [JBoss JIRA] Issue Comment Edited: (AS7-1807) Add support for rebranding jars
[
https://issues.jboss.org/browse/AS7-1807?page=com.atlassian.jira.plugin.s...
]
Paul Gier edited comment on AS7-1807 at 9/16/11 3:17 PM:
---------------------------------------------------------
The parts that we customized for EAP 6 so far include:
(1) The log messages (JBPAPP-6831)
(2) The welcome pages (JBPAPP-6838)
(3) The admin console - logos, colors, etc (JBPAPP-7111, JBPAPP-7031)
(4) The config profiles (JBPAPP-7032)
A single jar containing this content/configuration sounds like a good idea. Could this be
configured by changing standalone.conf and domain.conf?
was (Author: pgier):
The parts that we customized for EAP 6 so far include:
(1) The log messages (JBPAPP-6831)
(2) The welcome pages (JBPAPP-6838)
(3) The admin console (JBPAPP-7111, JBPAPP-7031)
(4) The config profiles (JBPAPP-7032)
A single jar containing this content/configuration sounds like a good idea. Could this be
configured by changing standalone.conf and domain.conf?
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: Jason Greene
Fix For: 7.1.0.Alpha1
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira