Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-21334

(7.3.z) Maven WARNING building wildfly-core-eap on 10.1.x and 11.0.x

    XMLWordPrintable

Details

    Description

      When building wildfly-core-eap 10.1.x and 11.0.x the following warning is shown:

      [WARNING]
[WARNING] Some problems were encountered while building the effective model for org.wildfly.core:wildfly-elytron-integration:jar:11.0.1.Final-redhat-SNAPSHOT
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.wildfly.core:wildfly-controller-client:jar -> duplicate declaration of version (?) @ line 150, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]

      The issue is the org.wildfly.core:wildfly-controller-client is added as a dependency in two scopes, for test and no explicit scope.

      Removing the dependency declaration on the test scope fix the issue.

       

      It seems it has been there since long time ago without any side effect but, it should be removed according to the warning

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-4943 Remove duplicate elytron's duplicate dependency to controller-client

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-21094 (7.3.z) Upgrade WildFly Core from 10.1.18.Final-redhat-00001 to 10.1.19.Final-redhat-00001

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              thofman Tomas Hofman
              yborgess1@redhat.com Yeray Borges Santana
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: