date:20160131

[Dev] Hesitating OAuth2 grant type

2016-01-31 Thread Xavier Pegenaute M2M


Hi all,

I 've been working a bit with the SCIM API which I think more or less 
everything is right. Now I have some hesitation about the grant type 
which fits better in our side.


Currently we thought that Resource Owner Password Credential Grant was 
the good one but there is something we need to workaround.


We have a main application and some services which are communicating 
with the application. These services interact with the main application 
using a specific system credentials, therefore some of them share the 
credentials.


The problem arises when one of these services call the revoke endpoint, 
after this call all the other services are revoked and they need to 
login again. My wish would be a different token for every service, 
therefore any service can login or logout without affecting the others.


Is there some method/config to allow wso2 to deal with this particular 
scenario?


Regards,
Xavi
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][JAGGERY] Getting Empty JSON when logging(log.info)

2016-01-31 Thread Chamara Philips

There is com.google.gson.Gson as well, which I have used in OIDCDiscovery
project [1], (which is not yet merged) to convert a Java object to JSON.
But jackson seems more suitable, as it supports data-binding functionality.

[1] https://github.com/wso2/carbon-identity/pull/1694/



On Sat, Jan 30, 2016 at 9:28 PM, Rajeenthini Satkunam 
wrote:

> Hi,
>
> I have worked on writing Jaggery test for Jaggery-Product.I can observe
> when we tried to log the object it always gives us empty JSON
> ({}).Currently the implementation goes this way when we try to log java
> object.
>
> So I was trying to get rid of this observed behavior of Jaggery.I have
> gone through a solution.
>
> *using Jackson[1] *
>
> We can convert java object to JSON[2] and can log it.
>
> I have shared the piece of code I have tried out with Jackson below.
>
> *Simple POJO Student class*
>
> public class Student {
> private int age;
> private String name;
> private String indexNo;
>
> public int getAge() {
> return age;
> }
>
> public void setAge(int age) {
> this.age = age;
> }
>
> public String getName() {
> return name;
> }
>
> public void setName(String name) {
> this.name = name;
> }
>
> public String getIndexNo() {
> return indexNo;
> }
>
> public void setIndexNo(String indexNo) {
> this.indexNo = indexNo;
> }
> }
>
> *Simple class to test Jackson*
>
> import com.fasterxml.jackson.databind.ObjectMapper;
> import util.Student;
> public class MyTest {
> public static void main(String args[]){
> Student st = new Student();
> st.setIndexNo("DS001");
> st.setAge(12);
> st.setName("kareena");
> try{
> ObjectMapper mapper = new ObjectMapper();
> String jsonInString = mapper.writeValueAsString(st);
> 
> System.out.println("");
> System.out.println(jsonInString);
> 
> System.out.println("");
>
> }catch(Exception e){
> System.out.print("Exception caught  "+ e);
> }
>
> }
> }
>
> Actual output by above code.
> 
> {"age":12,"name":"kareena","indexNo":"DS001"}
> 
>
> I have added a dependency in the POM.xml
>
> 
> com.fasterxml.jackson.core
> jackson-databind
> 2.6.3
> 
>
>
> IMHO we can use the same scenario in case of log JAVA object.Your help and
> suggestions are more appreciated and guide me if I am wrong or I can have
> better solution than this.
>
> [1] - https://github.com/FasterXML/jackson-databind
> [2] -
> http://www.mkyong.com/java/how-to-convert-java-object-to-from-json-jackson/
> --
>
> *Thank You.*
>
> *Rajeenthini Satkunam*
>
> *Associate Software Engineer | WSO2*
>
>
> *E:rajeenth...@wso2.com *
>
> *M :+94770832823 <%2B94770832823>   *
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Hareendra Chamara Philips
*Software  Engineer*
Mobile : +94 (0) 767 184161 <%2B94%20%280%29%20773%20451194>
chama...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Upgrading Smooks to version 1.5

2016-01-31 Thread Buddhima Wijeweera

Thanks Kasun,

[Adding dev mailing list]

On Mon, Feb 1, 2016 at 12:02 PM, Kasun Indrasiri  wrote:

> Shouldn't we discuss this in a mailing list?
>
> On Mon, Feb 1, 2016 at 12:00 PM, Buddhima Wijeweera 
> wrote:
>
>> Hi All,
>>
>> For the the next ESB release we need to upgrade Smooks version from 1.4
>> to 1.5. Currently Smooks bundle is created through orbit which reside in
>> location [1].
>>
>> According to offline discussion had with Kishanthan, we have asked to try
>> directly using smooks osgi bundle in carbon-mediation but we ended up with
>> a problem activating Smooks OSGI bundle as it required certain additional
>> dependencies.
>>
>> example:
>>
>> BundleException: The bundle "org.milyn.smooks.osgi_1.5.0 [142]" could not
>> be resolved. Reason: Missing Constraint: Import-Package: freemarker.cache;
>> version="2.3.15"
>>
>> Which means smooks osgi bundle is searching for freemarker dependency.
>>
>> The freemarker can be found as a jar [2]. But even after we add it to
>> "/lib" folder, still the smooks bundle fails to activate, since it can't
>> find the matching version (freemarker bundle is in active state).
>>
>> The reason behind this is the version of free marker carbon server
>> generated. Even by bundling freemarker as a orbit bundle (which adds "wso2"
>> post-fix to version), the exact version "2.3.15" cannot be satisfied,
>> according to my knowledge.
>>
>> The best option so far can be seen is to re-bundle smooks along
>> with dependencies as an orbit bundle, which is the way it was there before.
>>
>> Please let us know if there's any other alternative to overcome this
>> confusion.
>> [1] https://svn.wso2.org/repos/wso2/trunk/orbit/smooks/
>> [2] http://mvnrepository.com/artifact/org.freemarker/freemarker/2.3.15
>>
>> Thank you,
>> --
>> Buddhima Wijeweera
>> Software Engineer; WSO2 Inc.; http://wso2.com ,
>>
>> Mobile: +94 71 427 9966
>> Email: buddh...@wso2.com
>> Blog:   https://buddhimawijeweera.wordpress.com
>> GitHub Profile: https://github.com/Buddhima
>>
>
>
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>



-- 
Buddhima Wijeweera
Software Engineer; WSO2 Inc.; http://wso2.com ,

Mobile: +94 71 427 9966
Email: buddh...@wso2.com
Blog:   https://buddhimawijeweera.wordpress.com
GitHub Profile: https://github.com/Buddhima
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Puppet Modules 1.0.0 RC2

2016-01-31 Thread Isuru Haththotuwa

Hi,

AFAIU we can't just use this templates anyway as they are, but might need
to modify to fit to the usecase. These modules do not cover all the
parameters that each of the products have, just have the most basic set.
More importantly this set of puppet modules have standardized the
separation of data from puppet code by using hiera to use as a common set
of puppet modules for all WSO2 use cases. We can improve them as we move
along.

On Mon, Feb 1, 2016 at 11:46 AM, Ramith Jayasinghe  wrote:

