[jboss-jira] [JBoss JIRA] (WFLY-13741) The standalone-load-balancer configurations should depend on legacy-management

[Brian Stansberry (Jira)]

    [ https://issues.redhat.com/browse/WFLY-13741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14353803#comment-14353803 ] 

Brian Stansberry commented on WFLY-13741:
-----------------------------------------

Just an FYI re both this layer and the feature-group. The code for it is in https://github.com/wildfly/wildfly-core/tree/master/core-feature-pack/galleon-feature-pack instead of https://github.com/wildfly/wildfly-core/tree/master/core-feature-pack/galleon-common because the latter is meant to be "sharable" (i.e. sucked in as source using GAL-319 whereby the consuming f-p has no dependency on org.wildfly.core:wildfly-core-galleon-pack itself) while the former is not.

The layer and feature group are not in the sharable one because I want to avoid them leaking out into 'non-legacy' feature packs, i.e. the EE 9 one I'm doing.

This doesn't affect this particular JIRA. The wildfly-ee-galleon-pack uses the legacy feature-group; now it will use the legacy layer. Either way it is using legacy stuff, which is ok as it itself is 'legacy'.

> The standalone-load-balancer configurations should depend on legacy-management
> ------------------------------------------------------------------------------
>
>                 Key: WFLY-13741
>                 URL: https://issues.redhat.com/browse/WFLY-13741
>             Project: WildFly
>          Issue Type: Task
>          Components: Build System
>            Reporter: Darran Lofthouse
>            Assignee: Darran Lofthouse
>            Priority: Major
>             Fix For: 21.0.0.Beta1
>
>
> The standalone-load-balancer.xml/config.xml which can be found in ee-feature-pack and servlet-feature-pack should depend on the legacy-management layer instead of depending on management and adding security to it.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)