gt; [-] Broken - do not release (explain why)
>>>>>>
>>>>>> ~The WSO2 Integration Team~
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Himasha Guruge
>>&g
t; --
> *Regards,*
>
> *Kasun Siyambalapitiya*
> *Software Engineer*
> WSO2 Inc. - http://wso2.com/
> lean . enterprise . middleware
> Tel : 0715523466
> E mail : kasu...@wso2.com
> Blog: https://medium.com/@kasunsiyambalapitiya
> <https://wso2.com/signatu
efined in a string form as below
>>>
>>> org.apache.axis2.transport:org.apache.axis2.transport.jms.feature:
>>>> ${axis2-transports.wso2.version.1.1.0.wso2v17}
>>>
>>>
>>> and the version `${axis2-transports.wso2.version.1.1.0.wso2v17}` is
>>> r
[Adding Chamila]
On Mon, Sep 4, 2017 at 2:36 PM, Niranjan Karunanandham <niran...@wso2.com>
wrote:
> Hi Chamila,
>
> On Fri, Sep 1, 2017 at 9:57 AM, Chamila De Alwis <chami...@wso2.com>
> wrote:
>
>> Hi,
>>
>> Please find the meeting notes below.
&
t;>>>>>> configs we need.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> But with the suggested approach, we have to request the
>>>>>>>>>>>>>>> 1)config files, 2)all the environment variables and get the
>>>>>>>>>>>>>>> union to
>>>>>>>>>>>>>>> identify the changed configurations. IMO an additional effort.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hence considering the overhead on the support front I am -1
>>>>>>>>>>>>>>> for the suggested approach.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>> Jayanga.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> *Jayanga Dissanayake*
>>>>>>>>>>>>>>> Associate Technical Lead
>>>>>>>>>>>>>>> WSO2 Inc. - http://wso2.com/
>>>>>>>>>>>>>>> lean . enterprise . middleware
>>>>>>>>>>>>>>> email: jaya...@wso2.com
>>>>>>>>>>>>>>> mobile: +94772207259 <+94%2077%20220%207259>
>>>>>>>>>>>>>>> <http://wso2.com/signature>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Wed, Aug 23, 2017 at 9:16 AM, Danesh Kuruppu <
>>>>>>>>>>>>>>> dan...@wso2.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Created git issue[1] to track this improvement.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 1. https://github.com/wso2/carbon-config/issues/48
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tue, Aug 22, 2017 at 9:50 AM, Danesh Kuruppu <
>>>>>>>>>>>>>>>> dan...@wso2.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hi Chamila,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> +1 for the suggested approach. So we can have both ways to
>>>>>>>>>>>>>>>>> set environment variables either from placeholder
>>>>>>>>>>>>>>>>> ${env:} where we can
>>>>>>>>>>>>>>>>> specify any key for the variable or from the new approach.
>>>>>>>>>>>>>>>>> For the new
>>>>>>>>>>>>>>>>> approach, we need adhere to a certain format as suggested.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>> Danesh
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Mon, Aug 21, 2017 at 5:59 PM, Chamila De Alwis <
>>>>>>>>>>>>>>>>> chami...@wso2.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> In C5, the configuration lookup is done in the
>>>>>>>>>>>>>>>>>> environment variables, system properties, deployment.yaml
>>>>>>>>>>>>>>>>>> file, and the
>>>>>>>>>>>>>>>>>> value provided in the configuration bean class, in that
>>>>>>>>>>>>>>>>>> order. However, it
>>>>>>>>>>>>>>>>>> looks like environment variable lookup happens only if the
>>>>>>>>>>>>>>>>>> particular
>>>>>>>>>>>>>>>>>> configuration is noted to do so in the deployment.yaml,
>>>>>>>>>>>>>>>>>> specifically if the
>>>>>>>>>>>>>>>>>> value of the config is prefixed by a placeholder env:.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> gateWayEndpoint: ${env:gateWayEndpoint}
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> While this pattern may be easy to implement, it is
>>>>>>>>>>>>>>>>>> cumbersome to be followed in a Containerization approach and
>>>>>>>>>>>>>>>>>> IMO breaks the
>>>>>>>>>>>>>>>>>> 12Factor approach to configuration. This is because of the
>>>>>>>>>>>>>>>>>> need to edit a
>>>>>>>>>>>>>>>>>> physical file in order for the environment variables to be
>>>>>>>>>>>>>>>>>> queried. This
>>>>>>>>>>>>>>>>>> makes it harder to maintain a single Container Image for
>>>>>>>>>>>>>>>>>> different
>>>>>>>>>>>>>>>>>> deployments, and manipulate the Container runtimes via
>>>>>>>>>>>>>>>>>> environment
>>>>>>>>>>>>>>>>>> variables.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> AFAIU, this pattern emerges from the requirements in
>>>>>>>>>>>>>>>>>> SecureVault; having a ${sec:} prefix can mark the
>>>>>>>>>>>>>>>>>> configuration value to be
>>>>>>>>>>>>>>>>>> resolved through Secure Vault resolver. However IMO this,
>>>>>>>>>>>>>>>>>> value resolution,
>>>>>>>>>>>>>>>>>> is not the same as value lookup.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> IMO, the following should be the lookup order, without
>>>>>>>>>>>>>>>>>> having to mark a particular config in the deployment.yaml
>>>>>>>>>>>>>>>>>> file.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 1. Environment variables:
>>>>>>>>>>>>>>>>>> PREFIX_wso2.NAMESPACE_CONFIGKEY="value",
>>>>>>>>>>>>>>>>>> PREFIX_wso2.NAMESPACE_CONFIGPARENT_CONFIG2="value2"
>>>>>>>>>>>>>>>>>> 2. deployment.yaml:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> wso2.NAMESPACE:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> CONFIG_KEY: value
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> CONFIG_PARENT:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> CONFIG2: valu2
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 3. Default value in the code
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> This approach would be most Container friendly one as
>>>>>>>>>>>>>>>>>> there is no need to change files depending on deployment
>>>>>>>>>>>>>>>>>> patterns,
>>>>>>>>>>>>>>>>>> environments, etc.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> WDYT?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>>>> Chamila de Alwis
>>>>>>>>>>>>>>>>>> Committer and PMC Member - Apache Stratos
>>>>>>>>>>>>>>>>>> Senior Software Engineer | WSO2
>>>>>>>>>>>>>>>>>> Blog: https://medium.com/@chamilad
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> *Danesh Kuruppu*
>>>>>>>>>>>>>>>>> Senior Software Engineer | WSO2
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Email: dan...@wso2.com
>>>>>>>>>>>>>>>>> Mobile: +94 (77) 1690552 <+94%2077%20169%200552>
>>>>>>>>>>>>>>>>> Web: WSO2 Inc <https://wso2.com/signature>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> *Danesh Kuruppu*
>>>>>>>>>>>>>>>> Senior Software Engineer | WSO2
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Email: dan...@wso2.com
>>>>>>>>>>>>>>>> Mobile: +94 (77) 1690552 <+94%2077%20169%200552>
>>>>>>>>>>>>>>>> Web: WSO2 Inc <https://wso2.com/signature>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> ___
>>>>>>>>>>>>>>>> Architecture mailing list
>>>>>>>>>>>>>>>> Architecture@wso2.org
>>>>>>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> ___
>>>>>>>>>>>>>>> Architecture mailing list
>>>>>>>>>>>>>>> Architecture@wso2.org
>>>>>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Nuwan Dias
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Software Architect - WSO2, Inc. http://wso2.com
>>>>>>>>>>>>>> email : nuw...@wso2.com
>>>>>>>>>>>>>> Phone : +94 777 775 729 <+94%2077%20777%205729>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ___
>>>>>>>>>>>>>> Architecture mailing list
>>>>>>>>>>>>>> Architecture@wso2.org
>>>>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> ___
>>>>>>>>>>>>> Architecture mailing list
>>>>>>>>>>>>> Architecture@wso2.org
>>>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>>
>>>>>>>>>>> Isuru H.
>>>>>>>>>>> +94 716 358 048 <+94%2071%20635%208048>* <http://wso2.com/>*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>> Mobile : +94714289692 <071%20428%209692>
>>>>>>>>>> Blogs : https://medium.com/@lakwarus/
>>>>>>>>>> http://lakmalsview.blogspot.com/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Thanks and Regards,
>>>>>>>>>
>>>>>>>>> Isuru H.
>>>>>>>>> +94 716 358 048 <+94%2071%20635%208048>* <http://wso2.com/>*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Nuwan Dias
>>>>>>
>>>>>> Software Architect - WSO2, Inc. http://wso2.com
>>>>>> email : nuw...@wso2.com
>>>>>> Phone : +94 777 775 729 <+94%2077%20777%205729>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
Regards,
Nira
--
*Niranjan Karunanandham*
Associate Technical Lead - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Your comments are highly appreciated.
>>>
>>
>> As per the offline discussion, this issue is for generating the p2-repo.
>> You will need to check whether both versions of the feature are there in
>> the p2-repo that is being generated. If it does not exist then we wo
t; WSO2 Inc. - http://wso2.com/
> lean . enterprise . middleware
> Tel : 0715523466
> E mail : kasu...@wso2.com
> Blog: https://medium.com/@kasunsiyambalapitiya
> <https://wso2.com/signature>
>
Regards,
Nira
--
*Niranjan Karunanandham*
Associate Technical Lead - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
WDYT?
>>
>> Thanks,
>> Jayanga.
>>
>> *Jayanga Dissanayake*
>> Associate Technical Lead
>> WSO2 Inc. - http://wso2.com/
>> lean . enterprise . middleware
>> email: jaya...@wso2.com
>> mobile: +94772207259 <+94%2077%20220%207259&g
gt; | |___ bin
>>> | | |_ carbon.sh
>>> | |___ deployment
>>> |
>>> |___ lib (this will contains common jars)
ay 22, 2017 at 5:20 PM, Jayanga Dissanayake <jaya...@wso2.com>
> wrote:
>
>> Hi Ramith/Nira
>>
>> On Mon, May 22, 2017 at 2:56 PM, Niranjan Karunanandham <
>> niran...@wso2.com> wrote:
>>
>>>
>>> On Mon, May 22, 2017 at 12:34 P
, and there is a
separate script file to write selective components in the lib folder to
each runtime's bundle.info separately before starting up the server.
Regards,
Nira
On Mon, May 22, 2017 at 2:54 PM, Niranjan Karunanandham <niran...@wso2.com>
wrote:
> Hi Jayanga,
>
>
> On Mon, May 22, 2017 at
put bundles will complicate our
>>>> story, Hence, I would prefer to have one place where users put bundles
>>>> into. If that bundle is having a symbolic name and version equivalent to a
>>>> one in the plugins directory, it will act as a "patch" or else it wi
for temp purpose only.
>
> Thanks,
> Jayanga.
>
> *Jayanga Dissanayake*
> Associate Technical Lead
> WSO2 Inc. - http://wso2.com/
> lean . enterprise . middleware
> email: jaya...@wso2.com
> mobile: +94772207259 <+94%2077%20220%207259>
> <http://wso2.com/s
;>>>>> And
>>>>>> The logic in selecting effective bundles list should be changed to
>>>>>> not to give priority to bundles in the plugins directory. Instead modify
>>>>>> the entries, if a similar bundle (symbolic name and version) i
chitecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
Regards,
Nira
--
*Niranjan Karunanandham*
Associate Technical Lead - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
O2 Inc <https://wso2.com/signature>
>>>
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>>
>> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
>> email: kasung AT spamfree wso2.com
>> linked-in: http://lk.linkedin.com/in/gajasinghe
>> blog: http://kasunbg.org
>> phone: +1 650-745-4499 <(650)%20745-4499>, 77 678 0813
>>
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Thusitha Dayaratne
> WSO2 Inc. - lean . enterprise . middleware | wso2.com
>
> Mobile +94712756809 <+94%2071%20275%206809>
> Blog alokayasoya.blogspot.com
> Abouthttp://about.me/thusithathilina
> <http://wso2.com/signature>
>
>
Regards,
Nira
--
*Niranjan Karunanandham*
Associate Technical Lead - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
> WSO2 Inc. - http://wso2.com/
> lean . enterprise . middleware
> email: jaya...@wso2.com
> mobile: +94772207259 <+94%2077%20220%207259>
> <http://wso2.com/signature>
>
> On Fri, Mar 17, 2017 at 9:43 AM, Niranjan Karunanandham <niran...@wso2.com
> > wrote:
xygen-tank.10903.n7.nabble.com/C5-Moving-Carbon-Configuration-and-Carbon-Sec-Vault-to-2-Separate-Repositories-Removing-from-Kernel-td146953.html>
>>
>>
>> Best Regards,
>>
>> *Vidura Nanayakkara*
>> Software Engineer
>>
>> Email :
2] Carbon Secure Vault <https://github.com/wso2/carbon-secvault>
>
>
> On Fri, Mar 10, 2017 at 7:11 PM, Niranjan Karunanandham <niran...@wso2.com
> > wrote:
>
>> Hi all,
>>
>> On Fri, Mar 10, 2017 at 6:55 PM, Lakshman Udayakantha <lakshm...@wso2.c
can be preserved then please coordinate with
Lakshman.
> Thanks,
> Lakshman.
>
>>
>>- Then move above folder to [2] using a PR-X
>>- Once the PR-X is merged, apply your changes on top of it.
>>
>> [1] https://github.com/wso2/carbon-kernel/pull/
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057 <+94%2077%20374%202057>
> W: https://medium.com/@imesh TW: @imesh
> lean. enterprise. middleware
>
>
Regards,
Nira
--
*Niranjan Karunanandham*
Associate Technical Lead - WSO2 Inc.
WSO2 Inc.: http://
s://github.com/wso2/carbon-config/issues/1>
>>> [4] [Architecture] Carbon C5 - Server Configuration Model
>>> [5] Carbon configuration repo <https://github.com/wso2/carbon-config>
>>> [6] Carbon Secvault Repo <https://github.com/wso2/carbon-secvault>
>&
> [7] Carbon Kernel Repo <https://github.com/wso2/carbon-kernel>
>
>
> Best Regards,
>
> *Vidura Nanayakkara*
> Software Engineer
>
> Email : vidu...@wso2.com
> Mobile : +94 (0) 717 919277 <+94%2071%20791%209277>
> Web : http://wso2.com
> Blog : https://medium.com/@viduran <http://wso2.com/>
> Twitter : http://twitter.com/viduranana
> LinkedIn : https://lk.linkedin.com/in/vidura-nanayakkara
> <http://wso2.com/>
>
Regards,
Nira
--
*Niranjan Karunanandham*
Associate Technical Lead - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
;>>>> blog: http://kasunbg.org
>>>>>> phone: +1 650-745-4499 <+1%20650-745-4499>, 77 678 0813
>>>>>>
>>>>>>
>>>>>> ___
>>>>>> Architecture mailing li
kernel/releases
Thank you for your interest in WSO2 Carbon Kernel.
Best Regards
Carbon Team
--
*Niranjan Karunanandham*
Associate Technical Lead - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mai
- WSO2 Architecture List: architecture@wso2.org
Best Regards
Carbon Team
--
*Niranjan Karunanandham*
Associate Technical Lead - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/m
|--conf
> |--
> |--analytics
> |--tooling
> |--osgi
>|--plugins
>
>
> Thanks,
> *Jayanga Dissanayake*
> Associate Technical Lead
> WSO2 Inc. - http://wso2.com/
> lean . enterprise . middleware
> email: jaya...@wso2.com
>
profile support for C5 based products."
>
> Thanks,
> *Jayanga Dissanayake*
> Associate Technical Lead
> WSO2 Inc. - http://wso2.com/
> lean . enterprise . middleware
> email: jaya...@wso2.com
> mobile: +94772207259
> <http://wso2.com/signature>
>
Regards,
Nira
org/cgi-bin/mailman/listinfo/architecture
>
>
>
>
> --
> *Susinda Perera*
> Software Engineer
> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
> Mobile:(+94)716049075
> Blog: susinda.blogspot.com
> WSO2 Inc. http://wso2.com/
> Tel : 94 11 214 5345 Fax
; Mobile: +94713149860
>>
>>
>
>
> --
> Sameera Jayasoma,
> Software Architect,
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://blog.sameera.org
> twitter: https://twitter.com/sameerajayasoma
> flickr: http://www.flickr.com/photo
report issues, documentation errors regarding WSO2
Carbon Kernel 5.1.0 through the public issue tracking system
<https://wso2.org/jira/browse/CARBON>.
Thanks,
WSO2 Carbon Team
--
*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
__
wing mailing lists:
- WSO2 Developers List: d...@wso2.org
- WSO2 Architecture List: architecture@wso2.org
You can download the released distribution from the following location.
http://wso2.com/products/carbon/
Thank you for your interest in WSO2 Carbon Kernel.
Best Regards
Carbon Tea
thing else?
>
> [1]
> https://github.com/wso2/carbon-analytics-common/blob/v5.0.11/features/event-publisher/org.wso2.carbon.event.publisher.aggregate.feature/pom.xml
>
> On Fri, May 20, 2016 at 2:10 PM, Niranjan Karunanandham <niran...@wso2.com
> > wrote:
>
>> Hi Pulasthi,
>&
he carbon feature repository locally with the PR at [1] and point
> that as a local repository. Any possible causes for this?
>
> [1] https://github.com/wso2/carbon-feature-repository/pull/46
>
> On Wed, Apr 27, 2016 at 9:08 AM, Niranjan Karunanandham <niran...@wso2.c
e
>> *secrets*.properties
>>file and do not depend on the xpath to find the location of the secret
>>element.
>>
>> Thanks,
>> Nipuni
>>
>> --
>> Nipuni Perera
>> Software Engineer; WSO2 Inc.; http://wso2.com
>> Email: nip.
ou can download the released distribution from the following location.
http://wso2.com/products/carbon/
Thank you for your interest in WSO2 Carbon Kernel.
Best Regards
Carbon Team
--
*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.ws
nd merge this as an special case.
>>
>> Thanks,
>> Malith
>>
>> On Tue, Apr 12, 2016 at 10:56 AM, Niranjan Karunanandham <
>> niran...@wso2.com> wrote:
>>
>>> Hi Malith,
>>>
>>> On Fri, Mar 18, 2016 at 11:42 AM, Ma
wnload the released distribution from the following location.
http://wso2.com/products/carbon/
Thank you for your interest in WSO2 Carbon Kernel.
Best Regards
Carbon Team
--
*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.ws
06 693
>>>
>>> ___
>>> Dev mailing list
>>> d...@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Kishanthan Thangarajah
pers List: d...@wso2.org
- WSO2 Architecture List: architecture@wso2.org
Best Regards
Carbon Team
--
*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Architecture mailing list
Architecture@ws
leased distribution from the following location.
http://wso2.com/products/carbon/
Thank you for your interest in WSO2 Carbon Kernel.
Best Regards
Carbon Team
--
*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.ws
rg
- WSO2 Architecture List: architecture@wso2.org
You can download the released distribution from the following location.
http://wso2.com/products/carbon/
Thank you for your interest in WSO2 Carbon Kernel.
Best Regards
Carbon Team
--
*Niranjan Karunanandham*
Senior Software Engineer - WSO2 I
leased distribution from the following location.
http://wso2.com/products/carbon/
Thank you for your interest in WSO2 Carbon Kernel.
Best Regards
Carbon Team
--
*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.ws
Kernel.
Best Regards
Carbon Team
--
*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
@wso2.com* <az...@wso2.com>
>> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
>> *http://blog.afkham.org* <http://blog.afkham.org>
>> *twitter: **http://twitter.com/afkham_azeez*
>> <http://twitter.com/afkham_azeez>
>> *linked-in: **
On Tue, Jul 28, 2015 at 6:10 PM, Malaka Silva <mal...@wso2.com> wrote:
> Thx Niranjan Will do.
>
> On Tue, Jul 28, 2015 at 4:32 PM, Niranjan Karunanandham <niran...@wso2.com
> > wrote:
>
>> Hi Malaka,
>>
>> We are still in discussing the structure for
17, 2015 at 4:55 PM, Niranjan Karunanandham
niran...@wso2.com wrote:
Hi Chanaka,
For the p2 repo, we already have the carbon-feature-repository [1],
which will have all the features in the main pom.xml. We had a review [2]
with regard to this and during the review it was suggested whether we
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Architecture mailing list
, Prabath Abeysekera, Asok
Perera, Afkham Azeez, Geeth Munasinghe, Inosh Perera, Harshan
Liyanage, Niranjan Karunanandham, Sumedha Rubasinghe, Srinath
Perera, Manoj Dilshan
- Knowledge transfer of the current EMM architecture
- Moving all the device specific entries from Core EER to bundles
Hi Dilan,
In the case of iOS, it has the MDM in its OS and they have defined the
payload structure for each operation. Whereas in the case of Android, we
have an agent in the client side to perform the MDM operation. I believe
(please correct me if am wrong) that for windows also it is the same
.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman
. We were thinking
of having the same priority based model (explained above) for Roles also.
Is there something like this in IS roadmap in which case we can use the
same for EMM?
Regards,
Nira
--
*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
M: +94
and is
provided by the very same engineers who build the technology.
For additional support information please refer to http://wso2.com/support/
We welcome your feedback and would love to hear your thoughts on this
release of WSO2 EMM.
--WSO2 EMM Development Team--
--
*Niranjan Karunanandham
tokens are stored in the same field as a json string. Normal push
token is saved in reg id field. This needs to be refactored. How do you
deal with above 5 types of tokens in your new proposed way?
Regards,
Dilshan
On Mon, May 5, 2014 at 10:29 AM, Niranjan Karunanandham niran...@wso2.com
to be changed.
[1] -
https://github.com/wso2-dev/product-emm/commit/8396f05c8f82587f6e9eb1c6382138d6cf065381
Regards,
Nira
--
*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
M: +94 777 749 661 http
Edirisuriya
Senior Software Engineer - WSO2
Mob: + 94 777878905
http://wso2.com/
--
*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
M: +94 777 749 661 http:///
___
Architecture mailing list
Architecture
convention: hotfix-*) - This is created when
there is a critical bug that needs to be fixed in the released version
(master). Once the bug is fixed, it needs to be merged to the master
and develop branches.
[1] - http://nvie.com/posts/a-successful-git-branching-model/
--
*Niranjan
branch because of the above practical reason.
Cheers~
On Thu, Mar 27, 2014 at 9:49 PM, Niranjan Karunanandham niran...@wso2.com
wrote:
Hi all,
The blog [1] explains how the Git work flow works. Below I have
summarized what is mentioned in the blog.
This work flow consists of two main
://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
M: +94 777 749 661 http:///
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2
/cgi-bin/mailman/listinfo/architecture
--
*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
M: +94 777 749 661 http:///
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman
- it will be
added to the current node's file system. Afterwards DepSync will sync these
files across all nodes. We are currently discussing on how to isolate these
to a single storage app which is discussed in the architecture list [mail
thread subject: Unified Storage Proposal].
--
*Niranjan
://twitter.com/dulitharw*
--
*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2Mobile Inc.: http://wso2mobile.com
M: +94 777 749 661 http:///
6B0F5F81-A8A3-40B7-ADB4-486CED138701.png___
Architecture mailing list
Architecture@wso2.org
https
62 matches
Mail list logo