> had a chat with IsuruH and agreed to add the ability to configure this
> on next release.
>
> On Mon, Feb 1, 2016 at 11:25 AM, Ramith Jayasinghe 
> wrote:
> > HI,
> >  in :
> https://github.com/wso2/puppet-modules/blob/v1.0.0-rc2/modules/wso2mb/templates/3.0.0/repository/conf/datasources/master-datasources.xml.erb
> >  I see that,
> >  false is not added to MB
> > data-source (only MB data-source requires that). that would lead to
> > problems. shall we fix that.
> >  regards
> > Ramith
> >
> > On Mon, Feb 1, 2016 at 11:14 AM, Isuru Haththotuwa 
> wrote:
> >> Hi devs,
> >>
> >> This is the second release candidate of WSO2 Puppet Modules 1.0.0.
> Please
> >> download, test and vote.
> >>
> >> [ ] Broken - do not release (explain why)
> >> [ ] Stable - go ahead and release
> >>
> >> The tag to be voted upon:
> >> https://github.com/wso2/puppet-modules/tree/v1.0.0-rc2
> >>
> >> Source and binary distribution files:
> >> https://github.com/wso2/puppet-modules/releases/tag/v1.0.0-rc2
> >>
> >> The vote will be open for 72 hours or as needed.
> >>
> >> --
> >> Thanks,
> >> The WSO2 Private PaaS Team
> >>
> >>
> >>
> >> ___
> >> Dev mailing list
> >> Dev@wso2.org
> >> http://wso2.org/cgi-bin/mailman/listinfo/dev
> >>
> >
> >
> >
> > --
> > Ramith Jayasinghe
> > Technical Lead
> > WSO2 Inc., http://wso2.com
> > lean.enterprise.middleware
> >
> > E: ram...@wso2.com
> > P: +94 777542851
>
>
>
> --
> Ramith Jayasinghe
> Technical Lead
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> E: ram...@wso2.com
> P: +94 777542851
>



-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] How to add patch improvements for Developer Studio update site

2016-01-31 Thread Nuwan Pallewela

Hi All,

What is the process for adding improvements done for a patch, to Developer
Studio update site?

Thanks,
Nuwan

-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Puppet Modules 1.0.0 RC2

2016-01-31 Thread Ramith Jayasinghe

HI,
 in : 
https://github.com/wso2/puppet-modules/blob/v1.0.0-rc2/modules/wso2mb/templates/3.0.0/repository/conf/datasources/master-datasources.xml.erb
 I see that,
 false is not added to MB
data-source (only MB data-source requires that). that would lead to
problems. shall we fix that.
 regards
Ramith

On Mon, Feb 1, 2016 at 11:14 AM, Isuru Haththotuwa  wrote:
> Hi devs,
>
> This is the second release candidate of WSO2 Puppet Modules 1.0.0. Please
> download, test and vote.
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
> The tag to be voted upon:
> https://github.com/wso2/puppet-modules/tree/v1.0.0-rc2
>
> Source and binary distribution files:
> https://github.com/wso2/puppet-modules/releases/tag/v1.0.0-rc2
>
> The vote will be open for 72 hours or as needed.
>
> --
> Thanks,
> The WSO2 Private PaaS Team
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>



-- 
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

E: ram...@wso2.com
P: +94 777542851
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Puppet Modules 1.0.0 RC2

2016-01-31 Thread Ramith Jayasinghe

had a chat with IsuruH and agreed to add the ability to configure this
on next release.

On Mon, Feb 1, 2016 at 11:25 AM, Ramith Jayasinghe  wrote:
> HI,
>  in : 
> https://github.com/wso2/puppet-modules/blob/v1.0.0-rc2/modules/wso2mb/templates/3.0.0/repository/conf/datasources/master-datasources.xml.erb
>  I see that,
>  false is not added to MB
> data-source (only MB data-source requires that). that would lead to
> problems. shall we fix that.
>  regards
> Ramith
>
> On Mon, Feb 1, 2016 at 11:14 AM, Isuru Haththotuwa  wrote:
>> Hi devs,
>>
>> This is the second release candidate of WSO2 Puppet Modules 1.0.0. Please
>> download, test and vote.
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>> The tag to be voted upon:
>> https://github.com/wso2/puppet-modules/tree/v1.0.0-rc2
>>
>> Source and binary distribution files:
>> https://github.com/wso2/puppet-modules/releases/tag/v1.0.0-rc2
>>
>> The vote will be open for 72 hours or as needed.
>>
>> --
>> Thanks,
>> The WSO2 Private PaaS Team
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
>
> --
> Ramith Jayasinghe
> Technical Lead
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> E: ram...@wso2.com
> P: +94 777542851



-- 
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

E: ram...@wso2.com
P: +94 777542851
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Committers += Chamila Wijayarathna

2016-01-31 Thread Johann Nallathamby

Hi All,

It's my pleasure to announce Chamila Wijayarathna as a WSO2 Committer.
Chamila has been a valuable contributor for WSO2 Identity Server product,
and in recognition of his contribution to WSO2, he has been voted as a WSO2
Committer.

Chamila, congratulations and keep up the good work!

Thanks & Regards.

-- 

*Johann Dilantha Nallathamby*
Technical Lead & Product Lead of WSO2 Identity Server
Governance Technologies Team
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 Puppet Modules 1.0.0 RC2

2016-01-31 Thread Isuru Haththotuwa

Hi devs,

This is the second release candidate of WSO2 Puppet Modules 1.0.0. Please
download, test and vote.

[ ] Broken - do not release (explain why)
[ ] Stable - go ahead and release


*The tag to be voted upon:*
https://github.com/wso2/puppet-modules/tree/v1.0.0-rc2


*Source and binary distribution files:*
https://github.com/wso2/puppet-modules/releases/tag/v1.0.0-rc2

The vote will be open for 72 hours or as needed.

--
Thanks,
The WSO2 Private PaaS Team
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [EMM]Release progress update EMM 2.0.1

2016-01-31 Thread Kamidu Punchihewa

Hi,

Currently we are planning to release EMM 2.0.1-RC1 on the 12th of February.
This release will include fixes and enhancements in the following
components.9

   - UI/UX enhancements in User interface.
   - Known Issues in Mobile Application Management.
   - Known Issues in CDMF.


The Progress is Listed Below.
*Completed Jiras*
Bug

   - [EMM-918 ] - Validation criteria
   for user information should be consistent in both carbon management console
   and MDM dashboard
   - [EMM-1132 ] -
   'Application/' user roles should not be listed under roles in
   'Enterprise Install' UI
   - [EMM-1176 ] - Unable to perform
   user role edit, when user role name contains spaces
   - [EMM-1183 ] - Search policies
   by role name contains a blank field as search property
   - [EMM-1190 ] - Unable to perform
   user edit, when username contains spaces
   - [EMM-1191 ] - Need to add
   validation for user(s) and role(s) filed in policy creation and
   modification.
   - [EMM-1198 ] - When scrolling
   down, there's a shaky effect in the UI
   - [EMM-1199 ] - If Users/Roles
   are not assigned for the relevent policy. It should be hidden in the Policy
   list view.
   - [EMM-1201 ] - In edit user
   view, required asterisk is not required for username field
   - [EMM-1203 ] - Change buttons
   visibility based on the content availability
   - [EMM-1209 ] - If there are no
   devices enrolled,Device view icon should be hidden in the dashboard.
   - [EMM-1213 ] - Remove "from EMM
   User Store" wording and change to a meaningful text.
   - [EMM-1217 ] - Change add
   buttons to "Save" and edit buttons to "Update" in Add/Edit forms
   - [EMM-1227 ] - Login button and
   title text should be similar
   - [EMM-1230 ] - Policy publish
   text should be changed

Improvement

   - [EMM-1178 ] - Validations to
   user role and user name should be configurable
   - [EMM-1212 ] - Operation
   requseting time should not have milliseconds value in operation log
   - [EMM-1216 ] - Improve role
   create/edit interfaces
   - [EMM-1218 ] - Platform boxes
   should be similar in policy creation wizard.
   - [EMM-1221 ] - Loading icon and
   font are taking long time to fully loaded.
   - [EMM-1222 ] - Footer web
   address (wso2.org) should be changed to a link.
   - [EMM-1224 ] - Assign
   users/roles selection boxes should be validated in Policy creation.


