2.1.1 (under development)

• Improved clean mojo, added flags to clean Go path folder defined through goPath parameter, and added flag to delete whole storeFolder
• Added flag ignoreErrorExitCode to prevent failure for error exit code, it is useful in some test cases.
• Added parameter reportsFolder to define folder where some reports will be placed.
• Added parameters outLogFile and errLogFile to save execution console log as files in the report folder. By default such reports are not saved.
• Console log for test will be shown in maven log only in verbose mode

2.1.0 (28-may-2016)

• Output of environment variables has been moved under the verbose flag
• Added mvninstall goal which saves artifact into local maven repository during install phase,#2 request
• Added support of branches and tags into get, it works for Git, Hg and SVN repositories
• Improved archetype template, added example of test
• Fixed issue #3 "cannot run tests"

2.0.0 (17-apr-2016)

• Added maven archetype mvn-golang-hello to generate minimal GoLang "Hello World!" project
• Added mojo for run command.
• Removed <findExecInGoPath> property because the logic of search executable file has been reworked
• Added goBin parameter to provide $GOBIN value
• Improved CLEAN to delete also the project target folder
• The Banner is hidden by default
• Changed project folder structure to be closer to GoLang projects
• Added life-cycle for packaging mvn-golang with support of the standard GoLang project hierarchy, as example see adapted the Hello world example for the case
• Improved logging of command console output, now it is split to lines and every line logged separately
• Added support for loading of archives with Content-type application/x-gzip
• Increased number of test examples
• Build of example applications moved to the special profile examples

1.1.0 (05-apr-2016)

• Added test example for gomobile for Android ARM 7
• Added <findExecInGoPath>, it allows to find golang tool in $GOPATH instead of $GOROOT (by default false)
• Added <echo> and <echoWarn> to print echo messages into maven log
• Added <exec> parameter to define gotool name (by default go)
• Added <execSubpath> parameter to provide sub-path in SDK root to find golang tool (by default bin)
• Renamed parameter <name> to <resultName> and <target> to <resultFolder> for build
• Fixed racing issue for the maven -T4 flag
• Fixed "Truncated TAR archive exception" for Mac OS tar.gz archive
• Removed predefined values for <goVersion> and <osx>
• Minor refactoring

1.0.0 (26-mar-2016)

• initial version

Taste Go in just two commands!

mvn archetype:generate -B -DarchetypeGroupId=com.igormaznitsa -DarchetypeArtifactId=mvn-golang-hello -DarchetypeVersion=2.1.0 -DgroupId=com.go.test -DartifactId=gohello -Dversion=1.0-SNAPSHOT
mvn -f ./gohello package

I very much like Maven build tool and use it very actively in my daily work so that I decided to develop a plug-in to provide way to automate build of GoLang applications with maven.
The Plug-in wraps standard GoLang commands and even can download and unpack GoLang SDK from the main site.

On start the plug-in makes below steps:

• analyzing the current platform to generate needed distributive name (it can be defined directly through properties)
• check that such distributive already cached
  • if the distributive is not cached, then it will load the distributive list from the GoLang server and will find *.zip or *.tar.gz file and download and unpack that into cache folder of the plug-in
• execute needed go lang tool bin/go with defined command, the source folder will be set as current folder
• since 2.1.0 version, all folders of the project which are visible for maven (source folder, test folder, resource folders and test resource folders) will be zipped and saved as artifact into local maven repository as a file with mvn-golang extension

The Plug-in doesn't work with standard maven dependencies andf they must be defined through task of the plugin, the example of easiest case of dependencies is

<execution>
   <id>default-get</id>
   <configuration>
     <packages>
       <package>github.com/gizak/termui</package>
       <package>github.com/kataras/iris</package>
     </packages>
   </configuration>
</execution> 

it will be executed as bin/go get github.com/gizak/termui github.com/kataras/iris

If you want work with specific branch then use below snipet

<execution>
  <id>default-get</id>
  <configuration>
    <buildFlags>
    <flag>-u</flag>
    </buildFlags>
    <packages>
      <package>github.com/gizak/termui</package>
    </packages>
    <branch>v2</branch>
  </configuration>
</execution>

if you want to have several dependencies with different tag and branch then take a look at the snipet below

<execution>
  <id>dependency1</id>
  <goals>
    <goal>get</goal>
  </goals>
  <configuration>
    <packages>
      <package>github.com/some/framework</package>
    </packages>
    <tag>1.0.1<tag>
  </configuration>
</execution>
<execution>
  <id>dependency2</id>
  <goals>
    <goal>get</goal>
  </goals>
  <configuration>
    <packages>
      <package>github.com/some/another</package>
    </packages>
    <branch>v2</branch>
  </configuration>
</execution>

sometime GIT can produce cache errors and in the case you can try to turn on auto-fix of such errors with <autofixGitCache>true</autofixGitCache> flag.
Since 2.1.0 version it is possible to select branch and tag for dependencies, it works with Git and potentially work with Hg and Svn.

The Wrapper during install phase collects all sources ande resources from folders defined in maven configuration and pack them as zip file, then the archive is saved in the local maven repository as new artifact with extension mvn-golang.
If you want to save generated artifact then you can use snippet below

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-install-plugin</artifactId>
    <version>2.5.2</version>
    <executions>
      <execution>
        <id>save-result-as-artifact</id>
        <phase>install</phase>
        <goals>
          <goal>install-file</goal>
        </goals>
        <configuration>
          <file>${basedir}${file.separator}bin${file.separator}${project.build.finalName}</file>
          <groupId>${project.groupId}</groupId>
          <artifactId>${project.artifactId}-result</artifactId>
          <version>${project.version}</version>
          <!-- NB! packaging allows to select extension  -->
          <packaging>bin</packaging>
        </configuration>
      </execution>
    </executions>
</plugin>

if you want disable creation of artifact then you can use snippet

 <execution>
  <id>default-mvninstall</id>
  <phase>none</phase>
</execution>

About configuration parameters, you can read at the wiki page.

The Wrapper just wraps calls to Go tool and recognize the exit code, if call of go test is non-zero then build will be failed, it doesn't make any analysing of test reports!
Sometime it is useful to use GoConvey tool for testing, in the case use snippet below to add dependency and make testing verbose

<execution>
  <id>default-get</id>
  <configuration>
    <buildFlags>
      <flag>-u</flag>
    </buildFlags>
    <packages>
      <package>github.com/smartystreets/goconvey</package>
    </packages>
  </configuration>
</execution>
<execution>
  <id>default-test</id>
  <configuration>
    <buildFlags>
      <flag>-v</flag>
    </buildFlags>
  </configuration>
</execution>                    

• Simple "Hello world!" console application.
• Simple console application with embedded text resource prepared with the go-bindata utility.
• Simple console application with termui library (it needs installation of some native libraries!).
• NES emulator.
• Android application with gomobile.