ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From subin <subin.apa...@gmail.com>
Subject Re: Restructuring ambari-shell directory structure
Date Wed, 18 Jun 2014 16:43:36 GMT
Agreed.
my bad, my patch is pending for some time.
so let me get back on that.

-Subin


On Tue, Jun 17, 2014 at 7:19 PM, Siddharth Wagle <swagle@hortonworks.com>
wrote:

> Hi Subin,
>
> That does sound like a good idea but I think we should restructure once
> there are contributions towards a python shell. I guess what I am saying we
> should have a shell before restructuring, what do you think?
>
> The patch can include the restructure, +1 for that.
>
> Best Regards,
> Sid
>
>
> On Tue, Jun 17, 2014 at 6:36 PM, subin <subin.apache@gmail.com> wrote:
>
> > Hi Ambari devs,
> >
> > Our current project directory structure for Ambari shell is:
> >
> > ambari-shell/
> >
> > I propose that we restructure it as follows:
> >
> > ambari-shell/python-shell
> > ambari-shell/groovy-shell
> >
> > So that we can support python shell based on python client
> > https://issues.apache.org/jira/browse/AMBARI-6176
> > What do you all think?
> >
> >
> > Thanks
> > Subin
> >
> > On Fri, May 23, 2014 at 2:56 AM, Yusaku Sako <yusaku@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.
> > >
> >
> >
> >
> > --
> > ~Subin
> >
>
> --
> 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.
>



-- 
~Subin

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message