bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruno Mahé (JIRA) <j...@apache.org>
Subject [jira] [Updated] (BIGTOP-655) We build hadoop 2.0.0-alpha but mahout points to 2.0.0-SNAPSHOT
Date Tue, 26 Jun 2012 22:57:42 GMT

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

Bruno Mahé updated BIGTOP-655:
------------------------------

    Attachment: BIGTOP-655.patch

Here is a patch.
This one along with BIGTOP-656 and we should be good across all projects (I looked at all
the do-component-build)
                
> We build hadoop 2.0.0-alpha but mahout points to 2.0.0-SNAPSHOT
> ---------------------------------------------------------------
>
>                 Key: BIGTOP-655
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-655
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.4.0
>            Reporter: Bruno Mahé
>            Priority: Blocker
>             Fix For: 0.4.0
>
>         Attachments: BIGTOP-655.patch
>
>
> While looking at the RC bits, I noticed we force some dependencies to be pointed at some
SNAPSHOT versions.
> Ex: mahout is being pointed at hadoop-2.0.0-SNAPSHOT. But I haven't checked everywhere.
> Given that we are working on a release version of Apache Bigtop (incubating) that means
the build is not consistently reproducible. And Apache projects have also the habit of deleting
their SNAPSHOT artifacts when they move on onto other versions, which would mean that a release
of Apache Bigtop (incubating) may not be rebuildable at all in a month or two.

--
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

       

Mime
View raw message