Kauri Documentation
 PreviousHomeNext 
18.2.3 Plugin configuration propertiesBook Index18.2.5 Limitations

18.2.4 Executing the plugin as part of build lifecycle

If you want to execute the plugin as part of the build lifecycle, use the "attached-webapp" goal.

warning: when adding this in the root pom, be aware that this will run first, as part of the root pom, not after all the modules have been built. Define a separate project with approriate dependencies to force correct execution order. I think this is the only solution, though have not looked to deep into it yet. (what does assembly:attached do?). Anyway, I'd recommend calling it manually for now.

      <plugin>
        <groupId>org.kauriproject</groupId>
        <artifactId>kauri-package-plugin</artifactId>
        <version>${version.kauri}</version>
        <inherited>false</inherited>        
        <configuration>
          <confDirectory>${basedir}/conf</confDirectory>
        </configuration>
        <executions>
          <execution>
            <phase>install</phase>
            <goals>
              <goal>attached-webapp</goal>
            </goals>
          </execution>
        </executions>
      </plugin>
 PreviousHomeNext 
18.2.3 Plugin configuration properties18.2.5 Limitations