[Dev] 4.0.3 - 31/10/2012 product builds
http://builder3.us1.wso2.org/builds/31-oct-2012/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [BUILD FAILED] WSO2 Carbon 4.0.x Products_4.0.3 build #14
Hi All The carbon products build has failed due to the following error which has caused even the previous build to fail; 30-Oct-2012 22:31:20[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.7.2:test (default-test) on project identity-integration-tests: There are test failures.30-Oct-2012 22:31:20[ERROR] 30-Oct-2012 22:31:20[ERROR] Please refer to /home/bamboo/Bamboo-3.4/source-repository/build-dir/WCB001-PRO001-JOB1/products/is/4.0.0/modules/integration/target/surefire-reports for the individual test results.30-Oct-2012 22:31:20[ERROR] - [Help 1] -- Thanks Best Regards, Maheshika Goonetilleke Engineering Process Coordinator WSO2 Inc www.wso2.com/ M : 0773 596707 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Bamboo-Build] Developer Studio Eclipse-Tools #487 has FAILED. Change made by viraj.
--- Developer Studio Eclipse-Tools #487 failed. --- Code has been updated by viraj. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/DS0001-DSET01-487/ - Currently Responsible - No one is responsible for fixing this build. -- Failing Jobs -- - Default Job (Default Stage): No tests found. -- Code Changes -- viraj (146929): Completing Task Serializer viraj (146928): Completing Task Serializer viraj (146930): Adding path separator to be compatible with Windows OS -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] 4.0.3 - 31/10/2012 product builds
**BRS team, Please make sure to fix the license file since the purpose of releasing BRS with Carbon-4.0.3 is the issues in license in previous release. I can still find obsolete versions in license. For example, we have org.wso2.carbon.rule.backend_4.0.3.jar in repository/components/plugins but org.wso2.carbon.rule.backend_4.0.2 version is listed in license. Thanks! Charitha On Wed, Oct 31, 2012 at 12:16 PM, Rajika Kumarasiri raj...@wso2.com wrote: http://builder3.us1.wso2.org/builds/31-oct-2012/ ___ 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
[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x Kernel_4.0.3 #16 was SUCCESSFUL. Change made by suresh.
--- WSO2 Carbon 4.0.x Kernel_4.0.3 #16 was successful. --- Code has been updated by suresh. http://wso2.org/bamboo/browse/WCB001-KER001-16/ -- Code Changes -- suresh (146912): commenting out the extra claim mappings -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Best approach to fix https://wso2.org/jira/browse/REGISTRY-1378
Hi, For the issue [1] we cannot specify whitespaces in state ID. It is a constraint added by SCXML and it gives an exception when it tries to parse. According to this [2] release note they have mentioned not to add white spaces in state IDs. A fix would be to add a temporary element which will complaint with parsing and then again replace it with white space. Is that approach clean enough to introduce? Thanks [1] https://wso2.org/jira/browse/REGISTRY-1378 [2] http://svn.apache.org/repos/asf/commons/proper/scxml/tags/SCXML_0_7/RELEASE-NOTES.txt -- *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 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please add Identity Server Feature Category to 4.0.3 feature repository
I have added the IS feature categories into the 4.0.3 release. Rajika On Wed, Oct 31, 2012 at 11:20 AM, Dileepa Jayakody dile...@wso2.com wrote: On Wed, Oct 31, 2012 at 10:44 AM, Rajika Kumarasiri raj...@wso2.comwrote: I noticed that the current 4.0.3 feature is a copy from the 4.0.2, so it has all the released 4.0.2 features defined. Is this intentional or should it be fixed ? If this is indented behavior will that not build up the p2 repo size each time we do a release ? Yes this is intended, we followed the same flow since 4.0.0 release. With 4.0.0 only AM got released so it only had 1 product category in the repo. With 4.0.1 the new set of product categories were added with updated feature versions and the AM category already released was also included. Since not all the products are getting released in chunk releases, the features products already got released in prev. chunk releases should be in the p2-repo so users can install them as well. If any of their features got updated we need to update feature versions. So as a summary what needs to be done is; 1. Add new features or update features that are going to be released in 4.0.3 2. Add new product categories that are going to be released. eg: IS category *Note: With regard to Product categories* As per the discussion we had on current feature categorization we came to a conclusion that a product category should be defined in a clear and usable manner so a user can clearly identify the list of required features to install a product/product combination. Not all features in the p2-profile-gen need to be added to the category. Composite features aggregating required set of sub-features should be used as a best practice. This will become a form of sub-categories for the users in installing features. eg: when adding event features, don't add event.ui, event.common, event.server separately instead add the composite feature. Like wise every product category in the current p2-repo should be revised to remove unwanted features and include composite features in a logical manner. We need to go forward with a process for this where each product team need to restructure their categories in a meaningful way for the carbon users installing features. Will need help from each product team for this. Thanks, Dileepa Rajika On Wed, Oct 31, 2012 at 1:32 AM, Dileepa Jayakody dile...@wso2.comwrote: Hi IS team, Can we please add IS category to 4.0.3 p2 repo pom? This is vital to test IS feature group on top other carbon products. If you need further clarifications on defining the feature category please let me know. Thanks, Dileepa -- 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 -- 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] Developer Studio Eclipse-Tools #488 was SUCCESSFUL. Change made by jasintha and viraj.
--- Developer Studio Eclipse-Tools #488 was successful. --- Code has been updated by jasintha, viraj. http://wso2.org/bamboo/browse/DS0001-DSET01-488/ -- Code Changes -- viraj (146938): Avoid potential null pointer exception viraj (146937): Adding Task property editor to properties view jasintha (146935): update Rule mediator serializer -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Warnings when tenant logging - org.wso2.carbon.dataservices.core.DBDeployer
2012-10-31 17:04:07,047] WARN
{org.apache.axis2.deployment.AxisConfigBuilder} - Unable to instantiate
deployer org.wso2.carbon.dataservices.core.DBDeployer; see debug logs for
more details
[2012-10-31 17:04:07,391] INFO {or
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Intermittent error when using cache - Cache: The Disk store is not active
Hi,
I get this error intermittently when adding to cache...
Can I please know what might be the cause for this?
[2012-10-31 18:04:32,933] ERROR {net.sf.ehcache.store.DiskStore} -
SCIM_CACHECache: Could not read disk store element for key
admin@carbon.super. Initial cause was SCIM_CACHE Cache: The Disk store is
not active.
net.sf.ehcache.CacheException: SCIM_CACHE Cache: The Disk store is not
active.
at net.sf.ehcache.store.DiskStore.checkActive(DiskStore.java:232)
at net.sf.ehcache.store.DiskStore.getQuiet(DiskStore.java:322)
at net.sf.ehcache.Cache.searchInDiskStore(Cache.java:1204)
at net.sf.ehcache.Cache.getQuiet(Cache.java:1057)
at net.sf.ehcache.jcache.JCache.put(JCache.java:595)
at net.sf.ehcache.jcache.JCache.put(JCache.java:570)
at
org.wso2.carbon.identity.scim.common.config.SCIMProvisioningConfigManager.addEnabledToCache(SCIMProvisioningConfigManager.java:131)
Thanks,
Hasini.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] 4.0.3 build failure - org.wso2.carbon:org.wso2.carbon.bam.mediation.agent.feature:zip:4.0.3 not found
[INFO] Total time: 4:56.700s [INFO] Finished at: Wed Oct 31 06:49:59 PDT 2012 [INFO] Final Memory: 9M/106M [INFO] [ERROR] Failed to execute goal org.wso2.maven:carbon-p2-plugin:1.5.1:p2-repo-gen (2-p2-repo-generation) on project wso2carbon-feature-repository: Error occured when processing the Feature Artifact: org.wso2.carbon:org.wso2.carbon.bam.mediation.agent.feature:4.0.3: ERROR: Could not find artifact org.wso2.carbon:org.wso2.carbon.bam.mediation.agent.feature:zip:4.0.3 in wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) [ERROR] [ERROR] Try downloading the file manually from the project website. [ERROR] [ERROR] Then, install it using the command: [ERROR] mvn install:install-file -DgroupId=org.wso2.carbon -DartifactId=org.wso2.carbon.bam.mediation.agent.feature -Dversion=4.0.3 -Dpackaging=zip -Dfile=/path/to/file [ERROR] [ERROR] Alternatively, if you host your own repository you can deploy the file there: [ERROR] mvn deploy:deploy-file -DgroupId=org.wso2.carbon -DartifactId=org.wso2.carbon.bam.mediation.agent.feature -Dversion=4.0.3 -Dpackaging=zip -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] [ERROR] [ERROR] [ERROR] org.wso2.carbon:org.wso2.carbon.bam.mediation.agent.feature:zip:4.0.3 [ERROR] [ERROR] from the specified remote repositories: [ERROR] wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/, releases=true, snapshots=true), [ERROR] central (http://repo.maven.apache.org/maven2, releases=true, snapshots=false) [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/MojoExecutionExceptio ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] 4.0.3 - build error in clean repo check sum validation error
[ERROR] Failed to execute goal on project org.wso2.carbon.billing.mgt: Could not resolve dependencies for project org.wso2.carbon:org.wso2.carbon.billing.mgt:bundle:2.0.3: Failed to collect dependencies for [org.wso2.carbon:org.wso2.carbon.registry.core:jar:4.0.0 (compile), org.wso2.carbon:org.wso2.carbon.user.core:jar:4.0.0 (compile), commons-logging:commons-logging:jar:1.1.1 (compile), org.wso2.carbon:org.wso2.carbon.billing.core:jar:2.0.3 (compile), org.wso2.carbon:org.wso2.carbon.usage:jar:2.0.0 (compile), org.wso2.carbon:org.wso2.carbon.stratos.common:jar:2.0.0 (compile), org.wso2.carbon:org.wso2.carbon.throttling.agent:jar:2.0.0 (compile)]: Failed to read artifact descriptor for eclipse:validateutility:jar:0.95: Could not transfer artifact eclipse:validateutility:pom:0.95 from/to wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/): Checksum validation failed, no checksums available from the repository - [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/DependencyResolutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :org.wso2.carbon.billing.mgt ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] 4.0.3 - build error in clean repo check sum validation error
The check sum validation was ignored using the -c command line option to maven. Rajika On Wed, Oct 31, 2012 at 7:51 PM, Rajika Kumarasiri raj...@wso2.com wrote: [ERROR] Failed to execute goal on project org.wso2.carbon.billing.mgt: Could not resolve dependencies for project org.wso2.carbon:org.wso2.carbon.billing.mgt:bundle:2.0.3: Failed to collect dependencies for [org.wso2.carbon:org.wso2.carbon.registry.core:jar:4.0.0 (compile), org.wso2.carbon:org.wso2.carbon.user.core:jar:4.0.0 (compile), commons-logging:commons-logging:jar:1.1.1 (compile), org.wso2.carbon:org.wso2.carbon.billing.core:jar:2.0.3 (compile), org.wso2.carbon:org.wso2.carbon.usage:jar:2.0.0 (compile), org.wso2.carbon:org.wso2.carbon.stratos.common:jar:2.0.0 (compile), org.wso2.carbon:org.wso2.carbon.throttling.agent:jar:2.0.0 (compile)]: Failed to read artifact descriptor for eclipse:validateutility:jar:0.95: Could not transfer artifact eclipse:validateutility:pom:0.95 from/to wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/): Checksum validation failed, no checksums available from the repository - [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/DependencyResolutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :org.wso2.carbon.billing.mgt ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] How to write integration tests?
Hi, Does anyone know $subject. Do we not have unit tests now? Can I please get some pointers how to do so? Thanks, -Chintana -- Chintana Wilamuna Senior Technical Lead WSO2, Inc.; http://wso2.com lean.enterprise.middleware phone: +94 72 145 4545 blog: http://engwar.com/ photos: http://flickr.com/photos/chintana linkedin: http://www.linkedin.com/in/engwar twitter: twitter.com/std_err ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] 4.0.3 - clean repo build failure in manager
Installing org.wso2.carbon.rule.service.server.feature.group 4.0.2. Installation failed. Cannot complete the install because one or more required items could not be found. Software being installed: WSO2 Carbon - Logging Management Feature 4.0.3 (org.wso2.carbon.logging.mgt.feature.group 4.0.3) Missing requirement: org.wso2.carbon.logging.view.ui 4.0.3 (org.wso2.carbon.logging.view.ui 4.0.3) requires 'package org.wso2.carbon.logging.view.stub 4.0.3' but it could not be found Cannot satisfy dependency: From: WSO2 Carbon - Logging Management Feature 4.0.3 (org.wso2.carbon.logging.mgt.feature.group 4.0.3) To: org.wso2.carbon.logging.mgt.ui.feature.group [4.0.3] Cannot satisfy dependency: From: WSO2 Carbon - Logging Management UI Feature 4.0.3 (org.wso2.carbon.logging.mgt.ui.feature.group 4.0.3) To: org.wso2.carbon.logging.view.ui [4.0.3] Application failed, log file location: /home/wso2/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1351703158889.log ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How to write integration tests?
Your best bet would be to look into one of the integration test module in one of the products. Rajika On Wed, Oct 31, 2012 at 10:23 PM, Chintana Wilamuna chint...@wso2.comwrote: Hi, Does anyone know $subject. Do we not have unit tests now? Can I please get some pointers how to do so? Thanks, -Chintana -- Chintana Wilamuna Senior Technical Lead WSO2, Inc.; http://wso2.com lean.enterprise.middleware phone: +94 72 145 4545 blog: http://engwar.com/ photos: http://flickr.com/photos/chintana linkedin: http://www.linkedin.com/in/engwar twitter: twitter.com/std_err ___ 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
[Dev] 4.0.3 - 31/10/2012(r147004) product builds
http://builder3.us1.wso2.org/builds/31-oct-2012-r147004/ These were built with test in a clean repo on r147004. Manager has build failures reported in the other thread. Rajika ___ 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.3 #15 has FAILED. Change made by 12 authors.
--- WSO2 Carbon 4.0.x Products_4.0.3 #15 failed. --- This build occurred because it is a dependant of WCB001-PLA001-39. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-PRO001-15/ - Currently Responsible - No one is responsible for fixing this build. -- Failing Jobs -- - Default Job (Default Stage): No tests found. -- Code Changes -- hasini (146908): fixing issue: https://wso2.org/jira/browse/IDENTITY-507 rajika (146934): Added the IS feature categories. amilam (146923): Creating domain validator ui 2.0.3 -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How to write integration tests?
We do have unit tests only for some components such as org.wso2.carbon.dataservices.core and org.wso2.carbon.registry.core. No documents available on the subject yet. Rajika's suggestion would be the best approach. Thanks, Krishantha. On Wed, Oct 31, 2012 at 10:23 PM, Chintana Wilamuna chint...@wso2.comwrote: Hi, Does anyone know $subject. Do we not have unit tests now? Can I please get some pointers how to do so? Thanks, -Chintana -- Chintana Wilamuna Senior Technical Lead WSO2, Inc.; http://wso2.com lean.enterprise.middleware phone: +94 72 145 4545 blog: http://engwar.com/ photos: http://flickr.com/photos/chintana linkedin: http://www.linkedin.com/in/engwar twitter: twitter.com/std_err ___ 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] Best approach to fix https://wso2.org/jira/browse/REGISTRY-1378
Hi Shelan, Did you try defining the state ID by replacing all the whitespaces with '.' character. *Eg:- Ready For QA == Ready.For.QA* IIRC, it should show that correctly in the UI. Also IIRC, similar scenarios have been tested against lifecycles in past releases. Maybe QA folks can share more information on that. Thanks, Janaka On Wed, Oct 31, 2012 at 2:18 PM, Shelan Perera she...@wso2.com wrote: Hi, For the issue [1] we cannot specify whitespaces in state ID. It is a constraint added by SCXML and it gives an exception when it tries to parse. According to this [2] release note they have mentioned not to add white spaces in state IDs. A fix would be to add a temporary element which will complaint with parsing and then again replace it with white space. Is that approach clean enough to introduce? Thanks [1] https://wso2.org/jira/browse/REGISTRY-1378 [2] http://svn.apache.org/repos/asf/commons/proper/scxml/tags/SCXML_0_7/RELEASE-NOTES.txt -- *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 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Janaka Ranabahu Software Engineer WSO2 Inc. Mobile +94 718370861 Email : jan...@wso2.com Blog : janakaranabahu.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How to write integration tests?
It has to be the combination of Unit tests and Integration tests IMO. since they serve different purposes Regards, /Nuwan On Wed, Oct 31, 2012 at 10:47 AM, Krishantha Samaraweera krishan...@wso2.com wrote: We do have unit tests only for some components such as org.wso2.carbon.dataservices.core and org.wso2.carbon.registry.core. No documents available on the subject yet. Rajika's suggestion would be the best approach. Thanks, Krishantha. On Wed, Oct 31, 2012 at 10:23 PM, Chintana Wilamuna chint...@wso2.comwrote: Hi, Does anyone know $subject. Do we not have unit tests now? Can I please get some pointers how to do so? Thanks, -Chintana -- Chintana Wilamuna Senior Technical Lead WSO2, Inc.; http://wso2.com lean.enterprise.middleware phone: +94 72 145 4545 blog: http://engwar.com/ photos: http://flickr.com/photos/chintana linkedin: http://www.linkedin.com/in/engwar twitter: twitter.com/std_err ___ 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 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] How to write integration tests?
Hi, As suggested it was really helpful if you look into integration test of a product. I wrote a small blog post [1] which is very basic at the time we were assigned to convert Junit based integration tests to Testng last year. [1] http://blog.shelan.org/2012/02/better-testing-with-testng.html Thanks On Thu, Nov 1, 2012 at 12:08 AM, Nuwan Bandara nu...@wso2.com wrote: It has to be the combination of Unit tests and Integration tests IMO. since they serve different purposes Regards, /Nuwan On Wed, Oct 31, 2012 at 10:47 AM, Krishantha Samaraweera krishan...@wso2.com wrote: We do have unit tests only for some components such as org.wso2.carbon.dataservices.core and org.wso2.carbon.registry.core. No documents available on the subject yet. Rajika's suggestion would be the best approach. Thanks, Krishantha. On Wed, Oct 31, 2012 at 10:23 PM, Chintana Wilamuna chint...@wso2.comwrote: Hi, Does anyone know $subject. Do we not have unit tests now? Can I please get some pointers how to do so? Thanks, -Chintana -- Chintana Wilamuna Senior Technical Lead WSO2, Inc.; http://wso2.com lean.enterprise.middleware phone: +94 72 145 4545 blog: http://engwar.com/ photos: http://flickr.com/photos/chintana linkedin: http://www.linkedin.com/in/engwar twitter: twitter.com/std_err ___ 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 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 -- *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 ___ 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.3 #41 has FAILED. Change made by 5 authors.
--- WSO2 Carbon 4.0.x Platform_4.0.3 #41 failed. --- This build occurred because it is a dependant of WCB001-KER001-18. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-PLA001-41/ - Currently Responsible - No one is responsible for fixing this build. -- Failing Jobs -- - Default Job (Default Stage): 1005 tests passed. -- Code Changes -- isharak (147004): Change License file lalaji (147005): Added Chanaka's fix for docname validation rajika (147008): Updated releade me. -- 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.3 #42 has FAILED
--- WSO2 Carbon 4.0.x Platform_4.0.3 #42 failed. --- This build occurred because it is a dependant of WCB001-KER001-19. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-PLA001-42/ - Currently Responsible - No one is responsible for fixing this build. -- Failing Jobs -- - Default Job (Default Stage): 1005 tests passed. -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] 4.0.3 - clean repo build failure in manager
Hi I'm looking into this... Thanks, Reka On Wed, Oct 31, 2012 at 10:46 PM, Rajika Kumarasiri raj...@wso2.com wrote: Installing org.wso2.carbon.rule.service.server.feature.group 4.0.2. Installation failed. Cannot complete the install because one or more required items could not be found. Software being installed: WSO2 Carbon - Logging Management Feature 4.0.3 (org.wso2.carbon.logging.mgt.feature.group 4.0.3) Missing requirement: org.wso2.carbon.logging.view.ui 4.0.3 (org.wso2.carbon.logging.view.ui 4.0.3) requires 'package org.wso2.carbon.logging.view.stub 4.0.3' but it could not be found Cannot satisfy dependency: From: WSO2 Carbon - Logging Management Feature 4.0.3 (org.wso2.carbon.logging.mgt.feature.group 4.0.3) To: org.wso2.carbon.logging.mgt.ui.feature.group [4.0.3] Cannot satisfy dependency: From: WSO2 Carbon - Logging Management UI Feature 4.0.3 (org.wso2.carbon.logging.mgt.ui.feature.group 4.0.3) To: org.wso2.carbon.logging.view.ui [4.0.3] Application failed, log file location: /home/wso2/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1351703158889.log ___ 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
[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x Platform_4.0.3 #43 has FAILED. Change made by hasini.
--- WSO2 Carbon 4.0.x Platform_4.0.3 #43 failed. --- Code has been updated by hasini. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-PLA001-43/ - Currently Responsible - No one is responsible for fixing this build. -- Failing Jobs -- - Default Job (Default Stage): 1005 tests passed. -- Code Changes -- hasini (147019): changing the order of IdentityUtil registration as an OSGi service hasini (147020): integrating DB persistence and caching for scim provider retrieval in provisioning -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] DefaultRelamService#initalizeRelam() is called several times when creating a tenant - IDENTITY-536
On Wed, Oct 31, 2012 at 7:05 PM, Rajika Kumarasiri raj...@wso2.com wrote:
This is in the latest IS pack at
http://builder3.us1.wso2.org/builds/31-oct-2012/.
When creating a tenant following logs can be seen repeatedly. See
https://wso2.org/jira/browse/IDENTITY-536.
[2012-10-31 18:46:12,086] INFO
{org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager} - LDAP
connection created successfully in read-write mode.
When requesting the tenant user relam
(DefaultRelamService#getTenantUserRelam()) while creating the tenant it
seems that DefaultRelamService#initalizeRelam() is called several time
which ends up initialization ReadWriteLDAPUserStoreManager each time(hence
the repeating logs). I have attached a screen shot of the stack traces as
well.
This issue was not there in the IS alpha pack. Cloud you look into this ?
Should be fixed now.
thanks,
dimuthu
Rajika
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] DefaultRelamService#initalizeRelam() is called several times when creating a tenant - IDENTITY-536
It seems to be not fixed in the latest packs although the fix for
https://wso2.org/jira/browse/IDENTITY-491 was reverted in
https://wso2.org/jira/browse/IDENTITY-536 with r147001.
Can you please check whether the r147001 is the correct revert?
Thanks,
Hasini.
On Thu, Nov 1, 2012 at 8:51 AM, Dimuthu Leelarathne dimut...@wso2.comwrote:
On Wed, Oct 31, 2012 at 7:05 PM, Rajika Kumarasiri raj...@wso2.comwrote:
This is in the latest IS pack at
http://builder3.us1.wso2.org/builds/31-oct-2012/.
When creating a tenant following logs can be seen repeatedly. See
https://wso2.org/jira/browse/IDENTITY-536.
[2012-10-31 18:46:12,086] INFO
{org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager} - LDAP
connection created successfully in read-write mode.
When requesting the tenant user relam
(DefaultRelamService#getTenantUserRelam()) while creating the tenant it
seems that DefaultRelamService#initalizeRelam() is called several time
which ends up initialization ReadWriteLDAPUserStoreManager each time(hence
the repeating logs). I have attached a screen shot of the stack traces as
well.
This issue was not there in the IS alpha pack. Cloud you look into this ?
Should be fixed now.
thanks,
dimuthu
Rajika
___
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] DefaultRelamService#initalizeRelam() is called several times when creating a tenant - IDENTITY-536
On Thu, Nov 1, 2012 at 8:59 AM, Hasini Gunasinghe has...@wso2.com wrote:
It seems to be not fixed in the latest packs although the fix for
https://wso2.org/jira/browse/IDENTITY-491 was reverted in
https://wso2.org/jira/browse/IDENTITY-536 with r147001.
Can you please check whether the r147001 is the correct revert?
I attached the correct revert as a patch to 536.
thanks,
dimuthu
Thanks,
Hasini.
On Thu, Nov 1, 2012 at 8:51 AM, Dimuthu Leelarathne dimut...@wso2.comwrote:
On Wed, Oct 31, 2012 at 7:05 PM, Rajika Kumarasiri raj...@wso2.comwrote:
This is in the latest IS pack at
http://builder3.us1.wso2.org/builds/31-oct-2012/.
When creating a tenant following logs can be seen repeatedly. See
https://wso2.org/jira/browse/IDENTITY-536.
[2012-10-31 18:46:12,086] INFO
{org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager} - LDAP
connection created successfully in read-write mode.
When requesting the tenant user relam
(DefaultRelamService#getTenantUserRelam()) while creating the tenant it
seems that DefaultRelamService#initalizeRelam() is called several time
which ends up initialization ReadWriteLDAPUserStoreManager each time(hence
the repeating logs). I have attached a screen shot of the stack traces as
well.
This issue was not there in the IS alpha pack. Cloud you look into this
?
Should be fixed now.
thanks,
dimuthu
Rajika
___
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] 4.0.3 - clean repo build failure in manager
Hi The attached patch here with will solve the build failure. Can someone please commit this patches? Thanks, Reka On Thu, Nov 1, 2012 at 8:01 AM, Reka Thirunavukkarasu r...@wso2.com wrote: Hi I'm looking into this... Thanks, Reka On Wed, Oct 31, 2012 at 10:46 PM, Rajika Kumarasiri raj...@wso2.comwrote: Installing org.wso2.carbon.rule.service.server.feature.group 4.0.2. Installation failed. Cannot complete the install because one or more required items could not be found. Software being installed: WSO2 Carbon - Logging Management Feature 4.0.3 (org.wso2.carbon.logging.mgt.feature.group 4.0.3) Missing requirement: org.wso2.carbon.logging.view.ui 4.0.3 (org.wso2.carbon.logging.view.ui 4.0.3) requires 'package org.wso2.carbon.logging.view.stub 4.0.3' but it could not be found Cannot satisfy dependency: From: WSO2 Carbon - Logging Management Feature 4.0.3 (org.wso2.carbon.logging.mgt.feature.group 4.0.3) To: org.wso2.carbon.logging.mgt.ui.feature.group [4.0.3] Cannot satisfy dependency: From: WSO2 Carbon - Logging Management UI Feature 4.0.3 (org.wso2.carbon.logging.mgt.ui.feature.group 4.0.3) To: org.wso2.carbon.logging.view.ui [4.0.3] Application failed, log file location: /home/wso2/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1351703158889.log ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev logging-UI.patch Description: Binary data logging-feature-UI.patch Description: Binary data ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Best approach to fix https://wso2.org/jira/browse/REGISTRY-1378
Yes. We came across this issue while testing G-Reg 4.0.0 release and then the solution given was to use fullstops instead of spaces. In fact, in latest G-Reg packs, the default ServiceLifeCycle has a state in this format. : state id=Production datamodel data name=transitionExecution execution forEvent=Demote class=org.wso2.carbon.governance.registry.extensions.executors.DemoteActionExecutor /execution execution forEvent=Publish class=org.wso2.carbon.governance.registry.extensions.executors.apistore.ApiStoreExecutor /execution /data /datamodel transition event=Publish target= Published.to.APIStore/ transition event=Demote target=Testing/ /state state id=Published.to.APIStore /state : Regards, Evanthika On Wed, Oct 31, 2012 at 11:36 PM, Janaka Ranabahu jan...@wso2.com wrote: Hi Shelan, Did you try defining the state ID by replacing all the whitespaces with '.' character. *Eg:- Ready For QA == Ready.For.QA* IIRC, it should show that correctly in the UI. Also IIRC, similar scenarios have been tested against lifecycles in past releases. Maybe QA folks can share more information on that. Thanks, Janaka On Wed, Oct 31, 2012 at 2:18 PM, Shelan Perera she...@wso2.com wrote: Hi, For the issue [1] we cannot specify whitespaces in state ID. It is a constraint added by SCXML and it gives an exception when it tries to parse. According to this [2] release note they have mentioned not to add white spaces in state IDs. A fix would be to add a temporary element which will complaint with parsing and then again replace it with white space. Is that approach clean enough to introduce? Thanks [1] https://wso2.org/jira/browse/REGISTRY-1378 [2] http://svn.apache.org/repos/asf/commons/proper/scxml/tags/SCXML_0_7/RELEASE-NOTES.txt -- *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 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Janaka Ranabahu Software Engineer WSO2 Inc. Mobile +94 718370861 Email : jan...@wso2.com Blog : janakaranabahu.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] DefaultRelamService#initalizeRelam() is called several times when creating a tenant - IDENTITY-536
Patch applied in r147035.
Rajika
On Thu, Nov 1, 2012 at 9:02 AM, Dimuthu Leelarathne dimut...@wso2.comwrote:
On Thu, Nov 1, 2012 at 8:59 AM, Hasini Gunasinghe has...@wso2.com wrote:
It seems to be not fixed in the latest packs although the fix for
https://wso2.org/jira/browse/IDENTITY-491 was reverted in
https://wso2.org/jira/browse/IDENTITY-536 with r147001.
Can you please check whether the r147001 is the correct revert?
I attached the correct revert as a patch to 536.
thanks,
dimuthu
Thanks,
Hasini.
On Thu, Nov 1, 2012 at 8:51 AM, Dimuthu Leelarathne dimut...@wso2.comwrote:
On Wed, Oct 31, 2012 at 7:05 PM, Rajika Kumarasiri raj...@wso2.comwrote:
This is in the latest IS pack at
http://builder3.us1.wso2.org/builds/31-oct-2012/.
When creating a tenant following logs can be seen repeatedly. See
https://wso2.org/jira/browse/IDENTITY-536.
[2012-10-31 18:46:12,086] INFO
{org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager} - LDAP
connection created successfully in read-write mode.
When requesting the tenant user relam
(DefaultRelamService#getTenantUserRelam()) while creating the tenant it
seems that DefaultRelamService#initalizeRelam() is called several time
which ends up initialization ReadWriteLDAPUserStoreManager each time(hence
the repeating logs). I have attached a screen shot of the stack traces as
well.
This issue was not there in the IS alpha pack. Cloud you look into this
?
Should be fixed now.
thanks,
dimuthu
Rajika
___
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] 4.0.3 - clean repo build failure in manager
Patches were applied in r147047. Rajika On Thu, Nov 1, 2012 at 9:04 AM, Reka Thirunavukkarasu r...@wso2.com wrote: Hi The attached patch here with will solve the build failure. Can someone please commit this patches? Thanks, Reka On Thu, Nov 1, 2012 at 8:01 AM, Reka Thirunavukkarasu r...@wso2.comwrote: Hi I'm looking into this... Thanks, Reka On Wed, Oct 31, 2012 at 10:46 PM, Rajika Kumarasiri raj...@wso2.comwrote: Installing org.wso2.carbon.rule.service.server.feature.group 4.0.2. Installation failed. Cannot complete the install because one or more required items could not be found. Software being installed: WSO2 Carbon - Logging Management Feature 4.0.3 (org.wso2.carbon.logging.mgt.feature.group 4.0.3) Missing requirement: org.wso2.carbon.logging.view.ui 4.0.3 (org.wso2.carbon.logging.view.ui 4.0.3) requires 'package org.wso2.carbon.logging.view.stub 4.0.3' but it could not be found Cannot satisfy dependency: From: WSO2 Carbon - Logging Management Feature 4.0.3 (org.wso2.carbon.logging.mgt.feature.group 4.0.3) To: org.wso2.carbon.logging.mgt.ui.feature.group [4.0.3] Cannot satisfy dependency: From: WSO2 Carbon - Logging Management UI Feature 4.0.3 (org.wso2.carbon.logging.mgt.ui.feature.group 4.0.3) To: org.wso2.carbon.logging.view.ui [4.0.3] Application failed, log file location: /home/wso2/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1351703158889.log ___ 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
[Dev] Key store location should be configurable in checkin client.
Hi Senaka, Currently, we have hard coded the location at [1]. We should be able to pass the key store location as a parameter. [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/products/greg/4.5.2/modules/checkin-client/src/main/java/org/wso2/registry/checkin/ClientUtils.java Thanks Ajith -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94714631794 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Key store location should be configurable in checkin client.
https://wso2.org/jira/browse/REGISTRY-1478 Thanks Ajith On Thu, Nov 1, 2012 at 10:47 AM, Ajith Vitharana aji...@wso2.com wrote: Hi Senaka, Currently, we have hard coded the location at [1]. We should be able to pass the key store location as a parameter. [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/products/greg/4.5.2/modules/checkin-client/src/main/java/org/wso2/registry/checkin/ClientUtils.java Thanks Ajith -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94714631794 -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94714631794 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Key store location should be configurable in checkin client.
Hi All, Yes. Without this, we cannot use Check-In client when the default trust stores are changed. Thanks and Regards, Harshana On Thu, Nov 1, 2012 at 12:17 PM, Ajith Vitharana aji...@wso2.com wrote: Hi Senaka, Currently, we have hard coded the location at [1]. We should be able to pass the key store location as a parameter. [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/products/greg/4.5.2/modules/checkin-client/src/main/java/org/wso2/registry/checkin/ClientUtils.java Thanks Ajith -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94714631794 -- Harshana Martin Senior Software Engineer Member, Management Committee - Development Technologies WSO2 Inc. : http://wso2.com ; http://wso2.org Mobile: +94 775 998 115 Profile: https://www.google.com/profiles/harshana05 Blog: http://harshana05.blogspot.com Twitter: http://twitter.com/harshana05 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Key store location should be configurable in checkin client.
Hi Ajith, Where can we add this configuration? thanks Eranda On Thu, Nov 1, 2012 at 10:53 AM, Harshana Martin harsh...@wso2.com wrote: Hi All, Yes. Without this, we cannot use Check-In client when the default trust stores are changed. Thanks and Regards, Harshana On Thu, Nov 1, 2012 at 12:17 PM, Ajith Vitharana aji...@wso2.com wrote: Hi Senaka, Currently, we have hard coded the location at [1]. We should be able to pass the key store location as a parameter. [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/products/greg/4.5.2/modules/checkin-client/src/main/java/org/wso2/registry/checkin/ClientUtils.java Thanks Ajith -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94714631794 -- Harshana Martin Senior Software Engineer Member, Management Committee - Development Technologies WSO2 Inc. : http://wso2.com ; http://wso2.org Mobile: +94 775 998 115 Profile: https://www.google.com/profiles/harshana05 Blog: http://harshana05.blogspot.com Twitter: http://twitter.com/harshana05 -- *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] Key store location should be configurable in checkin client.
Hi Eranda, The location is available on the carbon.xml, and if someone has already set the property, we should use it instead of overriding it. Anyway we should see what and what check-in client needs from carbon.home, because ideally this should work in an environment that does not have a Carbon Server instance. Thanks, Senaka. On Thu, Nov 1, 2012 at 10:54 AM, Eranda Sooriyabandara era...@wso2.comwrote: Hi Ajith, Where can we add this configuration? thanks Eranda On Thu, Nov 1, 2012 at 10:53 AM, Harshana Martin harsh...@wso2.comwrote: Hi All, Yes. Without this, we cannot use Check-In client when the default trust stores are changed. Thanks and Regards, Harshana On Thu, Nov 1, 2012 at 12:17 PM, Ajith Vitharana aji...@wso2.com wrote: Hi Senaka, Currently, we have hard coded the location at [1]. We should be able to pass the key store location as a parameter. [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/products/greg/4.5.2/modules/checkin-client/src/main/java/org/wso2/registry/checkin/ClientUtils.java Thanks Ajith -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94714631794 -- Harshana Martin Senior Software Engineer Member, Management Committee - Development Technologies WSO2 Inc. : http://wso2.com ; http://wso2.org Mobile: +94 775 998 115 Profile: https://www.google.com/profiles/harshana05 Blog: http://harshana05.blogspot.com Twitter: http://twitter.com/harshana05 -- *Eranda Sooriyabandara *Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com * * -- *Senaka Fernando* Member - Integration Technologies Management Committee; Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *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.3 #44 has FAILED. Change made by hasini, asela and lalaji.
--- WSO2 Carbon 4.0.x Platform_4.0.3 #44 failed. --- This build occurred because it is a dependant of WCB001-KER001-20. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-PLA001-44/ - Currently Responsible - No one is responsible for fixing this build. -- Failing Jobs -- - Default Job (Default Stage): 1005 tests passed. -- Code Changes -- lalaji (147025): Corrected a sql query asela (147023): fixing caching issues lalaji (147029): Update license.xt/p2-profile and readme -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] 4.0.3 - clean repo build failure in manager
Thanks..! Reka On Thu, Nov 1, 2012 at 10:44 AM, Rajika Kumarasiri raj...@wso2.com wrote: Patches were applied in r147047. Rajika On Thu, Nov 1, 2012 at 9:04 AM, Reka Thirunavukkarasu r...@wso2.comwrote: Hi The attached patch here with will solve the build failure. Can someone please commit this patches? Thanks, Reka On Thu, Nov 1, 2012 at 8:01 AM, Reka Thirunavukkarasu r...@wso2.comwrote: Hi I'm looking into this... Thanks, Reka On Wed, Oct 31, 2012 at 10:46 PM, Rajika Kumarasiri raj...@wso2.comwrote: Installing org.wso2.carbon.rule.service.server.feature.group 4.0.2. Installation failed. Cannot complete the install because one or more required items could not be found. Software being installed: WSO2 Carbon - Logging Management Feature 4.0.3 (org.wso2.carbon.logging.mgt.feature.group 4.0.3) Missing requirement: org.wso2.carbon.logging.view.ui 4.0.3 (org.wso2.carbon.logging.view.ui 4.0.3) requires 'package org.wso2.carbon.logging.view.stub 4.0.3' but it could not be found Cannot satisfy dependency: From: WSO2 Carbon - Logging Management Feature 4.0.3 (org.wso2.carbon.logging.mgt.feature.group 4.0.3) To: org.wso2.carbon.logging.mgt.ui.feature.group [4.0.3] Cannot satisfy dependency: From: WSO2 Carbon - Logging Management UI Feature 4.0.3 (org.wso2.carbon.logging.mgt.ui.feature.group 4.0.3) To: org.wso2.carbon.logging.view.ui [4.0.3] Application failed, log file location: /home/wso2/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1351703158889.log ___ 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
