[jira] [Commented] (METRON-811) Enforce Maven Version in Top Level POM

["Tomas Zezula (JIRA)" <ji...@apache.org>]

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

Tomas Zezula commented on METRON-811:
-------------------------------------

Hi [~dlyle],
Can you please assign this issue to me? I don't seem to have permissions to do it myself. Cheers

Tomas

> Enforce Maven Version in Top Level POM
> --------------------------------------
>
>                 Key: METRON-811
>                 URL: https://issues.apache.org/jira/browse/METRON-811
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: David M. Lyle
>              Labels: newbie
>             Fix For: 0.3.2
>
>
> METRON-793 revealed a latent issue with one of my computers. That computer had been running Maven 3.2.3 without issue. Last night after a pull from master, Metron would no longer build. ( 
> metron-storm-kafka couldn't find Guava)
> At first, I suspected it was a change to the Reactor plugin ordering, but that wasn't the case. At this time, I haven't identified the cause, but upgrading to Maven 3.3.9 allowed the build to complete. 
> If we add the enforcer plugin to the top level pom and enforce the Maven version, we can give an actionable error message and avoid this kind of weirdness. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)