Peter Davis edited a comment on Improvement JENKINS-13188

I'd also love to see this fixed. In the meantime, I adapted Will Cain's workaround. I don't really like the JUnits to run during the "package" phase.

Assuming there is a maven-surefire-plugin declared in your parent pom:

<plugin>
	<groupId>com.github.searls</groupId>
	<artifactId>jasmine-maven-plugin</artifactId>
	<version>1.2.0.0</version>
...
</plugin>
<plugin>
	<artifactId>maven-surefire-plugin</artifactId>
	<executions>
		<execution>
			<!-- Ensure surefire runs after Jasmine.
			   - https://issues.jenkins-ci.org/browse/JENKINS-13188
			   - Maven plugins are run in the order specified in pom.xml, with inherited plugins first.
			   - So we must redefine the "test" goal's execution to be after Jasmine. -->
			<id>surefire-test</id>
			<phase>test</phase>
			<goals>
				<goal>test</goal>
			</goals>
			<configuration>
				<skipTests>${skipTests}</skipTests>
			</configuration>
		</execution>
	</executions>
	<configuration>
		<!-- Disable the default maven-surefire-plugin execution from parent pom. -->
		<skipTests>true</skipTests>
	</configuration>
</plugin>

Edit: just pointing out you can do pretty much the same thing with maven-failsafe-plugin:integration-test as maven-surefire-plugin:test if needed.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to