*Jiras In Progress*
Bug

   - [EMM-1147 ] - Exception when
   user clicks sign out button in 'Store' and 'Publisher'
   - [EMM-1208 ] - Loading dialog
   box should be moved to the appropriate context in list views

Improvement

   - [EMM-1166 ] - Capitals used in
   certain notifications, UI labels, etc need to be removed
   - [EMM-1195 ] - List View
   contains some unwanted white spaces.
   - [EMM-1196 ] - Apply changes
   button should be moved to the policy list view/priority view with a proper
   message.
   - [EMM-1207 ] - Required Field
   should be indicated using one method.
   - [EMM-1210 ] - Enable inline
   validation if possible
   - [EMM-1211 ] - Usage of
   placeholder text need to be valid


*Jiras to be Completed*
Bug

   - [EMM-1231 ] - Action of the
   enroll device on the app bar should be moved to appropriate position.
   - [EMM-1232 ] - If there are no
   any data,pagination controls should not be visible.
   - [EMM-1233 ] - Remove all 
   from button spacing

Improvement

   - [EMM-1200 ] - On small screens,
   detailed view of the menu items not get listed under relevant area
   - [EMM-1202 ] - Improve to behave
   policy view list as a policy priority list.
   - [EMM-1214 ]

[Dev] New global parent pom

2016-01-31 Thread Manuranga Perera

Hi Samiyuru,
Is there any reason why org.wso2.carbon.mss pom [1] not pointing to
carbon-mss as the parent. just wondering.

[1]
https://github.com/wso2/msf4j/blob/7eb8a028e7ea0cb343546492b1a7408ef2c0af06/carbon-mss/components/org.wso2.carbon.mss/pom.xml#L26

-- 
With regards,
*Manu*ranga Perera.

phone : 071 7 70 20 50
mail : m...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Upgrading Smooks to version 1.5

2016-01-31 Thread Kishanthan Thangarajah

Can we try with [1] or [2] as the FreeMaker OSGi bundle? If these doesn't
bring any additional OSGi dependencies, we can use it, but let's try out
these first.

[1]
http://ebr.springsource.com/repository/app/bundle/version/detail?name=com.springsource.freemarker=2.3.15
[2]
http://mvnrepository.com/artifact/org.apache.servicemix.bundles/org.apache.servicemix.bundles.freemarker/2.3.15_5

On Mon, Feb 1, 2016 at 12:04 PM, Buddhima Wijeweera 
wrote:

> Thanks Kasun,
>
> [Adding dev mailing list]
>
> On Mon, Feb 1, 2016 at 12:02 PM, Kasun Indrasiri  wrote:
>
>> Shouldn't we discuss this in a mailing list?
>>
>> On Mon, Feb 1, 2016 at 12:00 PM, Buddhima Wijeweera 
>> wrote:
>>
>>> Hi All,
>>>
>>> For the the next ESB release we need to upgrade Smooks version from 1.4
>>> to 1.5. Currently Smooks bundle is created through orbit which reside in
>>> location [1].
>>>
>>> According to offline discussion had with Kishanthan, we have asked to
>>> try directly using smooks osgi bundle in carbon-mediation but we ended up
>>> with a problem activating Smooks OSGI bundle as it required certain
>>> additional dependencies.
>>>
>>> example:
>>>
>>> BundleException: The bundle "org.milyn.smooks.osgi_1.5.0 [142]" could
>>> not be resolved. Reason: Missing Constraint: Import-Package:
>>> freemarker.cache; version="2.3.15"
>>>
>>> Which means smooks osgi bundle is searching for freemarker dependency.
>>>
>>> The freemarker can be found as a jar [2]. But even after we add it to
>>> "/lib" folder, still the smooks bundle fails to activate, since it can't
>>> find the matching version (freemarker bundle is in active state).
>>>
>>> The reason behind this is the version of free marker carbon server
>>> generated. Even by bundling freemarker as a orbit bundle (which adds "wso2"
>>> post-fix to version), the exact version "2.3.15" cannot be satisfied,
>>> according to my knowledge.
>>>
>>> The best option so far can be seen is to re-bundle smooks along
>>> with dependencies as an orbit bundle, which is the way it was there before.
>>>
>>> Please let us know if there's any other alternative to overcome this
>>> confusion.
>>> [1] https://svn.wso2.org/repos/wso2/trunk/orbit/smooks/
>>> [2] http://mvnrepository.com/artifact/org.freemarker/freemarker/2.3.15
>>>
>>> Thank you,
>>> --
>>> Buddhima Wijeweera
>>> Software Engineer; WSO2 Inc.; http://wso2.com ,
>>>
>>> Mobile: +94 71 427 9966
>>> Email: buddh...@wso2.com
>>> Blog:   https://buddhimawijeweera.wordpress.com
>>> GitHub Profile: https://github.com/Buddhima
>>>
>>
>>
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 77 556 5206
>> Blog : http://kasunpanorama.blogspot.com/
>>
>
>
>
> --
> Buddhima Wijeweera
> Software Engineer; WSO2 Inc.; http://wso2.com ,
>
> Mobile: +94 71 427 9966
> Email: buddh...@wso2.com
> Blog:   https://buddhimawijeweera.wordpress.com
> GitHub Profile: https://github.com/Buddhima
>



-- 
*Kishanthan Thangarajah*
Associate Technical Lead,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com *
Twitter - *http://twitter.com/kishanthan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Puppet Modules 1.0.0 RC1

2016-01-31 Thread Isuru Haththotuwa

We are canceling this vote due to missing License file in the distribution.
Will start RC2 asap.

On Sat, Jan 30, 2016 at 12:33 AM, Chamila De Alwis 
wrote:

> Verified BRS, DAS and GREG.
>
> Fixed the license and readme packaging issue with the distributions.
> Furthermore, added license headers to YAML files and added a pedantic
> profile with the RAT plugin to verify license header in source files.
>
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
> On Fri, Jan 29, 2016 at 4:25 PM, Imesh Gunaratne  wrote:
>
>> On Fri, Jan 29, 2016 at 3:52 PM, Sajith Kariyawasam 
>> wrote:
>>
>>> I verified CEP puppet modules with vagrant.
>>>
>>> But noticed that license headers are missing in yaml files. I think we
>>> need to include those.
>>>
>>
>> +1 Will cancel this vote and fix those problems.
>>
>>>
>>>
>>>
>>>
>>> On Fri, Jan 29, 2016 at 3:19 PM, Imesh Gunaratne  wrote:
>>>
 I verified AS, ESB, IS & BPS puppet modules with Vagrant. However it
 looks like we have not packaged README and LICENSE files to the
 distributions.

 Shall we add those and go for a RC2?

 Thanks

 On Wed, Jan 27, 2016 at 8:33 PM, Isuru Haththotuwa 
 wrote:

> Hi all,
>
> This is the first release candidate of WSO2 Puppet Modules 1.0.0.
> Please download, test and vote.
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
>
> *The tag to be voted upon:*
> https://github.com/wso2/puppet-modules/tree/v1.0.0-rc1
>
>
> *Source and binary distribution files:*
> https://github.com/wso2/puppet-modules/releases/tag/v1.0.0-rc1
>
> The vote will be open for 72 hours or as needed.
>
> --
> Thanks,
> The WSO2 Private PaaS Team
>
>
>
> ___
> 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


