You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Donald Woods (JIRA)" <ji...@apache.org> on 2010/11/02 22:21:05 UTC
[jira] Closed: (OPENJPA-949) Allow override of Surefire test
excludes from cmdline
[ https://issues.apache.org/jira/browse/OPENJPA-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods closed OPENJPA-949.
--------------------------------
Resolution: Won't Fix
not enough support for this
> Allow override of Surefire test excludes from cmdline
> -----------------------------------------------------
>
> Key: OPENJPA-949
> URL: https://issues.apache.org/jira/browse/OPENJPA-949
> Project: OpenJPA
> Issue Type: Improvement
> Components: build / infrastructure
> Reporter: Donald Woods
> Assignee: Donald Woods
> Priority: Minor
> Attachments: OPENJPA-949-trunk-20090302.patch
>
>
> Allow users to provide their own Surefire excludes list through an external file.
> This can be accomplished by using the gmaven-plugin and some Groovy code.
> The default set of excludes will still be provided and used by default in the builds, but will be moved to src/test/resources/excludes.xml.
> Users can provide their own version of excludes file by:
> mvn -DsurefireExcludesFile=<filename>
> where <filename> could be a local file like:
> -DsurefireExcludesFile=/tmp/excludes.xml
> or from a network share like:
> -DsurefireExcludesFile=/mnt/public/openjpa-persistence-jdbc/excludes.xml
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.