Mailing-List: contact bigtop-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bigtop-dev@incubator.apache.org
Date: Sat, 10 Mar 2012 02:24:58 +0000 (UTC)
From: =?utf-8?Q?Bruno_Mah=C3=A9_=28Commented=29_=28JIRA=29?= <jira@apache.org>
To: bigtop-dev@incubator.apache.org
Message-ID: 
 <1409059662.47046.1331346298164.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1661076602.35987.1331152019038.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (BIGTOP-435) need to split hadoop subpackages
 even further for hadoop-0.23
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/BIGTOP-435?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1322=
6723#comment-13226723 ]=20

Bruno Mah=C3=A9 commented on BIGTOP-435:
-----------------------------------

Do you know if your patch fixes BIGTOP-445 ?
               =20
> need to split hadoop subpackages even further for hadoop-0.23
> -------------------------------------------------------------
>
>                 Key: BIGTOP-435
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-435
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.4.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.4.0
>
>         Attachments: BIGTOP-435.patch.txt
>
>
> Now that Hadoop 0.23 has incorporate some of the proposed changes to maki=
ng the layout flexible, we no longer need the kind of hacks on which we use=
d to rely. The proposed patch accomplishes an almost complete clean split b=
etween hadoop subpackages (treating them as independent projects) with the =
following 2 exceptions:
>   # libexec still need to be a common location (currently /usr/lib/hadoop=
/libexec)
>   # configuration files still need to be in a common location (currently =
/etc/hadoop/conf)

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