[
https://issues.jboss.org/browse/AS7-6386?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-6386:
---------------------------------------
I modified the issue title and description to better reflect the work that must be done
for the community AS release. Policy decisions about how to ship the EAP console can be
made after the release. The EAP productization process installs a new module for the
console anyway.
See also
http://lists.jboss.org/pipermail/jboss-as7-dev/2012-December/007370.html for more
information about the 2nd option.
Support running the console as a separate layer, or as a versioned
module loadable from
---------------------------------------------------------------------------------------
Key: AS7-6386
URL:
https://issues.jboss.org/browse/AS7-6386
Project: Application Server 7
Issue Type: Sub-task
Components: Scripts, Server
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 7.2.0.Alpha1
It should not require a new AS/EAP release to get a console that can handle extensions
provided by non-AS/EAP layers or add-ons.
To ensure this the AS needs to support both of the following:
1) Distributing the console as a separate layer so we can have a separate release stream
to pick up new console releases that include new extensions.
2) Distributing the console as a module included with each layer or add-on, with the AS
able to determine which of the available console modules is the most recent version and
load it.
The former is a natural fallout of the parent task and requires no further work in the AS
itself.
The latter is a new capability.
It is not a requirement for community AS 7.2 that we choose which approach will be
followed when layered products are produced. However, we will need to settle that issue
before EAP 6.1 is finalized.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira