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

Sean Busbey commented on FLUME-3379:
------------------------------------

Several dependencies are still old enough that they or their transitive poms 
refer to HTTP repo urls that get blocked by current versions of maven. We 
should add the appropriate HTTPS repos where needed.

> Include maven repos needed for transitive dependencies
> ------------------------------------------------------
>
>                 Key: FLUME-3379
>                 URL: https://issues.apache.org/jira/browse/FLUME-3379
>             Project: Flume
>          Issue Type: Bug
>    Affects Versions: 1.9.0
>            Reporter: Luca Toscano
>            Assignee: Sean Busbey
>            Priority: Major
>
> Hi everybody,
> I have recently worked on a Bigtop 
> [issue|https://issues.apache.org/jira/browse/BIGTOP-3440] related to flume. 
> The main issue was related to the flume-ng-morphline-solr-sink, since there 
> were dependency problems while building.
> The first issue was related to the Twitter Maven repository, that gets fixed 
> when applying this 
> [commit|https://github.com/apache/flume/commit/9e0bc5bf4865673e6989ba887d27f468991c1e27]
>  on top of 1.9 sources. But then another problem pops up, this time with the 
> rome package (see [this comment 
> |https://issues.apache.org/jira/browse/BIGTOP-3440?focusedCommentId=17227827&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17227827]
>  for more info).
> For the moment the issue was solved in bigtop removing 
> flume-ng-morphline-solr-sink from the related pom.xml, but it would be great 
> to be able to re-enable it eventually (if possible). Let me know if you have 
> ideas :)
> Thanks in advance!



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to