>>>
>>>
>>> --
>>> Sajith Kariyawasam
>>> *Committer and PMC member, Apache Stratos, *
>>> *WSO2 Inc.; http://wso2.com *
>>> *Mobile: 0772269575 <0772269575>*
>>>
>>
>>
>>
>> --
>> *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
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error wile building carbon-feature-repository (branch: release-4.2.x)

2016-01-31 Thread Ruwan Abeykoon

Hi All,
Please disregard my previous comment. It is not applicable for Product v
1.1.0. Sorry.
>>(AppM v1.1.0 supposed to use carbon kernel 4.4.x, not 4.2.0, as it is
just carbon 4.4.x port of the v1.0.0 without any functionality changes.)

Cheers,
Ruwan

On Mon, Feb 1, 2016 at 10:37 AM, Tanya Madurapperuma  wrote:

>
>
> On Mon, Feb 1, 2016 at 10:10 AM, Ruwan Abeykoon  wrote:
>
>> Hi Tanya,
>> AppM v1.1.0 supposed to use carbon kernel 4.4.x, not 4.2.0, as it is just
>> carbon 4.4.x port of the v1.0.0 without any functionality changes.
>> Please let me know how you came up with this information,
>>
>
> Found out from the root pom of the product repo [1] carbon.kernel.version.
> [1] https://github.com/wso2/product-app-manager/blob/release-1.1.0/pom.xml
>
>
> Thanks,
> Tanya
>
> >>APPM 1.1.0 --> carbon kernel version 4.2.0 --> Jaggery version 0.10.1
>>
>> Cheers,
>> Ruwan
>>
>> Cheers,
>> Ruwan
>>
>> On Sun, Jan 31, 2016 at 9:15 PM, Tanya Madurapperuma 
>> wrote:
>>
>>> Hi Dinusha / Lahiru,
>>>
>>> When I checked the APPM releases found out the following according to
>>> the git.
>>>
>>> APPM 1.1.0 --> carbon kernel version 4.2.0 --> Jaggery version 0.10.1
>>> APPM 2.0.0 --> carbon kernel version 4.4.1 --> Jaggery version 0.10.1
>>>
>>> There seems to be a mismatch here. Because jaggery 0.10.1 version is
>>> released with carbon 4.4.0 but not with 4.2.x
>>> So there can be compatibility issues in APPM 1.1.0.
>>>
>>> I tried adding 0.10.1 version of jaggery in 4.2.x and when I was trying
>>> to install features pointing to the local p2-repo it threw a version
>>> mismatch issue in org.apache.commons.logging [1]
>>>
>>> Appreciate your insight. Do you require jaggery 0.10.1 to be included in
>>> 4.4.x p2-repo?
>>>
>>> [1] Cannot complete the install because one or more required items could
>>> not be found. Software being installed: Jaggery Server Feature 0.10.1
>>> (org.jaggeryjs.server.feature.group 0.10.1) Missing requirement:
>>> org.jaggeryjs.hostobjects.feed 0.10.1 (org.jaggeryjs.hostobjects.feed
>>> 0.10.1) requires 'package org.apache.commons.logging [1.2.0,2.0.0)' but it
>>> could not be found Cannot satisfy dependency: From: Jaggery Server Feature
>>> 0.10.1 (org.jaggeryjs.server.feature.group 0.10.1) To:
>>> org.jaggeryjs.hostobjects.feed [0.10.1]
>>>
>>> Thanks,
>>> Tanya
>>>
>>> On Fri, Jan 29, 2016 at 10:52 AM, Niranjan Karunanandham <
>>> niran...@wso2.com> wrote:
>>>
 Hi Tanya,

 I have update the repo. Please find the 4.2.x branch for
 carbon-feature-repository here [1].

 [1] - https://github.com/wso2/carbon-feature-repository/tree/4.2.x

 Regards,
 Nira

 On Fri, Jan 29, 2016 at 10:17 AM, Niranjan Karunanandham <
 niran...@wso2.com> wrote:

> Hi Tanya,
>
> Sorry for the delay. Will reply in this thread once the branch is
> ready.
>
> Regards,
> Nira
>
> On Fri, Jan 29, 2016 at 10:05 AM, Tanya Madurapperuma 
> wrote:
>
>> Hi Carbon team,
>>
>> If there are no objections, could you please create the above branch.
>>
>> Thanks,
>> Tanya
>>
>>
>> On Tue, Jan 26, 2016 at 4:53 PM, KasunG Gajasinghe 
>> wrote:
>>
>>>
>>>
>>> On Tue, Jan 26, 2016 at 2:37 PM, Niranjan Karunanandham <
>>> niran...@wso2.com> wrote:
>>>
 Hi Tanya,

 There was only a p2-repo release in the GIthub and there exists a
 branch called release-4.2.x[1]. This is the release branch and this was
 done by AmilaD for APIM. IMO if we are to do a new p2-repo release for
 kernel 4.2.0, then we need to rename this branch to 4.2.x and change 
 the
 version to 4.2.14-SNAPSHOT and new PRs for 4.2.x p2-repo need to be 
 sent to
 this branch.


>>> +1
>>>
>>>
 @Sameera / Kicha: WDYT?

 [1] -
 https://github.com/wso2/carbon-feature-repository/tree/release-4.2.x

 Regards,
 Nira

 On Tue, Jan 26, 2016 at 2:15 PM, Tanya Madurapperuma <
 ta...@wso2.com> wrote:

> Hi Sameera,
>
> As per the offline chat I had with Niranjan and Nipuni, in order
> to fulfil the above request from the app manager team, we need to 
> have  a
> development on-going branch for 4.2.x to send the PR with the missing
> features.
> But we couldn't locate such branch but the released branch
> (release-4.2.x) which has the version as 4.2.13
>
> Where should we send the PR to? Could you please advise.
>
> Thanks,
> Tanya
>
> On Mon, Jan 25, 2016 at 11:26 AM, Sinthuja Ragendran <
> sinth...@wso2.com> wrote:
>
>> Hi Tanya,
>>
>> Please check on this.
>>
>> Thanks,

Re: [Dev] WSO2 Committers += Malintha Amarasinghe

2016-01-31 Thread Praminda Jayawardana

Congratulations Malintha!

On Sun, Jan 31, 2016 at 7:22 PM, Kalyani Yogeswaranathan 
wrote:

> Congrats Malintha!
>
> On Sun, Jan 31, 2016 at 8:46 AM, Roshan Wijesena  wrote:
>
>> Congratulations !
>>
>> On Sat, Jan 30, 2016 at 8:34 PM, Hasunie Adikari 
>> wrote:
>>
>>> Congratz Malintha
>>>
>>> On Sat, Jan 30, 2016 at 7:03 PM, Rukshan Premathunga 
>>> wrote:
>>>
 congratz malintha...

 On Sat, Jan 30, 2016 at 6:57 PM, Isuru Wijesinghe 
 wrote:

