[
https://issues.apache.org/jira/browse/APEXMALHAR-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16192764#comment-16192764
]
ASF GitHub Bot commented on APEXMALHAR-2546:
--------------------------------------------
ananthc opened a new pull request #672:
APEXMALHAR-2546.Mocking-dependencies-should-be-part-of-parent-pom
URL: https://github.com/apache/apex-malhar/pull/672
@tweise - Here is a summary of this change:
- Moved the power mock module to the parent.
- Bumped the version of mock to 2.x versions. Please let me know if this
change requires a community discussion. The build did not fail on the local
machine.
Could you please review or assign this to someone who can help me with the
review ?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Mocking dependencies should ideally be in the maven parent instead of
> individual modules
> -----------------------------------------------------------------------------------------
>
> Key: APEXMALHAR-2546
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2546
> Project: Apache Apex Malhar
> Issue Type: Improvement
> Reporter: Ananth
> Assignee: Ananth
> Priority: Minor
>
> There are a couple of Mocking dependencies that were introduced in the Kudu
> implementation but the right fit for those mocking libraries is the top level
> parent.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
