[jboss-jira] [JBoss JIRA] (WFCORE-1658) JBEAP-2830 enhancements were not forward ported to upstream

Brian Stansberry (JIRA) issues at jboss.org
Mon Jul 18 00:50:00 EDT 2016


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

Brian Stansberry updated WFCORE-1658:
-------------------------------------
    Description: 
JBEAP-2830 includes changes to the logging subsystem's template.xml that EAP full relies upon. These were never forward ported to upstream, meaning that EAP builds can't consume core 2.2 or later.

I believe there's no problem applying the changes. EAP will use one of the supplements while WildFly will not.

  was:
JBEAP-2830 includes changes to the logging subsystem's template.xml that EAP full relies upon. These were never forward ported to upstream, meaning that EAP builds can't consume core 2.2 or later.

I believe there's no problem applying the changes. EAP will use on of the supplements while WildFly will not.



> JBEAP-2830 enhancements were not forward ported to upstream
> -----------------------------------------------------------
>
>                 Key: WFCORE-1658
>                 URL: https://issues.jboss.org/browse/WFCORE-1658
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Logging
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>            Priority: Blocker
>             Fix For: 2.2.0.CR8
>
>
> JBEAP-2830 includes changes to the logging subsystem's template.xml that EAP full relies upon. These were never forward ported to upstream, meaning that EAP builds can't consume core 2.2 or later.
> I believe there's no problem applying the changes. EAP will use one of the supplements while WildFly will not.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jboss-jira mailing list