[jboss-jira] [JBoss JIRA] (WFLY-405) Patching system

[Jason Greene (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Greene updated WFLY-405:
------------------------------

    Fix Version/s: 8.0.0.Beta1
                       (was: 8.0.0.Alpha4)

    
> Patching system
> ---------------
>
>                 Key: WFLY-405
>                 URL: https://issues.jboss.org/browse/WFLY-405
>             Project: WildFly
>          Issue Type: Task
>          Components: Domain Management
>            Reporter: Brian Stansberry
>            Assignee: Emanuel Muckenhuber
>            Priority: Blocker
>              Labels: rhq
>             Fix For: 8.0.0.Beta1
>
>
> "Server" side of the patching system. Server not in the sense of the domain model Server, but rather client-server where the client is whatever tool (JON) determines there are patches available and asks the server to apply them.
> This does not need to implemented until M2 but thinking about it during the design of the InstalledImage is good.
> Links to the current wiki articles:
> https://community.jboss.org/wiki/LayeredDistributionsAndModulePathOrganization
> https://community.jboss.org/wiki/SingleInstallationPatching
> https://community.jboss.org/wiki/ExperimentingWithSingleInstallationPatching

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