Cannot reload tests from Atlassian Plugin Test Console

Valentin Borlea January 25, 2015

Hi all,

I want to be able to update unit/integration tests within JIRA Plugin Test Console. The problem is that when I do a change in a test and I scan for tests, JIRA returns an error:

fastdeverror.PNG

 

Here is the plugin configuration:

<build>
        <plugins>
            <plugin>
                <groupId>com.atlassian.maven.plugins</groupId>
                <artifactId>maven-jira-plugin</artifactId>
                <version>${amps.version}</version>
                <extensions>true</extensions>
                <configuration>
                    <productVersion>${jira.version}</productVersion>
                    <productDataVersion>${jira.version}</productDataVersion>
                    <useFastdevCli>false</useFastdevCli>
                    <testGroups>
                        <testGroup>
                            <id>jira-integration</id>
                            <productIds>
                                <productId>jira</productId>
                            </productIds>
                            <includes>
                                <include>it/**/*Test.java</include>
                            </includes>
                        </testGroup>
                    </testGroups>
                </configuration>
            </plugin>
            <plugin> 
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
                <version>3.2</version>
                <configuration>
                    <source>1.6</source>
                    <target>1.6</target>
                </configuration>
            </plugin>
        </plugins>
    </build>
 
    <properties>
        <jira.version>6.3.12</jira.version>
        <amps.version>5.0.3</amps.version>
        <plugin.testrunner.version>1.1.5</plugin.testrunner.version>
        <!-- TestKit version 5.x for JIRA 5.x, 6.x for JIRA 6.x -->
        <testkit.version>5.2.26</testkit.version>
    </properties>

It looks like JIRA uses the amps.version for maven-compiler-plugin. That's why I specified a version for it, but it is not taken into account. (at first I didn't specified a version and the groupid for maven-compiler-plugin, but it didn't work too).

Does anyone have a idea how to solve this problem?

4 answers

0 votes
dbu November 10, 2015

I got the same error. This seems to be a bug in the SDK. I fixed it duplicating the maven-compiler-plugin folder for my version (3.3) in my local Maven repo (~/.m2/repository/org/apache/maven/plugins/maven-compiler-plugin/) under folder name of my AMPS version. Then I replaced all occurrences of the maven-compiler-plugin version 3.3 with my AMPS version. In short: I created a 5.0.13 version of the maven-compiler-plugin in my local Maven repo. It's not nice, but it works. If you update your AMPS, you have to repeat these steps with the new AMPS version.

0 votes
Mateusz Szafarz May 18, 2015

I have exactly the same error. Can anyone point me what can cause this error? Does anyone use this functionality with success? It's very annoying to have to restart jira after every change made in tests.

0 votes
Valentin Borlea January 28, 2015

I tried that and it's not working. It seems that fastDev uses <amps.version>5.0.3</amps.version> for maven-compiler-plugin and this version does not exist.

0 votes
Alexej Geldt
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 26, 2015

why? <useFastdevCli>false</useFastdevCli> remove that line and try again.

Suggest an answer

Log in or Sign up to answer