[jboss-jira] [JBoss JIRA] (WFLY-405) Patching system
RH Bugzilla Integration (JIRA)
issues at jboss.org
Sun Dec 15 11:22:37 EST 2013
[ https://issues.jboss.org/browse/WFLY-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931533#comment-12931533 ]
RH Bugzilla Integration commented on WFLY-405:
----------------------------------------------
mark yarborough <myarboro at redhat.com> changed the Status of [bug 999652|https://bugzilla.redhat.com/show_bug.cgi?id=999652] from VERIFIED to CLOSED
> Patching system
> ---------------
>
> Key: WFLY-405
> URL: https://issues.jboss.org/browse/WFLY-405
> Project: WildFly
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Domain Management, Patching
> Reporter: Brian Stansberry
> Assignee: Emanuel Muckenhuber
> Priority: Blocker
> Labels: rhq
> Fix For: 8.0.0.CR1
>
>
> "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
More information about the jboss-jira
mailing list