apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXMALHAR-2546) Mocking dependencies should ideally be in the maven parent instead of individual modules
Date Thu, 05 Oct 2017 20:18:01 GMT

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

ASF GitHub Bot commented on APEXMALHAR-2546:
--------------------------------------------

tweise closed pull request #672: APEXMALHAR-2546.Mocking-dependencies-should-be-part-of-parent-pom
URL: https://github.com/apache/apex-malhar/pull/672
 
 
   
 
----------------------------------------------------------------
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:
users@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)

Mime
View raw message