[JBoss JIRA] Created: (AS7-1807) Add support for rebranding jars

[JBoss JIRA] (JGRP-1409) Add...

[JBoss JIRA] (AS7-3116) implement...

Jason Greene (JIRA)

Tuesday, 13 September 2011 Tue, 13 Sep '11

12:45 p.m.

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 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

Show replies by date

Jason Greene (JIRA)

Tuesday, 13 September Tue, 13 Sep

12:45 p.m.

New subject: [JBoss JIRA] Assigned: (AS7-1807) Add support for rebranding jars

[ https://issues.jboss.org/browse/AS7-1807?page=com.atlassian.jira.plugin.s... ] Jason Greene reassigned AS7-1807: --------------------------------- Assignee: Jason Greene

...

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

Paul Gier (JIRA)

Wednesday, 14 September Wed, 14 Sep

8:53 p.m.

New subject: [JBoss JIRA] Commented: (AS7-1807) Add support for rebranding jars

[ https://issues.jboss.org/browse/AS7-1807?page=com.atlassian.jira.plugin.s... ] Paul Gier commented on AS7-1807: -------------------------------- The parts that we customized for EAP 6 so far include: (1) The log messages (2) The welcome pages (3) The admin console 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

Paul Gier (JIRA)

Thursday, 15 September Thu, 15 Sep

9:25 a.m.

New subject: [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/15/11 10:24 AM: ---------------------------------------------------------- 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? was (Author: pgier): The parts that we customized for EAP 6 so far include: (1) The log messages (2) The welcome pages (3) The admin console 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

Paul Gier (JIRA)

Friday, 16 September Fri, 16 Sep

2:19 p.m.

New subject: [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

Max Rydahl Andersen (JIRA)

Wednesday, 21 September Wed, 21 Sep

10:23 a.m.

New subject: [JBoss JIRA] Commented: (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: ------------------------------------------ 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

Jason Greene (JIRA)

Thursday, 22 September Thu, 22 Sep

10:19 p.m.

New subject: [JBoss JIRA] Updated: (AS7-1807) Add support for rebranding jars

[ https://issues.jboss.org/browse/AS7-1807?page=com.atlassian.jira.plugin.s... ] Jason Greene updated AS7-1807: ------------------------------ Fix Version/s: 7.1.0.Beta1 (was: 7.1.0.Alpha1)

...

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

Tristan Tarrant (JIRA)

Monday, 26 September Mon, 26 Sep

8:09 a.m.

New subject: [JBoss JIRA] Commented: (AS7-1807) Add support for rebranding jars

[ https://issues.jboss.org/browse/AS7-1807?page=com.atlassian.jira.plugin.s... ] Tristan Tarrant commented on AS7-1807: -------------------------------------- I agree with Max Andersen. Ideally we could have a module "org.jboss.as.branding" which each "consumer" can replace with their own custom one.

...

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

Julian Coleman (JIRA)

10:22 a.m.

New subject: [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

Jason Greene (Updated) (JIRA)

Friday, 4 November Fri, 4 Nov

1:11 p.m.

New subject: [JBoss JIRA] (AS7-1807) Add support for rebranding jars

[ https://issues.jboss.org/browse/AS7-1807?page=com.atlassian.jira.plugin.s... ] Jason Greene updated AS7-1807: ------------------------------ Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) Moving all non-critical issues to the CR. If you finish it before we release beta please correct the fix-for version. Thanks

...

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.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

Jason Greene (Updated) (JIRA)

1:11 p.m.

New subject: [JBoss JIRA] (AS7-1807) Add support for rebranding jars

[ https://issues.jboss.org/browse/AS7-1807?page=com.atlassian.jira.plugin.s... ] Jason Greene updated AS7-1807: ------------------------------ Moving all non-critical issues to the CR. If you finish it before we release beta please correct the fix-for version. Thanks

...

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.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.

Shelly McGowan (Updated) (JIRA)

2:26 p.m.

New subject: [JBoss JIRA] (AS7-1807) Add support for rebranding jars

[ https://issues.jboss.org/browse/AS7-1807?page=com.atlassian.jira.plugin.s... ] Shelly McGowan updated AS7-1807: -------------------------------- Assignee: Paul Gier (was: Jason Greene)

...

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.

Paul Gier (Updated) (JIRA)

Thursday, 17 November Thu, 17 Nov

10:54 a.m.

New subject: [JBoss JIRA] (AS7-1807) Add support for rebranding jars

[ https://issues.jboss.org/browse/AS7-1807?page=com.atlassian.jira.plugin.s... ] Paul Gier updated AS7-1807: --------------------------- Comment: was deleted (was: Moving all non-critical issues to the CR. If you finish it before we release beta please correct the fix-for version. Thanks)

...

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.

Paul Gier (Updated) (JIRA)

10:54 a.m.

New subject: [JBoss JIRA] (AS7-1807) Add support for rebranding jars

...

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.

David Lloyd (Commented) (JIRA)

10:58 a.m.

New subject: [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.

Max Rydahl Andersen (Commented) (JIRA)

Sunday, 4 December Sun, 4 Dec

7:54 a.m.

New subject: [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.

Heiko Rupp (Commented) (JIRA)

Tuesday, 13 December Tue, 13 Dec

3:47 p.m.

New subject: [JBoss JIRA] (AS7-1807) Add support for rebranding jars

[ https://issues.jboss.org/browse/AS7-1807?page=com.atlassian.jira.plugin.s... ] Heiko Rupp commented on AS7-1807: --------------------------------- Please don't forget the versions that are returned by [standalone@localhost:9999 /] :read-attribute(name=release-version) "result" => "7.1.0.Beta1-redhat-1" and [standalone@localhost:9999 /] :read-attribute(name=release-codename) "result" => "Tesla" Especially as the above is from DR8 and the boot log already shows the correct information. See also AS7-364

...

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.Final 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.

Jason Greene (Assigned) (JIRA)

Thursday, 29 December Thu, 29 Dec

11:03 p.m.

New subject: [JBoss JIRA] (AS7-1807) Add support for rebranding jars

[ https://issues.jboss.org/browse/AS7-1807?page=com.atlassian.jira.plugin.s... ] Jason Greene reassigned AS7-1807: --------------------------------- Assignee: Jason Greene (was: Paul Gier)

...

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.Final 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.

Jason Greene (Resolved) (JIRA)

11:05 p.m.

New subject: [JBoss JIRA] (AS7-1807) Add support for rebranding jars

[ https://issues.jboss.org/browse/AS7-1807?page=com.atlassian.jira.plugin.s... ] Jason Greene resolved AS7-1807. ------------------------------- Resolution: Done

...

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.Final 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.

Max Rydahl Andersen (JIRA)

Thursday, 12 January Thu, 12 Jan

5:33 a.m.

New subject: [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: ------------------------------------------ For future reference details discussed at: http://lists.jboss.org/pipermail/jboss-as7-dev/2012-January/005017.html and http://lists.jboss.org/pipermail/jboss-as7-dev/2012-January/004974.html

...

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.Final 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.

Max Rydahl Andersen (JIRA)

5:33 a.m.

New subject: [JBoss JIRA] (AS7-1807) Add support for rebranding jars

...

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.Final 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.

4651

days inactive

4772

days old

jboss-jira@lists.jboss.org

Manage subscription

20 comments

13 participants

tags (0)

participants (13)

David Lloyd (Commented) (JIRA)
Heiko Rupp (Commented) (JIRA)
Jason Greene (Assigned) (JIRA)
Jason Greene (JIRA)
Jason Greene (Resolved) (JIRA)
Jason Greene (Updated) (JIRA)
Julian Coleman (JIRA)
Max Rydahl Andersen (Commented) (JIRA)
Max Rydahl Andersen (JIRA)
Paul Gier (JIRA)
Paul Gier (Updated) (JIRA)
Shelly McGowan (Updated) (JIRA)
Tristan Tarrant (JIRA)

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

[JBoss JIRA] Created: (AS7-1807) Add support for rebranding jars