You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Bruno Mahé (JIRA)" <ji...@apache.org> on 2012/06/27 00:34:42 UTC
[jira] [Created] (BIGTOP-655) We build hadoop 2.0.0-alpha but
mahout points to 2.0.0-SNAPSHOT
Bruno Mahé 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é
Priority: Blocker
Fix For: 0.4.0
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
[jira] [Updated] (BIGTOP-655) We build hadoop 2.0.0-alpha but
mahout points to 2.0.0-SNAPSHOT
Posted by "Bruno Mahé (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (BIGTOP-655) We build hadoop 2.0.0-alpha but
mahout points to 2.0.0-SNAPSHOT
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402519#comment-13402519 ]
Roman Shaposhnik commented on BIGTOP-655:
-----------------------------------------
+1
> 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
[jira] [Closed] (BIGTOP-655) We build hadoop 2.0.0-alpha but mahout
points to 2.0.0-SNAPSHOT
Posted by "Bruno Mahé (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruno Mahé closed BIGTOP-655.
-----------------------------
> 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é
> Assignee: 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