> Congratzz Malintha :)
>
> On Sat, Jan 30, 2016 at 1:38 PM, Nuwan Dias  wrote:
>
>> Hi,
>>
>> It is with great pleasure we welcome Malintha Amarasinghe as a
>> WSO2 Committer. @Malintha, congratulations and keep up the good work!
>>
>> Thanks,
>> NuwanD.
>>
>> --
>> Nuwan Dias
>>
>> Technical Lead - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Isuru Wijesinghe
> *Software Engineer*
> WSO2 inc : http://wso2.com
> lean.enterprise.middleware
> Mobile: 0710933706
> isur...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Rukshan Chathuranga.
 Software Engineer.
 WSO2, Inc.

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> *Hasunie Adikari*
>>> Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>> blog http://hasuniea.blogspot.com
>>> Mobile:+94715139495
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Roshan Wijesena.
>> Senior Software Engineer-WSO2 Inc.
>> Mobile: *+94719154640 <%2B94719154640>*
>> Email: ros...@wso2.com
>> *WSO2, Inc. :** wso2.com *
>> lean.enterprise.middleware.
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Kalyani Yogeswaranathan*
>
> *Associate software engineer*
> *WSO2 Inc.*
>
> *Mobile: 0776390284*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Praminda Jayawardana*
Software Engineer
WSO2 Inc.; http://wso2.com
Mobile : +94 (0) 716 590818
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error wile building carbon-feature-repository (branch: release-4.2.x)

2016-01-31 Thread Ruwan Abeykoon

Hi Tanya,
AppM v1.1.0 supposed to use carbon kernel 4.4.x, not 4.2.0, as it is just
carbon 4.4.x port of the v1.0.0 without any functionality changes.
Please let me know how you came up with this information,
>>APPM 1.1.0 --> carbon kernel version 4.2.0 --> Jaggery version 0.10.1

Cheers,
Ruwan

Cheers,
Ruwan

On Sun, Jan 31, 2016 at 9:15 PM, Tanya Madurapperuma  wrote:

> Hi Dinusha / Lahiru,
>
> When I checked the APPM releases found out the following according to the
> git.
>
> APPM 1.1.0 --> carbon kernel version 4.2.0 --> Jaggery version 0.10.1
> APPM 2.0.0 --> carbon kernel version 4.4.1 --> Jaggery version 0.10.1
>
> There seems to be a mismatch here. Because jaggery 0.10.1 version is
> released with carbon 4.4.0 but not with 4.2.x
> So there can be compatibility issues in APPM 1.1.0.
>
> I tried adding 0.10.1 version of jaggery in 4.2.x and when I was trying to
> install features pointing to the local p2-repo it threw a version mismatch
> issue in org.apache.commons.logging [1]
>
> Appreciate your insight. Do you require jaggery 0.10.1 to be included in
> 4.4.x p2-repo?
>
> [1] Cannot complete the install because one or more required items could
> not be found. Software being installed: Jaggery Server Feature 0.10.1
> (org.jaggeryjs.server.feature.group 0.10.1) Missing requirement:
> org.jaggeryjs.hostobjects.feed 0.10.1 (org.jaggeryjs.hostobjects.feed
> 0.10.1) requires 'package org.apache.commons.logging [1.2.0,2.0.0)' but it
> could not be found Cannot satisfy dependency: From: Jaggery Server Feature
> 0.10.1 (org.jaggeryjs.server.feature.group 0.10.1) To:
> org.jaggeryjs.hostobjects.feed [0.10.1]
>
> Thanks,
> Tanya
>
> On Fri, Jan 29, 2016 at 10:52 AM, Niranjan Karunanandham <
> niran...@wso2.com> wrote:
>
>> Hi Tanya,
>>
>> I have update the repo. Please find the 4.2.x branch for
>> carbon-feature-repository here [1].
>>
>> [1] - https://github.com/wso2/carbon-feature-repository/tree/4.2.x
>>
>> Regards,
>> Nira
>>
>> On Fri, Jan 29, 2016 at 10:17 AM, Niranjan Karunanandham <
>> niran...@wso2.com> wrote:
>>
>>> Hi Tanya,
>>>
>>> Sorry for the delay. Will reply in this thread once the branch is ready.
>>>
>>> Regards,
>>> Nira
>>>
>>> On Fri, Jan 29, 2016 at 10:05 AM, Tanya Madurapperuma 
>>> wrote:
>>>
 Hi Carbon team,

 If there are no objections, could you please create the above branch.

 Thanks,
 Tanya


 On Tue, Jan 26, 2016 at 4:53 PM, KasunG Gajasinghe 
 wrote:

>
>
> On Tue, Jan 26, 2016 at 2:37 PM, Niranjan Karunanandham <
> niran...@wso2.com> wrote:
>
>> Hi Tanya,
>>
>> There was only a p2-repo release in the GIthub and there exists a
>> branch called release-4.2.x[1]. This is the release branch and this was
>> done by AmilaD for APIM. IMO if we are to do a new p2-repo release for
>> kernel 4.2.0, then we need to rename this branch to 4.2.x and change the
>> version to 4.2.14-SNAPSHOT and new PRs for 4.2.x p2-repo need to be sent 
>> to
>> this branch.
>>
>>
> +1
>
>
>> @Sameera / Kicha: WDYT?
>>
>> [1] -
>> https://github.com/wso2/carbon-feature-repository/tree/release-4.2.x
>>
>> Regards,
>> Nira
>>
>> On Tue, Jan 26, 2016 at 2:15 PM, Tanya Madurapperuma 
>> wrote:
>>
>>> Hi Sameera,
>>>
>>> As per the offline chat I had with Niranjan and Nipuni, in order to
>>> fulfil the above request from the app manager team, we need to have  a
>>> development on-going branch for 4.2.x to send the PR with the missing
>>> features.
>>> But we couldn't locate such branch but the released branch
>>> (release-4.2.x) which has the version as 4.2.13
>>>
>>> Where should we send the PR to? Could you please advise.
>>>
>>> Thanks,
>>> Tanya
>>>
>>> On Mon, Jan 25, 2016 at 11:26 AM, Sinthuja Ragendran <
>>> sinth...@wso2.com> wrote:
>>>
 Hi Tanya,

 Please check on this.

 Thanks,
 Sinthuja.

 On Mon, Jan 18, 2016 at 5:09 PM, Lahiru Cooray 
 wrote:

> adding Manu and Sinthuja
>
> On Mon, Jan 18, 2016 at 5:07 PM, Lahiru Cooray 
> wrote:
>
>> Hi Dakshika,
>> Currently we are using Jaggery Server Feature 0.10.1 and this
>> particular dependency is not included in released P2 repo.
>> (https://github.com/wso2/carbon-feature-repository >
>> release-4.2.x branch)
>>
>> Could you please update the repo with relevant dependencies so we
>> can proceed further.
>>
>> Thank you.
>>
>>
>> On Sat, Jan 9, 2016 at 4:02 PM, Lahiru Cooray 
>> wrote:
>>
>>> Hi Chamila,
>>> Thank you. Now its working.
>>>
>>>

Re: [Dev] Error wile building carbon-feature-repository (branch: release-4.2.x)

2016-01-31 Thread Lahiru Cooray

Hi Tanya,
Please refer the below comments:

APPM 1.1.0 --> carbon kernel version 4.2.0 --> Jaggery version 0.10.1

We noticed that mentioned Jaggery version in the root POM is invalid and
internally jaggery versions are hardcoded and has not used the mentioned
version. Sorry about the inconvenience caused. We will fix this.
Thank you..

On Sun, Jan 31, 2016 at 9:15 PM, Tanya Madurapperuma  wrote:

