[
https://issues.apache.org/jira/browse/ACCUMULO-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13703944#comment-13703944
]
Josh Elser commented on ACCUMULO-1537:
--------------------------------------
bq. Josh Elser and .. I think you mean "mvn verify".
Nope, meant what I wrote which was essentially the same thing you elaborated
upon. For day-to-day development, install is most likely not the lifecycle a
user should be invoking.
bq. If this causes a build that takes 30+ minutes, I am pretty sure this isn't
a great first-time developer experience (or a not-first-time developer
experience). Might I suggest putting a few choice integration tests on the main
"mvn clean install" pathway and hide the rest behind a profile?
I don't think we should be going against Maven conventions just to make a
random first-timer have a "better" experience. In my opinion, if anything, we
should go out of our way to encourage proper usage of Maven for the task at
hand, which, again, is likely not `mvn install` as releases are available
through maven-central (and wouldn't require a user to install the artifacts
into their local repository).
> convert auto tests to integration tests, where possible for continuous
> integration
> ----------------------------------------------------------------------------------
>
> Key: ACCUMULO-1537
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1537
> Project: Accumulo
> Issue Type: Sub-task
> Components: test
> Reporter: Eric Newton
> Assignee: Eric Newton
> Fix For: 1.6.0
>
>
> It would be good to run the functional tests on the build server. Now that
> we have MiniAccumuloCluster, most of these tests can be convert to simple
> java Integration Tests.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
