Problem with atlas-cli compiling Groovy code

[Erik Mason]

We got our plugin to compile during atlas-run just fine with these pom settings:

<build>
  <sourceDirectory>src/main/groovy</sourceDirectory>
  <testSourceDirectory>src/test/groovy</testSourceDirectory>
  <plugins>
    <plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-compiler-plugin</artifactId>
      <version>3.2</version>
      <configuration>
        <compilerId>groovy-eclipse-compiler</compilerId>
        <source>1.7</source>
        <target>1.7</target>
      </configuration>
      <dependencies>
        <dependency>
          <groupId>org.codehaus.groovy</groupId>
          <artifactId>groovy-eclipse-batch</artifactId>
          <version>2.3.4-01</version>
        </dependency>
        <dependency>
          <groupId>org.codehaus.groovy</groupId>
          <artifactId>groovy-eclipse-compiler</artifactId>
          <version>2.9.0-01</version>
        </dependency>
      </dependencies>
    </plugin>
    <plugin>
      <groupId>org.codehaus.groovy</groupId>
      <artifactId>groovy-eclipse-compiler</artifactId>
      <version>2.7.0-01</version>
      <extensions>true</extensions>
    </plugin>
    <plugin>
      <groupId>com.atlassian.maven.plugins</groupId>
      <artifactId>maven-amps-plugin</artifactId>
      <version>${amps.version}</version>
      <extensions>true</extensions>
      <configuration>
        <productVersion>${amps.version}</productVersion>
        <allowGoogleTracking>false</allowGoogleTracking>
        <useFastdevCli>false</useFastdevCli>
      </configuration>
    </plugin>
  </plugins>
</build>

However, when we try to run atlas-cli and the "pi" command we get:

[ERROR] Unable to complete running command: pi

java.lang.RuntimeException: org.apache.maven.plugin.MojoExecutionException: Unable to execute mojo
	at org.twdata.maven.cli.commands.ExecuteGoalCommand.run(ExecuteGoalCommand.java:112)
	at org.twdata.maven.cli.commands.ExecuteGoalCommand.run(ExecuteGoalCommand.java:107)
	at org.twdata.maven.cli.CliShell.interpretCommand(CliShell.java:48)
	at org.twdata.maven.cli.CliShell.run(CliShell.java:29)
	at org.twdata.maven.cli.AbstractCliMojo.displayShell(AbstractCliMojo.java:174)
	at org.twdata.maven.cli.AbstractCliMojo.access$000(AbstractCliMojo.java:22)
	at org.twdata.maven.cli.AbstractCliMojo$1.run(AbstractCliMojo.java:123)
Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to execute mojo
	at org.shaded.mojoexecutor.MojoExecutor.executeMojoImpl(MojoExecutor.java:174)
	at org.shaded.mojoexecutor.MojoExecutor$ExecutionEnvironmentM3.executeMojo(MojoExecutor.java:476)
	at org.shaded.mojoexecutor.MojoExecutor.executeMojo(MojoExecutor.java:75)
	at org.twdata.maven.cli.MojoCall.run(MojoCall.java:33)
	at org.twdata.maven.cli.commands.ExecuteGoalCommand.runMojo(ExecuteGoalCommand.java:126)
	at org.twdata.maven.cli.commands.ExecuteGoalCommand.run(ExecuteGoalCommand.java:105)
	... 6 more
Caused by: org.apache.maven.plugin.MojoExecutionException: No such compiler 'groovy-eclipse-compiler'.
	at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:427)
	at org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
	at org.shaded.mojoexecutor.MojoExecutor.executeMojoImpl(MojoExecutor.java:172)
	... 11 more

Sorry for the wall of text, but we can't seem to find a solution to make this work. We'd like to use atlas-cli so that we don't have to restart our local JIRA every time we make a Groovy/XML change. Any help would be greatly appreciated.

[Midori · Accepted solution]

You should make a try by running atlas-install-plugin (or it may be atlassin-plugin-install, I don't have a SDK here).

It will not be as fast as atlas-cli, because Maven is rather slow to start, but a full initialization is ran, your plugin is installed and no need to restart JIRA. 

It is not 100% solution, but it is not the first time when running commands with atlas-cli is not equivalent with running those commands one by one with atlas-mvn. 

[Erik Mason]

This worked! I'm so happy that we could finally figure out a way to do this, with your help @Ferenc Kiss [Midori]. We've only been working on our plugin for three weeks, but having to restart the local JIRA application so often was very painful. This ended up being our final update script (cc: @Jamie Echlin [Adaptavist]): atlas-install-plugin -Datlassian.pdk.server.home=jira -p 2990 --server localhost --context-path /jira After you run that, all you have to do is refresh a screen and it will show that a plugin is being reloaded.

[JamieA]

that did work for me too, the issue was trying to avoid slow maven startup time. However it wasn't nearly as bad with maven 3 compared to 2.

[JamieA]

Doesn't help, but I too was never able to get atlas-cli working with groovy-eclipse compiler. In the end I migrated to gradle, so never solved that problem.

[Erik Mason]

Sorry, I should mention that we're using 5.0.13 of the SDK, but I also tried it on 6.0.1 with the same result.