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

[email protected] commented on FLUME-1049:
------------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4460/
-----------------------------------------------------------

(Updated 2012-03-23 01:32:38.339964)


Review request for Flume.


Changes
-------

updated patch to use 1.0.1 instead of 1.0.0 which has some compatibility issues.


Summary
-------

There is no reason to have different build profiles for hadoop-0.20.205.0 and 
hadoop-1.0.0, which is just a renamed hadoop-0.20.205.1.

This patch removes the 20.205 profile in favor of 1.0.0 as the new default.


This addresses bug FLUME-1049.
    https://issues.apache.org/jira/browse/FLUME-1049


Diffs (updated)
-----

  pom.xml fc13691 

Diff: https://reviews.apache.org/r/4460/diff


Testing
-------

mvn clean package works like a charm.


Thanks,

Mike


                
> Use hadoop-1.0.0 as basis for default Flume build instead of 0.20.205
> ---------------------------------------------------------------------
>
>                 Key: FLUME-1049
>                 URL: https://issues.apache.org/jira/browse/FLUME-1049
>             Project: Flume
>          Issue Type: Improvement
>            Reporter: Mike Percy
>            Assignee: Mike Percy
>            Priority: Minor
>         Attachments: FLUME-1049-1.patch
>
>
> Simple maven cleanup task to not depend on hadoop-0.20.205.0 for the default 
> build. We should just use hadoop-1.0.0 which is the same thing as 
> hadoop-0.20.205.1
> This way we only have two profiles: one for 1.0 and the other for 0.23, which 
> are significantly different enough from a packaging & test perspective to 
> warrant their own build profiles.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to