nderwin-forks / megamek Goto Github PK

http://megamek.info/forums/index.php?topic=2315.0

Add the Maven source plugin to the Maven-ized build so the sources will be available with the main artifact.

When running the Maven verify goal, the OfficialUnitList.txt file is generated, but it lands in the docs folder in the main project, instead of the docs folder in the target directory. Need to research when this file should be generated, and see if the build process can be adjusted, or if the generation of the file can be updated to specify an output path.

When using the standard build.xml file to build the project, the testreport, teststaging, and unittests directories are included in the MegaMek.jar file. These should be ignored, as they are not a part of the runtime artifact.

Add the JaCoCo code coverage plugin to the Maven-ized build so that test coverage can be reported.

With the build process using Maven, add the Checkstyle plugin to enforce code style (4 space indents, etc. that have been specified by MegaMek).

Update the directory structure to conform to Maven standards, and remove the customized paths from the pom.

Set up a Maven pom file to perform the build and packaging process.

Add a Travis script (or similar) to the project so that it will automatically build after a push or merge.