[
https://issues.apache.org/jira/browse/OPENJPA-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678315#action_12678315
]
Donald Woods commented on OPENJPA-949:
--------------------------------------
Agree that allowing an override from a property in settings.xml in addition to
the cmdline would be a good change. If no one beats me to it, I'll work on
creating an updated patch after I finish working on OPENJPA-878.
> 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
> Fix For: 2.0.0
>
> 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.
