You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by Yusaku Sako <yu...@hortonworks.com> on 2014/05/22 23:26:00 UTC
Restructuring ambari-client directory structure
Hi Ambari devs,
There's new development [1] on Ambari Groovy client and Ambari Shell
that utilizes that client.
Our current project directory structure is:
ambari-client/<python-client>
In [1], the proposal is to restructure it as follows:
ambari-client/python-client
ambari-client/groovy-client
I think this is a good approach, as there could be other clients in
the future as well.
What do you all think?
[1] https://issues.apache.org/jira/browse/AMBARI-5482
Yusaku
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Restructuring ambari-client directory structure
Posted by Yusaku Sako <yu...@hortonworks.com>.
Thanks for your feedback, everyone.
We'll go ahead with the proposed directory structure.
Yusaku
On Tue, May 27, 2014 at 7:45 AM, Scott Creeley <sc...@redhat.com> wrote:
> +1
>
> ----- Original Message -----
> From: "Erin Boyd" <eb...@redhat.com>
> To: dev@ambari.apache.org
> Sent: Friday, May 23, 2014 11:41:00 AM
> Subject: Re: Restructuring ambari-client directory structure
>
> +1;
>
> ----- Original Message -----
> From: "Sumit Mohanty" <sm...@hortonworks.com>
> To: dev@ambari.apache.org
> Sent: Thursday, May 22, 2014 5:44:04 PM
> Subject: Re: Restructuring ambari-client directory structure
>
> +1
>
>
> On Thu, May 22, 2014 at 3:03 PM, Yusaku Sako <yu...@hortonworks.com> wrote:
>
>> Sid, I thought about that also.
>> I personally like the explicit names python-client, groovy-client
>> better vs just python, groovy, because it suggests whoever is looking
>> at the code that these are standalone client modules by themselves,
>> rather than subcomponents that make up the client.
>>
>> Yusaku
>>
>> On Thu, May 22, 2014 at 2:42 PM, Siddharth Wagle <sw...@hortonworks.com>
>> wrote:
>> > ambari-client/python
>> > ambari-client/groovy
>> >
>> > +1
>> >
>> >
>> > On Thu, May 22, 2014 at 2:29 PM, Jeff Sposetti <je...@hortonworks.com>
>> wrote:
>> >
>> >> +1
>> >>
>> >>
>> >> On Thu, May 22, 2014 at 5:26 PM, Yusaku Sako <yu...@hortonworks.com>
>> >> wrote:
>> >>
>> >> > Hi Ambari devs,
>> >> >
>> >> > There's new development [1] on Ambari Groovy client and Ambari Shell
>> >> > that utilizes that client.
>> >> > Our current project directory structure is:
>> >> >
>> >> > ambari-client/<python-client>
>> >> >
>> >> > In [1], the proposal is to restructure it as follows:
>> >> >
>> >> > ambari-client/python-client
>> >> > ambari-client/groovy-client
>> >> >
>> >> > I think this is a good approach, as there could be other clients in
>> >> > the future as well.
>> >> > What do you all think?
>> >> >
>> >> > [1] https://issues.apache.org/jira/browse/AMBARI-5482
>> >> >
>> >> > Yusaku
>> >> >
>> >> > --
>> >> > CONFIDENTIALITY NOTICE
>> >> > NOTICE: This message is intended for the use of the individual or
>> entity
>> >> to
>> >> > which it is addressed and may contain information that is
>> confidential,
>> >> > privileged and exempt from disclosure under applicable law. If the
>> reader
>> >> > of this message is not the intended recipient, you are hereby notified
>> >> that
>> >> > any printing, copying, dissemination, distribution, disclosure or
>> >> > forwarding of this communication is strictly prohibited. If you have
>> >> > received this communication in error, please contact the sender
>> >> immediately
>> >> > and delete it from your system. Thank You.
>> >> >
>> >>
>> >> --
>> >> CONFIDENTIALITY NOTICE
>> >> NOTICE: This message is intended for the use of the individual or
>> entity to
>> >> which it is addressed and may contain information that is confidential,
>> >> privileged and exempt from disclosure under applicable law. If the
>> reader
>> >> of this message is not the intended recipient, you are hereby notified
>> that
>> >> any printing, copying, dissemination, distribution, disclosure or
>> >> forwarding of this communication is strictly prohibited. If you have
>> >> received this communication in error, please contact the sender
>> immediately
>> >> and delete it from your system. Thank You.
>> >>
>> >
>> > --
>> > CONFIDENTIALITY NOTICE
>> > NOTICE: This message is intended for the use of the individual or entity
>> to
>> > which it is addressed and may contain information that is confidential,
>> > privileged and exempt from disclosure under applicable law. If the reader
>> > of this message is not the intended recipient, you are hereby notified
>> that
>> > any printing, copying, dissemination, distribution, disclosure or
>> > forwarding of this communication is strictly prohibited. If you have
>> > received this communication in error, please contact the sender
>> immediately
>> > and delete it from your system. Thank You.
>>
>> --
>> CONFIDENTIALITY NOTICE
>> NOTICE: This message is intended for the use of the individual or entity to
>> which it is addressed and may contain information that is confidential,
>> privileged and exempt from disclosure under applicable law. If the reader
>> of this message is not the intended recipient, you are hereby notified that
>> any printing, copying, dissemination, distribution, disclosure or
>> forwarding of this communication is strictly prohibited. If you have
>> received this communication in error, please contact the sender immediately
>> and delete it from your system. Thank You.
>>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Restructuring ambari-client directory structure
Posted by Scott Creeley <sc...@redhat.com>.
+1
----- Original Message -----
From: "Erin Boyd" <eb...@redhat.com>
To: dev@ambari.apache.org
Sent: Friday, May 23, 2014 11:41:00 AM
Subject: Re: Restructuring ambari-client directory structure
+1;
----- Original Message -----
From: "Sumit Mohanty" <sm...@hortonworks.com>
To: dev@ambari.apache.org
Sent: Thursday, May 22, 2014 5:44:04 PM
Subject: Re: Restructuring ambari-client directory structure
+1
On Thu, May 22, 2014 at 3:03 PM, Yusaku Sako <yu...@hortonworks.com> wrote:
> Sid, I thought about that also.
> I personally like the explicit names python-client, groovy-client
> better vs just python, groovy, because it suggests whoever is looking
> at the code that these are standalone client modules by themselves,
> rather than subcomponents that make up the client.
>
> Yusaku
>
> On Thu, May 22, 2014 at 2:42 PM, Siddharth Wagle <sw...@hortonworks.com>
> wrote:
> > ambari-client/python
> > ambari-client/groovy
> >
> > +1
> >
> >
> > On Thu, May 22, 2014 at 2:29 PM, Jeff Sposetti <je...@hortonworks.com>
> wrote:
> >
> >> +1
> >>
> >>
> >> On Thu, May 22, 2014 at 5:26 PM, Yusaku Sako <yu...@hortonworks.com>
> >> wrote:
> >>
> >> > Hi Ambari devs,
> >> >
> >> > There's new development [1] on Ambari Groovy client and Ambari Shell
> >> > that utilizes that client.
> >> > Our current project directory structure is:
> >> >
> >> > ambari-client/<python-client>
> >> >
> >> > In [1], the proposal is to restructure it as follows:
> >> >
> >> > ambari-client/python-client
> >> > ambari-client/groovy-client
> >> >
> >> > I think this is a good approach, as there could be other clients in
> >> > the future as well.
> >> > What do you all think?
> >> >
> >> > [1] https://issues.apache.org/jira/browse/AMBARI-5482
> >> >
> >> > Yusaku
> >> >
> >> > --
> >> > CONFIDENTIALITY NOTICE
> >> > NOTICE: This message is intended for the use of the individual or
> entity
> >> to
> >> > which it is addressed and may contain information that is
> confidential,
> >> > privileged and exempt from disclosure under applicable law. If the
> reader
> >> > of this message is not the intended recipient, you are hereby notified
> >> that
> >> > any printing, copying, dissemination, distribution, disclosure or
> >> > forwarding of this communication is strictly prohibited. If you have
> >> > received this communication in error, please contact the sender
> >> immediately
> >> > and delete it from your system. Thank You.
> >> >
> >>
> >> --
> >> CONFIDENTIALITY NOTICE
> >> NOTICE: This message is intended for the use of the individual or
> entity to
> >> which it is addressed and may contain information that is confidential,
> >> privileged and exempt from disclosure under applicable law. If the
> reader
> >> of this message is not the intended recipient, you are hereby notified
> that
> >> any printing, copying, dissemination, distribution, disclosure or
> >> forwarding of this communication is strictly prohibited. If you have
> >> received this communication in error, please contact the sender
> immediately
> >> and delete it from your system. Thank You.
> >>
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entity
> to
> > which it is addressed and may contain information that is confidential,
> > privileged and exempt from disclosure under applicable law. If the reader
> > of this message is not the intended recipient, you are hereby notified
> that
> > any printing, copying, dissemination, distribution, disclosure or
> > forwarding of this communication is strictly prohibited. If you have
> > received this communication in error, please contact the sender
> immediately
> > and delete it from your system. Thank You.
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Restructuring ambari-client directory structure
Posted by Erin Boyd <eb...@redhat.com>.
+1;
----- Original Message -----
From: "Sumit Mohanty" <sm...@hortonworks.com>
To: dev@ambari.apache.org
Sent: Thursday, May 22, 2014 5:44:04 PM
Subject: Re: Restructuring ambari-client directory structure
+1
On Thu, May 22, 2014 at 3:03 PM, Yusaku Sako <yu...@hortonworks.com> wrote:
> Sid, I thought about that also.
> I personally like the explicit names python-client, groovy-client
> better vs just python, groovy, because it suggests whoever is looking
> at the code that these are standalone client modules by themselves,
> rather than subcomponents that make up the client.
>
> Yusaku
>
> On Thu, May 22, 2014 at 2:42 PM, Siddharth Wagle <sw...@hortonworks.com>
> wrote:
> > ambari-client/python
> > ambari-client/groovy
> >
> > +1
> >
> >
> > On Thu, May 22, 2014 at 2:29 PM, Jeff Sposetti <je...@hortonworks.com>
> wrote:
> >
> >> +1
> >>
> >>
> >> On Thu, May 22, 2014 at 5:26 PM, Yusaku Sako <yu...@hortonworks.com>
> >> wrote:
> >>
> >> > Hi Ambari devs,
> >> >
> >> > There's new development [1] on Ambari Groovy client and Ambari Shell
> >> > that utilizes that client.
> >> > Our current project directory structure is:
> >> >
> >> > ambari-client/<python-client>
> >> >
> >> > In [1], the proposal is to restructure it as follows:
> >> >
> >> > ambari-client/python-client
> >> > ambari-client/groovy-client
> >> >
> >> > I think this is a good approach, as there could be other clients in
> >> > the future as well.
> >> > What do you all think?
> >> >
> >> > [1] https://issues.apache.org/jira/browse/AMBARI-5482
> >> >
> >> > Yusaku
> >> >
> >> > --
> >> > CONFIDENTIALITY NOTICE
> >> > NOTICE: This message is intended for the use of the individual or
> entity
> >> to
> >> > which it is addressed and may contain information that is
> confidential,
> >> > privileged and exempt from disclosure under applicable law. If the
> reader
> >> > of this message is not the intended recipient, you are hereby notified
> >> that
> >> > any printing, copying, dissemination, distribution, disclosure or
> >> > forwarding of this communication is strictly prohibited. If you have
> >> > received this communication in error, please contact the sender
> >> immediately
> >> > and delete it from your system. Thank You.
> >> >
> >>
> >> --
> >> CONFIDENTIALITY NOTICE
> >> NOTICE: This message is intended for the use of the individual or
> entity to
> >> which it is addressed and may contain information that is confidential,
> >> privileged and exempt from disclosure under applicable law. If the
> reader
> >> of this message is not the intended recipient, you are hereby notified
> that
> >> any printing, copying, dissemination, distribution, disclosure or
> >> forwarding of this communication is strictly prohibited. If you have
> >> received this communication in error, please contact the sender
> immediately
> >> and delete it from your system. Thank You.
> >>
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entity
> to
> > which it is addressed and may contain information that is confidential,
> > privileged and exempt from disclosure under applicable law. If the reader
> > of this message is not the intended recipient, you are hereby notified
> that
> > any printing, copying, dissemination, distribution, disclosure or
> > forwarding of this communication is strictly prohibited. If you have
> > received this communication in error, please contact the sender
> immediately
> > and delete it from your system. Thank You.
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Restructuring ambari-client directory structure
Posted by Sumit Mohanty <sm...@hortonworks.com>.
+1
On Thu, May 22, 2014 at 3:03 PM, Yusaku Sako <yu...@hortonworks.com> wrote:
> Sid, I thought about that also.
> I personally like the explicit names python-client, groovy-client
> better vs just python, groovy, because it suggests whoever is looking
> at the code that these are standalone client modules by themselves,
> rather than subcomponents that make up the client.
>
> Yusaku
>
> On Thu, May 22, 2014 at 2:42 PM, Siddharth Wagle <sw...@hortonworks.com>
> wrote:
> > ambari-client/python
> > ambari-client/groovy
> >
> > +1
> >
> >
> > On Thu, May 22, 2014 at 2:29 PM, Jeff Sposetti <je...@hortonworks.com>
> wrote:
> >
> >> +1
> >>
> >>
> >> On Thu, May 22, 2014 at 5:26 PM, Yusaku Sako <yu...@hortonworks.com>
> >> wrote:
> >>
> >> > Hi Ambari devs,
> >> >
> >> > There's new development [1] on Ambari Groovy client and Ambari Shell
> >> > that utilizes that client.
> >> > Our current project directory structure is:
> >> >
> >> > ambari-client/<python-client>
> >> >
> >> > In [1], the proposal is to restructure it as follows:
> >> >
> >> > ambari-client/python-client
> >> > ambari-client/groovy-client
> >> >
> >> > I think this is a good approach, as there could be other clients in
> >> > the future as well.
> >> > What do you all think?
> >> >
> >> > [1] https://issues.apache.org/jira/browse/AMBARI-5482
> >> >
> >> > Yusaku
> >> >
> >> > --
> >> > CONFIDENTIALITY NOTICE
> >> > NOTICE: This message is intended for the use of the individual or
> entity
> >> to
> >> > which it is addressed and may contain information that is
> confidential,
> >> > privileged and exempt from disclosure under applicable law. If the
> reader
> >> > of this message is not the intended recipient, you are hereby notified
> >> that
> >> > any printing, copying, dissemination, distribution, disclosure or
> >> > forwarding of this communication is strictly prohibited. If you have
> >> > received this communication in error, please contact the sender
> >> immediately
> >> > and delete it from your system. Thank You.
> >> >
> >>
> >> --
> >> CONFIDENTIALITY NOTICE
> >> NOTICE: This message is intended for the use of the individual or
> entity to
> >> which it is addressed and may contain information that is confidential,
> >> privileged and exempt from disclosure under applicable law. If the
> reader
> >> of this message is not the intended recipient, you are hereby notified
> that
> >> any printing, copying, dissemination, distribution, disclosure or
> >> forwarding of this communication is strictly prohibited. If you have
> >> received this communication in error, please contact the sender
> immediately
> >> and delete it from your system. Thank You.
> >>
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entity
> to
> > which it is addressed and may contain information that is confidential,
> > privileged and exempt from disclosure under applicable law. If the reader
> > of this message is not the intended recipient, you are hereby notified
> that
> > any printing, copying, dissemination, distribution, disclosure or
> > forwarding of this communication is strictly prohibited. If you have
> > received this communication in error, please contact the sender
> immediately
> > and delete it from your system. Thank You.
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Restructuring ambari-client directory structure
Posted by Yusaku Sako <yu...@hortonworks.com>.
Sid, I thought about that also.
I personally like the explicit names python-client, groovy-client
better vs just python, groovy, because it suggests whoever is looking
at the code that these are standalone client modules by themselves,
rather than subcomponents that make up the client.
Yusaku
On Thu, May 22, 2014 at 2:42 PM, Siddharth Wagle <sw...@hortonworks.com> wrote:
> ambari-client/python
> ambari-client/groovy
>
> +1
>
>
> On Thu, May 22, 2014 at 2:29 PM, Jeff Sposetti <je...@hortonworks.com> wrote:
>
>> +1
>>
>>
>> On Thu, May 22, 2014 at 5:26 PM, Yusaku Sako <yu...@hortonworks.com>
>> wrote:
>>
>> > Hi Ambari devs,
>> >
>> > There's new development [1] on Ambari Groovy client and Ambari Shell
>> > that utilizes that client.
>> > Our current project directory structure is:
>> >
>> > ambari-client/<python-client>
>> >
>> > In [1], the proposal is to restructure it as follows:
>> >
>> > ambari-client/python-client
>> > ambari-client/groovy-client
>> >
>> > I think this is a good approach, as there could be other clients in
>> > the future as well.
>> > What do you all think?
>> >
>> > [1] https://issues.apache.org/jira/browse/AMBARI-5482
>> >
>> > Yusaku
>> >
>> > --
>> > CONFIDENTIALITY NOTICE
>> > NOTICE: This message is intended for the use of the individual or entity
>> to
>> > which it is addressed and may contain information that is confidential,
>> > privileged and exempt from disclosure under applicable law. If the reader
>> > of this message is not the intended recipient, you are hereby notified
>> that
>> > any printing, copying, dissemination, distribution, disclosure or
>> > forwarding of this communication is strictly prohibited. If you have
>> > received this communication in error, please contact the sender
>> immediately
>> > and delete it from your system. Thank You.
>> >
>>
>> --
>> CONFIDENTIALITY NOTICE
>> NOTICE: This message is intended for the use of the individual or entity to
>> which it is addressed and may contain information that is confidential,
>> privileged and exempt from disclosure under applicable law. If the reader
>> of this message is not the intended recipient, you are hereby notified that
>> any printing, copying, dissemination, distribution, disclosure or
>> forwarding of this communication is strictly prohibited. If you have
>> received this communication in error, please contact the sender immediately
>> and delete it from your system. Thank You.
>>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Restructuring ambari-client directory structure
Posted by Siddharth Wagle <sw...@hortonworks.com>.
ambari-client/python
ambari-client/groovy
+1
On Thu, May 22, 2014 at 2:29 PM, Jeff Sposetti <je...@hortonworks.com> wrote:
> +1
>
>
> On Thu, May 22, 2014 at 5:26 PM, Yusaku Sako <yu...@hortonworks.com>
> wrote:
>
> > Hi Ambari devs,
> >
> > There's new development [1] on Ambari Groovy client and Ambari Shell
> > that utilizes that client.
> > Our current project directory structure is:
> >
> > ambari-client/<python-client>
> >
> > In [1], the proposal is to restructure it as follows:
> >
> > ambari-client/python-client
> > ambari-client/groovy-client
> >
> > I think this is a good approach, as there could be other clients in
> > the future as well.
> > What do you all think?
> >
> > [1] https://issues.apache.org/jira/browse/AMBARI-5482
> >
> > Yusaku
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entity
> to
> > which it is addressed and may contain information that is confidential,
> > privileged and exempt from disclosure under applicable law. If the reader
> > of this message is not the intended recipient, you are hereby notified
> that
> > any printing, copying, dissemination, distribution, disclosure or
> > forwarding of this communication is strictly prohibited. If you have
> > received this communication in error, please contact the sender
> immediately
> > and delete it from your system. Thank You.
> >
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Restructuring ambari-client directory structure
Posted by Jeff Sposetti <je...@hortonworks.com>.
+1
On Thu, May 22, 2014 at 5:26 PM, Yusaku Sako <yu...@hortonworks.com> wrote:
> Hi Ambari devs,
>
> There's new development [1] on Ambari Groovy client and Ambari Shell
> that utilizes that client.
> Our current project directory structure is:
>
> ambari-client/<python-client>
>
> In [1], the proposal is to restructure it as follows:
>
> ambari-client/python-client
> ambari-client/groovy-client
>
> I think this is a good approach, as there could be other clients in
> the future as well.
> What do you all think?
>
> [1] https://issues.apache.org/jira/browse/AMBARI-5482
>
> Yusaku
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.