Maven plugin to aid in migration from other build systems
Java HTML Groovy
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
src
LICENSE-2.0.html
README.md Add tests and allow mainArtifact to be optional May 25, 2016
pom.xml

README.md

Build Migration Maven Plugin

This plugin is meant to be a small collection of helpers to smooth the migration path from another build system, like Ant, to Maven. The plugins will probably all be very simple, yet they will address use cases that are currently not supported by any plugin, or are excessively complicated to configure.

The main-artifact Goal

The main-artifact goal can set the file of the project's main artifact and main pom file. It can also attach auxillary artifacts to be deployed (in the same way as the build-helper-maven-plugin)

Parameters Type Required Description
mainArtifact String No File path to the new main artifact to deploy
mainPom String No File path to the replacement main pom to deploy
artifacts Artifact[] No Attach an array of artifacts to the project

This can be useful if you're wrapping another build system's output with Maven pom.xml files, and need to get Maven to recognize the build output for purposes of installation or deployment. Its use is very simple:

<project>
  [...]
  <build>
    <plugins>
      <plugin>
        <artifactId>maven-antrun-plugin</artifactId>
        <executions>
          <execution>
            <id>build-ant</id>
            <goals>
              <goal>run</goal>
            </goals>
            <configuration>
              <target>
                  <ant antfile="build.xml" inheritAll="true" inheritRefs="true" target="all"/>
              </target>
            </configuration>
          </execution>
        </executions>
      </plugin>

      <plugin>
        <groupId>org.commonjava.maven.plugins</groupId>
        <artifactId>build-migration-maven-plugin</artifactId>
        <version>0.4</version>
        <executions>
          <execution>
            <id>main-artifact</id>
            <goals>
              <goal>main-artifact</goal>
            </goals>
            <configuration>
              <mainArtifact>build/project-1.1.jar</mainArtifact>
              <mainPom>resources/myproject.pom</mainPom>
              <artifacts>
                <artifact>
                  <file>myproject-sources.jar</file>
                  <type>jar</type>
                  <classifier>sources</classifier>
                </artifact>
              </artifacts>
            </configuration>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>
</project>

By default, the main-artifact goal will run in the package phase, which means it will normally run after the jar:jar goal has run. If you want to disable the jar:jar goal, one way to do that is with something like the following:

<plugin>
  <artifactId>maven-jar-plugin</artifactId>
  <configuration>
    <excludes>
      <exclude>**/*</exclude>
    </excludes>
    <skipIfEmpty>true</skipIfEmpty>
  </configuration>
</plugin>

This tells the jar plugin to skip all classes, and then skip building the jar (since it would be empty).

Another way would be to bind the maven-jar-plugin to a disabled phase:

<plugin>
  <artifactId>maven-jar-plugin</artifactId>
  <executions>
    <execution>
      <id>default-jar</id>
      <phase>DISABLED</phase>
     </execution>
   </executions>
 </plugin>