> Hi Dinusha / Lahiru,
>
> When I checked the APPM releases found out the following according to the
> git.
>
> APPM 1.1.0 --> carbon kernel version 4.2.0 --> Jaggery version 0.10.1
> APPM 2.0.0 --> carbon kernel version 4.4.1 --> Jaggery version 0.10.1
>
> There seems to be a mismatch here. Because jaggery 0.10.1 version is
> released with carbon 4.4.0 but not with 4.2.x
> So there can be compatibility issues in APPM 1.1.0.
>
> I tried adding 0.10.1 version of jaggery in 4.2.x and when I was trying to
> install features pointing to the local p2-repo it threw a version mismatch
> issue in org.apache.commons.logging [1]
>
> Appreciate your insight. Do you require jaggery 0.10.1 to be included in
> 4.4.x p2-repo?
>
> [1] Cannot complete the install because one or more required items could
> not be found. Software being installed: Jaggery Server Feature 0.10.1
> (org.jaggeryjs.server.feature.group 0.10.1) Missing requirement:
> org.jaggeryjs.hostobjects.feed 0.10.1 (org.jaggeryjs.hostobjects.feed
> 0.10.1) requires 'package org.apache.commons.logging [1.2.0,2.0.0)' but it
> could not be found Cannot satisfy dependency: From: Jaggery Server Feature
> 0.10.1 (org.jaggeryjs.server.feature.group 0.10.1) To:
> org.jaggeryjs.hostobjects.feed [0.10.1]
>
> Thanks,
> Tanya
>
> On Fri, Jan 29, 2016 at 10:52 AM, Niranjan Karunanandham <
> niran...@wso2.com> wrote:
>
>> Hi Tanya,
>>
>> I have update the repo. Please find the 4.2.x branch for
>> carbon-feature-repository here [1].
>>
>> [1] - https://github.com/wso2/carbon-feature-repository/tree/4.2.x
>>
>> Regards,
>> Nira
>>
>> On Fri, Jan 29, 2016 at 10:17 AM, Niranjan Karunanandham <
>> niran...@wso2.com> wrote:
>>
>>> Hi Tanya,
>>>
>>> Sorry for the delay. Will reply in this thread once the branch is ready.
>>>
>>> Regards,
>>> Nira
>>>
>>> On Fri, Jan 29, 2016 at 10:05 AM, Tanya Madurapperuma 
>>> wrote:
>>>
 Hi Carbon team,

 If there are no objections, could you please create the above branch.

 Thanks,
 Tanya


 On Tue, Jan 26, 2016 at 4:53 PM, KasunG Gajasinghe 
 wrote:

>
>
> On Tue, Jan 26, 2016 at 2:37 PM, Niranjan Karunanandham <
> niran...@wso2.com> wrote:
>
>> Hi Tanya,
>>
>> There was only a p2-repo release in the GIthub and there exists a
>> branch called release-4.2.x[1]. This is the release branch and this was
>> done by AmilaD for APIM. IMO if we are to do a new p2-repo release for
>> kernel 4.2.0, then we need to rename this branch to 4.2.x and change the
>> version to 4.2.14-SNAPSHOT and new PRs for 4.2.x p2-repo need to be sent 
>> to
>> this branch.
>>
>>
> +1
>
>
>> @Sameera / Kicha: WDYT?
>>
>> [1] -
>> https://github.com/wso2/carbon-feature-repository/tree/release-4.2.x
>>
>> Regards,
>> Nira
>>
>> On Tue, Jan 26, 2016 at 2:15 PM, Tanya Madurapperuma 
>> wrote:
>>
>>> Hi Sameera,
>>>
>>> As per the offline chat I had with Niranjan and Nipuni, in order to
>>> fulfil the above request from the app manager team, we need to have  a
>>> development on-going branch for 4.2.x to send the PR with the missing
>>> features.
>>> But we couldn't locate such branch but the released branch
>>> (release-4.2.x) which has the version as 4.2.13
>>>
>>> Where should we send the PR to? Could you please advise.
>>>
>>> Thanks,
>>> Tanya
>>>
>>> On Mon, Jan 25, 2016 at 11:26 AM, Sinthuja Ragendran <
>>> sinth...@wso2.com> wrote:
>>>
 Hi Tanya,

 Please check on this.

 Thanks,
 Sinthuja.

 On Mon, Jan 18, 2016 at 5:09 PM, Lahiru Cooray 
 wrote:

> adding Manu and Sinthuja
>
> On Mon, Jan 18, 2016 at 5:07 PM, Lahiru Cooray 
> wrote:
>
>> Hi Dakshika,
>> Currently we are using Jaggery Server Feature 0.10.1 and this
>> particular dependency is not included in released P2 repo.
>> (https://github.com/wso2/carbon-feature-repository >
>> release-4.2.x branch)
>>
>> Could you please update the repo with relevant dependencies so we
>> can proceed further.
>>
>> Thank you.
>>
>>
>> On Sat, Jan 9, 2016 at 4:02 PM, Lahiru Cooray 
>> wrote:
>>
>>> Hi Chamila,
>>> Thank you. Now its

Re: [Dev] Error wile building carbon-feature-repository (branch: release-4.2.x)

2016-01-31 Thread Tanya Madurapperuma

On Mon, Feb 1, 2016 at 10:10 AM, Ruwan Abeykoon  wrote:

> Hi Tanya,
> AppM v1.1.0 supposed to use carbon kernel 4.4.x, not 4.2.0, as it is just
> carbon 4.4.x port of the v1.0.0 without any functionality changes.
> Please let me know how you came up with this information,
>

Found out from the root pom of the product repo [1] carbon.kernel.version.
[1] https://github.com/wso2/product-app-manager/blob/release-1.1.0/pom.xml

Thanks,
Tanya

>>APPM 1.1.0 --> carbon kernel version 4.2.0 --> Jaggery version 0.10.1
>
> Cheers,
> Ruwan
>
> Cheers,
> Ruwan
>
> On Sun, Jan 31, 2016 at 9:15 PM, Tanya Madurapperuma 
> wrote:
>
>> Hi Dinusha / Lahiru,
>>
>> When I checked the APPM releases found out the following according to the
>> git.
>>
>> APPM 1.1.0 --> carbon kernel version 4.2.0 --> Jaggery version 0.10.1
>> APPM 2.0.0 --> carbon kernel version 4.4.1 --> Jaggery version 0.10.1
>>
>> There seems to be a mismatch here. Because jaggery 0.10.1 version is
>> released with carbon 4.4.0 but not with 4.2.x
>> So there can be compatibility issues in APPM 1.1.0.
>>
>> I tried adding 0.10.1 version of jaggery in 4.2.x and when I was trying
>> to install features pointing to the local p2-repo it threw a version
>> mismatch issue in org.apache.commons.logging [1]
>>
>> Appreciate your insight. Do you require jaggery 0.10.1 to be included in
>> 4.4.x p2-repo?
>>
>> [1] Cannot complete the install because one or more required items could
>> not be found. Software being installed: Jaggery Server Feature 0.10.1
>> (org.jaggeryjs.server.feature.group 0.10.1) Missing requirement:
>> org.jaggeryjs.hostobjects.feed 0.10.1 (org.jaggeryjs.hostobjects.feed
>> 0.10.1) requires 'package org.apache.commons.logging [1.2.0,2.0.0)' but it
>> could not be found Cannot satisfy dependency: From: Jaggery Server Feature
>> 0.10.1 (org.jaggeryjs.server.feature.group 0.10.1) To:
>> org.jaggeryjs.hostobjects.feed [0.10.1]
>>
>> Thanks,
>> Tanya
>>
>> On Fri, Jan 29, 2016 at 10:52 AM, Niranjan Karunanandham <
>> niran...@wso2.com> wrote:
>>
>>> Hi Tanya,
>>>
>>> I have update the repo. Please find the 4.2.x branch for
>>> carbon-feature-repository here [1].
>>>
>>> [1] - https://github.com/wso2/carbon-feature-repository/tree/4.2.x
>>>
>>> Regards,
>>> Nira
>>>
>>> On Fri, Jan 29, 2016 at 10:17 AM, Niranjan Karunanandham <
>>> niran...@wso2.com> wrote:
>>>
 Hi Tanya,

 Sorry for the delay. Will reply in this thread once the branch is ready.

 Regards,
 Nira

 On Fri, Jan 29, 2016 at 10:05 AM, Tanya Madurapperuma 
 wrote:

