Mailing-List: contact bigtop-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bigtop-dev@incubator.apache.org
Date: Tue, 26 Jun 2012 22:34:42 +0000 (UTC)
From: =?utf-8?Q?Bruno_Mah=C3=A9_=28JIRA=29?= <jira@apache.org>
To: bigtop-dev@incubator.apache.org
Message-ID: <1438054806.58826.1340750084043.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Created] (BIGTOP-655) We build hadoop 2.0.0-alpha but
 mahout points to 2.0.0-SNAPSHOT
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Bruno Mah=C3=A9 created BIGTOP-655:
---------------------------------

             Summary: 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=C3=A9
            Priority: Blocker
             Fix For: 0.4.0


While looking at the RC bits, I noticed we force some dependencies to be po=
inted 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 project=
s have also the habit of deleting their SNAPSHOT artifacts when they move o=
n onto other versions, which would mean that a release of Apache Bigtop (in=
cubating) 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 administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira