[jboss-jira] [JBoss JIRA] Commented: (AS7-1807) Add support for rebranding jars
[
https://issues.jboss.org/browse/AS7-1807?page=com.atlassian.jira.plugin.s...
]
Julian Coleman commented on AS7-1807:
-------------------------------------
For SOA-P and BRMS-P we would also want to customise the same parts as EAP. Having
the replacable parts as a separate build artifact (or more than one) would be very
useful here. AS7 would supply a default, and the platforms would provide customised
versions.
However, we will also include additional components (e.g. SwitchYard and Drools).
If we need to modify existing configuration files because of the extra components,
it would be good to split those configuration files into separate build artifacts
too. These could be looked at individually as they arise though.
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.Beta1
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