> Hi Carbon team,
>
> If there are no objections, could you please create the above branch.
>
> Thanks,
> Tanya
>
>
> On Tue, Jan 26, 2016 at 4:53 PM, KasunG Gajasinghe 
> wrote:
>
>>
>>
>> On Tue, Jan 26, 2016 at 2:37 PM, Niranjan Karunanandham <
>> niran...@wso2.com> wrote:
>>
>>> Hi Tanya,
>>>
>>> There was only a p2-repo release in the GIthub and there exists a
>>> branch called release-4.2.x[1]. This is the release branch and this was
>>> done by AmilaD for APIM. IMO if we are to do a new p2-repo release for
>>> kernel 4.2.0, then we need to rename this branch to 4.2.x and change the
>>> version to 4.2.14-SNAPSHOT and new PRs for 4.2.x p2-repo need to be 
>>> sent to
>>> this branch.
>>>
>>>
>> +1
>>
>>
>>> @Sameera / Kicha: WDYT?
>>>
>>> [1] -
>>> https://github.com/wso2/carbon-feature-repository/tree/release-4.2.x
>>>
>>> Regards,
>>> Nira
>>>
>>> On Tue, Jan 26, 2016 at 2:15 PM, Tanya Madurapperuma >> > wrote:
>>>
 Hi Sameera,

 As per the offline chat I had with Niranjan and Nipuni, in order to
 fulfil the above request from the app manager team, we need to have  a
 development on-going branch for 4.2.x to send the PR with the missing
 features.
 But we couldn't locate such branch but the released branch
 (release-4.2.x) which has the version as 4.2.13

 Where should we send the PR to? Could you please advise.

 Thanks,
 Tanya

 On Mon, Jan 25, 2016 at 11:26 AM, Sinthuja Ragendran <
 sinth...@wso2.com> wrote:

> Hi Tanya,
>
> Please check on this.
>
> Thanks,
> Sinthuja.
>
> On Mon, Jan 18, 2016 at 5:09 PM, Lahiru Cooray 
> wrote:
>
>> adding Manu and Sinthuja
>>
>> On Mon, Jan 18, 2016 at 5:07 PM, Lahiru Cooray 
>> wrote:
>>
>>> Hi Dakshika,
>>> Currently we are using Jaggery Server Feature 0.10.1 and this
>>> particular dependency is not included in released P2 repo.
>>> (https://github.com/wso2/carbon-feature-repository

Re: [Dev] WSO2 Committers += Malintha Amarasinghe

2016-01-31 Thread Chamalee De Silva

Congrats Malintha 

On Mon, Feb 1, 2016 at 9:28 AM, Praminda Jayawardana 
wrote:

> Congratulations Malintha!
>
> On Sun, Jan 31, 2016 at 7:22 PM, Kalyani Yogeswaranathan  > wrote:
>
>> Congrats Malintha!
>>
>> On Sun, Jan 31, 2016 at 8:46 AM, Roshan Wijesena  wrote:
>>
>>> Congratulations !
>>>
>>> On Sat, Jan 30, 2016 at 8:34 PM, Hasunie Adikari 
>>> wrote:
>>>
 Congratz Malintha

 On Sat, Jan 30, 2016 at 7:03 PM, Rukshan Premathunga 
 wrote:

> congratz malintha...
>
> On Sat, Jan 30, 2016 at 6:57 PM, Isuru Wijesinghe 
> wrote:
>
>> Congratzz Malintha :)
>>
>> On Sat, Jan 30, 2016 at 1:38 PM, Nuwan Dias  wrote:
>>
>>> Hi,
>>>
>>> It is with great pleasure we welcome Malintha Amarasinghe as a
>>> WSO2 Committer. @Malintha, congratulations and keep up the good
>>> work!
>>>
>>> Thanks,
>>> NuwanD.
>>>
>>> --
>>> Nuwan Dias
>>>
>>> Technical Lead - WSO2, Inc. http://wso2.com
>>> email : nuw...@wso2.com
>>> Phone : +94 777 775 729
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Isuru Wijesinghe
>> *Software Engineer*
>> WSO2 inc : http://wso2.com
>> lean.enterprise.middleware
>> Mobile: 0710933706
>> isur...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Rukshan Chathuranga.
> Software Engineer.
> WSO2, Inc.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Hasunie Adikari*
 Software Engineer
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware
 blog http://hasuniea.blogspot.com
 Mobile:+94715139495

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Roshan Wijesena.
>>> Senior Software Engineer-WSO2 Inc.
>>> Mobile: *+94719154640 <%2B94719154640>*
>>> Email: ros...@wso2.com
>>> *WSO2, Inc. :** wso2.com *
>>> lean.enterprise.middleware.
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Kalyani Yogeswaranathan*
>>
>> *Associate software engineer*
>> *WSO2 Inc.*
>>
>> *Mobile: 0776390284*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Praminda Jayawardana*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> Mobile : +94 (0) 716 590818
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*


* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Committers += Nuwan Pallewela

2016-01-31 Thread Jasintha Dasanayake

Hi All,

It's my distinct pleasure to welcome Nuwan Pallewela as a WSO2 Committer.

Nuwan has  been a valuable contributor for WSO2 Developer Studio since he
joined WSO2. In recognition of his contributions to WSO2, he has been voted
as a WSO2 Committer.

Nuwan, Congratulations and Keep up the good work!

Thanks and Regards,
/Jasintha

-- 

*Jasintha Dasanayake*

*Senior Software EngineerWSO2 Inc. | http://wso2.com lean
. enterprise . middleware*


*mobile :- 0711368118*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error wile building carbon-feature-repository (branch: release-4.2.x)

2016-01-31 Thread Tanya Madurapperuma

Hi Dinusha / Lahiru,

When I checked the APPM releases found out the following according to the
git.

APPM 1.1.0 --> carbon kernel version 4.2.0 --> Jaggery version 0.10.1
APPM 2.0.0 --> carbon kernel version 4.4.1 --> Jaggery version 0.10.1

There seems to be a mismatch here. Because jaggery 0.10.1 version is
released with carbon 4.4.0 but not with 4.2.x
So there can be compatibility issues in APPM 1.1.0.

I tried adding 0.10.1 version of jaggery in 4.2.x and when I was trying to
install features pointing to the local p2-repo it threw a version mismatch
issue in org.apache.commons.logging [1]

Appreciate your insight. Do you require jaggery 0.10.1 to be included in
4.4.x p2-repo?

[1] Cannot complete the install because one or more required items could
not be found. Software being installed: Jaggery Server Feature 0.10.1
(org.jaggeryjs.server.feature.group 0.10.1) Missing requirement:
org.jaggeryjs.hostobjects.feed 0.10.1 (org.jaggeryjs.hostobjects.feed
0.10.1) requires 'package org.apache.commons.logging [1.2.0,2.0.0)' but it
could not be found Cannot satisfy dependency: From: Jaggery Server Feature
0.10.1 (org.jaggeryjs.server.feature.group 0.10.1) To:
org.jaggeryjs.hostobjects.feed [0.10.1]

Thanks,
Tanya

On Fri, Jan 29, 2016 at 10:52 AM, Niranjan Karunanandham 
wrote:

