We can't create repos for such minor features. Those need to reside in existing repos. If there are dependency issues, the code has to be refactored to resolve them.
On Tue, Jul 1, 2014 at 2:28 PM, Chanika Geeganage <[email protected]> wrote: > Hi, > > Since ntask component depends on remote-task service stubs we cannot go > with the option 2. Therefore, we need to create a separate git repo for > task related components . i.e ntask and remote-task. I hope this approach > is convenient. > > Thanks > > > On Mon, Jun 30, 2014 at 1:56 PM, Chanika Geeganage <[email protected]> > wrote: > >> Hi, >> >> Currently ntask and remote-task components are in carbon-utils. The >> remote-task component is only used by Task Server as for now and the ntask >> is shipped by almost all the products. So what is the best way to maintain >> these components in git. Some suggestions are: >> >> 1. Keeping ntask and remote-task in a separate git repository. >> 2. Keeping ntask in carbon-utils and moving remote-task to the product-ts >> repository. >> >> Any thoughts regarding this? >> >> Thanks >> >> -- >> Best Regards.. >> >> Chanika Geeganage >> Software Engineer >> WSO2, Inc.; http://wso2.com >> >> > > > -- > Best Regards.. > > Chanika Geeganage > Software Engineer > WSO2, Inc.; http://wso2.com > > -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>* *email: **[email protected]* <[email protected]> * cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org> *twitter: **http://twitter.com/afkham_azeez* <http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez <http://lk.linkedin.com/in/afkhamazeez>* *Lean . Enterprise . Middleware*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
