Chris Hennick created SUREFIRE-1414:
---------------------------------------
Summary: Configuration still considered "same" after Proguard has
rewritten the jar
Key: SUREFIRE-1414
URL: https://issues.apache.org/jira/browse/SUREFIRE-1414
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 2.14.1
Environment: Ubuntu 14.04.3
Reporter: Chris Hennick
I run my unit tests for a library twice: once to generate a coverage report,
then again after running Proguard to verify the Proguard settings. When I try
to do the latter after the former in the same script, I get "Skipping execution
of surefire because it has already been run for this configuration". This could
be fixed by including checksums of the jar's class files in the identity
checksum of the configuration.
My combined test script, including a workaround, is:
{code:bash}
#!/bin/sh
cd betterrandom
# Coverage test
mvn clean install jacoco:prepare-agent test jacoco:report -e
STATUS=$?
if [ "$STATUS" = 0 ]; then
if [ "$TRAVIS" = "true" ]; then
mvn coveralls:report
fi
rm .surefire-* # Avoid false detection of redundancy
# Post-Proguard test (verifies Proguard settings)
mvn package proguard:proguard install test
STATUS=$?
fi
cd ..
exit "$STATUS"
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