> Hi Tanya,
>
> I have update the repo. Please find the 4.2.x branch for
> carbon-feature-repository here [1].
>
> [1] - https://github.com/wso2/carbon-feature-repository/tree/4.2.x
>
> Regards,
> Nira
>
> On Fri, Jan 29, 2016 at 10:17 AM, Niranjan Karunanandham <
> niran...@wso2.com> wrote:
>
>> Hi Tanya,
>>
>> Sorry for the delay. Will reply in this thread once the branch is ready.
>>
>> Regards,
>> Nira
>>
>> On Fri, Jan 29, 2016 at 10:05 AM, Tanya Madurapperuma 
>> wrote:
>>
>>> Hi Carbon team,
>>>
>>> If there are no objections, could you please create the above branch.
>>>
>>> Thanks,
>>> Tanya
>>>
>>>
>>> On Tue, Jan 26, 2016 at 4:53 PM, KasunG Gajasinghe 
>>> wrote:
>>>


 On Tue, Jan 26, 2016 at 2:37 PM, Niranjan Karunanandham <
 niran...@wso2.com> wrote:

> Hi Tanya,
>
> There was only a p2-repo release in the GIthub and there exists a
> branch called release-4.2.x[1]. This is the release branch and this was
> done by AmilaD for APIM. IMO if we are to do a new p2-repo release for
> kernel 4.2.0, then we need to rename this branch to 4.2.x and change the
> version to 4.2.14-SNAPSHOT and new PRs for 4.2.x p2-repo need to be sent 
> to
> this branch.
>
>
 +1


> @Sameera / Kicha: WDYT?
>
> [1] -
> https://github.com/wso2/carbon-feature-repository/tree/release-4.2.x
>
> Regards,
> Nira
>
> On Tue, Jan 26, 2016 at 2:15 PM, Tanya Madurapperuma 
> wrote:
>
>> Hi Sameera,
>>
>> As per the offline chat I had with Niranjan and Nipuni, in order to
>> fulfil the above request from the app manager team, we need to have  a
>> development on-going branch for 4.2.x to send the PR with the missing
>> features.
>> But we couldn't locate such branch but the released branch
>> (release-4.2.x) which has the version as 4.2.13
>>
>> Where should we send the PR to? Could you please advise.
>>
>> Thanks,
>> Tanya
>>
>> On Mon, Jan 25, 2016 at 11:26 AM, Sinthuja Ragendran <
>> sinth...@wso2.com> wrote:
>>
>>> Hi Tanya,
>>>
>>> Please check on this.
>>>
>>> Thanks,
>>> Sinthuja.
>>>
>>> On Mon, Jan 18, 2016 at 5:09 PM, Lahiru Cooray 
>>> wrote:
>>>
 adding Manu and Sinthuja

 On Mon, Jan 18, 2016 at 5:07 PM, Lahiru Cooray 
 wrote:

> Hi Dakshika,
> Currently we are using Jaggery Server Feature 0.10.1 and this
> particular dependency is not included in released P2 repo.
> (https://github.com/wso2/carbon-feature-repository >
> release-4.2.x branch)
>
> Could you please update the repo with relevant dependencies so we
> can proceed further.
>
> Thank you.
>
>
> On Sat, Jan 9, 2016 at 4:02 PM, Lahiru Cooray 
> wrote:
>
>> Hi Chamila,
>> Thank you. Now its working.
>>
>> On Fri, Jan 8, 2016 at 6:09 PM, Chamila Adhikarinayake <
>> chami...@wso2.com> wrote:
>>
>>> Hi Lahiru,
>>> Released the missing repos. You can try building it now.
>>>
>>> Chamila
>>>
>>> On Wed, Jan 6, 2016 at 12:32 PM, Lahiru Cooray >> > wrote:
>>>
 Hi APIM team,
 Could you please update the repo with missing versions.

 Thank you..

 On Tue, Jan 5, 2016 at 7:06 PM, Lahiru Cooray

Re: [Dev] WSO2 Committers += Malintha Amarasinghe

2016-01-31 Thread Kalyani Yogeswaranathan

Congrats Malintha!

On Sun, Jan 31, 2016 at 8:46 AM, Roshan Wijesena  wrote:

> Congratulations !
>
> On Sat, Jan 30, 2016 at 8:34 PM, Hasunie Adikari  wrote:
>
>> Congratz Malintha
>>
>> On Sat, Jan 30, 2016 at 7:03 PM, Rukshan Premathunga 
>> wrote:
>>
>>> congratz malintha...
>>>
>>> On Sat, Jan 30, 2016 at 6:57 PM, Isuru Wijesinghe 
>>> wrote:
>>>
 Congratzz Malintha :)

 On Sat, Jan 30, 2016 at 1:38 PM, Nuwan Dias  wrote:

> Hi,
>
> It is with great pleasure we welcome Malintha Amarasinghe as a
> WSO2 Committer. @Malintha, congratulations and keep up the good work!
>
> Thanks,
> NuwanD.
>
> --
> Nuwan Dias
>
> Technical Lead - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Isuru Wijesinghe
 *Software Engineer*
 WSO2 inc : http://wso2.com
 lean.enterprise.middleware
 Mobile: 0710933706
 isur...@wso2.com

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Rukshan Chathuranga.
>>> Software Engineer.
>>> WSO2, Inc.
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Hasunie Adikari*
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>> blog http://hasuniea.blogspot.com
>> Mobile:+94715139495
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Roshan Wijesena.
> Senior Software Engineer-WSO2 Inc.
> Mobile: *+94719154640 <%2B94719154640>*
> Email: ros...@wso2.com
> *WSO2, Inc. :** wso2.com *
> lean.enterprise.middleware.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Kalyani Yogeswaranathan*

*Associate software engineer*
*WSO2 Inc.*

*Mobile: 0776390284*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Hesitating OAuth2 grant type

Re: [Dev] [DEV][JAGGERY] Getting Empty JSON when logging(log.info)

Re: [Dev] Upgrading Smooks to version 1.5

Re: [Dev] [VOTE] Release WSO2 Puppet Modules 1.0.0 RC2

[Dev] How to add patch improvements for Developer Studio update site

Re: [Dev] [VOTE] Release WSO2 Puppet Modules 1.0.0 RC2

Re: [Dev] [VOTE] Release WSO2 Puppet Modules 1.0.0 RC2

[Dev] WSO2 Committers += Chamila Wijayarathna

[Dev] [VOTE] Release WSO2 Puppet Modules 1.0.0 RC2

[Dev] [EMM]Release progress update EMM 2.0.1

[Dev] New global parent pom

Re: [Dev] Upgrading Smooks to version 1.5

Re: [Dev] [VOTE] Release WSO2 Puppet Modules 1.0.0 RC1

Re: [Dev] Error wile building carbon-feature-repository (branch: release-4.2.x)

Re: [Dev] WSO2 Committers += Malintha Amarasinghe

Re: [Dev] Error wile building carbon-feature-repository (branch: release-4.2.x)

Re: [Dev] Error wile building carbon-feature-repository (branch: release-4.2.x)

Re: [Dev] Error wile building carbon-feature-repository (branch: release-4.2.x)

Re: [Dev] WSO2 Committers += Malintha Amarasinghe

[Dev] WSO2 Committers += Nuwan Pallewela

Re: [Dev] Error wile building carbon-feature-repository (branch: release-4.2.x)

Re: [Dev] WSO2 Committers += Malintha Amarasinghe

22 matches

Site Navigation

Mail list logo

Footer information