[ 
https://issues.apache.org/jira/browse/ACCUMULO-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Billie Rinaldi updated ACCUMULO-1354:
-------------------------------------

    Attachment: ACCUMULO-1354.patch

I got clean package to succeed for hadoop 1.0.4 and 2.0.3-alpha without 
profiles in the attached patch.  I had to comment out a couple of tests from 
test/.../ShellServerTest because they used org.apache.hadoop.tools.DistCp which 
has moved from the hadoop-tools artifact to the hadoop-distcp artifact.  (I did 
not include the test removal in this initial patch so we can decide what we 
want to do.)  Just one incompatibility to work out is great, I was expecting 
worse.

I was trying to remember why we didn't do this in the first place, and I 
suspect it was because we still had hope of 0.20 compatibility at that point.
                
> Pom simplification with hadoop-client
> -------------------------------------
>
>                 Key: ACCUMULO-1354
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1354
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: dist
>            Reporter: John Vines
>            Assignee: John Vines
>         Attachments: ACCUMULO-1354.patch
>
>
> We currently utilize build profiles to hit hadoop 1 vs. hadoop 2 vs. other 
> hadoop releases. One of the big differences between the two releases is 
> hadoop-core vs. hadoop-client. However, as of hadoop 1.0.1, hadoop-client has 
> been in existance for convenience. We can significantly simplify our builds, 
> I think, by switching to only hadoop-client. This will result is only having 
> to declare a hadoop 1 profile in a few test jars (for hadoop-test and 
> hadoop-tools). All the poms will still need hadoop2 profiles, but being able 
> to remove the default build profile through a majority of the poms should 
> simplify them.
> I'm also not sure if this is something we want to do for 1.5.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to