[jboss-jira] [JBoss JIRA] Commented: (JBAS-6750) get Admin Console WAR integrated into JBAS 5.1 distribution

[Jesper Pedersen (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-6750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12462154#action_12462154 ] 

Jesper Pedersen commented on JBAS-6750:
---------------------------------------

Create thread on jboss-development about this - having a common/deploy doesn't make sense if you don't plan to support all configuration under server/ - like minimal. Also remember that the idea of having configurations under server is to enable users to create their own. Are you going to support these also ? Email or forum thread, please.

> get Admin Console WAR integrated into JBAS 5.1 distribution
> -----------------------------------------------------------
>
>                 Key: JBAS-6750
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6750
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Build System
>            Reporter: Ian Springer
>            Assignee: Paul Gier
>            Priority: Critical
>         Attachments: jopr-embedded.patch
>
>
> We're getting close to the AS 5.1 release date, so it's probably time to get jbas5-admin-console.war integrated into the AS dist. This will entail the following steps:
> 1) Stick an exploded copy of the WAR under the deploy/ dir of each config set we want it deployed to by default. The JMX console WAR is deployed to the 'default', 'all', 'standard', and 'web' config sets. The difference is that jbas5-admin-console.war is 10.7 MB (exploded), while jmx-console.war is only 96.6 KB. Adding jbas5-admin-console.war to all 4 config sets would increase the AS 5.1 installation size by 42.8 MB, and the distribution zipfile size by roughly 39.2 MB. We could also look into reducing the size of the admin console WAR - 6.5 out of its 10.7 MB is Seam and RichFaces; perhaps these could be moved to some shared lib directory, which all four config sets could reference.
> 2) In each config set with which we decide to include the admin console WAR, add a link to /admin-console in deploy/ROOT.war/index.html.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira