[
https://issues.apache.org/jira/browse/ACCUMULO-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15472502#comment-15472502
]
Josh Elser commented on ACCUMULO-4443:
--------------------------------------
Missed your reply, [~ctubbsii]. Sorry about that.
The docs are definitely clear on how to enable/disable each category, and, I
would guess, that people can reason about how to chain these together.
I still think forcing users to write the long command out by hand is
unnecessarily difficult. {{mvn verify -Psunny}} is great because it's so
concise, but I have a feeling that you and I still disagree on this point given
the profiles that I originally added were removed.
> Make performance test category usage consistent with other categories
> ---------------------------------------------------------------------
>
> Key: ACCUMULO-4443
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4443
> Project: Accumulo
> Issue Type: Sub-task
> Components: test
> Affects Versions: 1.8.0
> Reporter: Christopher Tubbs
> Assignee: Christopher Tubbs
> Priority: Minor
> Fix For: 1.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, performance tests categories are excluded by default in 1.8+
> branches.
> This is unexpected when trying to do a full build.
> It is also documented as being triggered differently than other test
> categories, even though it is using the same basic categorization method.
> For consistency, we should include all tests by default, and update the
> performance tests documentation to match how the other test categories are
> documented and used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
