[jboss-jira] [JBoss JIRA] (WFCORE-5015) Create 'core-specific' variants of Galleon feature groups and packages that are 'overridden' in full WildFly

[Brian Stansberry (Jira)]

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

Brian Stansberry updated WFCORE-5015:
-------------------------------------
    Description: 
See  [https://lists.jboss.org/pipermail/wildfly-dev/2020-June/007342.html] for background.

For the wildfly-core galleon pack feature groups and packages that are 'overridden' in full WildFly, create a differently named variant in the galleon-common module that can be referenced in full WF. This eliminates the 'overriding/subclassing' and in a GAL-319 type future setup will allow the 'core' source item to be directly incorporated in the target FP in full without conflicting with an item with the same name in that target FP.

 

Feature groups:

 

domain-host-excludes

domain-interfaces

domain-profile

host-master

host-slave

host

standalone-profile

 

Packages:

bin.common

bin.vaulttools

docs.licenses.merge

misc.common

misc.domain

misc.standalone

 

  was:
See  [https://lists.jboss.org/pipermail/wildfly-dev/2020-June/007342.html] for background.

For the wildfly-core galleon pack feature groups and packages that are 'overridden' in full WildFly, create a differently named variant in the galleon-common module that can be referenced in full WF. This eliminates the 'overriding/subclassing' and in a GAL-319 type future setup will allow the 'core' source item to be directly incorporated in the target FP in full without conflicting with an item with the same name in that target FP.



> Create 'core-specific' variants of Galleon feature groups and packages that are 'overridden' in full WildFly
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: WFCORE-5015
>                 URL: https://issues.redhat.com/browse/WFCORE-5015
>             Project: WildFly Core
>          Issue Type: Task
>          Components: Build System
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>            Priority: Major
>
> See  [https://lists.jboss.org/pipermail/wildfly-dev/2020-June/007342.html] for background.
> For the wildfly-core galleon pack feature groups and packages that are 'overridden' in full WildFly, create a differently named variant in the galleon-common module that can be referenced in full WF. This eliminates the 'overriding/subclassing' and in a GAL-319 type future setup will allow the 'core' source item to be directly incorporated in the target FP in full without conflicting with an item with the same name in that target FP.
>  
> Feature groups:
>  
> domain-host-excludes
> domain-interfaces
> domain-profile
> host-master
> host-slave
> host
> standalone-profile
>  
> Packages:
> bin.common
> bin.vaulttools
> docs.licenses.merge
> misc.common
> misc.domain
> misc.standalone
>  



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