Kelven can chime in here but my understanding is that we used the client stub libraries that VmWare generated, hence there's a problem with licensing. I don't see why there would be a problem if we actually went against the published wsdl themselves.
--Alex > -----Original Message----- > From: Gavin Lee [mailto:gavin....@gmail.com] > Sent: Wednesday, December 26, 2012 7:34 AM > To: cloudstack-dev@incubator.apache.org > Subject: Re: Mistakenly push the nonoss public, now reverted > > Is it a hack method? > +1 for non-oss converting if possible. > Keep things simple is important and attractive. > > On Wed, Dec 26, 2012 at 10:52 PM, Alex Huang <alex.hu...@citrix.com> > wrote: > > I would like to see how we can move the non-oss components into oss. > For example, my understanding is that for vmware, if we went against their > web services apis and generated that ourselves, it wouldn't need to be in > non-oss. > > > > We should file bugs against each component in non-oss and see if anyone > can help in converting them. > > > > --Alex > > > >> -----Original Message----- > >> From: Gavin Lee [mailto:gavin....@gmail.com] > >> Sent: Wednesday, December 26, 2012 5:40 AM > >> To: cloudstack-dev@incubator.apache.org > >> Subject: Re: Mistakenly push the nonoss public, now reverted > >> > >> Hi, Nitin > >> It'll be helpful if we have a method to double confirm. Push --dry-run > >> could not help with the mistake I did. > >> For me, I learnt a lot from this mistake. > >> > >> Thanks. > >> > >> > >> > >> On Wed, Dec 26, 2012 at 8:18 PM, Nitin Mehta <nitin.me...@citrix.com> > >> wrote: > >> > Gavin - Should we put in a git hook to avoid this from happening in > future ? > >> > > >> > Thanks, > >> > -Nitin > >> > > >> > On 26-Dec-2012, at 7:43 AM, Gavin Lee wrote: > >> > > >> >> Dear all, > >> >> I made a big mistake of pushing nonoss lib into remote. > >> >> commit id: > >> >> a387fcdd7cc10b7443453fbe84afc06cf51d2902 > >> >> 20fab87108ab4e6790709d4784ce6994467d3067 > >> >> > >> >> I did a revert this morning with commit id: > >> >> 333e7c4ae69bf35fb62eafde18908ba9f674b46c > >> >> > >> >> Sorry for my mistake, I'll more careful next time of PUSH operation. > >> >> Please let me know if you still have concerns. > >> >> > >> >> Sorry again. > >> >> > >> >> -- > >> >> Gavin > >> > > >> > >> > >> > >> -- > >> Gavin > > > > -- > Gavin
