Great help if each product team can review jarlist what we are using to take
code coverage.

Regards,
Chamara

On Thu, Mar 24, 2011 at 10:08 AM, Chamara Silva <[email protected]> wrote:

> Having separate jar list for each and every product difficult to maintain
> in future.IMHO we need to create dynamic jar list in test runtime.
>
> Regards,
> Chamara
>
>
> On Thu, Mar 24, 2011 at 7:47 AM, Thilini Ishaka <[email protected]> wrote:
>
>> Hi All,
>>
>> This is how we we can integrate Emma to find test coverage.
>>
>> Add following system properties to every test module pom files.
>>
>>                          <property>
>>                             <name>extracted.dir</name>
>>                             <value>wso2appserver-${pom.version}</value>
>>                         </property>
>>                         <property>
>>                             <name>emma.home</name>
>>                             <value>${basedir}/target/lib</value>
>>                         </property>
>>                         <property>
>>                             <name>jar.list</name>
>>
>> <value>${basedir}/../src/test/resources/jarlist.txt</value>
>>                         </property>
>>                         <property>
>>                             <name>emma.output</name>
>>                             <value>${basedir}/../target/emma</value>
>>                         </property>
>>
>> Add plugin to the test module pom.
>>
>>             <plugin>
>>                 <artifactId>maven-dependency-plugin</artifactId>
>>                 <executions>
>>                     <execution>
>>                         <phase>compile</phase>
>>                         <goals>
>>                             <goal>copy-dependencies</goal>
>>                         </goals>
>>                         <configuration>
>>
>> <outputDirectory>${project.build.directory}/lib</outputDirectory>
>>                             <includeTypes>jar</includeTypes>
>>
>> <includeArtifactIds>emma,org.wso2.carbon.integration.core</includeArtifactIds>
>>                         </configuration>
>>                     </execution>
>>                 </executions>
>>             </plugin>
>>
>>
>> Build test modules and find generated .ec, .em files and jarlist.txt, ruby
>> script, emmar.jar inside carbontmp/xxx_SNAPSHOT directory. Then generate the
>> coverage report using 'ruby gen_emma_coverage.rb report'.
>>
>> Add jarlist.txt (jarlist differs for each product) to a relevant location.
>> [we have already given it as a system property above as shown in highlighted
>> value  <value>${basedir}/../src/test/resources/jarlist.txt</value>.
>> Change the property value with respect to the jarlist location].
>>
>> Added a sample jarlist herewith for reference.
>>
>> If you do have any query pls feel free to ask.
>>
>> Thanks
>>
>> Regards,
>> Thilini
>>
>>
>>
>>
>>
>>
>>>
>> On Thu, Mar 24, 2011 at 7:10 AM, Charitha Kankanamge 
>> <[email protected]>wrote:
>>
>>> Hi RMs,
>>>
>>> Thilini has been working on getting the test coverage of few products at
>>> the moment. As Samisa mentioned, this should be done by each product team.
>>> Can all RMs look at how Emma is integrated in G-reg and start finding the
>>> test coverage of your product ASAP.
>>> Please reply to this thread with % coverage of your integration tests
>>> once you are done with the report.
>>>
>>> Regards
>>> Charitha
>>>
>>> ---------- Forwarded message ----------
>>> From: Samisa Abeysinghe <[email protected]>
>>> Date: Wed, Mar 23, 2011 at 10:03 PM
>>> Subject: Re: Extending "Release Readiness Week"
>>> To: Charitha Kankanamge <[email protected]>
>>> Cc: Senaka Fernando <[email protected]>, Prabath Abeysekera <
>>> [email protected]>, Support-Dev-Group <[email protected]>,
>>> Afkham Azeez <[email protected]>
>>>
>>>
>>>
>>>
>>> On Wed, Mar 23, 2011 at 9:49 PM, Charitha Kankanamge 
>>> <[email protected]>wrote:
>>>
>>>> Thilini has been preparing code coverage results (But she faced some
>>>> issues when getting coverage of few of the products. She will update
>>>> everyone ASAP). As I heard, G-reg coverage is ~50%
>>>>
>>>
>>> Please get from product people and get the code coverage for all products
>>> ASAP. We need to evaluate the effort put on this for the past one and half
>>> week (yes the build was not working till last Wednesday, but still)
>>>
>>>
>>>>
>>>> Regards
>>>> Charitha
>>>>
>>>>
>>>>
>>>> On Wed, Mar 23, 2011 at 8:30 PM, Samisa Abeysinghe <[email protected]>wrote:
>>>>
>>>>> Do we have code coverage results? What is the status of test automation
>>>>> for each product?
>>>>>
>>>>> We need to move on to issue fixing now. We have to absolutely freeze
>>>>> all features now.
>>>>>
>>>>>
>>>>> On Mon, Mar 21, 2011 at 9:56 PM, Senaka Fernando <[email protected]>wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Mar 21, 2011 at 8:59 PM, Samisa Abeysinghe 
>>>>>> <[email protected]>wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Mar 21, 2011 at 8:59 PM, Samisa Abeysinghe 
>>>>>>> <[email protected]>wrote:
>>>>>>>
>>>>>>>> Can we host the test results somewhere?
>>>>>>>
>>>>>>>
>>>>>>> I meant to say code coverage results.
>>>>>>>
>>>>>>
>>>>>> Yes, that should be possible, as they are in HTML format. Will work
>>>>>> with Denis et al, to get this done.
>>>>>>
>>>>>> Thanks,
>>>>>> Senaka.
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Like we have the packs in builder?
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Mar 21, 2011 at 8:30 PM, Senaka Fernando 
>>>>>>>> <[email protected]>wrote:
>>>>>>>>
>>>>>>>>> Hi Charitha,
>>>>>>>>>
>>>>>>>>> On Mon, Mar 21, 2011 at 3:11 PM, Charitha Kankanamge <
>>>>>>>>> [email protected]> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Mar 21, 2011 at 3:08 PM, Prabath Abeysekera <
>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> We've managed to implement the required tests for almost all the
>>>>>>>>>>> functionalities
>>>>>>>>>>> of DSS.
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Fantastic! Lets run Emma over DS and findout the coverage. Thanks
>>>>>>>>>> Prabath!
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> And we are currently in the middle of addressing some minor
>>>>>>>>>>> requirements
>>>>>>>>>>>  related to the subject!
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Mar 21, 2011 at 2:58 PM, Charitha Kankanamge <
>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Based on a chat with few RMs, it seems we are on track w.r.t
>>>>>>>>>>>> integration tests.
>>>>>>>>>>>> Can all RMs please reply to this thread and update the status of
>>>>>>>>>>>> your integration tests?
>>>>>>>>>>>>
>>>>>>>>>>>> Senaka/Thilini are still working on Emma integration hence we
>>>>>>>>>>>> cannot measure the coverage yet.
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>> This is complete. And, the G-Reg tests are using this. Please
>>>>>>>>> follow [1] for more information.
>>>>>>>>>
>>>>>>>>> There are few minor improvements that has to be made to this (which
>>>>>>>>> can be done later).
>>>>>>>>>
>>>>>>>>> 1. We need to get rid of the jarlist.txt file. Ideally, there
>>>>>>>>> should not be a jar list, and we should be able to instrument all 
>>>>>>>>> jars. (We
>>>>>>>>> hit a few roadblocks with some jars such as org.wso2.carbon.server and
>>>>>>>>> org.wso2.carbon.user.core and gave up the idea for now).
>>>>>>>>>
>>>>>>>>> 2. We need to replace the ruby script with some java code.
>>>>>>>>> Bottom-line is that Ruby should not be a dependency for running the 
>>>>>>>>> test
>>>>>>>>> framework.
>>>>>>>>>
>>>>>>>>> 3. Try to use the EclEmma, [2] instead of patching OSGi bundles.
>>>>>>>>>
>>>>>>>>> [1]
>>>>>>>>> https://svn.wso2.org/repos/wso2/trunk/carbon/products/greg/modules/integration/registry/registry-handler-test/pom.xml
>>>>>>>>> [2] http://www.eclemma.org/research/instrumentingosgi/index.html
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Senaka.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>> Regards
>>>>>>>>>>>> Charitha
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Sun, Mar 20, 2011 at 9:46 PM, Senaka Fernando <
>>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sun, Mar 20, 2011 at 9:34 PM, Samisa Abeysinghe <
>>>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> We have 150 L1 issues in Carbon. I hope we can complete this
>>>>>>>>>>>>>> test automation/samples cycle by Wednesday and move on to L1s.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 150 L1s is a great concern.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> +1, we cannot afford to drag this till Friday.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>> Senaka.
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Sun, Mar 20, 2011 at 7:54 AM, Afkham Azeez <[email protected]
>>>>>>>>>>>>>> > wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Sun, Mar 20, 2011 at 7:42 AM, Charitha Kankanamge <
>>>>>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Sun, Mar 20, 2011 at 7:26 AM, Samisa Abeysinghe <
>>>>>>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Charitha, can you please update on the status as of Last
>>>>>>>>>>>>>>>>> Friday?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Each team is writing tests. There are some issues with ESB
>>>>>>>>>>>>>>>> intergartion tests and Hiranya and team discussed those issues 
>>>>>>>>>>>>>>>> in carbon-dev
>>>>>>>>>>>>>>>> Also, the intermittent server-startup issue discussed in 
>>>>>>>>>>>>>>>> "Issues
>>>>>>>>>>>>>>>> with our Integration test framework" @carbon-dev is not 
>>>>>>>>>>>>>>>> resolved yet. Azeez
>>>>>>>>>>>>>>>> is also looking in to that issue, Azeez?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Everything seems OK. Isuru had fixed AppServer tests. Other
>>>>>>>>>>>>>>> issues related to relative paths have also been sorted out.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Do we have code coverage setup?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Not yet. There are some issues (issues are discussed at "Adding
>>>>>>>>>>>>>>>> emma instrumentation method to ServerUtils in 
>>>>>>>>>>>>>>>> carbon/core/integration" @
>>>>>>>>>>>>>>>> carbon-dev list) with Emma integration. Thilini is looking
>>>>>>>>>>>>>>>> in to these issues at the moment.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> What is the coverage for each product?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Wed, Mar 16, 2011 at 2:48 PM, Afkham Azeez <
>>>>>>>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Build has to work fine before EOD today. We expect
>>>>>>>>>>>>>>>>>> everybody's cooperation.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Wed, Mar 16, 2011 at 2:15 PM, Samisa Abeysinghe <
>>>>>>>>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Please make sure to evaluate code coverage for each
>>>>>>>>>>>>>>>>>>> product with tests/samples that are automated
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Wed, Mar 16, 2011 at 1:46 PM, Charitha Kankanamge <
>>>>>>>>>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Had an offline chat with Samisa. Since we are facing
>>>>>>>>>>>>>>>>>>>> build issues and people are still struggling with building 
>>>>>>>>>>>>>>>>>>>> trunk, we have to
>>>>>>>>>>>>>>>>>>>> extend the "release readiness week" until 23rd of March 
>>>>>>>>>>>>>>>>>>>> (next Wednesday).
>>>>>>>>>>>>>>>>>>>> Please make sure to focus on adding integration tests
>>>>>>>>>>>>>>>>>>>> and samples and have acceptable test coverage by 23rd.
>>>>>>>>>>>>>>>>>>>> We hope each product team in a position to start adding
>>>>>>>>>>>>>>>>>>>> the first few tests now. If you cannot proceed due to any 
>>>>>>>>>>>>>>>>>>>> issue, please let
>>>>>>>>>>>>>>>>>>>> everyone know.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Regards
>>>>>>>>>>>>>>>>>>>> Charitha
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>> Samisa...
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Samisa Abeysinghe
>>>>>>>>>>>>>>>>>>> VP Engineering
>>>>>>>>>>>>>>>>>>> WSO2 Inc.
>>>>>>>>>>>>>>>>>>> http://wso2.com
>>>>>>>>>>>>>>>>>>> http://wso2.org
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> *Afkham Azeez*
>>>>>>>>>>>>>>>>>> Senior Software Architect & Senior Manager; 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*
>>>>>>>>>>>>>>>>>> *
>>>>>>>>>>>>>>>>>> *
>>>>>>>>>>>>>>>>>> *Lean . Enterprise . Middleware*
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>  Thanks,
>>>>>>>>>>>>>>>>> Samisa...
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Samisa Abeysinghe
>>>>>>>>>>>>>>>>> VP Engineering
>>>>>>>>>>>>>>>>> WSO2 Inc.
>>>>>>>>>>>>>>>>> http://wso2.com
>>>>>>>>>>>>>>>>> http://wso2.org
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> *Afkham Azeez*
>>>>>>>>>>>>>>> Senior Software Architect & Senior Manager; 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*
>>>>>>>>>>>>>>> *
>>>>>>>>>>>>>>> *
>>>>>>>>>>>>>>> *Lean . Enterprise . Middleware*
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>> Samisa...
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Samisa Abeysinghe
>>>>>>>>>>>>>> VP Engineering
>>>>>>>>>>>>>> WSO2 Inc.
>>>>>>>>>>>>>> http://wso2.com
>>>>>>>>>>>>>> http://wso2.org
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> *Senaka Fernando*
>>>>>>>>>>>>> Product Manager - WSO2 Governance Registry;
>>>>>>>>>>>>> Associate Technical Lead; WSO2, Inc.; http://wso2.com*
>>>>>>>>>>>>> Member; Apache Software Foundation; http://apache.org
>>>>>>>>>>>>>
>>>>>>>>>>>>> E-mail: senaka AT wso2.com
>>>>>>>>>>>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>>>>>>>>>>>>> Linked-In: http://www.linkedin.com/in/senakafernando
>>>>>>>>>>>>>
>>>>>>>>>>>>> *Lean . Enterprise . Middleware
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Prabath Abeysekara
>>>>>>>>>>> Software Engineer
>>>>>>>>>>> WSO2 Inc.
>>>>>>>>>>> Email: [email protected] <[email protected]>
>>>>>>>>>>> Mobile: +94774171471
>>>>>>>>>>>
>>>>>>>>>>> <http://harshana05.blogspot.com/>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> *Senaka Fernando*
>>>>>>>>> Product Manager - WSO2 Governance Registry;
>>>>>>>>> Associate Technical Lead; WSO2, Inc.; http://wso2.com*
>>>>>>>>> Member; Apache Software Foundation; http://apache.org
>>>>>>>>>
>>>>>>>>> E-mail: senaka AT wso2.com
>>>>>>>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>>>>>>>>> Linked-In: http://www.linkedin.com/in/senakafernando
>>>>>>>>>
>>>>>>>>> *Lean . Enterprise . Middleware
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>> Samisa...
>>>>>>>>
>>>>>>>> Samisa Abeysinghe
>>>>>>>> VP Engineering
>>>>>>>> WSO2 Inc.
>>>>>>>> http://wso2.com
>>>>>>>> http://wso2.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>> Samisa...
>>>>>>>
>>>>>>> Samisa Abeysinghe
>>>>>>> VP Engineering
>>>>>>> WSO2 Inc.
>>>>>>> http://wso2.com
>>>>>>> http://wso2.org
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Senaka Fernando*
>>>>>> Product Manager - WSO2 Governance Registry;
>>>>>> Associate Technical Lead; WSO2, Inc.; http://wso2.com*
>>>>>> Member; Apache Software Foundation; http://apache.org
>>>>>>
>>>>>> E-mail: senaka AT wso2.com
>>>>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>>>>>> Linked-In: http://www.linkedin.com/in/senakafernando
>>>>>>
>>>>>> *Lean . Enterprise . Middleware
>>>>>>
>>>>>> Thanks,
>>>>> Samisa...
>>>>>
>>>>> Samisa Abeysinghe
>>>>> VP Engineering
>>>>> WSO2 Inc.
>>>>> http://wso2.com
>>>>> http://wso2.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>> Thanks,
>>> Samisa...
>>>
>>> Samisa Abeysinghe
>>> VP Engineering
>>> WSO2 Inc.
>>> http://wso2.com
>>> http://wso2.org
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Thilini Ishaka
>> Software Engineer
>> WSO2 Inc
>>
>>
>
>
> --
> Suminda Chamara Silva
> WSO2 Inc.
> Mobile: +94 718 302858
> blog: http://chamaras.blogspot.com
>



-- 
Suminda Chamara Silva
WSO2 Inc.
Mobile: +94 718 302858
blog: http://chamaras.blogspot.com
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to