How do I configure atlas-run to start up JIRA in other tomcat version?

Jannik Luyten
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.
July 30, 2013

Hi guys

When I run atlas-run, my local JIRA starts up in tomcat7. When I run atlas-run --container tomcat6x, JIRA is started up in tomcat6x. Because I don't want to include this parameter every time (and so our CI runs the plugin in tomcat6 aswell), I want to add this configuration to my POM.xml. How can I do this? Here is the relevant part of my pom:

<build>
		<plugins>
			<plugin>
				<groupId>com.atlassian.maven.plugins</groupId>
				<artifactId>maven-jira-plugin</artifactId>
				<version>${amps.version}</version>
				<extensions>true</extensions>
				<configuration>
					<server>localhost</server>
					<productVersion>${jira.version}</productVersion>
					<productDataVersion>${jira.data.version}</productDataVersion>
					<productDataPath>${basedir}/src/test/resources/generated-test-resources.zip</productDataPath>
					<log4jProperties>src/test/resources/log4j.properties</log4jProperties>
				</configuration>
			</plugin>
			<plugin>
				<artifactId>maven-compiler-plugin</artifactId>
				<configuration>
					<source>1.6</source>
					<target>1.6</target>
				</configuration>
			</plugin>
		</plugins>
	</build>

I tried adding <container>tomcat6x</container> to my build.plugins.plugin.configuration, but this did not work.

I am using the Atlassian-SDK 4.2.3.

Thank you.

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

5 votes
Answer accepted
Tom Moors
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.
July 30, 2013

The maven-jira-plugin is part of AMPS. According to this documentation, the required argument is called containerId. Can you try adding this one to your configuration section and see if it works?

Jannik Luyten
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.
July 31, 2013

Thanks Tom! Works like a charm!

...

&lt;configuration&gt;
					&lt;server&gt;localhost&lt;/server&gt;
					&lt;productVersion&gt;${jira.version}&lt;/productVersion&gt;
					&lt;productDataVersion&gt;${jira.data.version}&lt;/productDataVersion&gt;
					&lt;productDataPath&gt;${basedir}/src/test/resources/generated-test-resources.zip&lt;/productDataPath&gt;
					&lt;log4jProperties&gt;src/test/resources/log4j.properties&lt;/log4jProperties&gt;
					&lt;containerId&gt;tomcat6x&lt;/containerId&gt;
				&lt;/configuration&gt;

...

TAGS
AUG Leaders

Atlassian Community Events