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

wildfly-maven-plugin resolves different build than it is present in the EAP channel

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Critical Critical
    • None
    • 8.0.0.Beta-CR1
    • EAP Maven Plugin
    • False
    • None
    • False

      Maven repository bit contains artifacts which are expected to be there according to EAP channel, but when I provision EAP using eap-maven-plugin version 1.0.0.Beta6-redhat-00001 I happen to get io.netty:netty-handler-proxy:jar:4.1.77.Final-redhat-00003 instead of io.netty:netty-handler-proxy:jar:4.1.77.Final-redhat-00001 build.

      [DEBUG] WildFly Galleon Installation Plugin
      [DEBUG] Channel artifact resolution enabled=true
      ...
      [DEBUG] Resolving io.netty:netty-handler-proxy:jar:4.1.77.Final-redhat-00001
      [DEBUG] Resolved io.netty:netty-handler-proxy:jar:4.1.77.Final-redhat-00003
      

      The difference between "Resolving" and "Resolved" should fail the build.

            Unassigned Unassigned
            jkasik@redhat.com Jan Kašík
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: