Note that the produced fat JAR is ignored when running the dev,image,start or run goals.

Defining a channel:

       
    
        
        
         
            
          org.wildfly.channels
          
            
          wildfly-30.0
          
        
         
    
        
    
        
        
         
            
          https://example.example.org/channel/30
          
        
         
    
        

       

The wildfly.channels property can be used pass a comma delimited string for the channels. The channel can be a URL or a Maven GAV. If a Maven GAV is used, the groupId and artifactId are required.
Examples:

    -Dwildfly.channels="https://channels.example.org/30"
    -Dwildfly.channels="https://channels.example.org/30,org.example.channel:updates-30"
    -Dwildfly.channels="https://channels.example.org/30,org.example.channel:updates-30:1.0.2"

By enabling this feature, the set of Galleon feature-packs and layers are automatically discovered by scanning the deployed application. You can configure the following items:

  <discover-provisioning-info>
    <context>cloud</context>
    <profile>ha</profile>
    <addOns>
      <addOn>wildfly-cli</addOn>
      <addOn>openapi</addOn>
    </addOns>
    <layersForJndi>
      <layer>mail</layer>
    </layersForJndi>
  </discover-provisioning-info>

The filename property does have a default of ${project.build.finalName}.${project.packaging}. The default value is not injected as it normally would be due to packaging types like ejb that result in a file with a .jar extension rather than an .ejb extension.

  <galleon-options>
    <jboss-fork-embedded>true</jboss-fork-embedded>
  </galleon-options>

The image goal accepts the following configuration:

<image>
  <!-- (optional) set it to false to skip build the application image (true by default) -->
  <build>true</build>

  <!-- (optional) set it to true to (login and) push the application image to the container registry (false by default).

    If user and password are not specified, the image goal will not attempt to login to the container
    registry prior to pushing the image.
    The login to the container registry must then be performed before Maven is run.
    -->
  <push>true</push>

  <!-- (optional) The binary used to perform image commands (build, login, push) (default is "docker") -->
  <docker-binary>docker</docker-binary>

  <!-- (optional) the JDK version used by the application. Allowed values are "11" and "17". If unspecified, the "latest" tag is used to determine the JDK version used by WildFly runtime image -->
  <jdk-version>11</jdk-version>

  <!-- (optional) The group part of the name of the application image -->
  <group>${user.name}</group>

  <!-- (optional) The name part of the application image. If not set, the value of the artifactId (in lower case) is used -->
  <name>${project.artifactId}</name>

  <!-- (optional) The tag part of the application image (default is "latest") -->
  <tag>latest</tag>

  <!-- (optional) The container registry. If set, the registry is added to the application name.
    If the image is pushed and the registry is not set, it defaults to "docker.io" to login to the registry
    -->
  <registry>quay.io</registry>

  <!-- (optional) The user name to login to the container registry (if push is enabled). -->
  <user>${user.name}</user>

  <!-- (optional) The password login to the container registry (if push is enabled) -->
  <password>${my.secret.password}</password>
</image>

When the deployment is copied to the server, it is renamed with this name.

  <packaging-scripts>
    <packaging-script>
      <scripts>
        <script>../scripts/script1.cli</script>
      </scripts>
      <commands>
        <command>/system-property=foo:add(value=bar)</command>
      </commands>
      <properties-files>
        <property-file>my-properties.properties</property-file>
      </properties-files>
      <java-opts>
        <java-opt>-Xmx256m</java-opt>
      </java-opts>
      <!-- Expressions resolved during server execution -->
      <resolve-expressions>false</resolve-expressions>
    </packaging-script>
  </packaging-scripts>

When the deployment is copied to the server, it is renamed with the runtime-name. If both name and runtime-name are specified, runtime-name is used.

The value of this parameter is also ignored if any layers are defined.