On Wed, Jan 21, 2015 at 8:56 PM, Ayesha Dissanayaka aye...@wso2.com wrote:
Hi Prabath et. al,
These database scripts[2] and some of the files in [3] are bound to both
org.wso2.es.feature and org.wso2.store.feature.
Basically, both these features serve the same purpose, i.e. expose ES apps
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
Hi Prabath et. al,
These database scripts[2] and some of the files in [3] are bound to both
org.wso2.es.feature and org.wso2.store.feature.
Basically, both these features serve the same purpose, i.e. expose ES apps
[4].
org.wso2.es.feature exports ES apps with a prefix(ex: es-store,
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
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.
-
+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:
