Hi Ayesha, On Tue, Jan 20, 2015 at 8:28 PM, Ayesha Dissanayaka <aye...@wso2.com> wrote:
> Hi all, > > I have completed basic repo separation discussed above along with commit > history of the code base.(https://github.com/ayshsandu/carbon-store). I > still need to include some necessary resource directories to this repo for > it to be fully functional. > > There are 3 folders listed under product-es/disribution/src [1] > > - *product-es/disribution/src/dbscripts/storage* [2] > - contains ES storage related dbscripts and exported from > "org.wso2.es.feature" and "org.wso2.store.feature". > - In our repo separation we should move this to *carbon-store* repo. > - I suggest this can be located in below directory structure in > *carbon-store* repo, and update export paths in > "org.wso2.es.feature" and "org.wso2.store.feature". > - *carbon-store/features/resources/dbscripts* > - Otherwise where should this be located? > > If these database scripts are bound to some specific feature, why don't we bundle them up with that particular feature instead of having them copied into a location common to all features (i.e. *carbon-store/features/resources/dbscripts*)? Cheers, Prabath > > - *product-es/distribution/src/repository *[3] > - This folder is also exported from "org.wso2.es.feature" and > "org.wso2.store.feature". > - There are several folders in this location and as I see most of > them are ES prodouct specific. > - I suggest that we keep product specific stuff in > *product-es/disribution/src/repository* as it is and move other > necessary files to *carbon-store/features/resources/repository *location > and update export paths in "org.wso2.es.feature" and > "org.wso2.store.feature". > - But I am having hard-time on exactly identifying files in > *product-es/disribution/src/repository > *location what are ES-product related and what should be exported > from features. Please, advice on this separation. > > > - *product-es/distribution/src/assembly* > - This contains ES product specific files and will be kept in > product-es as it is. > > Please suggest your concerns on above points. > > [1] > https://github.com/wso2/product-es/tree/master/modules/distribution/src > [2] > https://github.com/wso2/product-es/tree/master/modules/distribution/src/dbscripts/storage > [3] > https://github.com/wso2/product-es/tree/master/modules/distribution/src/repository > > Thanks! > - Ayesha > > On Mon, Jan 19, 2015 at 8:10 PM, Sagara Gunathunga <sag...@wso2.com> > wrote: > >> +1 >> >> Thanks ! >> >> On Mon, Jan 19, 2015 at 7:33 PM, Ayesha Dissanayaka <aye...@wso2.com> >> wrote: >> >>> Hi, >>> >>> Please refer the repo structure mentioned above as below. >>> >>> >>> >>> Sorry about missing it fist-place. >>> >>> Thanks! >>> -Ayesha >>> >>> On Mon, Jan 19, 2015 at 7:24 PM, Ayesha Dissanayaka <aye...@wso2.com> >>> wrote: >>> >>>> Hi all, >>>> >>>> I have started creating carbon-store GitHub repo as suggested in the >>>> mail thread "Creating carbon-store GitHub repo". >>>> >>>> Along with *components* and *features* we will be moving *apps* and >>>> *jaggery-modules >>>> *into this repo. Finally the main repo structure would be like below. >>>> >>>> >>>> >>>> >>>> - *apps**[1] *will contain jaggeryapps we ship with ES pack and >>>> reused by other products. >>>> - *jaggery-modules* [2] are reusable and required by *apps* >>>> >>>> After completing this repo separation, other products which are using >>>> ES stuffs will be able to integrate all the ES related components via this >>>> *carbon-store >>>> *repo and will not be depend on *product-es*. >>>> >>>> What are the other inputs on this? >>>> How have APIM has exposed jaggery related components in this case? >>>> >>>> [1] https://github.com/wso2/product-es/tree/master/modules/apps >>>> [2] >>>> https://github.com/wso2/product-es/tree/master/modules/jaggery-modules/ >>>> >>>> Thanks! >>>> - Ayesha >>>> -- >>>> *Ayesha Dissanayaka* >>>> Software Engineer, >>>> WSO2, Inc : http://wso2.com >>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> >>>> 20, Palmgrove Avenue, Colombo 3 >>>> E-Mail: aye...@wso2.com <ayshsa...@gmail.com> >>>> >>> >>> >>> >>> -- >>> *Ayesha Dissanayaka* >>> Software Engineer, >>> WSO2, Inc : http://wso2.com >>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> >>> 20, Palmgrove Avenue, Colombo 3 >>> E-Mail: aye...@wso2.com <ayshsa...@gmail.com> >>> >> >> >> >> -- >> Sagara Gunathunga >> >> Senior Technical Lead; WSO2, Inc.; http://wso2.com >> V.P Apache Web Services; http://ws.apache.org/ >> Linkedin; http://www.linkedin.com/in/ssagara >> Blog ; http://ssagara.blogspot.com >> >> > > > -- > *Ayesha Dissanayaka* > Software Engineer, > WSO2, Inc : http://wso2.com > <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> > 20, Palmgrove Avenue, Colombo 3 > E-Mail: aye...@wso2.com <ayshsa...@gmail.com> > -- Prabath Abeysekara Associate Technical Lead, Data TG. WSO2 Inc. Email: praba...@wso2.com Mobile: +94774171471
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
