[
https://issues.apache.org/jira/browse/NIFI-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16427692#comment-16427692
]
Otto Fowler commented on NIFI-5020:
-----------------------------------
[https://maven.apache.org/plugins-archives/maven-surefire-plugin-2.12.4/examples/skipping-test.html]
Seems to imply that skipTests is preferred. It is what I personally do, and
what we do on the METRON project.
Is there a compelling reason to support maven.test.skip? If so can you explain
a bit?
> Consider treating test resources/utilities as a main module
> -----------------------------------------------------------
>
> Key: NIFI-5020
> URL: https://issues.apache.org/jira/browse/NIFI-5020
> Project: Apache NiFi
> Issue Type: Task
> Components: Tools and Build
> Reporter: Aldrin Piri
> Priority: Major
>
> NIFI-5013 took care of consolidating duplicate resources by making a test-jar
> available. However, as reported on the mailing list, when building with
> maven.test.skip (this is distinct from skipTests), the test artifact will not
> be built and preclude projects that depend upon it (even in the scenario when
> all tests are skipped) from building correctly.
> Source mailing list thread:
> https://lists.apache.org/thread.html/ff4e44d1c40519959fbff579bad587a458833c703b5162248bf8812b@%3Cdev.nifi.apache.org%3E
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
