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

(8.1.z) [wildfly-maven-plugin] Bootable JAR won't be created if server provisioning-dir already exists

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      Set overwrite-provisioned-server to true, so everything will be re-provisioned.

      Show
      Set overwrite-provisioned-server to true, so everything will be re-provisioned.
    • Hide
      1. Create bootable JAR with wildfly-maven-plugin
      2. Remove created bootable JAR
      3. Run Maven with same configuration as in step 1
      4. Bootable JAR won't be created because whole packaging process will be skipped due to fact that provisioning-dir already exists.
      Show
      Create bootable JAR with wildfly-maven-plugin Remove created bootable JAR Run Maven with same configuration as in step 1 Bootable JAR won't be created because whole packaging process will be skipped due to fact that provisioning-dir already exists.

      When a directory set to provisioning-dir already exists, bootable-jar option is set to true, but the bootable JAR artifact doesn't exist, bootable JAR won't be created.

              lvydra Lukas Vydra
              jkasik@redhat.com Jan Kašík
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: