You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Jeremy Hughes (JIRA)" <ji...@apache.org> on 2010/04/20 13:01:51 UTC
[jira] Created: (ARIES-295) Move the maven-release-plugin
configuration to skip tests from module poms to parent pom
Move the maven-release-plugin configuration to skip tests from module poms to parent pom
----------------------------------------------------------------------------------------
Key: ARIES-295
URL: https://issues.apache.org/jira/browse/ARIES-295
Project: Aries
Issue Type: Sub-task
Reporter: Jeremy Hughes
Assignee: Jeremy Hughes
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ARIES-295) Move the maven-release-plugin
configuration to skip tests from module poms to parent pom
Posted by "Jeremy Hughes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859792#action_12859792 ]
Jeremy Hughes commented on ARIES-295:
-------------------------------------
What I was trying to do was push the maven-release-plugin specific config of:
<configuration>
<arguments>-Papache-release -DskipTests=true</arguments>
</configuration>
down to the blueprint-itests module where it belongs. I wanted just the blueprint-itests tests to not run when mvn release:prepare. However, it's not that simple. It turns out that when running mvn release:prepare at the blueprint module level, when it gets to running the blueprint-itests sub module, the maven-release-plugin doesn't get configured with the config in the sub module pom. It's not surprising really.
Since -DskipTests is the only way I've figured out to prevent the surefire plugin from causing this error while running under the release plugin:
[INFO] [INFO] [surefire:test {execution: default-test}]
[INFO] [INFO] Surefire report directory: C:\cygwin\home\hughesj\oss\aries\branches\0.1-incubating-RC1\blueprint\blueprint-itests\target\surefire-reports
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [ERROR] BUILD FAILURE
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] There are test failures.
[INFO]
[INFO] Please refer to C:\cygwin\home\hughesj\oss\aries\branches\0.1-incubating-RC1\blueprint\blueprint-itests\target\surefire-reports for the individual test results.
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] For more information, run Maven with the -e switch
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Total time: 1 minute 31 seconds
[INFO] [INFO] Finished at: Thu Apr 22 12:07:14 BST 2010
[INFO] [INFO] Final Memory: 99M/155M
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Maven execution failed, exit code: '1'
(even the latest v2.5 of the surefire plugin fails in this way where no surefire-reports directory is created).
So I'm going to fall back to configuring the maven-release-plugin with -DskipTests. Since there are quite a lot of itest modules causing this problem, I'm going to push the <arguments> modification into parent/pom.xml
> Move the maven-release-plugin configuration to skip tests from module poms to parent pom
> ----------------------------------------------------------------------------------------
>
> Key: ARIES-295
> URL: https://issues.apache.org/jira/browse/ARIES-295
> Project: Aries
> Issue Type: Sub-task
> Reporter: Jeremy Hughes
> Assignee: Jeremy Hughes
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.