[Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk WSO2 Carbon - Platform Trunk #142 has FAILED (1 tests failed, no failures were new). Change made by krishantha.
--- WSO2 Carbon Trunk WSO2 Carbon - Platform Trunk #142 failed. --- Code has been updated by krishantha. 1/7588 tests failed, no failures were new. http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-142/ -- Failing Jobs -- - WSO2 Carbon Trunk Build Process (Default Stage): 1 of 7588 tests failed. -- Code Changes -- krishantha (119345): cleaning up loggin antipattern -- Tests -- Existing Test Failures (1) - GSTestServerManager: Start server -- This message is automatically generated by Atlassian Bamboo___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Build problems with BAM2
Hi Maninda, Posting the error log where you get the build failure would be helpful to locate the errors. Thanks. On Tue, Jan 24, 2012 at 1:24 PM, Maninda Edirisooriya mani...@wso2.comwrote: BAM2 cannot build just using carbon trunk. It needs branch 3.2.0 to be built to include required dependencies into .m2 repo. And also it need to build patches in that branch. Then some dependencies have to be added manually. But still I could not build bam2 in products. Need some help. Thank you. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-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 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Build problems with BAM2
This is the error arises when I install bam2.
[INFO] Generating feature archive:
/home/maninda/carbon-source/carbon/products/bam2/modules/features/product/org.wso2.bam.styles.feature/target/org.wso2.bam.styles.feature-2.0.0-ALPHA.zip
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/home/maninda/carbon-source/carbon/products/bam2/modules/features/product/org.wso2.bam.styles.feature/pom.xml
to
/home/maninda/.m2/repository/org/wso2/bam/org.wso2.bam.styles.feature/2.0.0-ALPHA/org.wso2.bam.styles.feature-2.0.0-ALPHA.pom
[INFO] Installing
/home/maninda/carbon-source/carbon/products/bam2/modules/features/product/org.wso2.bam.styles.feature/target/org.wso2.bam.styles.feature-2.0.0-ALPHA.zip
to
/home/maninda/.m2/repository/org/wso2/bam/org.wso2.bam.styles.feature/2.0.0-ALPHA/org.wso2.bam.styles.feature-2.0.0-ALPHA.zip
[INFO]
[INFO] Building WSO2 Business Activity Monitor P2 Profile Generation Parent
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean {execution: default-clean}]
[INFO] [incremental-build:incremental-build {execution: default}]
[INFO] Verifying module descriptor ...
[INFO] Pom descriptor modification detected.
[INFO] Deleting
/home/maninda/carbon-source/carbon/products/bam2/modules/p2-profile-gen/target
[INFO] [clean:clean {execution: auto-clean}]
[INFO] Deleting
/home/maninda/carbon-source/carbon/products/bam2/modules/p2-profile-gen/target
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/home/maninda/carbon-source/carbon/products/bam2/modules/p2-profile-gen/pom.xml
to
/home/maninda/.m2/repository/org/wso2/bam/wso2bam-p2-profile-gen-parent/2.0.0-ALPHA/wso2bam-p2-profile-gen-parent-2.0.0-ALPHA.pom
[INFO]
[INFO] Building WSO2 BAM Server - BAM Server Profile Generation
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting
/home/maninda/carbon-source/carbon/products/bam2/modules/p2-profile-gen/product/target
[INFO] [incremental-build:incremental-build {execution: default}]
[INFO] Verifying module descriptor ...
[INFO] Pom descriptor modification detected.
[INFO] Deleting
/home/maninda/carbon-source/carbon/products/bam2/modules/p2-profile-gen/product/target
[INFO] [clean:clean {execution: auto-clean}]
[INFO] Deleting
/home/maninda/carbon-source/carbon/products/bam2/modules/p2-profile-gen/product/target
[INFO] [dependency:unpack {execution: 1-unpack-p2-agent-distribution}]
[INFO] Configured Artifact: org.wso2.carbon:wso2-p2-agent:3.2.0:zip
[INFO] Configured Artifact: org.wso2.carbon:wso2carbon-core:3.2.2:zip
[INFO] Expanding:
/home/maninda/.m2/repository/org/wso2/carbon/wso2-p2-agent/3.2.0/wso2-p2-agent-3.2.0.zip
into
/home/maninda/carbon-source/carbon/products/bam2/modules/p2-profile-gen/product/target/p2-agent
[INFO] Expanding:
/home/maninda/.m2/repository/org/wso2/carbon/wso2carbon-core/3.2.2/wso2carbon-core-3.2.2.zip
into
/home/maninda/carbon-source/carbon/products/bam2/modules/p2-profile-gen/product/target
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [carbon-p2:p2-repo-gen {execution: 2-p2-repo-generation}]
[INFO] Extracting feature
org.wso2.carbon:org.wso2.carbon.dashboard.dashboardpopulator.server.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.dashboard.feature
[INFO] Extracting feature
org.wso2.carbon:org.wso2.carbon.gadget.editor.ui.feature
[INFO] Extracting feature
org.wso2.carbon:org.wso2.carbon.gadget.editor.feature
[INFO] Extracting feature
org.wso2.carbon:org.wso2.carbon.cassandra.dataaccess.feature
[INFO] Extracting feature
org.wso2.carbon:org.wso2.carbon.cassandra.server.feature
[INFO] Extracting feature
org.wso2.carbon:org.wso2.carbon.logging.mgt.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.wsdl.tools.feature
[INFO] Extracting feature
org.wso2.carbon:org.wso2.carbon.security.mgt.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.datasource.feature
[INFO] Extracting feature
org.wso2.carbon:org.wso2.carbon.service.mgt.feature
[INFO] Extracting feature
org.wso2.carbon:org.wso2.carbon.transport.mgt.feature
[INFO] Extracting feature
org.wso2.carbon:org.wso2.carbon.event.server.feature
[INFO] Extracting feature
org.wso2.carbon:org.wso2.carbon.event.common.feature
[INFO] Extracting feature
org.wso2.carbon:org.wso2.carbon.registry.core.feature
[INFO] Extracting feature
org.wso2.carbon:org.wso2.carbon.registry.ui.menu.feature
[INFO] Extracting feature
org.wso2.carbon:org.wso2.carbon.registry.resource.properties.feature
[INFO] Extracting feature
org.wso2.carbon:org.wso2.carbon.bam.analyzer.feature
[INFO] Extracting feature
Re: [Carbon-dev] Build problems with BAM2
This is the content of log file. !SESSION 2012-01-24 12:12:31.758 --- eclipse.buildId=unknown java.version=1.6.0_26 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -application org.eclipse.equinox.p2.director -metadataRepository file:/home/maninda/carbon-source/carbon/products/bam2/modules/p2-profile-gen/product/target/p2-repo -artifactRepository file:/home/maninda/carbon-source/carbon/products/bam2/modules/p2-profile-gen/product/target/p2-repo -installIU org.wso2.carbon.dashboard.dashboardpopulator.server.feature.group/3.2.2,org.wso2.carbon.gadget.editor.ui.feature.group/3.2.0,org.wso2.carbon.gadget.editor.feature.group/3.2.0,org.wso2.carbon.cassandra.dataaccess.feature.group/3.2.2,org.wso2.carbon.cassandra.server.feature.group/3.2.3,org.wso2.carbon.dashboard.feature.group/3.2.2,org.wso2.carbon.gadget.ide.feature.group/3.2.3,org.wso2.carbon.logging.mgt.feature.group/3.2.2,org.wso2.carbon.security.mgt.feature.group/3.2.2,org.wso2.carbon.datasource.feature.group/3.2.2,org.wso2.carbon.transport.mgt.feature.group/3.2.0,org.wso2.carbon.event.server.feature.group/3.2.1,org.wso2.carbon.event.common.feature.group/3.2.0,org.wso2.carbon.registry.core.feature.group/3.2.0,org.wso2.carbon.registry.ui.menu.feature.group/3.2.0,org.wso2.carbon.registry.resource.properties.feature.group/3.2.0,org.wso2.carbon.bam.analyzer.feature.group/3.2.3,org.wso2.carbon.bam.receiver.server.feature.group/3.2.3,org.wso2.carbon.bam.presentation.ui.feature.group/3.2.3,org.wso2.carbon.reporting.feature.group/3.2.1,org.wso2.bam.styles.feature.group/2.0.0.ALPHA,org.wso2.carbon.identity.authenticator.token.feature.group/3.2.0,org.apache.synapse.wso2.feature.group/2.1.0.wso2v3,org.wso2.carbon.mediation.initializer.server.feature.group/3.2.1,org.wso2.carbon.task.server.feature.group/3.2.0,org.wso2.carbon.admin.mgt.server.feature.group/3.2.0,org.wso2.carbon.admin.mgt.ui.feature.group/3.2.0, -destination /home/maninda/carbon-source/carbon/products/bam2/modules/p2-profile-gen/product/target/wso2carbon-core-3.2.2/repository/components -profile WSO2CarbonProfile Command-line arguments: -application org.eclipse.equinox.p2.director -metadataRepository file:/home/maninda/carbon-source/carbon/products/bam2/modules/p2-profile-gen/product/target/p2-repo -artifactRepository file:/home/maninda/carbon-source/carbon/products/bam2/modules/p2-profile-gen/product/target/p2-repo -installIU org.wso2.carbon.dashboard.dashboardpopulator.server.feature.group/3.2.2,org.wso2.carbon.gadget.editor.ui.feature.group/3.2.0,org.wso2.carbon.gadget.editor.feature.group/3.2.0,org.wso2.carbon.cassandra.dataaccess.feature.group/3.2.2,org.wso2.carbon.cassandra.server.feature.group/3.2.3,org.wso2.carbon.dashboard.feature.group/3.2.2,org.wso2.carbon.gadget.ide.feature.group/3.2.3,org.wso2.carbon.logging.mgt.feature.group/3.2.2,org.wso2.carbon.security.mgt.feature.group/3.2.2,org.wso2.carbon.datasource.feature.group/3.2.2,org.wso2.carbon.transport.mgt.feature.group/3.2.0,org.wso2.carbon.event.server.feature.group/3.2.1,org.wso2.carbon.event.common.feature.group/3.2.0,org.wso2.carbon.registry.core.feature.group/3.2.0,org.wso2.carbon.registry.ui.menu.feature.group/3.2.0,org.wso2.carbon.registry.resource.properties.feature.group/3.2.0,org.wso2.carbon.bam.analyzer.feature.group/3.2.3,org.wso2.carbon.bam.receiver.server.feature.group/3.2.3,org.wso2.carbon.bam.presentation.ui.feature.group/3.2.3,org.wso2.carbon.reporting.feature.group/3.2.1,org.wso2.bam.styles.feature.group/2.0.0.ALPHA,org.wso2.carbon.identity.authenticator.token.feature.group/3.2.0,org.apache.synapse.wso2.feature.group/2.1.0.wso2v3,org.wso2.carbon.mediation.initializer.server.feature.group/3.2.1,org.wso2.carbon.task.server.feature.group/3.2.0,org.wso2.carbon.admin.mgt.server.feature.group/3.2.0,org.wso2.carbon.admin.mgt.ui.feature.group/3.2.0, -destination /home/maninda/carbon-source/carbon/products/bam2/modules/p2-profile-gen/product/target/wso2carbon-core-3.2.2/repository/components -profile WSO2CarbonProfile !ENTRY org.eclipse.osgi 4 0 2012-01-24 12:12:32.193 !MESSAGE Bundle reference:file:org.wso2.carbon.osgi.security-3.2.0-SNAPSHOT.jar@1:start not found. !ENTRY org.eclipse.equinox.p2.director 4 1 2012-01-24 12:12:39.693 !MESSAGE Cannot complete the install because one or more required items could not be found. !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2012-01-24 12:12:39.693 !MESSAGE Software being installed: WSO2 Carbon - Event Common Feature 3.2.0 (org.wso2.carbon.event.common.feature.group 3.2.0) !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2012-01-24 12:12:39.693 !MESSAGE Missing requirement: org.wso2.carbon.event.client 3.2.0 (org.wso2.carbon.event.client 3.2.0) requires 'package org.wso2.carbon.event.client.stub.generated [3.2.0,3.3.0)' but it could not be found !SUBENTRY 1 org.eclipse.equinox.p2.director 4 1 2012-01-24 12:12:39.693 !MESSAGE Cannot satisfy dependency: !SUBENTRY 2
Re: [Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk WSO2 Carbon - Platform Trunk #142 has FAILED (1 tests failed, no failures were new). Change made by krishantha.
Hi Amila, Could you please have a look. [ERROR] Failed to execute goal on project org.wso2.carbon.rule.ws.ui: Could not resolve dependencies for project org.wso2.carbon:org.wso2.carbon.rule.ws.ui:bundle:4.0.0-SNAPSHOT: Failure to find org.wso2.carbon:org.wso2.carbon.rule.ws.stub:jar:4.0.0-SNAPSHOT in http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the local repository, resolution will not be reattempted until the update interval of wso2-nexus has elapsed or updates are forced - [Help 1] Thanks Shammi On Tue, Jan 24, 2012 at 1:29 PM, Bamboo cbuil...@wso2.org wrote: [image: Failed] WSO2 Carbon Trunkhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK/› WSO2 Carbon - Platform Trunkhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK/› #142http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-142/ failed Code has been updated by krishanthahttp://builder4.us1.wso2.org:/bamboo/browse/author/krishantha . *1/7588* tests failed. Failing Jobshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-142/ Job Duration Tests[image: Failed] WSO2 Carbon Trunk Build Processhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-142/ (Default Stage) 280 minutes 1 of 7588 failed Logshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-142/log| Artifactshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-142/artifact Code Changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-142/commit/ View full change detailshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-142/commit/ krishanthahttp://builder4.us1.wso2.org:/bamboo/browse/author/krishantha cleaning up loggin antipattern 119345 Testshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-142/test View full test detailshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-142/test 1 Existing Test Failures Test Job GSTestServerManager startServerhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-142/test/case/5932756 WSO2 Carbon Trunk Build Processhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-142/test View Onlinehttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-142 | Add Commentshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-142?commentMode=true This message was sent by Atlassian Bamboohttp://builder4.us1.wso2.org:/bamboo . If you wish to stop receiving these emails edit your user profilehttp://builder4.us1.wso2.org:/bamboo/profile/userNotifications.actionor notify your administratorhttp://builder4.us1.wso2.org:/bamboo/viewAdministrators.action . ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Best Regards,* Shammi Jayasinghe* Senior Software Engineer; WSO2, Inc.; http://wso2.com, mobile: +94 71 4493085 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk WSO2 Carbon - Platform Trunk #142 has FAILED (1 tests failed, no failures were new). Change made by krishantha.
Hi Nuwan, Could you please have a look. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (default-compile) on project org.wso2.carbon.jaggery.core: Compilation failure: Compilation failure:23-Jan-2012 23:45:12[ERROR] /home/bamboo/Bamboo-3.4/source-repository/build-dir/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1/components/jaggery/org.wso2.carbon.jaggery.core/src/main/java/org/wso2/carbon/jaggery/core/WebAppManager.java:[17,29] cannot find symbol23-Jan-2012 23:45:12[ERROR] symbol : variable CommonManager23-Jan-2012 23:45:12[ERROR] location: class org.wso2.carbon.jaggery.core.WebAppManager23-Jan-2012 23:45:12[ERROR] 23-Jan-2012 23:45:12[ERROR] /home/bamboo/Bamboo-3.4/source-repository/build-dir/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1/components/jaggery/org.wso2.carbon.jaggery.core/src/main/java/org/wso2/carbon/jaggery/core/WebAppManager.java:[32,29] cannot find symbol23-Jan-2012 23:45:12[ERROR] symbol : variable CommonManager23-Jan-2012 23:45:12[ERROR] location: class org.wso2.carbon.jaggery.core.WebAppManager23-Jan-2012 23:45:12[ERROR] 23-Jan-2012 23:45:12[ERROR] /home/bamboo/Bamboo-3.4/source-repository/build-dir/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1/components/jaggery/org.wso2.carbon.jaggery.core/src/main/java/org/wso2/carbon/jaggery/core/WebAppManager.java:[74,48] cannot find symbol23-Jan-2012 23:45:12[ERROR] symbol : variable CommonManager23-Jan-2012 23:45:12[ERROR] location: class org.wso2.carbon.jaggery.core.WebAppManager23-Jan-2012 23:45:12[ERROR] 23-Jan-2012 23:45:12[ERROR] /home/bamboo/Bamboo-3.4/source-repository/build-dir/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1/components/jaggery/org.wso2.carbon.jaggery.core/src/main/java/org/wso2/carbon/jaggery/core/WebAppManager.java:[77,52] cannot find symbol23-Jan-2012 23:45:12[ERROR] symbol : variable CommonManager23-Jan-2012 23:45:12[ERROR] location: class org.wso2.carbon.jaggery.core.WebAppManager23-Jan-2012 23:45:12[ERROR] 23-Jan-2012 23:45:12[ERROR] /home/bamboo/Bamboo-3.4/source-repository/build-dir/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1/components/jaggery/org.wso2.carbon.jaggery.core/src/main/java/org/wso2/carbon/jaggery/core/WebAppManager.java:[77,12] cannot find symbol23-Jan-2012 23:45:12[ERROR] symbol : variable ScriptParser23-Jan-2012 23:45:12[ERROR] location: class org.wso2.carbon.jaggery.core.WebAppManager23-Jan-2012 23:45:12[ERROR] - [Help 2] Thanks Shammi On Tue, Jan 24, 2012 at 1:54 PM, Shammi Jayasinghe sha...@wso2.com wrote: Hi Amila, Could you please have a look. [ERROR] Failed to execute goal on project org.wso2.carbon.rule.ws.ui: Could not resolve dependencies for project org.wso2.carbon:org.wso2.carbon.rule.ws.ui:bundle:4.0.0-SNAPSHOT: Failure to find org.wso2.carbon:org.wso2.carbon.rule.ws.stub:jar:4.0.0-SNAPSHOT in http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the local repository, resolution will not be reattempted until the update interval of wso2-nexus has elapsed or updates are forced - [Help 1] Thanks Shammi On Tue, Jan 24, 2012 at 1:29 PM, Bamboo cbuil...@wso2.org wrote: [image: Failed] WSO2 Carbon Trunkhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK/› WSO2 Carbon - Platform Trunkhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK/› #142http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-142/ failed Code has been updated by krishanthahttp://builder4.us1.wso2.org:/bamboo/browse/author/krishantha . *1/7588* tests failed. Failing Jobshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-142/ Job Duration Tests[image: Failed] WSO2 Carbon Trunk Build Processhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-142/ (Default Stage) 280 minutes 1 of 7588 failed Logshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-142/log| Artifactshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-142/artifact Code Changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-142/commit/ View full change detailshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-142/commit/ krishanthahttp://builder4.us1.wso2.org:/bamboo/browse/author/krishantha cleaning up loggin antipattern 119345 Testshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-142/test View full test detailshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-142/test 1 Existing Test Failures Test Job GSTestServerManager startServerhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-142/test/case/5932756 WSO2 Carbon Trunk Build
[Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk WSO2 Carbon - Platform Trunk #143 has FAILED. Change made by 5 authors.
--- WSO2 Carbon Trunk WSO2 Carbon - Platform Trunk #143 failed. --- Code has been updated by rajika, dharshana, subash, lalaji, nuwan. No failed tests found, a possible compilation error. http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-143/ -- Failing Jobs -- - WSO2 Carbon Trunk Build Process (Default Stage): 1478 tests passed. -- Code Changes -- nuwan (119356): jaggery code subash (119354): Fixed Rigstry Node issues and implemented two new methods rajika (119353): Added new icons. -- This message is automatically generated by Atlassian Bamboo___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk WSO2 Carbon - Platform Trunk #144 has FAILED. Change made by sanjeewa and lalaji.
--- WSO2 Carbon Trunk WSO2 Carbon - Platform Trunk #144 failed. --- This build was manually triggered by BambooBuilder. No failed tests found, a possible compilation error. http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144/ -- Failing Jobs -- - WSO2 Carbon Trunk Build Process (Default Stage): No tests found. -- Code Changes -- sanjeewa (119359): aplying patch provided by nirmal for issue https://wso2.org/jira/browse/STRATOS-1992 lalaji (119361): Updated hostobjects poms lalaji (119362): Added jaggery feature to trunk -- This message is automatically generated by Atlassian Bamboo___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Build problems with BAM2
I manually built event in feature. It failed.
[INFO] Installing /home/maninda/carbon-source/carbon/features/event/pom.xml
to
/home/maninda/.m2/repository/org/wso2/carbon/event-feature/4.0.0-SNAPSHOT/event-feature-4.0.0-SNAPSHOT.pom
[INFO]
[INFO] Building WSO2 Carbon - Event Common Feature
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean {execution: default-clean}]
Downloading:
http://maven.wso2.org/nexus/content/groups/wso2-public//org/wso2/carbon/org.wso2.carbon.event.client/4.0.0-SNAPSHOT/org.wso2.carbon.event.client-4.0.0-SNAPSHOT.pom
[INFO] Unable to find resource
'org.wso2.carbon:org.wso2.carbon.event.client:pom:4.0.0-SNAPSHOT' in
repository wso2-nexus (
http://maven.wso2.org/nexus/content/groups/wso2-public/)
Downloading:
http://maven.wso2.org/nexus/content/groups/wso2-public//org/wso2/carbon/org.wso2.carbon.event.common/4.0.0-SNAPSHOT/org.wso2.carbon.event.common-4.0.0-SNAPSHOT.pom
[INFO] Unable to find resource
'org.wso2.carbon:org.wso2.carbon.event.common:pom:4.0.0-SNAPSHOT' in
repository wso2-nexus (
http://maven.wso2.org/nexus/content/groups/wso2-public/)
[WARNING] Overriding profile: 'product-wsas' (source: pom) with new
instance from source: pom
Downloading:
http://maven.wso2.org/nexus/content/groups/wso2-public//org/wso2/carbon/org.wso2.carbon.event.client/4.0.0-SNAPSHOT/org.wso2.carbon.event.client-4.0.0-SNAPSHOT.jar
[INFO] Unable to find resource
'org.wso2.carbon:org.wso2.carbon.event.client:jar:4.0.0-SNAPSHOT' in
repository wso2-nexus (
http://maven.wso2.org/nexus/content/groups/wso2-public/)
Downloading:
http://maven.wso2.org/nexus/content/groups/wso2-public//org/wso2/carbon/org.wso2.carbon.event.common/4.0.0-SNAPSHOT/org.wso2.carbon.event.common-4.0.0-SNAPSHOT.jar
[INFO] Unable to find resource
'org.wso2.carbon:org.wso2.carbon.event.common:jar:4.0.0-SNAPSHOT' in
repository wso2-nexus (
http://maven.wso2.org/nexus/content/groups/wso2-public/)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1) org.wso2.carbon:org.wso2.carbon.event.client:jar:4.0.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.wso2.carbon
-DartifactId=org.wso2.carbon.event.client -Dversion=4.0.0-SNAPSHOT
-Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.wso2.carbon
-DartifactId=org.wso2.carbon.event.client -Dversion=4.0.0-SNAPSHOT
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1)
org.wso2.carbon:org.wso2.carbon.event.common.feature:pom:4.0.0-SNAPSHOT
2) org.wso2.carbon:org.wso2.carbon.event.client:jar:4.0.0-SNAPSHOT
2) org.wso2.carbon:org.wso2.carbon.event.common:jar:4.0.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.wso2.carbon
-DartifactId=org.wso2.carbon.event.common -Dversion=4.0.0-SNAPSHOT
-Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.wso2.carbon
-DartifactId=org.wso2.carbon.event.common -Dversion=4.0.0-SNAPSHOT
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1)
org.wso2.carbon:org.wso2.carbon.event.common.feature:pom:4.0.0-SNAPSHOT
2) org.wso2.carbon:org.wso2.carbon.event.common:jar:4.0.0-SNAPSHOT
--
2 required artifacts are missing.
for artifact:
org.wso2.carbon:org.wso2.carbon.event.common.feature:pom:4.0.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/)
On Tue, Jan 24, 2012 at 2:19 PM, Tharindu Mathew thari...@wso2.com wrote:
Maninda,
Did you build the event feature?
You are missing the stub component of event.
On Tue, Jan 24, 2012 at 1:48 PM, Maninda Edirisooriya mani...@wso2.comwrote:
This is the content of log file.
!SESSION 2012-01-24 12:12:31.758
---
eclipse.buildId=unknown
java.version=1.6.0_26
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -application org.eclipse.equinox.p2.director
-metadataRepository
file:/home/maninda/carbon-source/carbon/products/bam2/modules/p2-profile-gen/product/target/p2-repo
-artifactRepository
file:/home/maninda/carbon-source/carbon/products/bam2/modules/p2-profile-gen/product/target/p2-repo
-installIU
Re: [Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk WSO2 Carbon - Platform Trunk #144 has FAILED. Change made by sanjeewa and lalaji.
Please Ignore this. I had to manually stop the job to test the Carbon server shutdown script. Now We are running that cleanup script before every build. thanks, Charith On Tue, Jan 24, 2012 at 2:33 PM, Bamboo cbuil...@wso2.org wrote: [image: Failed] WSO2 Carbon Trunkhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK/› WSO2 Carbon - Platform Trunkhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK/› #144http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144/ failed This build was manually triggered by BambooBuilderhttp://builder4.us1.wso2.org:/bamboo/browse/user/bamboo_builder . No failed tests found, a possible compilation error. Failing Jobshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144/ Job Duration Tests[image: Failed] WSO2 Carbon Trunk Build Processhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-144/ (Default Stage) 1 second No tests found Logshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-144/log| Artifactshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-144/artifact Code Changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144/commit/ View all 4 code changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144/commit/ lalaji http://builder4.us1.wso2.org:/bamboo/browse/author/lalaji Added jaggery feature to trunk 119362 lalajihttp://builder4.us1.wso2.org:/bamboo/browse/author/lalaji Updated hostobjects poms 119361 lalajihttp://builder4.us1.wso2.org:/bamboo/browse/author/lalaji Updated jaggery core pom 119360 1 more changes…http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144/commit View Onlinehttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144 | Add Commentshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144?commentMode=true This message was sent by Atlassian Bamboohttp://builder4.us1.wso2.org:/bamboo . If you wish to stop receiving these emails edit your user profilehttp://builder4.us1.wso2.org:/bamboo/profile/userNotifications.actionor notify your administratorhttp://builder4.us1.wso2.org:/bamboo/viewAdministrators.action . ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Charith Dhanushka Wickramarachchi Software Engineer WSO2 Inc http://wso2.com/ http://wso2.org/ blog http://charithwiki.blogspot.com/ twitter http://twitter.com/charithwiki Mobile : 0776706568 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Broker 2 in trunk
I can see lots of jar files have been committed to the svn. Can we get rid of these jar files? Thanks, Sameera. Adependencies/broker2/java/lib/jython-2.5.0.jar Adependencies/broker2/java/lib/org.eclipse.ui_3.4.1.M20080910-0800.jar A dependencies/broker2/java/lib/org.eclipse.jface.databinding_1.2.1.M20080827-0800a.jar Adependencies/broker2/java/lib/FastInfoset-1.2.2.jar A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.gtk.solaris.sparc_1.0.101.R34x_v20080731 A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.gtk.solaris.sparc_1.0.101.R34x_v20080731/META-INF A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.gtk.solaris.sparc_1.0.101.R34x_v20080731/META-INF/eclipse.inf A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.gtk.solaris.sparc_1.0.101.R34x_v20080731/META-INF/MANIFEST.MF A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.gtk.solaris.sparc_1.0.101.R34x_v20080731/META-INF/ECLIPSE.RSA A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.gtk.solaris.sparc_1.0.101.R34x_v20080731/META-INF/ECLIPSE.SF A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.gtk.solaris.sparc_1.0.101.R34x_v20080731/launcher.gtk.solaris.sparc.properties A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.gtk.solaris.sparc_1.0.101.R34x_v20080731/about.html Adependencies/broker2/java/lib/commons-pool-1.5.3.jar A dependencies/broker2/java/lib/org.eclipse.equinox.common_3.4.0.v20080421-2006.jar A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.101.R34x_v20080805 A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.101.R34x_v20080805/META-INF A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.101.R34x_v20080805/META-INF/eclipse.inf A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.101.R34x_v20080805/META-INF/MANIFEST.MF A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.101.R34x_v20080805/META-INF/ECLIPSE.RSA A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.101.R34x_v20080805/META-INF/ECLIPSE.SF A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.101.R34x_v20080805/launcher.gtk.linux.x86.properties A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.101.R34x_v20080805/about.html Adependencies/broker2/java/lib/servlet-api.jar Adependencies/broker2/java/lib/geronimo-jms_1.1_spec-1.0.jar Adependencies/broker2/java/lib/jul-to-slf4j-1.6.1.jar Adependencies/broker2/java/lib/log4j-1.2.12.jar A dependencies/broker2/java/lib/org.eclipse.core.databinding_1.1.1.M20080827-0800b.jar Adependencies/broker2/java/lib/log4j-1.2.13.jar A dependencies/broker2/java/lib/org.eclipse.osgi_3.4.2.R34x_v20080826-1230.jar Adependencies/broker2/java/lib/log4j-1.2.14.jar A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731 A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731/META-INF A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731/META-INF/eclipse.inf A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731/META-INF/MANIFEST.MF A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731/META-INF/ECLIPSE.RSA A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731/META-INF/ECLIPSE.SF A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731/launcher.win32.win32.x86.properties A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731/eclipse_1115.dll A dependencies/broker2/java/lib/org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731/about.html Adependencies/broker2/java/lib/poms Adependencies/broker2/java/lib/poms/commons-configuration-1.6.xml Adependencies/broker2/java/lib/poms/commons-digester-1.8.1.xml Adependencies/broker2/java/lib/poms/commons-pool-1.4.xml Adependencies/broker2/java/lib/poms/derby-10.6.1.0.xml Adependencies/broker2/java/lib/poms/commons-codec-1.3.xml Adependencies/broker2/java/lib/poms/commons-beanutils-core-1.8.0.xml Adependencies/broker2/java/lib/poms/commons-collections-3.2.xml Adependencies/broker2/java/lib/poms/commons-lang-2.2.xml Adependencies/broker2/java/lib/poms/slf4j-api-1.6.1.xml Adependencies/broker2/java/lib/poms/geronimo-jms_1.1_spec-1.0.xml Adependencies/broker2/java/lib/poms/commons-logging-1.0.4.xml Adependencies/broker2/java/lib/poms/junit-3.8.1.xml Adependencies/broker2/java/lib/poms/log4j-1.2.12.xml Adependencies/broker2/java/lib/poms/slf4j-log4j12-1.6.1.xml A
Re: [Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk WSO2 Carbon - Platform Trunk #144 has FAILED. Change made by sanjeewa and lalaji.
Can we send these Bamboo emails to carbon-build list? Thanks, Sameera. On Tue, Jan 24, 2012 at 2:33 PM, Bamboo cbuil...@wso2.org wrote: [image: Failed] WSO2 Carbon Trunkhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK/› WSO2 Carbon - Platform Trunkhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK/› #144http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144/ failed This build was manually triggered by BambooBuilderhttp://builder4.us1.wso2.org:/bamboo/browse/user/bamboo_builder . No failed tests found, a possible compilation error. Failing Jobshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144/ Job Duration Tests[image: Failed] WSO2 Carbon Trunk Build Processhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-144/ (Default Stage) 1 second No tests found Logshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-144/log| Artifactshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-144/artifact Code Changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144/commit/ View all 4 code changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144/commit/ lalaji http://builder4.us1.wso2.org:/bamboo/browse/author/lalaji Added jaggery feature to trunk 119362 lalajihttp://builder4.us1.wso2.org:/bamboo/browse/author/lalaji Updated hostobjects poms 119361 lalajihttp://builder4.us1.wso2.org:/bamboo/browse/author/lalaji Updated jaggery core pom 119360 1 more changes…http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144/commit View Onlinehttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144 | Add Commentshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144?commentMode=true This message was sent by Atlassian Bamboohttp://builder4.us1.wso2.org:/bamboo . If you wish to stop receiving these emails edit your user profilehttp://builder4.us1.wso2.org:/bamboo/profile/userNotifications.actionor notify your administratorhttp://builder4.us1.wso2.org:/bamboo/viewAdministrators.action . ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk WSO2 Carbon - Platform Trunk #144 has FAILED. Change made by sanjeewa and lalaji.
I also suggested that first but Srinath wanted these mails sent to carbon-dev, which I feel in retrospect was the correct decision. Now whenever the build breaks, people promptly attend to it since the mail is sent to carbon-dev. So, let's stick with sending the build status mails to carbon-dev. On Tue, Jan 24, 2012 at 3:04 PM, Sameera Jayasoma same...@wso2.com wrote: Can we send these Bamboo emails to carbon-build list? Thanks, Sameera. On Tue, Jan 24, 2012 at 2:33 PM, Bamboo cbuil...@wso2.org wrote: [image: Failed] WSO2 Carbon Trunkhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK/› WSO2 Carbon - Platform Trunkhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK/› #144http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144/ failed This build was manually triggered by BambooBuilderhttp://builder4.us1.wso2.org:/bamboo/browse/user/bamboo_builder . No failed tests found, a possible compilation error. Failing Jobshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144/ Job Duration Tests[image: Failed] WSO2 Carbon Trunk Build Processhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-144/ (Default Stage) 1 second No tests found Logshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-144/log| Artifactshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-144/artifact Code Changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144/commit/ View all 4 code changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144/commit/ lalaji http://builder4.us1.wso2.org:/bamboo/browse/author/lalaji Added jaggery feature to trunk 119362 lalajihttp://builder4.us1.wso2.org:/bamboo/browse/author/lalaji Updated hostobjects poms 119361 lalajihttp://builder4.us1.wso2.org:/bamboo/browse/author/lalaji Updated jaggery core pom 119360 1 more changes…http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144/commit View Onlinehttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144 | Add Commentshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144?commentMode=true This message was sent by Atlassian Bamboohttp://builder4.us1.wso2.org:/bamboo . If you wish to stop receiving these emails edit your user profilehttp://builder4.us1.wso2.org:/bamboo/profile/userNotifications.actionor notify your administratorhttp://builder4.us1.wso2.org:/bamboo/viewAdministrators.action . ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk WSO2 Carbon - Platform Trunk #144 has FAILED. Change made by sanjeewa and lalaji.
On Tue, Jan 24, 2012 at 3:09 PM, Afkham Azeez az...@wso2.com wrote: I also suggested that first but Srinath wanted these mails sent to carbon-dev, which I feel in retrospect was the correct decision. Now whenever the build breaks, people promptly attend to it since the mail is sent to carbon-dev. So, let's stick with sending the build status mails to carbon-dev. +1. Sameera. On Tue, Jan 24, 2012 at 3:04 PM, Sameera Jayasoma same...@wso2.comwrote: Can we send these Bamboo emails to carbon-build list? Thanks, Sameera. On Tue, Jan 24, 2012 at 2:33 PM, Bamboo cbuil...@wso2.org wrote: [image: Failed] WSO2 Carbon Trunkhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK/› WSO2 Carbon - Platform Trunkhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK/› #144http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144/ failed This build was manually triggered by BambooBuilderhttp://builder4.us1.wso2.org:/bamboo/browse/user/bamboo_builder . No failed tests found, a possible compilation error. Failing Jobshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144/ Job Duration Tests[image: Failed] WSO2 Carbon Trunk Build Processhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-144/ (Default Stage) 1 second No tests found Logshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-144/log| Artifactshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-144/artifact Code Changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144/commit/ View all 4 code changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144/commit/ lalaji http://builder4.us1.wso2.org:/bamboo/browse/author/lalaji Added jaggery feature to trunk 119362 lalajihttp://builder4.us1.wso2.org:/bamboo/browse/author/lalaji Updated hostobjects poms 119361 lalajihttp://builder4.us1.wso2.org:/bamboo/browse/author/lalaji Updated jaggery core pom 119360 1 more changes…http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144/commit View Onlinehttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144 | Add Commentshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-144?commentMode=true This message was sent by Atlassian Bamboohttp://builder4.us1.wso2.org:/bamboo . If you wish to stop receiving these emails edit your user profilehttp://builder4.us1.wso2.org:/bamboo/profile/userNotifications.actionor notify your administratorhttp://builder4.us1.wso2.org:/bamboo/viewAdministrators.action . ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Build problems with BAM2
Hi Maninda,
In the first build log you sent, I see different versions of jars are used
for building. For example, it has 3.2.0, 3.2.3 etc. And, the stub you are
trying to build right now is 4.0.0. I see several version mismatches there.
If I'm correct most of these should be 4.0.0-SNAPSHOT.
In this case, org.wso2.carbon.event.common.feature.group 3.2.0 is
apparently built, your last log is looking for
org.wso2.carbon.event.common.feature.group
4.0.0-SNAPSHOT. So, either there are incorrect versions in some bam sub
projects or you haven't taken a platform-wide svn update. Can you do a
quick check on the versions?
Regards,
--KasunG
On Tue, Jan 24, 2012 at 2:39 PM, Maninda Edirisooriya mani...@wso2.comwrote:
I manually built event in feature. It failed.
[INFO] Installing
/home/maninda/carbon-source/carbon/features/event/pom.xml to
/home/maninda/.m2/repository/org/wso2/carbon/event-feature/4.0.0-SNAPSHOT/event-feature-4.0.0-SNAPSHOT.pom
[INFO]
[INFO] Building WSO2 Carbon - Event Common Feature
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean {execution: default-clean}]
Downloading:
http://maven.wso2.org/nexus/content/groups/wso2-public//org/wso2/carbon/org.wso2.carbon.event.client/4.0.0-SNAPSHOT/org.wso2.carbon.event.client-4.0.0-SNAPSHOT.pom
[INFO] Unable to find resource
'org.wso2.carbon:org.wso2.carbon.event.client:pom:4.0.0-SNAPSHOT' in
repository wso2-nexus (
http://maven.wso2.org/nexus/content/groups/wso2-public/)
Downloading:
http://maven.wso2.org/nexus/content/groups/wso2-public//org/wso2/carbon/org.wso2.carbon.event.common/4.0.0-SNAPSHOT/org.wso2.carbon.event.common-4.0.0-SNAPSHOT.pom
[INFO] Unable to find resource
'org.wso2.carbon:org.wso2.carbon.event.common:pom:4.0.0-SNAPSHOT' in
repository wso2-nexus (
http://maven.wso2.org/nexus/content/groups/wso2-public/)
[WARNING] Overriding profile: 'product-wsas' (source: pom) with new
instance from source: pom
Downloading:
http://maven.wso2.org/nexus/content/groups/wso2-public//org/wso2/carbon/org.wso2.carbon.event.client/4.0.0-SNAPSHOT/org.wso2.carbon.event.client-4.0.0-SNAPSHOT.jar
[INFO] Unable to find resource
'org.wso2.carbon:org.wso2.carbon.event.client:jar:4.0.0-SNAPSHOT' in
repository wso2-nexus (
http://maven.wso2.org/nexus/content/groups/wso2-public/)
Downloading:
http://maven.wso2.org/nexus/content/groups/wso2-public//org/wso2/carbon/org.wso2.carbon.event.common/4.0.0-SNAPSHOT/org.wso2.carbon.event.common-4.0.0-SNAPSHOT.jar
[INFO] Unable to find resource
'org.wso2.carbon:org.wso2.carbon.event.common:jar:4.0.0-SNAPSHOT' in
repository wso2-nexus (
http://maven.wso2.org/nexus/content/groups/wso2-public/)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1) org.wso2.carbon:org.wso2.carbon.event.client:jar:4.0.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.wso2.carbon
-DartifactId=org.wso2.carbon.event.client -Dversion=4.0.0-SNAPSHOT
-Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.wso2.carbon
-DartifactId=org.wso2.carbon.event.client -Dversion=4.0.0-SNAPSHOT
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1)
org.wso2.carbon:org.wso2.carbon.event.common.feature:pom:4.0.0-SNAPSHOT
2) org.wso2.carbon:org.wso2.carbon.event.client:jar:4.0.0-SNAPSHOT
2) org.wso2.carbon:org.wso2.carbon.event.common:jar:4.0.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.wso2.carbon
-DartifactId=org.wso2.carbon.event.common -Dversion=4.0.0-SNAPSHOT
-Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.wso2.carbon
-DartifactId=org.wso2.carbon.event.common -Dversion=4.0.0-SNAPSHOT
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1)
org.wso2.carbon:org.wso2.carbon.event.common.feature:pom:4.0.0-SNAPSHOT
2) org.wso2.carbon:org.wso2.carbon.event.common:jar:4.0.0-SNAPSHOT
--
2 required artifacts are missing.
for artifact:
org.wso2.carbon:org.wso2.carbon.event.common.feature:pom:4.0.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/)
On Tue, Jan 24, 2012 at 2:19 PM, Tharindu
Re: [Carbon-dev] Build problems with BAM2
You are building the wrong version.
Seems, you need go through the pain of learning maven ;)
On Tue, Jan 24, 2012 at 2:39 PM, Maninda Edirisooriya mani...@wso2.comwrote:
I manually built event in feature. It failed.
[INFO] Installing
/home/maninda/carbon-source/carbon/features/event/pom.xml to
/home/maninda/.m2/repository/org/wso2/carbon/event-feature/4.0.0-SNAPSHOT/event-feature-4.0.0-SNAPSHOT.pom
[INFO]
[INFO] Building WSO2 Carbon - Event Common Feature
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean {execution: default-clean}]
Downloading:
http://maven.wso2.org/nexus/content/groups/wso2-public//org/wso2/carbon/org.wso2.carbon.event.client/4.0.0-SNAPSHOT/org.wso2.carbon.event.client-4.0.0-SNAPSHOT.pom
[INFO] Unable to find resource
'org.wso2.carbon:org.wso2.carbon.event.client:pom:4.0.0-SNAPSHOT' in
repository wso2-nexus (
http://maven.wso2.org/nexus/content/groups/wso2-public/)
Downloading:
http://maven.wso2.org/nexus/content/groups/wso2-public//org/wso2/carbon/org.wso2.carbon.event.common/4.0.0-SNAPSHOT/org.wso2.carbon.event.common-4.0.0-SNAPSHOT.pom
[INFO] Unable to find resource
'org.wso2.carbon:org.wso2.carbon.event.common:pom:4.0.0-SNAPSHOT' in
repository wso2-nexus (
http://maven.wso2.org/nexus/content/groups/wso2-public/)
[WARNING] Overriding profile: 'product-wsas' (source: pom) with new
instance from source: pom
Downloading:
http://maven.wso2.org/nexus/content/groups/wso2-public//org/wso2/carbon/org.wso2.carbon.event.client/4.0.0-SNAPSHOT/org.wso2.carbon.event.client-4.0.0-SNAPSHOT.jar
[INFO] Unable to find resource
'org.wso2.carbon:org.wso2.carbon.event.client:jar:4.0.0-SNAPSHOT' in
repository wso2-nexus (
http://maven.wso2.org/nexus/content/groups/wso2-public/)
Downloading:
http://maven.wso2.org/nexus/content/groups/wso2-public//org/wso2/carbon/org.wso2.carbon.event.common/4.0.0-SNAPSHOT/org.wso2.carbon.event.common-4.0.0-SNAPSHOT.jar
[INFO] Unable to find resource
'org.wso2.carbon:org.wso2.carbon.event.common:jar:4.0.0-SNAPSHOT' in
repository wso2-nexus (
http://maven.wso2.org/nexus/content/groups/wso2-public/)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1) org.wso2.carbon:org.wso2.carbon.event.client:jar:4.0.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.wso2.carbon
-DartifactId=org.wso2.carbon.event.client -Dversion=4.0.0-SNAPSHOT
-Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.wso2.carbon
-DartifactId=org.wso2.carbon.event.client -Dversion=4.0.0-SNAPSHOT
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1)
org.wso2.carbon:org.wso2.carbon.event.common.feature:pom:4.0.0-SNAPSHOT
2) org.wso2.carbon:org.wso2.carbon.event.client:jar:4.0.0-SNAPSHOT
2) org.wso2.carbon:org.wso2.carbon.event.common:jar:4.0.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.wso2.carbon
-DartifactId=org.wso2.carbon.event.common -Dversion=4.0.0-SNAPSHOT
-Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.wso2.carbon
-DartifactId=org.wso2.carbon.event.common -Dversion=4.0.0-SNAPSHOT
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1)
org.wso2.carbon:org.wso2.carbon.event.common.feature:pom:4.0.0-SNAPSHOT
2) org.wso2.carbon:org.wso2.carbon.event.common:jar:4.0.0-SNAPSHOT
--
2 required artifacts are missing.
for artifact:
org.wso2.carbon:org.wso2.carbon.event.common.feature:pom:4.0.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/)
On Tue, Jan 24, 2012 at 2:19 PM, Tharindu Mathew thari...@wso2.comwrote:
Maninda,
Did you build the event feature?
You are missing the stub component of event.
On Tue, Jan 24, 2012 at 1:48 PM, Maninda Edirisooriya
mani...@wso2.comwrote:
This is the content of log file.
!SESSION 2012-01-24 12:12:31.758
---
eclipse.buildId=unknown
java.version=1.6.0_26
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -application org.eclipse.equinox.p2.director
Re: [Carbon-dev] About WSO2 ESB by Example - Pub/Sub in SOA sandesha2 issue
As the guide instructs did you use the given ant command to run the sample ? ant soapjmsclient -Dsymbol=IBM -DtopicName=SimpleStockQuoteService -Dcarbon_home=$CARBON_HOME ? where $CARBON_HOME, is the root location of one of the carbon servers used. Rajika On Mon, Jan 23, 2012 at 7:50 PM, Jorge Infante Osorio jorg...@uci.cuwrote: Hi all. I´m working in the implementation of this scenario: “A SOAP JMS client as a publisher” using WSO2 ESB by Example - Pub/Sub in SOA tutorial. ** ** ** ** When I try to implement the soap jms client I receive this error: ** ** log4j:WARN No appenders could be found for logger (org.apache.axiom.om.util.StAXUtils). log4j:WARN Please initialize the log4j system properly. Exception in thread main java.lang.ExceptionInInitializerError at org.apache.sandesha2.SandeshaModule.init(*SandeshaModule.java:86 *) at org.apache.axis2.context.ConfigurationContextFactory.initModules( *ConfigurationContextFactory.java:252*) at org.apache.axis2.context.ConfigurationContextFactory.init(* ConfigurationContextFactory.java:230*) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext( *ConfigurationContextFactory.java:93*) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem( *ConfigurationContextFactory.java:210*) at cu.uci.cdae.TopicPublisher.main(*TopicPublisher.java:32*) Caused by: *java.util.MissingResourceException*: Cannot find resource 'org.apache.sandesha2.i18n.resource' at org.apache.axis2.i18n.ProjectResourceBundle.getBundle(* ProjectResourceBundle.java:260*) at org.apache.sandesha2.i18n.SandeshaMessageHelper.clinit(* SandeshaMessageHelper.java:38*) ... 6 more ** ** In the mar file providing in [1] I cannot find the 'org.apache.sandesha2.i18n.resource' ** ** ** ** [1] http://wso2.org/files/pub-sub-sample-config.zip ** ** Saludos, Ing. Jorge Infante Osorio. J´Dpto Soluciones SOA. CDAE. Fac. 5. UCI. ** ** http://www.antiterroristas.cu/ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] About WSO2 ESB by Example - Pub/Sub in SOA sandesha2 issue
Hi, The said resource is located at *sandesha2-core *jar not in the sandesha2 mar. I'm not sure how this sample fulfill this dependency, but somehow this jar should be available in the classpath of the client. (Just fyi, I didn't see this jar in AS pack, may be it's available in ESB packs?) On Mon, Jan 23, 2012 at 7:50 PM, Jorge Infante Osorio jorg...@uci.cuwrote: Hi all. I´m working in the implementation of this scenario: “A SOAP JMS client as a publisher” using WSO2 ESB by Example - Pub/Sub in SOA tutorial. ** ** ** ** When I try to implement the soap jms client I receive this error: ** ** log4j:WARN No appenders could be found for logger (org.apache.axiom.om.util.StAXUtils). log4j:WARN Please initialize the log4j system properly. Exception in thread main java.lang.ExceptionInInitializerError at org.apache.sandesha2.SandeshaModule.init(*SandeshaModule.java:86 *) at org.apache.axis2.context.ConfigurationContextFactory.initModules( *ConfigurationContextFactory.java:252*) at org.apache.axis2.context.ConfigurationContextFactory.init(* ConfigurationContextFactory.java:230*) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext( *ConfigurationContextFactory.java:93*) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem( *ConfigurationContextFactory.java:210*) at cu.uci.cdae.TopicPublisher.main(*TopicPublisher.java:32*) Caused by: *java.util.MissingResourceException*: Cannot find resource 'org.apache.sandesha2.i18n.resource' at org.apache.axis2.i18n.ProjectResourceBundle.getBundle(* ProjectResourceBundle.java:260*) at org.apache.sandesha2.i18n.SandeshaMessageHelper.clinit(* SandeshaMessageHelper.java:38*) ... 6 more ** ** In the mar file providing in [1] I cannot find the 'org.apache.sandesha2.i18n.resource' ** ** ** ** [1] http://wso2.org/files/pub-sub-sample-config.zip ** ** Saludos, Ing. Jorge Infante Osorio. J´Dpto Soluciones SOA. CDAE. Fac. 5. UCI. ** ** http://www.antiterroristas.cu/ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Kasun Gajasinghe* Software Engineer; WSO2 Inc.; http://wso2.com , *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813* *blog: **http://blog.kasunbg.org* http://blog.kasunbg.org * twitter: **http://twitter.com/kasunbg* http://twitter.com/kasunbg * * ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Creating Apache Axis2 1.6.1-wso2v5 branch
Hi Devs, WSO2 Carbon trunk uses the Apache Axis2 1.6.1-wso2v4 version. This Axis2 version is released with the Carbon 3.2.3 release. I got some fixes which needs to go to the Axis2 branch, but I cannot commit them to 1.6.1-wso2v4. Since it has already been released. Hence I am planning to create Axis2 1.6.1-wso2v5 branch. During this process I will update the Carbon trunk to use this Axis2 version as well. Thanks, Sameera. -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Carbon build failure
I got the following failure with a full update this morning; [INFO] WSO2 WSF/Java - Distribution .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 2:39:44.779s [INFO] Finished at: Tue Jan 24 15:27:51 IST 2012 [INFO] Final Memory: 882M/1713M [INFO] [ERROR] Failed to execute goal on project org.wso2.carbon.rule.ws.ui: Could not resolve dependencies for project org.wso2.carbon:org.wso2.carbon.rule.ws.ui:bundle:4.0.0-SNAPSHOT: Could not find artifact org.wso2.carbon:org.wso2.carbon.rule.ws.stub:jar:4.0.0-SNAPSHOT in wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) - [Help 1] [ERROR] -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Creating Apache Axis2 1.6.1-wso2v5 branch
Hi, On Tue, Jan 24, 2012 at 4:44 PM, Sameera Jayasoma same...@wso2.com wrote: Hi Devs, WSO2 Carbon trunk uses the Apache Axis2 1.6.1-wso2v4 version. This Axis2 version is released with the Carbon 3.2.3 release. I got some fixes which needs to go to the Axis2 branch, but I cannot commit them to 1.6.1-wso2v4. Since it has already been released. Hence I am planning to create Axis2 1.6.1-wso2v5 branch. During this process I will update the Carbon trunk to use this Axis2 version as well. What about moving to axis 1.7 (1.7-SNAPSHOT) ? thanks, Thanks, Sameera. -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-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 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Carbon build failure
org.wso2.carbon.rule.ws.stub has not been added to service stubs pom.xml will add that. thanks, Amila. On Tue, Jan 24, 2012 at 4:55 PM, Afkham Azeez az...@wso2.com wrote: I got the following failure with a full update this morning; [INFO] WSO2 WSF/Java - Distribution .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 2:39:44.779s [INFO] Finished at: Tue Jan 24 15:27:51 IST 2012 [INFO] Final Memory: 882M/1713M [INFO] [ERROR] Failed to execute goal on project org.wso2.carbon.rule.ws.ui: Could not resolve dependencies for project org.wso2.carbon:org.wso2.carbon.rule.ws.ui:bundle:4.0.0-SNAPSHOT: Could not find artifact org.wso2.carbon:org.wso2.carbon.rule.ws.stub:jar:4.0.0-SNAPSHOT in wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) - [Help 1] [ERROR] -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] [Trunk]Build issue : p2-profile-generation
Hi All, While i'm building the latest carbon trunk in a clean repository I got the following error. And also .m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1327403376606.log has mentioned the *Error-2*. Finally found the solution in this post [1] and that answer worked for me. :) [1] http://stackoverflow.com/questions/6582849/eclipse-on-macosx-org-osgi-service-application-applicationexception-no-applica *Error -2* !ENTRY org.eclipse.osgi 4 0 2012-01-24 16:39:37.369 !MESSAGE Application error !STACK 1 *org.osgi.service.application.ApplicationException: No application id has been found.* at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:262) at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:29) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) = [ERROR] P2 publisher return code was 13 org.apache.maven.plugin.MojoFailureException: P2 publisher return code was 13 at org.wso2.maven.p2.RepositoryGenMojo.generateRepository(RepositoryGenMojo.java:254) at org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:204) at org.wso2.maven.p2.RepositoryGenMojo.execute(RepositoryGenMojo.java:191) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352 -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94714631794 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [Trunk]Build issue : p2-profile-generation
thanks Ajith, Denis encountered the same. I could not figure out. --Pradeep ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] WS-HumanTask Implementation - Rendering task input and output messages.
Hi All, In HumanTask implementation, we need to display the task's input message and construct the task's output based on data captured from the user who completes the task. For this purpose we thought of using JSP files to display the task input message and constructing the task output (both are XML messages). JSP files should be implemented by the user who implements the task. The resulting human task package structure would be like in [1] As of now we have the Carbon support of including external JSPs. But the problem arises when there are JAR files in the lib folder. (This is required as we need to enable the users to construct the task output message by using generated code rather than creating the output element manually.) Currently there's no mechanism to load these jar files from the lib folder. Sameera is looking into a way of supporting this in Carbon. At the Human Task architecture review, Srinath gave an alternative to this approach. That is to create a separate WAR file out of the JSP files and the lib folder and deploy it as a war . In this approach we include 2 links(for input and output) to the JSPs in the web app, at the task display page. But with this approach we need to do the task completion at the deployed web app. As the operations happen at 2 different places we do not have a way of managing authentication. Your input about these two approaches as well as any other ideas are appreciated. [1] https://docs.google.com/a/wso2.com/drawings/d/1ieqf9sBHVH1gPHX5B_ZlUTCRvVNT8Tw20L42M1Kqnzc/edit?hl=en_US Regards, SanjayaV -- Sanjaya Vithanagama Senior Software Engineer WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 71 342 2881 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] System Test Framework Integration with Bamboo trunk build.
We will have a separate Gdoc to capture the platform test scenarios. See [1] (in progress version) The test artifacts produced by us in these scenarios will be merged into the system framework. [1]https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0Arh4GwhkOX3ndEZnRll4eFhjRjhqVGlJUEd1b0FsZ0Ehl=en_US#gid=0 /Charitha On Fri, Jan 20, 2012 at 1:52 PM, Charitha Kankanamge chari...@wso2.com wrote: Hi Srinath, We already have TestPlan docs such as [1] which we maintain against each release. However we categorized them according to products. What we can do is, add an additional sheet with platform test scenarios and include the cases which needs to be done, which has already been automated etc.. [1]https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0AvhVRxNoCg0KdDJPY2RMN0xncTFPM1h5Y3NOblVCOEEhl=en_USpli=1#gid=27 /Charitha On Fri, Jan 20, 2012 at 1:28 PM, Srinath Perera srin...@wso2.com wrote: Shall we have a test metric defined in a google doc and keep track of what to be done etc through that test matrix? --Srinath On Fri, Jan 20, 2012 at 1:00 PM, Charitha Kankanamge chari...@wso2.com wrote: On Fri, Jan 20, 2012 at 11:44 AM, Krishantha Samaraweera krishan...@wso2.com wrote: Hi Srinath, On Fri, Jan 20, 2012 at 5:28 AM, Srinath Perera srin...@wso2.com wrote: Thanks Krishantha!! How good are we with test coverage (including introps and perf)? Can you send the current status and plan to cover other products? As I mentioned in the earlier mail, there were few issue with Ravana, the perf test framework. Recent updates to the framework causing some troubles with integration. I will work with Damitha to find possible solution. Sorry I forgot to mention about the interops tests. We haven't integrate interop tests to framework trunk yet. Dharshana is working on it. Will update the status once it is done. We may need to have a distributed product setup if we are going to cover other products. Since running 13 products on the same machine will not be practical. Currently automation team is more focusing on our main products. And, the plan is to automate system/platform test plans that is going to prepared by QA team. +1. Our plan is to come up with various test scenarios which involves multiple product interactions. These test artifacts will be checked-in to test artifacts directory of svn and automation team and QA team will integrate it with the system test framework. And, also includes automation fixes done for external issues. Did we start running Bamboo again since this is fixed? Bamboo scheduled builds are running now. Do we run introps and perf tests with this? --Srinath On Fri, Jan 20, 2012 at 12:28 AM, Krishantha Samaraweera krishan...@wso2.com wrote: We need to monitor how this works for few days. If everything runs smoothly then we can enable test failure notifications. Thanks, Krishantha. On Fri, Jan 20, 2012 at 12:23 AM, Krishantha Samaraweera krishan...@wso2.com wrote: Hi, We have done the $subject on Bamboo machine and it is working. You can find the last successful test build at [1]. Test framework has been configured to use packs generated by trunk build. The test setup consists of five products (ESB, G-Reg, AS, BPS and DSS) with registry mounts on top of Mysql. This include Selenium test for G-Reg as well. I had to exclude Ravana tests due to few issues after updating the Ravana framework. Will get them fix by tomorrow. Thanks, Krishantha. [1] http://wso2.org/bamboo/browse/WSO2CARBONTUNK-AUTOMATIONTEST-13/ -- Srinath Perera, Ph.D. Senior Software Architect, WSO2 Inc. Visiting Faculty, University of Moratuwa Member, Apache Software Foundation Research Scientist, Lanka Software Foundation Blog: http://srinathsview.blogspot.com/ Photos: http://www.flickr.com/photos/hemapani/ Phone: 0772360902 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Srinath Perera, Ph.D. Senior Software Architect, WSO2 Inc. Visiting Faculty, University of Moratuwa Member, Apache Software Foundation Research Scientist, Lanka Software Foundation Blog: http://srinathsview.blogspot.com/ Photos: http://www.flickr.com/photos/hemapani/ Phone: 0772360902 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] System Test Framework Integration with Bamboo trunk build.
Hi Shariq, IMO, we can think about Stratos deployment based on trunk builds after we finish with Stratos Services Deployment management tool. At the moment what we can easily do is to, setting up the framework to monitor SL. We can configure it to run once per every two days. WDYT? Thanks, Krishantha. On Mon, Jan 23, 2012 at 9:35 AM, Muhammed Shariq sha...@wso2.com wrote: On Fri, Jan 20, 2012 at 12:59 PM, Krishantha Samaraweera krishan...@wso2.com wrote: On Fri, Jan 20, 2012 at 9:51 AM, Muhammed Shariq sha...@wso2.com wrote: Hi Krishantha et al, If I am not mistaken we are running these test for products only right, at the moment? How about the possibility of running these test on the stratos services too ? I had a chat with Dhrashana and we most of the tests that covers multitenancy aspect, so its a matter of setting up a stratos deployment in the bamboo machins right? I can work with the automation team to get this running. IIRC we even used these test suite to smoke test SLive after migrations etc, so we already have it. +1, we have written automation test to run on Stratos services and products. These tests cover tenant and multi-tenancy aspects as well. Yes it is matter to setting the things in bamboo machine. But we need to solve resource problems first. You cannot run startos setup on a single machine. How about using the machines used to run the Dev environment to set up the trunk stratos builds. If I am not mistaken we have the scripts etc for Dev too. Now that we are moving to the trunk, the Dev environment should run on the trunk builds right? Also it would be ideal since any failures can be patched and verified then and there, so it will save cycles as well. Only issue is we need a to copy the packs to these machines and then set it up (would some scripts, scp etc work ?). Its important to automate this task, else we will be wasting cycles.! If we can somehow figure out a way to set this packs up remotely (ideally in the dev setup) then we could run the tests from the bamboo machines, and generate the results, notification etc. Setting up the dev cloud once a week should be sufficient IMO? My concern is that, once we start developing new features we usually do development and testing cycles with the product. Ultimately the services gets side lined until quite late in the release cycle. If we can run a full test round once a week maybe and get notifications of the failures (or on the build status dashboard itself), we wouldn't need to worry about the status of the trunk at any time. WDYT ? +1, As far as you admit that failures are not false positives :)) Of course I admit that there are issues ;)) On a related note, there was a thread on adding TestNG integration test to cover tenant aspects as well, wonder if we have made any progress in that front? Thinking about it, we first need to create a tenant, and also some of the tenant related test would require a proper setup (with mounting etc) prior to running the tests. Guess we need to put more thought into that? Integration tests are different from platform tests. Integration test covers features that grouped in to products. But Platform test covers integrated product deployment (whole platform). We already have test to check tenant aspects. Even you can specify your tenant on the test configuration and run tests on your tenant. Setting up stratos evn would be to call startos setup script though the automation framework. We may need to find a way for distributed deployment of each service. Yes we need to test the status of the current trunk with exact setup, configs etc. If not we can't be sure the trunks is stable in terms of functionality. Shall we try to come up with a plan and set this up ASAP, as part of the stabilization effort it self? Thanks, Krishantha. On Fri, Jan 20, 2012 at 12:23 AM, Krishantha Samaraweera krishan...@wso2.com wrote: Hi, We have done the $subject on Bamboo machine and it is working. You can find the last successful test build at [1]. Test framework has been configured to use packs generated by trunk build. The test setup consists of five products (ESB, G-Reg, AS, BPS and DSS) with registry mounts on top of Mysql. This include Selenium test for G-Reg as well. I had to exclude Ravana tests due to few issues after updating the Ravana framework. Will get them fix by tomorrow. Thanks, Krishantha. [1] http://wso2.org/bamboo/browse/WSO2CARBONTUNK-AUTOMATIONTEST-13/ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Thanks, Shariq. Phone: +94 777 202 225 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org
Re: [Carbon-dev] WS-HumanTask Implementation - Rendering task input and output messages.
Basically idea was to deploy the war that does UI for human tasks as a webapp and link to it rather than running it within carbon and dealing with class loaders. Problem is when we going to the UI that runs as a war, we need users to automatically login and access the page if user has already logged in to the carbon account. --Srinath On Tue, Jan 24, 2012 at 6:10 PM, Sanjaya Vithanagama sanja...@wso2.com wrote: Hi All, In HumanTask implementation, we need to display the task's input message and construct the task's output based on data captured from the user who completes the task. For this purpose we thought of using JSP files to display the task input message and constructing the task output (both are XML messages). JSP files should be implemented by the user who implements the task. The resulting human task package structure would be like in [1] As of now we have the Carbon support of including external JSPs. But the problem arises when there are JAR files in the lib folder. (This is required as we need to enable the users to construct the task output message by using generated code rather than creating the output element manually.) Currently there's no mechanism to load these jar files from the lib folder. Sameera is looking into a way of supporting this in Carbon. At the Human Task architecture review, Srinath gave an alternative to this approach. That is to create a separate WAR file out of the JSP files and the lib folder and deploy it as a war . In this approach we include 2 links(for input and output) to the JSPs in the web app, at the task display page. But with this approach we need to do the task completion at the deployed web app. As the operations happen at 2 different places we do not have a way of managing authentication. Your input about these two approaches as well as any other ideas are appreciated. [1]https://docs.google.com/a/wso2.com/drawings/d/1ieqf9sBHVH1gPHX5B_ZlUTCRvVNT8Tw20L42M1Kqnzc/edit?hl=en_US Regards, SanjayaV -- Sanjaya Vithanagama Senior Software Engineer WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 71 342 2881 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Srinath Perera, Ph.D. Senior Software Architect, WSO2 Inc. Visiting Faculty, University of Moratuwa Member, Apache Software Foundation Research Scientist, Lanka Software Foundation Blog: http://srinathsview.blogspot.com/ Photos: http://www.flickr.com/photos/hemapani/ Phone: 0772360902 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk WSO2 Carbon - Platform Trunk #146 has FAILED. Change made by 7 authors.
--- WSO2 Carbon Trunk WSO2 Carbon - Platform Trunk #146 failed. --- Code has been updated by rajika, tharindu, shammi, subash, amila, dinusha, buddhikac. No failed tests found, a possible compilation error. http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-146/ -- Failing Jobs -- - WSO2 Carbon Trunk Build Process (Default Stage): 7835 tests passed. -- Code Changes -- subash (119364): Added integration tests tobuild with the product rajika (119368): Fixed callback store keeps on growing issue if the back end is gone. dinusha (119378): Removing samples getting depoyed to dss-service. -- This message is automatically generated by Atlassian Bamboo___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk WSO2 Carbon - Platform Trunk #147 has FAILED. Change made by janaka, charith and amila.
--- WSO2 Carbon Trunk WSO2 Carbon - Platform Trunk #147 failed. --- Code has been updated by janaka, charith, amila. No failed tests found, a possible compilation error. http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-147/ -- Failing Jobs -- - WSO2 Carbon Trunk Build Process (Default Stage): 7835 tests passed. -- Code Changes -- amila (119392): appliying the patch for CARBON-12253 charith (119395): adding group based recovery for queue workers in case of a node failure charith (119396): applying a patch for ESBJAVA-884 thanks Charitham for Contribution -- This message is automatically generated by Atlassian Bamboo___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk WSO2 Carbon - Platform Trunk #147 has FAILED. Change made by janaka, charith and amila.
Hi, Following error[1] was due to not having the org.wso2.carbon.rule.ws.stub module included in the service-stubs pom.xml. I added and committed it. Thanks Shammi [1] [ERROR] Failed to execute goal on project org.wso2.carbon.rule.ws.ui: Could not resolve dependencies for project org.wso2.carbon:org.wso2.carbon.rule.ws.ui:bundle:4.0.0-SNAPSHOT: Failure to find org.wso2.carbon:org.wso2.carbon.rule.ws.stub:jar:4.0.0-SNAPSHOT in http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the local repository, resolution will not be reattempted until the update interval of wso2-nexus has elapsed or updates are forced - [Help 1] On Wed, Jan 25, 2012 at 7:59 AM, Bamboo cbuil...@wso2.org wrote: [image: Failed] WSO2 Carbon Trunkhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK/› WSO2 Carbon - Platform Trunkhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK/› #147http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-147/ failed Code has been updated by janakahttp://builder4.us1.wso2.org:/bamboo/browse/author/janaka, charith http://builder4.us1.wso2.org:/bamboo/browse/author/charith, amila http://builder4.us1.wso2.org:/bamboo/browse/author/amila. No failed tests found, a possible compilation error. Failing Jobshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-147/ Job Duration Tests[image: Failed] WSO2 Carbon Trunk Build Processhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-147/ (Default Stage) 319 minutes 7835 passed Logshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-147/log| Artifactshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-147/artifact Code Changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-147/commit/ View all 4 code changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-147/commit/ charith http://builder4.us1.wso2.org:/bamboo/browse/author/charith applying a patch for ESBJAVA-884http://builder4.us1.wso2.org:/bamboo/project/jiraRedirect.action?jiraIssueKey=ESBJAVA-884bambooProjectKey=WSO2CARBONTUNKthanks Charitham for Contribution 119396 charithhttp://builder4.us1.wso2.org:/bamboo/browse/author/charith adding group based recovery for queue workers in case of a node failure 119395 janakahttp://builder4.us1.wso2.org:/bamboo/browse/author/janaka Adding fix for CARBON-11411http://builder4.us1.wso2.org:/bamboo/project/jiraRedirect.action?jiraIssueKey=CARBON-11411bambooProjectKey=WSO2CARBONTUNK 119394 1 more changes…http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-147/commit View Onlinehttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-147 | Add Commentshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-147?commentMode=true This message was sent by Atlassian Bamboohttp://builder4.us1.wso2.org:/bamboo . If you wish to stop receiving these emails edit your user profilehttp://builder4.us1.wso2.org:/bamboo/profile/userNotifications.actionor notify your administratorhttp://builder4.us1.wso2.org:/bamboo/viewAdministrators.action . ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Best Regards,* Shammi Jayasinghe* Senior Software Engineer; WSO2, Inc.; http://wso2.com, mobile: +94 71 4493085 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [Carbon Studio] ESB Graphical editor - Example 1
Hi, We had a discussion on ESB Graphical Editor with Hiranya. In this discussion we figured out how to overcome existing issues in the editor. Followings are the proposed solutions. - We are not going to represent Local Entries graphically inside the editor, Instead we put them on the tool palette.Then user can add them to relevant mediators using the context menu. - And also we can add defined sequences to receive attribute in the Send Mediator using the context menu as above. It is not necessary to represent this relationship in graphically. And also following issues were recognized in this discussion. - When we add a new Sequence, a dialog box should not be appeared to request a name for sequence. - In Failover endpoint, Loadbalance endpoint, Switch mediator and Clone mediator, there should not be an option to add output connectors manually.It should be automated. - File name should be appeared in the editor header. - Defined endpoints should also go to the pallet as re-usable components. - Endpoints in the border should be handled in a better way. - When open the sequence editor diagram, area for the diagram should be auto generated. - Name of the sequence should be displayed in the top of the page as well as in the sequence. - Name of the mediators and endpoints should be appeared in their figure. - Mediator grouping should be added. - A suitable extensions should be used for ESB Graphical editor files and for Sequence editor files. Thanks, On Tue, Jan 24, 2012 at 12:18 PM, Viraj Rajaguru vi...@wso2.com wrote: Hi , I tried to generate a Sample Synapse Configuration (See attached file Synapse Configuration - Example 1.txt) using the ESB Graphical editor. There were some issues while design the diagram. - How can we represent the Local Entry graphically ? - Send mediator has only input connector and output connector (See attached Send_Mediator.png). How can we represent the value of the receive attribute in Send mediator.(For a example, send receive=geoResponseSeq .In this case geoResponseSeq is a defined sequence.How can we represent this relationship between sequence and Send mediator inside the graphical editor.) ? Please comment on these issues if you have any idea. Screen shots for Relevant Diagram for the Synapse Configuration - Example 1 and the generated Synapse configuration are attached with this. Thanks, -- *Viraj Rajaguru* email: vi...@wso2.com email%3avi...@wso2.com cell: +94 77 3683068 -- *Viraj Rajaguru* email: vi...@wso2.com email%3avi...@wso2.com cell: +94 77 3683068 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Fwd: Need help for Smooks in carbon studio
-- Forwarded message -- From: raja sekhar raj.amruthal...@gmail.com Date: Wed, Jan 25, 2012 at 10:03 AM Subject: Need help for Smooks in carbon studio To: carbon-dev@wso2.org carbon-dev@wso2.org Cc: raja sekhar raj.amruthal...@gmail.com Hi I am Raj... I saw your article How to perform Data Mapping via the Smooks Editor in WSO2 Carbon Studio ,which verygood and helped a lot to me. In this you have given CSV to xml example for a simple csv file with only one record type. But My requirement is to create csv smooks config file with multiple record types Like *TYPE|DOC_INDEX|ACCOUNT_NUMBER|BILLING_PERIOD_START* H|1|0XX|06/09/2009 *TYPE|DOC_INDEX|MI_DATE|MI_METERNUMBER|MI_READINGTYPE* M|1|07/10|097161888|TOT KWH M|1|07/10|097161888|ON PK KW *TYPE|DOC_INDEX|CP_DESC *P|1|CHARGE P|1|CHARGE H --- Header tyep M and P Details Pls,Can you give any suggesion to do mapping for this type of CSV -- Thanks Regards, Raj. -- Thanks Regards, Raj. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] System Test Framework Integration with Bamboo trunk build.
On Tue, Jan 24, 2012 at 6:51 PM, Krishantha Samaraweera krishan...@wso2.com wrote: Hi Shariq, IMO, we can think about Stratos deployment based on trunk builds after we finish with Stratos Services Deployment management tool. Yes +1. I had a chat with Chamith and Sanjaya regarding how we can setup the packs from bamboo to dev, and it seems we can use Puppet to handle the deployment in an elegant manner. So lets go with that. At the moment what we can easily do is to, setting up the framework to monitor SL. We can configure it to run once per every two days. WDYT? +1. For the moment I am building the stratos services locally and good news is most of the services start up without any errors / exceptions :). However there are a few issues, and I am working with the relevant teams to fix those. Will update once done. Thanks, Krishantha. On Mon, Jan 23, 2012 at 9:35 AM, Muhammed Shariq sha...@wso2.com wrote: On Fri, Jan 20, 2012 at 12:59 PM, Krishantha Samaraweera krishan...@wso2.com wrote: On Fri, Jan 20, 2012 at 9:51 AM, Muhammed Shariq sha...@wso2.comwrote: Hi Krishantha et al, If I am not mistaken we are running these test for products only right, at the moment? How about the possibility of running these test on the stratos services too ? I had a chat with Dhrashana and we most of the tests that covers multitenancy aspect, so its a matter of setting up a stratos deployment in the bamboo machins right? I can work with the automation team to get this running. IIRC we even used these test suite to smoke test SLive after migrations etc, so we already have it. +1, we have written automation test to run on Stratos services and products. These tests cover tenant and multi-tenancy aspects as well. Yes it is matter to setting the things in bamboo machine. But we need to solve resource problems first. You cannot run startos setup on a single machine. How about using the machines used to run the Dev environment to set up the trunk stratos builds. If I am not mistaken we have the scripts etc for Dev too. Now that we are moving to the trunk, the Dev environment should run on the trunk builds right? Also it would be ideal since any failures can be patched and verified then and there, so it will save cycles as well. Only issue is we need a to copy the packs to these machines and then set it up (would some scripts, scp etc work ?). Its important to automate this task, else we will be wasting cycles.! If we can somehow figure out a way to set this packs up remotely (ideally in the dev setup) then we could run the tests from the bamboo machines, and generate the results, notification etc. Setting up the dev cloud once a week should be sufficient IMO? My concern is that, once we start developing new features we usually do development and testing cycles with the product. Ultimately the services gets side lined until quite late in the release cycle. If we can run a full test round once a week maybe and get notifications of the failures (or on the build status dashboard itself), we wouldn't need to worry about the status of the trunk at any time. WDYT ? +1, As far as you admit that failures are not false positives :)) Of course I admit that there are issues ;)) On a related note, there was a thread on adding TestNG integration test to cover tenant aspects as well, wonder if we have made any progress in that front? Thinking about it, we first need to create a tenant, and also some of the tenant related test would require a proper setup (with mounting etc) prior to running the tests. Guess we need to put more thought into that? Integration tests are different from platform tests. Integration test covers features that grouped in to products. But Platform test covers integrated product deployment (whole platform). We already have test to check tenant aspects. Even you can specify your tenant on the test configuration and run tests on your tenant. Setting up stratos evn would be to call startos setup script though the automation framework. We may need to find a way for distributed deployment of each service. Yes we need to test the status of the current trunk with exact setup, configs etc. If not we can't be sure the trunks is stable in terms of functionality. Shall we try to come up with a plan and set this up ASAP, as part of the stabilization effort it self? Thanks, Krishantha. On Fri, Jan 20, 2012 at 12:23 AM, Krishantha Samaraweera krishan...@wso2.com wrote: Hi, We have done the $subject on Bamboo machine and it is working. You can find the last successful test build at [1]. Test framework has been configured to use packs generated by trunk build. The test setup consists of five products (ESB, G-Reg, AS, BPS and DSS) with registry mounts on top of Mysql. This include Selenium test for G-Reg as well. I had to exclude Ravana tests due to few issues after updating the Ravana framework. Will get them fix by tomorrow.
