[jboss-jira] [JBoss JIRA] (WFCORE-3928) Exclusion groupId and artifactId in the wrong order in the root pom

[Kabir Khan (JIRA)]

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

Kabir Khan moved WFLY-10572 to WFCORE-3928:
-------------------------------------------

              Project: WildFly Core  (was: WildFly)
                  Key: WFCORE-3928  (was: WFLY-10572)
          Component/s: Build System
                           (was: Build System)
    Affects Version/s: 5.0.0.Final
                           (was: 13.0.0.Final)
        Fix Version/s: 6.0.0.Alpha2
                           (was: 14.0.0.CR1)


> Exclusion groupId and artifactId in the wrong order in the root pom
> -------------------------------------------------------------------
>
>                 Key: WFCORE-3928
>                 URL: https://issues.jboss.org/browse/WFCORE-3928
>             Project: WildFly Core
>          Issue Type: Task
>          Components: Build System
>    Affects Versions: 5.0.0.Final
>            Reporter: Kabir Khan
>            Assignee: Kabir Khan
>            Priority: Trivial
>             Fix For: 6.0.0.Alpha2
>
>
> e.g. in https://github.com/wildfly/wildfly/blob/13.0.0.Final/pom.xml#L4198 the exclusions have groupId and artifactId in the wrong order. e.g. 
> {code}
>                     <exclusion>
>                         <artifactId>hal-ballroom</artifactId>
>                         <groupId>org.jboss.hal</groupId>
>                     </exclusion>
> {code}
> should be
> {code}
>                     <exclusion>
>                         <groupId>org.jboss.hal</groupId>
>                         <artifactId>hal-ballroom</artifactId>
>                     </exclusion>
> {code}
> While the former is valid, it is confusing, and seems to have been introduced in the refactoring to use the component-matrix (which was later undone)



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)