Re: [Dev] Build failed in trunk with clean repo
I raised the same concern earlier. This sounds not correct. If you are building the trunk, ideally you shouldn't need to build a branch. On Mar 3, 2013 11:00 AM, Eranda Sooriyabandara era...@wso2.com wrote: Hi Dileepa, Yes, the tomcat 7.0.34.wso2v1 bundle is not added to trunk. it's in 4.1.0 branch, and we haven't released it yet. So for the moment we'll have to build (only) orbit 4.1.0 branch before building trunk. Normally we branch from trunk. What I have felt here is on the other way around. When creating the 4.1.0 branch the code what you mentioned missing should be there in the orbit trunk. Isn't it what should be? thanks Eranda * * ___ 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
Re: [Dev] Build failed in trunk with clean repo
On Sun, Mar 3, 2013 at 11:00 AM, Eranda Sooriyabandara era...@wso2.comwrote: Hi Dileepa, Yes, the tomcat 7.0.34.wso2v1 bundle is not added to trunk. it's in 4.1.0 branch, and we haven't released it yet. So for the moment we'll have to build (only) orbit 4.1.0 branch before building trunk. Normally we branch from trunk. What I have felt here is on the other way around. When creating the 4.1.0 branch the code what you mentioned missing should be there in the orbit trunk. Isn't it what should be? Yes, I think the reason is orbit 4.1.0 branch has being created separately without merging from orbit trunk, hence the new tomcat orbit version is not there in trunk. Perhaps we should merge the 4.1.0 orbits to trunk. @Kishanthan, was there any specific reason to add the new tomcat bundles to 4.1.0 branch and not trunk?maybe we can commit them to trunk to avoid build failures? Thanks, Dileepa thanks Eranda * * -- Dileepa Jayakody, Software Engineer, WSO2 Inc. Lean . Enterprise . Middleware Mobile : +94777-857616 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x Products 4.0.7 #93 has FAILED. Change made by Eranda Sooriyabandara.
--- WSO2 Carbon 4.0.x Products 4.0.7 #93 failed. --- Code has been updated by Eranda Sooriyabandara. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-PRO007-93/ - Currently Responsible - Isuru Udana Loku Narangoda (Automatically assigned) Manu Perera (Automatically assigned) Ruchira Wageesha (Automatically assigned) -- Failing Jobs -- - Default Job (Default Stage): 9 tests passed. -- Code Changes -- Eranda Sooriyabandara (166518): Adding rest api new code by Sriragu Eranda Sooriyabandara (166517): Deleting rest api 4.0.8 Eranda Sooriyabandara (166519): Adding REST API patch by Sriragu -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Test Failures on project org.wso2.carbon.user.core branch 4.1.0
Hi Geeth, Did you able to fix this issue ? Thanks ! On Fri, Mar 1, 2013 at 10:30 PM, Pradeep Fernando prad...@wso2.com wrote: Hi Geeth, AFAIR, these are hard coded path related issues, normally pops up right after branching. Find the abstract test class and fix the path. Ignore if it is not the case. I didnt look at the surefire reports. :) On Fri, Mar 1, 2013 at 7:42 PM, Geeth Munasinghe ge...@wso2.com wrote: Hi There are test failures on kernal/4.1.0 Results : Tests in error: testStuff(org.wso2.carbon.user.core.authman.AdvancedPermissionTreeTest) testAddToCache(org.wso2.carbon.user.core.authorization.AuthorizationCacheTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testAddCacheHit(org.wso2.carbon.user.core.authorization.AuthorizationCacheTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testHybridRoleManager(org.wso2.carbon.user.core.hybrid.HybridRoleManagerTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testHybridRoleManager(org.wso2.carbon.user.core.hybrid.AdvancedHybridRoleManagerTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testStuff(org.wso2.carbon.user.core.jdbc.PermissionTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testStuff(org.wso2.carbon.user.core.jdbc.AdvancedJDBCRealmTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testStuff(org.wso2.carbon.user.core.jdbc.JDBCConfigurationTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testStuff(org.wso2.carbon.user.core.jdbc.JDBCRealmTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testAuthorizationClearence(org.wso2.carbon.user.core.jdbc.JDBCRealmTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testStuff(org.wso2.carbon.user.core.jdbc.AdvancedReadOnlyJDBCRealmTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testStuff(org.wso2.carbon.user.core.jdbc.ReadOnlyJDBCRealmTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testClaimsAndProfilePersisting(org.wso2.carbon.user.core.claim.ClaimDAOTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testClaimManger(org.wso2.carbon.user.core.claim.AdvancedClaimManagerTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testProfileConfigManager(org.wso2.carbon.user.core.profile.AdvancedProfileConfigManagerTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testTenantManager(org.wso2.carbon.user.core.tenant.TestTenantManager): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder Tests run: 16, Failures: 0, Errors: 16, Skipped: 0 Please find the sure fire report attached with Thanks *G. K. S. Munasinghe * *Software Engineer,* *WSO2, Inc. http://wso2.com * *lean.enterprise.middleware.* * * email: ge...@wso2.com phone:(+94) 777911226 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Pradeep Fernando* Member, Management Committee - Platform Cloud Technologies Senior Software Engineer;WSO2 Inc.; http://wso2.com blog: http://pradeepfernando.blogspot.com m: +94776603662 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services ; http://ws.apache.org/ Blog ; http://ssagara.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Build failed in trunk with clean repo
On Sun, Mar 3, 2013 at 2:50 PM, Dileepa Jayakody dile...@wso2.com wrote: On Sun, Mar 3, 2013 at 11:00 AM, Eranda Sooriyabandara era...@wso2.comwrote: Hi Dileepa, Yes, the tomcat 7.0.34.wso2v1 bundle is not added to trunk. it's in 4.1.0 branch, and we haven't released it yet. So for the moment we'll have to build (only) orbit 4.1.0 branch before building trunk. Normally we branch from trunk. What I have felt here is on the other way around. When creating the 4.1.0 branch the code what you mentioned missing should be there in the orbit trunk. Isn't it what should be? Yes, I think the reason is orbit 4.1.0 branch has being created separately without merging from orbit trunk, hence the new tomcat orbit version is not there in trunk. Perhaps we should merge the 4.1.0 orbits to trunk. Yes, That was the reason. @Kishanthan, was there any specific reason to add the new tomcat bundles to 4.1.0 branch and not trunk?maybe we can commit them to trunk to avoid build failures? There is no specific reason, please go ahead and merge to the trunk. Thanks ! Thanks, Dileepa thanks Eranda * * -- Dileepa Jayakody, Software Engineer, WSO2 Inc. Lean . Enterprise . Middleware Mobile : +94777-857616 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services ; http://ws.apache.org/ Blog ; http://ssagara.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Build failed in trunk with clean repo
Hi, First of all, there is no orbit trunk as for the moment. There is a svn dir. but that pretty much outdated. Since we need some orbit bundles for the 4.1.0 release, we decided to directly create orbit 4.1.0 branch instead of orbit trunk. So if you are building trunk, please keep in mind there is no orbit trunk at the moment, and the trunk is dependent on the 4.1.0 orbit branch. Guess that'a fair enough. And if this still concerns, we shld be able to release the orbit 4.1.0 now. thanks, On Sun, Mar 3, 2013 at 3:52 PM, Sagara Gunathunga sag...@wso2.com wrote: On Sun, Mar 3, 2013 at 2:50 PM, Dileepa Jayakody dile...@wso2.com wrote: On Sun, Mar 3, 2013 at 11:00 AM, Eranda Sooriyabandara era...@wso2.comwrote: Hi Dileepa, Yes, the tomcat 7.0.34.wso2v1 bundle is not added to trunk. it's in 4.1.0 branch, and we haven't released it yet. So for the moment we'll have to build (only) orbit 4.1.0 branch before building trunk. Normally we branch from trunk. What I have felt here is on the other way around. When creating the 4.1.0 branch the code what you mentioned missing should be there in the orbit trunk. Isn't it what should be? Yes, I think the reason is orbit 4.1.0 branch has being created separately without merging from orbit trunk, hence the new tomcat orbit version is not there in trunk. Perhaps we should merge the 4.1.0 orbits to trunk. Yes, That was the reason. @Kishanthan, was there any specific reason to add the new tomcat bundles to 4.1.0 branch and not trunk?maybe we can commit them to trunk to avoid build failures? There is no specific reason, please go ahead and merge to the trunk. Thanks ! Thanks, Dileepa thanks Eranda * * -- Dileepa Jayakody, Software Engineer, WSO2 Inc. Lean . Enterprise . Middleware Mobile : +94777-857616 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services ; http://ws.apache.org/ Blog ; http://ssagara.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x Platform 4.0.7 #103 has FAILED. Change made by Eranda Sooriyabandara.
--- WSO2 Carbon 4.0.x Platform 4.0.7 #103 failed. --- Code has been updated by Eranda Sooriyabandara. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-PLA007-103/ - Currently Responsible - Eranda Sooriyabandara (Automatically assigned) lakmali Baminiwatta (Automatically assigned) Lalaji Sureshika (Automatically assigned) Madhuka Udantha (Automatically assigned) Nuwan Wimalasekara (Automatically assigned) Thilini Ishaka (Automatically assigned) -- Failing Jobs -- - Default Job (Default Stage): No tests found. -- Code Changes -- Eranda Sooriyabandara (166518): Adding rest api new code by Sriragu Eranda Sooriyabandara (166517): Deleting rest api 4.0.8 Eranda Sooriyabandara (166519): Adding REST API patch by Sriragu -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Build failed in trunk with clean repo
Hi all, What you guys suggest was a workaround and it is fundamentally wrong. Isn't it? One who checking out and build the trunk also need to checkout the 4.1.0 branch and build. Anyway since we don't have people who work with trunk, no trouble. thanks Eranda On Sun, Mar 3, 2013 at 4:09 PM, Supun Malinga sup...@wso2.com wrote: Hi, First of all, there is no orbit trunk as for the moment. There is a svn dir. but that pretty much outdated. Since we need some orbit bundles for the 4.1.0 release, we decided to directly create orbit 4.1.0 branch instead of orbit trunk. So if you are building trunk, please keep in mind there is no orbit trunk at the moment, and the trunk is dependent on the 4.1.0 orbit branch. Guess that'a fair enough. And if this still concerns, we shld be able to release the orbit 4.1.0 now. thanks, On Sun, Mar 3, 2013 at 3:52 PM, Sagara Gunathunga sag...@wso2.com wrote: On Sun, Mar 3, 2013 at 2:50 PM, Dileepa Jayakody dile...@wso2.comwrote: On Sun, Mar 3, 2013 at 11:00 AM, Eranda Sooriyabandara era...@wso2.comwrote: Hi Dileepa, Yes, the tomcat 7.0.34.wso2v1 bundle is not added to trunk. it's in 4.1.0 branch, and we haven't released it yet. So for the moment we'll have to build (only) orbit 4.1.0 branch before building trunk. Normally we branch from trunk. What I have felt here is on the other way around. When creating the 4.1.0 branch the code what you mentioned missing should be there in the orbit trunk. Isn't it what should be? Yes, I think the reason is orbit 4.1.0 branch has being created separately without merging from orbit trunk, hence the new tomcat orbit version is not there in trunk. Perhaps we should merge the 4.1.0 orbits to trunk. Yes, That was the reason. @Kishanthan, was there any specific reason to add the new tomcat bundles to 4.1.0 branch and not trunk?maybe we can commit them to trunk to avoid build failures? There is no specific reason, please go ahead and merge to the trunk. Thanks ! Thanks, Dileepa thanks Eranda * * -- Dileepa Jayakody, Software Engineer, WSO2 Inc. Lean . Enterprise . Middleware Mobile : +94777-857616 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services ; http://ws.apache.org/ Blog ; http://ssagara.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Eranda Sooriyabandara *Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com * * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Build failed in trunk with clean repo
Hi Eranda, On Sun, Mar 3, 2013 at 6:00 PM, Eranda Sooriyabandara era...@wso2.comwrote: Hi all, What you guys suggest was a workaround and it is fundamentally wrong. Isn't it? One who checking out and build the trunk also need to checkout the 4.1.0 branch and build. Anyway since we don't have people who work with trunk, no trouble. There will be a little annoyance until we do the 4.1.0 release which is due in less than two weeks. When it's released, we will be hosting the orbit bundles in wso2 nexus maven repo. After that, you do not have to build the 4.1.0 orbit branch. We have only maintained 4.1.0 orbit branch, and haven't worked on orbit trunk. This isn't really a workaround rather an annoyance until the release. Hope you understand. thanks Eranda On Sun, Mar 3, 2013 at 4:09 PM, Supun Malinga sup...@wso2.com wrote: Hi, First of all, there is no orbit trunk as for the moment. There is a svn dir. but that pretty much outdated. Since we need some orbit bundles for the 4.1.0 release, we decided to directly create orbit 4.1.0 branch instead of orbit trunk. So if you are building trunk, please keep in mind there is no orbit trunk at the moment, and the trunk is dependent on the 4.1.0 orbit branch. Guess that'a fair enough. And if this still concerns, we shld be able to release the orbit 4.1.0 now. thanks, On Sun, Mar 3, 2013 at 3:52 PM, Sagara Gunathunga sag...@wso2.comwrote: On Sun, Mar 3, 2013 at 2:50 PM, Dileepa Jayakody dile...@wso2.comwrote: On Sun, Mar 3, 2013 at 11:00 AM, Eranda Sooriyabandara era...@wso2.com wrote: Hi Dileepa, Yes, the tomcat 7.0.34.wso2v1 bundle is not added to trunk. it's in 4.1.0 branch, and we haven't released it yet. So for the moment we'll have to build (only) orbit 4.1.0 branch before building trunk. Normally we branch from trunk. What I have felt here is on the other way around. When creating the 4.1.0 branch the code what you mentioned missing should be there in the orbit trunk. Isn't it what should be? Yes, I think the reason is orbit 4.1.0 branch has being created separately without merging from orbit trunk, hence the new tomcat orbit version is not there in trunk. Perhaps we should merge the 4.1.0 orbits to trunk. Yes, That was the reason. @Kishanthan, was there any specific reason to add the new tomcat bundles to 4.1.0 branch and not trunk?maybe we can commit them to trunk to avoid build failures? There is no specific reason, please go ahead and merge to the trunk. Thanks ! Thanks, Dileepa thanks Eranda * * -- Dileepa Jayakody, Software Engineer, WSO2 Inc. Lean . Enterprise . Middleware Mobile : +94777-857616 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services ; http://ws.apache.org/ Blog ; http://ssagara.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Eranda Sooriyabandara *Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com * * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Kasun Gajasinghe* Software Engineer; Development Technologies Team, WSO2 Inc.; http://wso2.com , *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813* *linked-in: *http://lk.linkedin.com/in/gajasinghe* * *blog: **http://blog.kasunbg.org* http://blog.kasunbg.org* twitter: **http://twitter.com/kasunbg* http://twitter.com/kasunbg* * On Sun, Mar 3, 2013 at 6:00 PM, Eranda Sooriyabandara era...@wso2.comwrote: Hi all, What you guys suggest was a workaround and it is fundamentally wrong. Isn't it? One who checking out and build the trunk also need to checkout the 4.1.0 branch and build. Anyway since we don't have people who work with trunk, no trouble. thanks Eranda On Sun, Mar 3, 2013 at 4:09 PM, Supun Malinga sup...@wso2.com wrote: Hi, First of all, there is no orbit trunk as for the moment. There is a svn dir. but that pretty much outdated. Since we need some orbit bundles for the 4.1.0 release, we decided to directly create orbit 4.1.0 branch instead of orbit trunk. So if you are building trunk, please keep in mind there is no orbit trunk at the moment, and the trunk is dependent on the 4.1.0 orbit branch. Guess that'a fair enough. And if this still concerns, we shld be able to release the orbit 4.1.0 now. thanks, On Sun, Mar 3, 2013 at 3:52 PM, Sagara Gunathunga sag...@wso2.comwrote:
Re: [Dev] Test Failures on project org.wso2.carbon.user.core branch 4.1.0
Hi I am working on this now. Thanks *G. K. S. Munasinghe * *Software Engineer,* *WSO2, Inc. http://wso2.com * *lean.enterprise.middleware.* * * email: ge...@wso2.com phone:(+94) 777911226 On Sun, Mar 3, 2013 at 3:46 PM, Sagara Gunathunga sag...@wso2.com wrote: Hi Geeth, Did you able to fix this issue ? Thanks ! On Fri, Mar 1, 2013 at 10:30 PM, Pradeep Fernando prad...@wso2.comwrote: Hi Geeth, AFAIR, these are hard coded path related issues, normally pops up right after branching. Find the abstract test class and fix the path. Ignore if it is not the case. I didnt look at the surefire reports. :) On Fri, Mar 1, 2013 at 7:42 PM, Geeth Munasinghe ge...@wso2.com wrote: Hi There are test failures on kernal/4.1.0 Results : Tests in error: testStuff(org.wso2.carbon.user.core.authman.AdvancedPermissionTreeTest) testAddToCache(org.wso2.carbon.user.core.authorization.AuthorizationCacheTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testAddCacheHit(org.wso2.carbon.user.core.authorization.AuthorizationCacheTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testHybridRoleManager(org.wso2.carbon.user.core.hybrid.HybridRoleManagerTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testHybridRoleManager(org.wso2.carbon.user.core.hybrid.AdvancedHybridRoleManagerTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testStuff(org.wso2.carbon.user.core.jdbc.PermissionTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testStuff(org.wso2.carbon.user.core.jdbc.AdvancedJDBCRealmTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testStuff(org.wso2.carbon.user.core.jdbc.JDBCConfigurationTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testStuff(org.wso2.carbon.user.core.jdbc.JDBCRealmTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testAuthorizationClearence(org.wso2.carbon.user.core.jdbc.JDBCRealmTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testStuff(org.wso2.carbon.user.core.jdbc.AdvancedReadOnlyJDBCRealmTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testStuff(org.wso2.carbon.user.core.jdbc.ReadOnlyJDBCRealmTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testClaimsAndProfilePersisting(org.wso2.carbon.user.core.claim.ClaimDAOTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testClaimManger(org.wso2.carbon.user.core.claim.AdvancedClaimManagerTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testProfileConfigManager(org.wso2.carbon.user.core.profile.AdvancedProfileConfigManagerTest): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder testTenantManager(org.wso2.carbon.user.core.tenant.TestTenantManager): Could not initialize class org.wso2.carbon.context.internal.CarbonContextDataHolder Tests run: 16, Failures: 0, Errors: 16, Skipped: 0 Please find the sure fire report attached with Thanks *G. K. S. Munasinghe * *Software Engineer,* *WSO2, Inc. http://wso2.com * *lean.enterprise.middleware.* * * email: ge...@wso2.com phone:(+94) 777911226 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Pradeep Fernando* Member, Management Committee - Platform Cloud Technologies Senior Software Engineer;WSO2 Inc.; http://wso2.com blog: http://pradeepfernando.blogspot.com m: +94776603662 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services ; http://ws.apache.org/ Blog ; http://ssagara.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x Products 4.0.7 #94 has FAILED. Change made by Suresh Attanayake, Eranda Sooriyabandara and Janaka Ranabahu.
--- WSO2 Carbon 4.0.x Products 4.0.7 #94 failed. --- Code has been updated by Suresh Attanayake, Eranda Sooriyabandara, Janaka Ranabahu. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-PRO007-94/ - Currently Responsible - Isuru Udana Loku Narangoda (Automatically assigned) Manu Perera (Automatically assigned) Ruchira Wageesha (Automatically assigned) -- Failing Jobs -- - Default Job (Default Stage): 9 tests passed. -- Code Changes -- Suresh Attanayake (166527): updated stub for openid connect Suresh Attanayake (166526): adding new method to the client to read user claims Janaka Ranabahu (166524): Adding the latest configs used in alpha 1 -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Registry question
Hi, Can someone please answer the question at [1]. This guy is working on one of our projects using G-Reg. Thanks, Isuru [1] http://stackoverflow.com/questions/15188317/how-to-get-symbolic-link-information-for-wso2-registry-resource ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x Platform 4.0.7 #104 has FAILED. Change made by Suresh Attanayake, Eranda Sooriyabandara and Janaka Ranabahu.
--- WSO2 Carbon 4.0.x Platform 4.0.7 #104 failed. --- Code has been updated by Suresh Attanayake, Eranda Sooriyabandara, Janaka Ranabahu. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-PLA007-104/ - Currently Responsible - Eranda Sooriyabandara (Automatically assigned) lakmali Baminiwatta (Automatically assigned) Lalaji Sureshika (Automatically assigned) Madhuka Udantha (Automatically assigned) Nuwan Wimalasekara (Automatically assigned) Thilini Ishaka (Automatically assigned) -- Failing Jobs -- - Default Job (Default Stage): No tests found. -- Code Changes -- Suresh Attanayake (166527): updated stub for openid connect Suresh Attanayake (166526): adding new method to the client to read user claims Janaka Ranabahu (166524): Adding the latest configs used in alpha 1 -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x - Nightly Kernel_4.0.7 #5 has FAILED. Change made by 5 authors.
--- WSO2 Carbon 4.0.x - Nightly Kernel_4.0.7 #5 failed. --- This build occurred because it is a dependant of WCB002-NORB004-55. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB002-NKER005-5/ - Currently Responsible - No one is responsible for fixing this build. -- Failing Jobs -- - Default Job (Default Stage): No tests found. -- Code Changes -- Asela Pathberiya (166536): Fix UI issues in user mgt pages Kasun Indrasiri (166516): Changing axis2 version Asela Pathberiya (166538): fix sub string issue -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x Products 4.0.7 #95 has FAILED. Change made by Suresh Attanayake, Eranda Sooriyabandara and Dinusha Dilrukshi.
--- WSO2 Carbon 4.0.x Products 4.0.7 #95 failed. --- Code has been updated by Suresh Attanayake, Eranda Sooriyabandara, Dinusha Dilrukshi. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-PRO007-95/ - Currently Responsible - Isuru Udana Loku Narangoda (Automatically assigned) Manu Perera (Automatically assigned) Ruchira Wageesha (Automatically assigned) -- Failing Jobs -- - Default Job (Default Stage): 9 tests passed. -- Code Changes -- Suresh Attanayake (166531): adding bean Eranda Sooriyabandara (166540): Deleting for adding new Dinusha Dilrukshi (166534): updating dependency versions. -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x Kernel 4.0.7 #24 has FAILED. Change made by Prabath Siriwardena and Johann Nallathamby.
--- WSO2 Carbon 4.0.x Kernel 4.0.7 #24 failed. --- Code has been updated by Prabath Siriwardena, Johann Nallathamby. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-KER007-24/ - Currently Responsible - Asela Pathberiya (Assigned by Maheshika Goonetilleke) -- Failing Jobs -- - Default Job (Default Stage): No tests found. -- Code Changes -- Johann Nallathamby (166550): Committing patch provided by Sriragu Prabath Siriwardena (166553): adding informix script -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x Platform 4.0.7 #105 has FAILED. Change made by Eranda Sooriyabandara, Prabath Siriwardena and Dinusha Dilrukshi.
--- WSO2 Carbon 4.0.x Platform 4.0.7 #105 failed. --- Code has been updated by Eranda Sooriyabandara, Prabath Siriwardena, Dinusha Dilrukshi. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-PLA007-105/ - Currently Responsible - Eranda Sooriyabandara (Automatically assigned) lakmali Baminiwatta (Automatically assigned) Lalaji Sureshika (Automatically assigned) Madhuka Udantha (Automatically assigned) Nuwan Wimalasekara (Automatically assigned) Thilini Ishaka (Automatically assigned) -- Failing Jobs -- - Default Job (Default Stage): No tests found. -- Code Changes -- Prabath Siriwardena (166557): fixing the string for informix Prabath Siriwardena (166556): adding informix support Dinusha Dilrukshi (166534): updating dependency versions. -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Two bam modules in components and features
Hi bam folks, components/bam, components/bam2 features/bam, features/bam2 I know bam2 is the improved bam version. But do we still use both?. We should either merge or remove /bam. thanks, -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x Products 4.0.7 #96 has FAILED. Change made by Eranda Sooriyabandara and Prabath Siriwardena.
--- WSO2 Carbon 4.0.x Products 4.0.7 #96 failed. --- Code has been updated by Eranda Sooriyabandara, Prabath Siriwardena. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-PRO007-96/ - Currently Responsible - Isuru Udana Loku Narangoda (Automatically assigned) Manu Perera (Automatically assigned) Ruchira Wageesha (Automatically assigned) -- Failing Jobs -- - Default Job (Default Stage): 9 tests passed. -- Code Changes -- Eranda Sooriyabandara (166549): Removing Prabath Siriwardena (166557): fixing the string for informix Prabath Siriwardena (166556): adding informix support -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] BAM 2.2.0 toolbox issue in windows7
Hi all; I tried with BAM 2.0.1 ..No luck..I tried the phonetollbox sample.same issue i got.. Created the jira with the details https://wso2.org/jira/browse/BAM-1106 Thanks I On 3 March 2013 10:15, Tharindu Mathew thari...@wso2.com wrote: Thanks Shelan. Ratha, can you try with a fresh pack? Just a log a jira as this maybe a genuine issue... On Sun, Mar 3, 2013 at 10:11 AM, Shelan Perera she...@wso2.com wrote: Hi, On Sat, Mar 2, 2013 at 8:30 PM, Tharindu Mathew thari...@wso2.comwrote: Great Shelan. Just double checking whether it's 2.2.0 and Windows 7? Yes. BAM 2.2.0 (Downloaded yesterday from OT and ) and windows 7 On Sun, Mar 3, 2013 at 9:34 AM, Shelan Perera she...@wso2.com wrote: Hi, FYI, I was able to run Mediation Toolbox yesterday in Windows without any issue after installing cygwin. Thanks On Sat, Mar 2, 2013 at 7:58 PM, Tharindu Mathew thari...@wso2.comwrote: Buddhika, I guess we need to do a 2.2.1 if this is regression is present. Ratha, can you confirm? On Fri, Mar 1, 2013 at 7:07 PM, Buddhika Chamith buddhi...@wso2.comwrote: Can you check the same with BAM 2.0.1? I suspect this might be a regression due to some reason fixes done to Hadoop and Hive. Regards Buddhika On Fri, Mar 1, 2013 at 8:04 AM, Vijayaratha Vijayasingam rat...@wso2.com wrote: Hi all; I have installed cygwin and when i tried to execute a hivescript im getting following[1] folder not found issue. That particular folder is existing and i tried coping the exact folder path in the address bar and it finds the folder location correctly. There is no any permission issues. Does anybody know how can i fix this issue? [1] at org.apache.hadoop.util.RunJar.main(RunJar.java:156) Job Submission failed with exception 'org.apache.hadoop.util.Shell$ExitCodeException(chmod: C:\Users\TOSHIBA\Downloads\wso2bam-2.2.0\tmp\hadoop\local\ -532323203\archive\6488787564537180850_-311551688_637947327\file\C\Users\TOSHIBA\Downloads\wso2bam-2.2.0\repository\components\configuration\org.eclip se.osgi\bundles\55\1\.cp\hive-builtins-0.8.1-wso2v6.jar-work-3046470035301427082: No such file or directory )' [2013-03-01 18:27:12,460] ERROR {org.apache.hadoop.hive.ql.exec.ExecDriver} - Job Submission failed with exception 'org.apache.hadoop.util.Shell$Exit CodeException(chmod: C:\Users\TOSHIBA\Downloads\wso2bam-2.2.0\tmp\hadoop\local\-532323203\archive\6488787564537180850_-311551688_637947327\file\C\User s\TOSHIBA\Downloads\wso2bam-2.2.0\repository\components\configuration\org.eclipse.osgi\bundles\55\1\.cp\hive-builtins-0.8.1-wso2v6.jar-work- 3046470035 301427082: No such file or directory )' org.apache.hadoop.util.Shell$ExitCodeException: chmod: C:\Users\TOSHIBA\Downloads\wso2bam-2.2.0\tmp\hadoop\local\-532323203\archive\648878756453718085 0_-311551688_637947327\file\C\Users\TOSHIBA\Downloads\wso2bam-2.2.0\repository\components\configuration\org.eclipse.osgi\bundles\55\1\.cp\hive-builtin s-0.8.1-wso2v6.jar-work-3046470035301427082: No such file or directory ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Regards, Tharindu Mathew Associate Technical Lead, WSO2 BAM Member - Data Mgmt. Committee blog: http://tharindumathew.com/ M: +9459908 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Shelan Perera* Software Engineer ** *WSO2, Inc. : wso2.com* lean.enterprise.middleware. *Home Page* : shelan.org *Blog* : blog.shelan.org *Linked-i*n : http://www.linkedin.com/pub/shelan-perera/a/194/465 *Twitter* :https://twitter.com/#!/shelan *Mobile* : +94 772 604 402 -- Regards, Tharindu Mathew Associate Technical Lead, WSO2 BAM Member - Data Mgmt. Committee blog: http://tharindumathew.com/ M: +9459908 -- *Shelan Perera* Software Engineer ** *WSO2, Inc. : wso2.com* lean.enterprise.middleware. *Home Page* : shelan.org *Blog* : blog.shelan.org *Linked-i*n : http://www.linkedin.com/pub/shelan-perera/a/194/465 *Twitter* :https://twitter.com/#!/shelan *Mobile* : +94 772 604 402 -- Regards, Tharindu Mathew Associate Technical Lead, WSO2 BAM Member - Data Mgmt. Committee blog: http://tharindumathew.com/ M: +9459908 ___ 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
Re: [Dev] Two bam modules in components and features
+1, Please remove from both trunk and branch(4.1.0) accordingly. thanks, On Mon, Mar 4, 2013 at 10:01 AM, Amila Maha Arachchi ami...@wso2.comwrote: Yes, now we are not using them. Lets remove and fix if there are any build failures. On Mon, Mar 4, 2013 at 9:49 AM, Kasun Weranga kas...@wso2.com wrote: Hi, We didn't remove it because stratos billing and metering was using those earlier bam components until they move to new bam. I think now we can remove it. When removing if they still have references to old bam components there can be build failures. So need check that before removing. Thanks, KasunW. On Sun, Mar 3, 2013 at 7:24 PM, Supun Malinga sup...@wso2.com wrote: Hi bam folks, components/bam, components/bam2 features/bam, features/bam2 I know bam2 is the improved bam version. But do we still use both?. We should either merge or remove /bam. thanks, -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 -- *Kasun Weranga* ** Member, Management Committee - Data Technologies Software Engineer *WSO2, Inc. *lean.enterprise.middleware. mobile : +94 772314602 http://sanjeewamalalgoda.blogspot.com/blog : http://kasunweranga.blogspot.com/ -- *Amila Maharachchi* Technical Lead Member, Management Committee - Cloud Platform TG WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Build failed in trunk with clean repo
Hi, Since most folks who are starting to build trunk get confused of this we will add orbit 4.1.0 bundles as externals to the orbit trunk, for the moment. After orbit 4.1.0 is released, we will remove the external. Also right now wadl-core is duplicated in both trunk and branch. Either upgrade the trunk version or remove the trunk wadl-core and add an external from the branch. thanks, On Sun, Mar 3, 2013 at 6:12 PM, Kasun Gajasinghe kas...@wso2.com wrote: Hi Eranda, On Sun, Mar 3, 2013 at 6:00 PM, Eranda Sooriyabandara era...@wso2.comwrote: Hi all, What you guys suggest was a workaround and it is fundamentally wrong. Isn't it? One who checking out and build the trunk also need to checkout the 4.1.0 branch and build. Anyway since we don't have people who work with trunk, no trouble. There will be a little annoyance until we do the 4.1.0 release which is due in less than two weeks. When it's released, we will be hosting the orbit bundles in wso2 nexus maven repo. After that, you do not have to build the 4.1.0 orbit branch. We have only maintained 4.1.0 orbit branch, and haven't worked on orbit trunk. This isn't really a workaround rather an annoyance until the release. Hope you understand. thanks Eranda On Sun, Mar 3, 2013 at 4:09 PM, Supun Malinga sup...@wso2.com wrote: Hi, First of all, there is no orbit trunk as for the moment. There is a svn dir. but that pretty much outdated. Since we need some orbit bundles for the 4.1.0 release, we decided to directly create orbit 4.1.0 branch instead of orbit trunk. So if you are building trunk, please keep in mind there is no orbit trunk at the moment, and the trunk is dependent on the 4.1.0 orbit branch. Guess that'a fair enough. And if this still concerns, we shld be able to release the orbit 4.1.0 now. thanks, On Sun, Mar 3, 2013 at 3:52 PM, Sagara Gunathunga sag...@wso2.comwrote: On Sun, Mar 3, 2013 at 2:50 PM, Dileepa Jayakody dile...@wso2.comwrote: On Sun, Mar 3, 2013 at 11:00 AM, Eranda Sooriyabandara era...@wso2.com wrote: Hi Dileepa, Yes, the tomcat 7.0.34.wso2v1 bundle is not added to trunk. it's in 4.1.0 branch, and we haven't released it yet. So for the moment we'll have to build (only) orbit 4.1.0 branch before building trunk. Normally we branch from trunk. What I have felt here is on the other way around. When creating the 4.1.0 branch the code what you mentioned missing should be there in the orbit trunk. Isn't it what should be? Yes, I think the reason is orbit 4.1.0 branch has being created separately without merging from orbit trunk, hence the new tomcat orbit version is not there in trunk. Perhaps we should merge the 4.1.0 orbits to trunk. Yes, That was the reason. @Kishanthan, was there any specific reason to add the new tomcat bundles to 4.1.0 branch and not trunk?maybe we can commit them to trunk to avoid build failures? There is no specific reason, please go ahead and merge to the trunk. Thanks ! Thanks, Dileepa thanks Eranda * * -- Dileepa Jayakody, Software Engineer, WSO2 Inc. Lean . Enterprise . Middleware Mobile : +94777-857616 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services ; http://ws.apache.org/ Blog ; http://ssagara.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Eranda Sooriyabandara *Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com * * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Kasun Gajasinghe* Software Engineer; Development Technologies Team, WSO2 Inc.; http://wso2.com , *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813* *linked-in: *http://lk.linkedin.com/in/gajasinghe* * *blog: **http://blog.kasunbg.org* http://blog.kasunbg.org* twitter: **http://twitter.com/kasunbg* http://twitter.com/kasunbg* * On Sun, Mar 3, 2013 at 6:00 PM, Eranda Sooriyabandara era...@wso2.comwrote: Hi all, What you guys suggest was a workaround and it is fundamentally wrong. Isn't it? One who checking out and build the trunk also need to checkout the 4.1.0 branch and build. Anyway since we don't have people who work with trunk, no trouble. thanks Eranda On Sun, Mar 3, 2013 at 4:09 PM, Supun Malinga sup...@wso2.com wrote: Hi, First of all, there is no orbit trunk as for the moment. There is a svn dir. but that
[Dev] Uploading Same Jaggery App Again Without Deleting Previous One
Hi All, $subject fails with back end log Jaggery app with the same name already exists.But in the case of Web App it first undeploy the previous one and deploy the new one.Which is the correct behavior ? Thanks -- ajanthan -- Ajanthan Balachandiran Software Engineer; WSO2, Inc.; http://wso2.com/ email: ajant...@wso2.com; cell: +94775581497 blog: http://bkayts.blogspot.com/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x Platform 4.0.7 #106 has FAILED. Change made by Eranda Sooriyabandara.
--- WSO2 Carbon 4.0.x Platform 4.0.7 #106 failed. --- Code has been updated by Eranda Sooriyabandara. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-PLA007-106/ - Currently Responsible - Eranda Sooriyabandara (Automatically assigned) lakmali Baminiwatta (Automatically assigned) Lalaji Sureshika (Automatically assigned) Madhuka Udantha (Automatically assigned) Nuwan Wimalasekara (Automatically assigned) Thilini Ishaka (Automatically assigned) -- Failing Jobs -- - Default Job (Default Stage): No tests found. -- Code Changes -- Eranda Sooriyabandara (166565): Fixing version inssue -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Uploading Same Jaggery App Again Without Deleting Previous One
Hi Ajanthan, This has been done intentionally to prevent accidental replacement of any existing apps. i.e. Let's say in a running server, there is an active app called foo. Then some other user in the same role, logs into the server and upload another app as foo without knowing about the existing app. Then the existing app will be replaced with a totally different one without knowing everyone. That's why it is needed to delete prior to the upload. Anyway, I don't thing just replacing the existing one would be a better approach. Instead we can notify the user about the existing one and get the confirmation, then replace or cancel. WDYT? On Mon, Mar 4, 2013 at 12:16 PM, Ajanthan Balachandran ajant...@wso2.comwrote: Hi All, $subject fails with back end log Jaggery app with the same name already exists.But in the case of Web App it first undeploy the previous one and deploy the new one.Which is the correct behavior ? Thanks -- ajanthan -- Ajanthan Balachandiran Software Engineer; WSO2, Inc.; http://wso2.com/ email: ajant...@wso2.com; cell: +94775581497 blog: http://bkayts.blogspot.com/ Lean . Enterprise . Middleware -- *Ruchira Wageesha Senior Software Engineer Member, Management Committee, Development Technologies* *WSO2 Inc. - lean . enterprise . middleware | wso2.com* * email: ruch...@wso2.com, blog: ruchirawageesha.blogspot.com, mobile: +94 77 5493444* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Test failures due to changes of org.wso2.carbon.user.mgt
On Mon, Mar 4, 2013 at 11:42 AM, Dimuthu De Lanerolle dimut...@wso2.comwrote: Hi All, This is fixed now. But i'm getting following compilation failure with latest updates. Please check again. [INFO] BUILD FAILURE [INFO] [INFO] Total time: 11.355s [INFO] Finished at: Mon Mar 04 12:41:38 IST 2013 [INFO] Final Memory: 56M/704M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile (default-testCompile) on project org.wso2.carbon.registry.test.ui: Compilation failure: Compilation failure: [ERROR] /home/ajith/wso2/build/branches/4.0.4/platform/4.0.0/products/greg/4.6.0/modules/integration/registry/tests-ui/src/test/java/org/wso2/carbon/registry/integration/ui/CarbonTestCase.java:[9,53] cannot find symbol [ERROR] symbol : class CappHome [ERROR] location: package org.wso2.carbon.automation.api.selenium.carbon [ERROR] /home/ajith/wso2/build/branches/4.0.4/platform/4.0.0/products/greg/4.6.0/modules/integration/registry/tests-ui/src/test/java/org/wso2/carbon/registry/integration/ui/CarbonTestCase.java:[9,53] cannot find symbol [ERROR] symbol : class CappHome [ERROR] location: package org.wso2.carbon.automation.api.selenium.carbon [ERROR] /home/ajith/wso2/build/branches/4.0.4/platform/4.0.0/products/greg/4.6.0/modules/integration/registry/tests-ui/src/test/java/org/wso2/carbon/registry/integration/ui/CarbonTestCase.java:[30,8] cannot find symbol [ERROR] symbol : class CappHome [ERROR] location: class org.wso2.carbon.registry.integration.ui.CarbonTestCase [ERROR] /home/ajith/wso2/build/branches/4.0.4/platform/4.0.0/products/greg/4.6.0/modules/integration/registry/tests-ui/src/test/java/org/wso2/carbon/registry/integration/ui/CarbonTestCase.java:[30,32] cannot find symbol [ERROR] symbol : class CappHome [ERROR] location: class org.wso2.carbon.registry.integration.ui.CarbonTestCase [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :org.wso2.carbon.registry.test.ui Thanks Ajith Regards, On Fri, Mar 1, 2013 at 11:07 AM, Dimuthu De Lanerolle dimut...@wso2.comwrote: Hi All, There are some API changes (due to org.wso2.carbon.user.mgt.stub change) needs to be fixed. I am still working on this. Regards, On Fri, Mar 1, 2013 at 10:52 AM, Eranda Sooriyabandara era...@wso2.comwrote: Hi Dimuthu, Still I don't see user management dependencies updated. Update the dependencies and fix the build failures will make things easier. thanks Eranda On Fri, Mar 1, 2013 at 10:49 AM, Ajith Vitharana aji...@wso2.comwrote: Hi DimuthuD On Thu, Feb 28, 2013 at 5:46 PM, Krishantha Samaraweera krishan...@wso2.com wrote: Hi Dimuthud, Can you please check this issue. Seems like user mgt API has been changed. We will have to change the framework accordingly. Any update on this ? Thanks Ajith Thanks, Krishantha. On Thu, Feb 28, 2013 at 5:05 PM, Eranda Sooriyabandara era...@wso2.com wrote: Hi Krishantha, We face this problem due to clarity framework doesn't have the latest dependencies of user management bundles. Can you please have a look at them. thanks Eranda * * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ajith Vitharana. Senior Software Engineer, Member,Management Committee, Integration Technologies. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 -- *Eranda Sooriyabandara *Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com * * -- Dimuthu De Lanerolle Software Engineer (Automation) WSO2 Inc. -- Dimuthu De Lanerolle Software Engineer (Automation) WSO2 Inc. -- Ajith Vitharana. Senior Software Engineer, Member,Management Committee, Integration Technologies. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Uploading Same Jaggery App Again Without Deleting Previous One
On Mon, Mar 4, 2013 at 12:16 PM, Ajanthan Balachandran ajant...@wso2.comwrote: Hi All, $subject fails with back end log Jaggery app with the same name already exists.But in the case of Web App it first undeploy the previous one and deploy the new one.Which is the correct behavior ? I think Jaggery behaves correctly. Imagine, user X creates an app called Foo and uses it, and later User Y logs in and add a new app called foo, If we silently replace the app, then its a problem. we give a warning. If its a conscious decision, he can remove the old foo first and deploy the new one. Regards, /Nuwan Thanks -- ajanthan -- Ajanthan Balachandiran Software Engineer; WSO2, Inc.; http://wso2.com/ email: ajant...@wso2.com; cell: +94775581497 blog: http://bkayts.blogspot.com/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Thanks Regards, Nuwan Bandara Associate Technical Lead Member, MC, Development Technologies WSO2 Inc. - lean . enterprise . middleware | http://wso2.com blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763 9629 * http://www.nuwanbando.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Test failures due to changes of org.wso2.carbon.user.mgt
Hi Ajith, Can you please get the svn update on clarity-framework 4.0.8 and build. It will solve this issue. because there was a change of a class name. Thanks, Nuwanw On Mon, Mar 4, 2013 at 12:43 PM, Ajith Vitharana aji...@wso2.com wrote: On Mon, Mar 4, 2013 at 11:42 AM, Dimuthu De Lanerolle dimut...@wso2.comwrote: Hi All, This is fixed now. But i'm getting following compilation failure with latest updates. Please check again. [INFO] BUILD FAILURE [INFO] [INFO] Total time: 11.355s [INFO] Finished at: Mon Mar 04 12:41:38 IST 2013 [INFO] Final Memory: 56M/704M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile (default-testCompile) on project org.wso2.carbon.registry.test.ui: Compilation failure: Compilation failure: [ERROR] /home/ajith/wso2/build/branches/4.0.4/platform/4.0.0/products/greg/4.6.0/modules/integration/registry/tests-ui/src/test/java/org/wso2/carbon/registry/integration/ui/CarbonTestCase.java:[9,53] cannot find symbol [ERROR] symbol : class CappHome [ERROR] location: package org.wso2.carbon.automation.api.selenium.carbon [ERROR] /home/ajith/wso2/build/branches/4.0.4/platform/4.0.0/products/greg/4.6.0/modules/integration/registry/tests-ui/src/test/java/org/wso2/carbon/registry/integration/ui/CarbonTestCase.java:[9,53] cannot find symbol [ERROR] symbol : class CappHome [ERROR] location: package org.wso2.carbon.automation.api.selenium.carbon [ERROR] /home/ajith/wso2/build/branches/4.0.4/platform/4.0.0/products/greg/4.6.0/modules/integration/registry/tests-ui/src/test/java/org/wso2/carbon/registry/integration/ui/CarbonTestCase.java:[30,8] cannot find symbol [ERROR] symbol : class CappHome [ERROR] location: class org.wso2.carbon.registry.integration.ui.CarbonTestCase [ERROR] /home/ajith/wso2/build/branches/4.0.4/platform/4.0.0/products/greg/4.6.0/modules/integration/registry/tests-ui/src/test/java/org/wso2/carbon/registry/integration/ui/CarbonTestCase.java:[30,32] cannot find symbol [ERROR] symbol : class CappHome [ERROR] location: class org.wso2.carbon.registry.integration.ui.CarbonTestCase [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :org.wso2.carbon.registry.test.ui Thanks Ajith Regards, On Fri, Mar 1, 2013 at 11:07 AM, Dimuthu De Lanerolle dimut...@wso2.comwrote: Hi All, There are some API changes (due to org.wso2.carbon.user.mgt.stub change) needs to be fixed. I am still working on this. Regards, On Fri, Mar 1, 2013 at 10:52 AM, Eranda Sooriyabandara era...@wso2.comwrote: Hi Dimuthu, Still I don't see user management dependencies updated. Update the dependencies and fix the build failures will make things easier. thanks Eranda On Fri, Mar 1, 2013 at 10:49 AM, Ajith Vitharana aji...@wso2.comwrote: Hi DimuthuD On Thu, Feb 28, 2013 at 5:46 PM, Krishantha Samaraweera krishan...@wso2.com wrote: Hi Dimuthud, Can you please check this issue. Seems like user mgt API has been changed. We will have to change the framework accordingly. Any update on this ? Thanks Ajith Thanks, Krishantha. On Thu, Feb 28, 2013 at 5:05 PM, Eranda Sooriyabandara era...@wso2.com wrote: Hi Krishantha, We face this problem due to clarity framework doesn't have the latest dependencies of user management bundles. Can you please have a look at them. thanks Eranda * * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ajith Vitharana. Senior Software Engineer, Member,Management Committee, Integration Technologies. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 -- *Eranda Sooriyabandara *Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com * * -- Dimuthu De Lanerolle Software Engineer (Automation) WSO2 Inc. -- Dimuthu De Lanerolle Software Engineer (Automation) WSO2 Inc. -- Ajith Vitharana. Senior Software Engineer, Member,Management Committee, Integration Technologies. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Nuwan Wimalasekara Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean.
Re: [Dev] Build failed in trunk with clean repo
I have added the svn externals to orbit trunk. So, there's no need to build 4.1.0 orbit branch anymore. Please take an update in orbit *trunk*, and build it before building kernel and platform. On Mon, Mar 4, 2013 at 11:49 AM, Supun Malinga sup...@wso2.com wrote: Hi, Since most folks who are starting to build trunk get confused of this we will add orbit 4.1.0 bundles as externals to the orbit trunk, for the moment. After orbit 4.1.0 is released, we will remove the external. Also right now wadl-core is duplicated in both trunk and branch. Either upgrade the trunk version or remove the trunk wadl-core and add an external from the branch. thanks, On Sun, Mar 3, 2013 at 6:12 PM, Kasun Gajasinghe kas...@wso2.com wrote: Hi Eranda, On Sun, Mar 3, 2013 at 6:00 PM, Eranda Sooriyabandara era...@wso2.comwrote: Hi all, What you guys suggest was a workaround and it is fundamentally wrong. Isn't it? One who checking out and build the trunk also need to checkout the 4.1.0 branch and build. Anyway since we don't have people who work with trunk, no trouble. There will be a little annoyance until we do the 4.1.0 release which is due in less than two weeks. When it's released, we will be hosting the orbit bundles in wso2 nexus maven repo. After that, you do not have to build the 4.1.0 orbit branch. We have only maintained 4.1.0 orbit branch, and haven't worked on orbit trunk. This isn't really a workaround rather an annoyance until the release. Hope you understand. thanks Eranda On Sun, Mar 3, 2013 at 4:09 PM, Supun Malinga sup...@wso2.com wrote: Hi, First of all, there is no orbit trunk as for the moment. There is a svn dir. but that pretty much outdated. Since we need some orbit bundles for the 4.1.0 release, we decided to directly create orbit 4.1.0 branch instead of orbit trunk. So if you are building trunk, please keep in mind there is no orbit trunk at the moment, and the trunk is dependent on the 4.1.0 orbit branch. Guess that'a fair enough. And if this still concerns, we shld be able to release the orbit 4.1.0 now. thanks, On Sun, Mar 3, 2013 at 3:52 PM, Sagara Gunathunga sag...@wso2.comwrote: On Sun, Mar 3, 2013 at 2:50 PM, Dileepa Jayakody dile...@wso2.comwrote: On Sun, Mar 3, 2013 at 11:00 AM, Eranda Sooriyabandara era...@wso2.com wrote: Hi Dileepa, Yes, the tomcat 7.0.34.wso2v1 bundle is not added to trunk. it's in 4.1.0 branch, and we haven't released it yet. So for the moment we'll have to build (only) orbit 4.1.0 branch before building trunk. Normally we branch from trunk. What I have felt here is on the other way around. When creating the 4.1.0 branch the code what you mentioned missing should be there in the orbit trunk. Isn't it what should be? Yes, I think the reason is orbit 4.1.0 branch has being created separately without merging from orbit trunk, hence the new tomcat orbit version is not there in trunk. Perhaps we should merge the 4.1.0 orbits to trunk. Yes, That was the reason. @Kishanthan, was there any specific reason to add the new tomcat bundles to 4.1.0 branch and not trunk?maybe we can commit them to trunk to avoid build failures? There is no specific reason, please go ahead and merge to the trunk. Thanks ! Thanks, Dileepa thanks Eranda * * -- Dileepa Jayakody, Software Engineer, WSO2 Inc. Lean . Enterprise . Middleware Mobile : +94777-857616 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services ; http://ws.apache.org/ Blog ; http://ssagara.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Eranda Sooriyabandara *Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com * * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Kasun Gajasinghe* Software Engineer; Development Technologies Team, WSO2 Inc.; http://wso2.com , *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813* *linked-in: *http://lk.linkedin.com/in/gajasinghe* * *blog: **http://blog.kasunbg.org* http://blog.kasunbg.org* twitter: **http://twitter.com/kasunbg* http://twitter.com/kasunbg* * On Sun, Mar 3, 2013 at 6:00 PM, Eranda Sooriyabandara era...@wso2.comwrote: Hi all, What you guys suggest was a workaround and it is fundamentally wrong. Isn't it? One who checking out and build the trunk also need to checkout the
[Dev] CarbonContext.getCurrentContext().getUsername() gives a null value in an Axis2Handler
Hi Dev, I wrote an Axis2 module and its handlers are engaged to the opPhase of the in flow. In this handler I need to get the logged in username. So I use the following method. It returns null. CarbonContext.getCurrentContext().getUsername(). But if I invoked the same method inside the service, I get the username correctly. Please let me know, if anyone know whats happening here. Thanks, Sameera. -- Sameera Jayasoma Senior Technical Lead WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://sameera.adahas.org Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x Kernel 4.0.7 #25 has FAILED. Change made by Kasun Indrasiri.
--- WSO2 Carbon 4.0.x Kernel 4.0.7 #25 failed. --- Code has been updated by Kasun Indrasiri. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-KER007-25/ - Currently Responsible - Asela Pathberiya (Assigned by Maheshika Goonetilleke) -- Failing Jobs -- - Default Job (Default Stage): No tests found. -- Code Changes -- Kasun Indrasiri (166567): reverting a wrong commit -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev