[
https://issues.jboss.org/browse/AS7-1807?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen commented on AS7-1807:
------------------------------------------
Great to have a switch for it but could we please avoid requiring to have these listed on
startup/shellscripts ?
Otherwise when you launch the as process without using the run scripts it will be branded
wrong.
Examples of things that launch AS without the run script is arquillian, maven and
IDE's that need
to be able to kill and/or control the output and process.
This actually apply to *all* switches but if branding is done this way it becomes very
visible ;)
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