Hi, I've restructured the repo considering what we discussed here. I've also added a distribution for VM related files.
Final directory structure as follows; ├── common │ ├── configurator │ │ ├── live-test │ │ │ ├── src │ │ ├── src │ │ │ ├── assembly │ │ │ └── main │ ├── docker │ │ ├── base-image │ │ │ ├── packages │ │ │ └── scripts │ │ └── scripts │ ├── plugins │ └── vm │ ├── assembly │ ├── init-scripts │ │ ├── ec2 │ │ ├── gce │ │ ├── openstack │ │ └── vcloud │ ├── puppet │ │ ├── manifests │ │ └── modules ├── wso2am │ ├── 1.9.0 │ │ ├── assembly │ │ ├── docker │ │ │ ├── packages │ │ │ ├── plugins │ │ │ └── scripts │ │ ├── plugins │ │ ├── samples │ │ │ ├── application-policies │ │ │ ├── applications │ │ │ ├── autoscaling-policies │ │ │ ├── cartridge-groups │ │ │ ├── cartridges │ │ │ ├── deployment-policies │ │ │ ├── kubernetes-clusters │ │ │ ├── network-partitions │ │ │ └── template-modules │ │ └── template-module │ │ ├── files │ │ ├── src │ │ └── templates ├── wso2as │ ├── 5.2.1 │ │ ├── assembly │ │ ├── docker │ │ │ ├── packages │ │ │ ├── plugins │ │ │ └── scripts │ │ ├── plugins │ │ ├── samples │ │ │ ├── application-policies │ │ │ ├── applications │ │ │ ├── autoscaling-policies │ │ │ ├── cartridge-groups │ │ │ ├── cartridges │ │ │ ├── deployment-policies │ │ │ ├── kubernetes-clusters │ │ │ ├── network-partitions │ │ │ ├── signups │ │ │ └── template-modules │ │ └── template-module │ │ ├── files │ │ ├── src │ │ └── templates ├── wso2esb │ ├── 4.8.1 │ │ ├── assembly │ │ ├── docker │ │ │ ├── packages │ │ │ ├── plugins │ │ │ └── scripts │ │ ├── plugins │ │ ├── samples │ │ │ ├── application-policies │ │ │ ├── applications │ │ │ ├── autoscaling-policies │ │ │ ├── cartridge-groups │ │ │ ├── cartridges │ │ │ ├── deployment-policies │ │ │ ├── kubernetes-clusters │ │ │ ├── network-partitions │ │ │ ├── signups │ │ │ └── template-modules │ │ │ ├── archive-tmp │ │ │ └── maven-shared-archive-resources │ │ └── template-module │ │ ├── files │ │ ├── src │ │ └── templates └── wso2is ├── 5.0.0 │ ├── assembly │ ├── docker │ │ ├── packages │ │ ├── plugins │ │ └── scripts │ ├── plugins │ ├── samples │ │ ├── application-policies │ │ ├── applications │ │ ├── autoscaling-policies │ │ ├── cartridge-groups │ │ ├── cartridges │ │ ├── deployment-policies │ │ ├── kubernetes-clusters │ │ ├── network-partitions │ │ ├── signups │ │ └── template-modules │ └── template-module │ ├── files │ ├── src │ └── templates On Sun, Oct 4, 2015 at 10:04 PM, Imesh Gunaratne <im...@wso2.com> wrote: > On Fri, Oct 2, 2015 at 2:25 PM, Thanuja Uruththirakodeeswaran < > thanu...@wso2.com> wrote: > >> Hi All, >> >> We have folder for base-image and inside that we have a folder called >> 'docker' for docker base image. In the VM scenario, we are using >> init-scripts to create the vm base image. So what if we move the >> init-scripts folder inside /common/base-image/vm/ path? >> > > Yes, a good point! May be we can do the necessary changes. > > Thanks > > On Fri, Oct 2, 2015 at 2:25 PM, Thanuja Uruththirakodeeswaran < > thanu...@wso2.com> wrote: > >> Hi All, >> >> We have folder for base-image and inside that we have a folder called >> 'docker' for docker base image. In the VM scenario, we are using >> init-scripts to create the vm base image. So what if we move the >> init-scripts folder inside /common/base-image/vm/ path? >> >> ├── common >> │ ├── base-image >> │ │ └── docker >> │ ├── common-plugins >> │ │ ├── wso2-cleanup-handler.py >> │ │ └── wso2-cleanup-handler.yapsy-plugin >> │ ├── configurator >> │ │ ├── live-test >> │ │ ├── org.wso2.ppaas.cartridges.common.configurator.iml >> │ │ ├── pom.xml >> │ │ ├── README.md >> │ │ ├── src >> │ │ └── target >> │ ├── init-scripts >> │ │ ├── ec2 >> │ │ ├── gce >> │ │ ├── openstack >> │ │ ├── README.md >> │ │ └── vcloud >> >> Thanks. >> >> On Thu, Oct 1, 2015 at 6:32 PM, Reka Thirunavukkarasu <r...@wso2.com> >> wrote: >> >>> Hi Gayan >>> >>> On Thu, Oct 1, 2015 at 6:16 PM, Gayan Gunarathne <gay...@wso2.com> >>> wrote: >>> >>>> >>>> >>>> On Thu, Oct 1, 2015 at 6:06 PM, Reka Thirunavukkarasu <r...@wso2.com> >>>> wrote: >>>> >>>>> Hi >>>>> >>>>> Shall we maintain an installer as well(specially for VM cartridges) in >>>>> this repository to quickly create specific cartridges in puppet? What this >>>>> installer could do is, >>>>> >>>>> User has to provide the packs and set of values for the environment >>>>> variables. >>>>> >>>>> - Install puppet master >>>>> - Locate the relevant cartridges puppet modules >>>>> - Place the packs, template modules and plugins to right location >>>>> - Export all the user given environment variables >>>>> - Execute configurator to configure the samples >>>>> >>>>> WDYT? >>>>> >>>> >>>> Good thought reka. As our offline chat , we can plan to have two >>>> installers for ppaas and ppaas cartridges.We can have the ppaas installer >>>> to set up the ppaas related stuff while ppaas cartridge installer to set up >>>> the cartridge specific installations. >>>> >>> +1. We can check whether we can modify the stratos-installer and use it >>> as a ppaas-installer rather writing it from the scratch. >>> >>> Thanks, >>> Reka >>> >>>> >>>>> Thanks, >>>>> Reka >>>>> >>>>> On Thu, Oct 1, 2015 at 2:01 PM, Gayan Gunarathne <gay...@wso2.com> >>>>> wrote: >>>>> >>>>>> Hi Akila, >>>>>> >>>>>> Common folder has all the common stuff related to the cartridges.So >>>>>> if someone can navigate to the common folder and get the stuff shared >>>>>> among >>>>>> the cartridges. >>>>>> >>>>>> I think it is meaningful to have those common stuff at a one place, >>>>>> then someone new to this repository also have a feeling those stuff will >>>>>> be >>>>>> common for all the cartridges.Common PCA plugins and utils also we can >>>>>> have >>>>>> inside the common folder >>>>>> >>>>>> Thanks, >>>>>> Gayan >>>>>> >>>>>> On Thu, Oct 1, 2015 at 12:52 PM, Akila Ravihansa Perera < >>>>>> raviha...@wso2.com> wrote: >>>>>> >>>>>>> Hi Gayan, >>>>>>> >>>>>>> Wouldn't it be easier to navigate if we move those common folders to >>>>>>> root folder? >>>>>>> >>>>>>> We can create a common folder under /plugins/ folder to keep common >>>>>>> PCA plugins and util files. >>>>>>> >>>>>>> Just a thought...wdyt? >>>>>>> >>>>>>> Thanks. >>>>>>> >>>>>>> On Thu, Oct 1, 2015 at 10:29 AM, Gayan Gunarathne <gay...@wso2.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Adding to the Dev list >>>>>>>> >>>>>>>> >>>>>>>> On Thu, Oct 1, 2015 at 7:05 AM, Imesh Gunaratne <im...@wso2.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Shall we move this discussion to Dev? >>>>>>>>> >>>>>>>>> Thanks >>>>>>>>> >>>>>>>>> On Wed, Sep 30, 2015 at 11:02 PM, Gayan Gunarathne < >>>>>>>>> gay...@wso2.com> wrote: >>>>>>>>> >>>>>>>>>> As puppet,init-scripts,base image are common for all the >>>>>>>>>> cartridges,shall we group them under common? >>>>>>>>>> Also what about the configurator?I can see two options >>>>>>>>>> One option will be move the configurator to the private-paas >>>>>>>>>> repository and release it with the private paas.Other option will be >>>>>>>>>> we can >>>>>>>>>> do the separate release for the configurator.Seems it is better to >>>>>>>>>> have a >>>>>>>>>> separate release for the configurator. WDYT? >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> Gayan >>>>>>>>>> >>>>>>>>>> On Wed, Sep 30, 2015 at 10:44 PM, Gayan Gunarathne < >>>>>>>>>> gay...@wso2.com> wrote: >>>>>>>>>> >>>>>>>>>>> Hi, >>>>>>>>>>> >>>>>>>>>>> On Wed, Sep 30, 2015 at 9:48 PM, Akila Ravihansa Perera < >>>>>>>>>>> raviha...@wso2.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> +1 for having a simple folder structure. I think we can move >>>>>>>>>>>> the contents in /common/ folder to root folder. One can easily >>>>>>>>>>>> identify the >>>>>>>>>>>> important files available and easy to navigate as well. >>>>>>>>>>>> >>>>>>>>>>>> What should be the Maven groupId for this repo? How about >>>>>>>>>>>> "org.wso2.ppaas.cartridges" or "org.wso2.cartridges" ? >>>>>>>>>>>> >>>>>>>>>>> We can use org.wso2.ppaas.cartridges as groupId >>>>>>>>>>> >>>>>>>>>>> Thanks, >>>>>>>>>>> Gayan >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> On Wed, Sep 30, 2015 at 9:24 PM, Imesh Gunaratne < >>>>>>>>>>>> im...@wso2.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> I would like to reduce the complexity of the folder structure >>>>>>>>>>>>> and make it much simple. Shall we have some thing like below: >>>>>>>>>>>>> >>>>>>>>>>>>> private-paas-cartridges/ >>>>>>>>>>>>> |----------------------/common/ >>>>>>>>>>>>> |------/configurator/ >>>>>>>>>>>>> |------/puppet/ >>>>>>>>>>>>> |------/wso2-installer/ >>>>>>>>>>>>> |------/scripts/ >>>>>>>>>>>>> |-------/ec2/init.sh >>>>>>>>>>>>> |-------/openstack/init.sh >>>>>>>>>>>>> >>>>>>>>>>>>> |----------------------/wso2esb/4.9.0/ >>>>>>>>>>>>> |-----/template-module/ >>>>>>>>>>>>> |-----/cartridge-agent-plugins/ >>>>>>>>>>>>> |-----/application/ >>>>>>>>>>>>> |-----/docker/ >>>>>>>>>>>>> >>>>>>>>>>>>> Thanks >>>>>>>>>>>>> >>>>>>>>>>>>> On Wed, Sep 30, 2015 at 9:13 PM, Imesh Gunaratne < >>>>>>>>>>>>> im...@wso2.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> May be we can have this discussion in Dev, I cannot see any >>>>>>>>>>>>>> reason to take this private. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Thanks >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Wed, Sep 30, 2015 at 6:26 PM, Gayan Gunarathne < >>>>>>>>>>>>>> gay...@wso2.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Adding Engineering group >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> ---------- Forwarded message ---------- >>>>>>>>>>>>>>> From: Gayan Gunarathne <gay...@wso2.com> >>>>>>>>>>>>>>> Date: Wed, Sep 30, 2015 at 6:26 PM >>>>>>>>>>>>>>> Subject: [PPaaS] private-paas-cartridges repository structure >>>>>>>>>>>>>>> To: Imesh Gunaratne <im...@wso2.com>, Reka Thirunavukkarasu >>>>>>>>>>>>>>> <r...@wso2.com>, Udara Liyanage <ud...@wso2.com>, Lahiru >>>>>>>>>>>>>>> Sandaruwan <lahi...@wso2.com>, Rajkumar Rajaratnam < >>>>>>>>>>>>>>> rajkum...@wso2.com>, Sajith Kariyawasam <saj...@wso2.com>, >>>>>>>>>>>>>>> Isuru Haththotuwa <isu...@wso2.com>, Lasindu Charith < >>>>>>>>>>>>>>> lasi...@wso2.com>, Akila Ravihansa Perera < >>>>>>>>>>>>>>> raviha...@wso2.com>, Chamila De Alwis <chami...@wso2.com>, >>>>>>>>>>>>>>> Vishanth Balasubramaniam <vishan...@wso2.com>, Dinithi De >>>>>>>>>>>>>>> Silva <dinit...@wso2.com>, Anuruddha Liyanarachchi < >>>>>>>>>>>>>>> anurudd...@wso2.com>, Pubudu Gunatilaka <pubu...@wso2.com>, >>>>>>>>>>>>>>> Thanuja Uruththirakodeeswaran <thanu...@wso2.com> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi All, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Shall we have the following structure with >>>>>>>>>>>>>>> the private-paas-cartridges[1] repository >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> 1. Maintain the separate directory for each cartridge >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Suggested directory structure as following >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> . >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> ├── base-image >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> │ └── docker >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> │ └── scripts >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> │ └── start-agent.sh >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> ├── vm >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> │ ├── init-scripts >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> │ │ >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> │ ├── puppet >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> │ │ >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> │ └── README.md >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> ├── wso2_product >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> ├── Version >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> │ ├── docker >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> │ │ >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> │ ├── plugins >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> │ │ >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> │ ├── templates-modules >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> │ │ >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> │ ├── Samples >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> │ └── README.md >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Also we can move the samples to the related product folder. >>>>>>>>>>>>>>> Then as a best practice we need to have a separate sample for >>>>>>>>>>>>>>> each >>>>>>>>>>>>>>> cartridge. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Advantage of this structure is we will be able to release >>>>>>>>>>>>>>> the cartridges separately. We don't need to wait for a PPaaS >>>>>>>>>>>>>>> cartridges >>>>>>>>>>>>>>> repository release for release the cartridge. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> 2. Move the configurator to the private-paas repo or other >>>>>>>>>>>>>>> repo as the responsibility of the configurator is to generate >>>>>>>>>>>>>>> the products >>>>>>>>>>>>>>> configurations based on the template module of the cartridge. >>>>>>>>>>>>>>> So we can >>>>>>>>>>>>>>> separate it from the cartridge repository. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Please share your thoughts on this. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> [1]https://github.com/wso2/private-paas-cartridges >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>> Gayan >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Gayan Gunarathne >>>>>>>>>>>>>>> Technical Lead, WSO2 Inc. (http://wso2.com) >>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos >>>>>>>>>>>>>>> email : gay...@wso2.com | mobile : +94 775030545 >>>>>>>>>>>>>>> <%2B94%20766819985> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Gayan Gunarathne >>>>>>>>>>>>>>> Technical Lead, WSO2 Inc. (http://wso2.com) >>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos >>>>>>>>>>>>>>> email : gay...@wso2.com | mobile : +94 775030545 >>>>>>>>>>>>>>> <%2B94%20766819985> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> You received this message because you are subscribed to the >>>>>>>>>>>>>>> Google Groups "WSO2 Engineering Group" group. >>>>>>>>>>>>>>> To unsubscribe from this group and stop receiving emails >>>>>>>>>>>>>>> from it, send an email to >>>>>>>>>>>>>>> engineering-group+unsubscr...@wso2.com. >>>>>>>>>>>>>>> For more options, visit >>>>>>>>>>>>>>> https://groups.google.com/a/wso2.com/d/optout. >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> *Imesh Gunaratne* >>>>>>>>>>>>>> Senior Technical Lead >>>>>>>>>>>>>> WSO2 Inc: http://wso2.com >>>>>>>>>>>>>> T: +94 11 214 5345 M: +94 77 374 2057 >>>>>>>>>>>>>> W: http://imesh.gunaratne.org >>>>>>>>>>>>>> Lean . Enterprise . Middleware >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> *Imesh Gunaratne* >>>>>>>>>>>>> Senior Technical Lead >>>>>>>>>>>>> WSO2 Inc: http://wso2.com >>>>>>>>>>>>> T: +94 11 214 5345 M: +94 77 374 2057 >>>>>>>>>>>>> W: http://imesh.gunaratne.org >>>>>>>>>>>>> Lean . Enterprise . Middleware >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> You received this message because you are subscribed to the >>>>>>>>>>>>> Google Groups "WSO2 Engineering Group" group. >>>>>>>>>>>>> To unsubscribe from this group and stop receiving emails from >>>>>>>>>>>>> it, send an email to engineering-group+unsubscr...@wso2.com. >>>>>>>>>>>>> For more options, visit >>>>>>>>>>>>> https://groups.google.com/a/wso2.com/d/optout. >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Akila Ravihansa Perera >>>>>>>>>>>> WSO2 Inc.; http://wso2.com/ >>>>>>>>>>>> >>>>>>>>>>>> Blog: http://ravihansa3000.blogspot.com >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> >>>>>>>>>>> Gayan Gunarathne >>>>>>>>>>> Technical Lead, WSO2 Inc. (http://wso2.com) >>>>>>>>>>> Committer & PMC Member, Apache Stratos >>>>>>>>>>> email : gay...@wso2.com | mobile : +94 775030545 >>>>>>>>>>> <%2B94%20766819985> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> >>>>>>>>>> Gayan Gunarathne >>>>>>>>>> Technical Lead, WSO2 Inc. (http://wso2.com) >>>>>>>>>> Committer & PMC Member, Apache Stratos >>>>>>>>>> email : gay...@wso2.com | mobile : +94 775030545 >>>>>>>>>> <%2B94%20766819985> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> *Imesh Gunaratne* >>>>>>>>> Senior Technical Lead >>>>>>>>> WSO2 Inc: http://wso2.com >>>>>>>>> T: +94 11 214 5345 M: +94 77 374 2057 >>>>>>>>> W: http://imesh.gunaratne.org >>>>>>>>> Lean . Enterprise . Middleware >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> Gayan Gunarathne >>>>>>>> Technical Lead, WSO2 Inc. (http://wso2.com) >>>>>>>> Committer & PMC Member, Apache Stratos >>>>>>>> email : gay...@wso2.com | mobile : +94 775030545 >>>>>>>> <%2B94%20766819985> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Akila Ravihansa Perera >>>>>>> WSO2 Inc.; http://wso2.com/ >>>>>>> >>>>>>> Blog: http://ravihansa3000.blogspot.com >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> Gayan Gunarathne >>>>>> Technical Lead, WSO2 Inc. (http://wso2.com) >>>>>> Committer & PMC Member, Apache Stratos >>>>>> email : gay...@wso2.com | mobile : +94 775030545 <%2B94%20766819985> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Reka Thirunavukkarasu >>>>> Senior Software Engineer, >>>>> WSO2, Inc.:http://wso2.com, >>>>> Mobile: +94776442007 >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> Gayan Gunarathne >>>> Technical Lead, WSO2 Inc. (http://wso2.com) >>>> Committer & PMC Member, Apache Stratos >>>> email : gay...@wso2.com | mobile : +94 775030545 <%2B94%20766819985> >>>> >>>> >>>> >>> >>> >>> >>> -- >>> Reka Thirunavukkarasu >>> Senior Software Engineer, >>> WSO2, Inc.:http://wso2.com, >>> Mobile: +94776442007 >>> >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Thanuja Uruththirakodeeswaran >> Software Engineer >> WSO2 Inc.;http://wso2.com >> lean.enterprise.middleware >> >> mobile: +94 774363167 >> >> _______________________________________________ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Imesh Gunaratne* > Senior Technical Lead > WSO2 Inc: http://wso2.com > T: +94 11 214 5345 M: +94 77 374 2057 > W: http://imesh.gunaratne.org > Lean . Enterprise . Middleware > > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Akila Ravihansa Perera WSO2 Inc.; http://wso2.com/ Blog: http://ravihansa3000.blogspot.com
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev