openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Commented: (OPENJPA-949) Allow override of Surefire test excludes from cmdline
Date Mon, 02 Mar 2009 21:54:56 GMT


David Jencks commented on OPENJPA-949:

I haven't actually looked at either patch so I might be repeating one or the other but my
initial approach would be to have all tests run by default (at least those not annotated to
not run) and have a profile with the exclusion set from a property.  Then you can set the
property on the command line or in ~/.m2/settings.xml or probably in a project specific xml
file (not sure about how to do that).  So to use the externally set exclusions you'd use the

> Allow override of Surefire test excludes from cmdline
> -----------------------------------------------------
>                 Key: OPENJPA-949
>                 URL:
>             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.

View raw message