accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Havanki (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2920) test-accumulo-maven-plugin profile should heed skipTests too
Date Thu, 26 Jun 2014 22:41:25 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14045283#comment-14045283
] 

Bill Havanki commented on ACCUMULO-2920:
----------------------------------------

I've found that (with Maven 2.0.10 and higher) you can deactivate the profile on the command
line:

{noformat}
mvn -P '!test-accumulo-maven-plugin' verify
{noformat}

Single quotes are needed in bash to avoid shell interpretation. This can't be set in MAVEN_OPTS,
so it must be typed out for each build.

> test-accumulo-maven-plugin profile should heed skipTests too
> ------------------------------------------------------------
>
>                 Key: ACCUMULO-2920
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2920
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: build, maven-plugin
>    Affects Versions: 1.6.0
>            Reporter: Bill Havanki
>            Assignee: Christopher Tubbs
>            Priority: Minor
>              Labels: maven
>
> The POM for the maven-plugin module provides a "test-accumulo-maven-plugin" profile for
running integration tests on the plugin. The profile activates only when the skipITs property,
the same property referenced by the failsafe plugin, is not set.
> It should also require that the skipTests property be unset. The skipTests property already
controls whether tests are run by the surefire _or_ failsafe plugins, and having the same
behavior here would be beneficial. Today, to run {{mvn install}} without any tests, you must
say {{mvn -DskipTests -DskipITs install}}. It should be enough to say {{mvn -DskipTests install}}.
> The problem is that it doesn't appear that Maven supports this level of logic in its
profile activation syntax, at least not in any straightforward manner.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message