On Fri, May 4, 2012 at 9:37 AM, Srinath Perera srin...@wso2.com wrote:
pls invite me as well when rescheduling
Sure, Srinath! Please excuse me for not inviting you personally. :)
On Thu, May 3, 2012 at 3:15 PM, Nirmal Fernando nir...@wso2.com wrote:
We've currently facing some issues
On Fri, May 4, 2012 at 11:46 AM, Srinath Perera srin...@wso2.com wrote:
Look like we cannot build the source packs?
There are several users questioning this in stackoverflow.
Also want to make sure we push all jars to M2 repos when we release
--Srinath
--
On Fri, May 4, 2012 at 11:57 AM, Ramith Jayasinghe ram...@wso2.com wrote:
Hi Guys,
I download the source pack of ESB and tried to build it (mvn clean
install). It failed.
So I have 2 questions about it.
1. Publicly available source pack is around 600MB in size. But when I
build the source
On Fri, May 4, 2012 at 12:48 PM, Paul Fremantle p...@wso2.com wrote:
Sure - Srinath got there first with that slot!
:)
11:30 BST is great.
Awesome! Will send an invitation!
Thanks
Paul
On 4 May 2012 08:13, Nirmal Fernando nir...@wso2.com wrote:
Hi Paul,
On Wed, May 2, 2012 at
Thanks Achala for the comprehensive update. I will svn up and check now.
On Fri, May 4, 2012 at 12:41 PM, Nuwan Bandara nu...@wso2.com wrote:
Who has made r125454 ? If such changes are made, please be careful enough
to do a full products build and see if they work okey.
On Fri, May 4, 2012
Hi all,
The recent product build task which is [Bamboo-Build] WSO2 Carbon
Products #85 says *No failed tests found, a possible compilation error.
*.
but actually in the full build log, it shows couple of integration test
failures. So the relevant parties of the test failures, probably get
---
WSO2 Carbon platform #156 failed.
---
Code has been updated by lalaji.
No failed tests found, a possible compilation error.
This has been fixed as of r126448.
Regards
Buddhika
On Fri, May 4, 2012 at 1:59 PM, Bamboo cbuil...@wso2.org wrote:
[image: Failed] WSO2 Carbonhttp://wso2.org/bamboo/browse/WSO2CARBON/›
platform http://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM/ ›
Ah yes. But 11am BST should be ok.
Paul
On 4 May 2012 08:27, Nirmal Fernando nir...@wso2.com wrote:
On Fri, May 4, 2012 at 12:50 PM, Nirmal Fernando nir...@wso2.com wrote:
On Fri, May 4, 2012 at 12:48 PM, Paul Fremantle p...@wso2.com wrote:
Sure - Srinath got there first with that
Hi,
In 3.2.0 branch we have aws.java.sdk orbit bundle and it is not there in
the trunk. Any specific reason for this issue?
We need this bundle for EC2 auto-scaling stuff. So shall we add this to
trunk?
Thank You.
Ranga.
--
Ranga Siriwardena
Software Engineer
WSO2 Inc.
I think thats a bug in TryIt. In fact it might even create a way of
attacking from one tenant to another? I think the right thing to do here is
to fix TryIt so each tenant uses only their own per-tenant services.
Paul
On 4 May 2012 09:42, Sanjeewa Malalgoda sanje...@wso2.com wrote:
Hi,
I
On Fri, May 4, 2012 at 2:08 PM, Ranga Siriwardena ra...@wso2.com wrote:
Hi,
In 3.2.0 branch we have aws.java.sdk orbit bundle and it is not there in
the trunk. Any specific reason for this issue?
We need this bundle for EC2 auto-scaling stuff. So shall we add this to
trunk?
Must have been
Hi,
This has been fixed as of r126448. Can you take an up of depedencies and
try.
Regards
Buddhika
On Fri, May 4, 2012 at 2:47 PM, Dimuthu Leelarathne dimut...@wso2.comwrote:
Hi all,
I am getting this error on revision 126436.
[ERROR] Failed to execute goal on project datanucleus-core:
On Fri, May 4, 2012 at 12:44 PM, Achala Aponso ach...@wso2.com wrote:
Hi,
The dashboard is not working due to the above commit.
So basically the dashboard component depends on the older version of
google-collect? In that case better revert the commit for the moment. It
would most certainly
HI Guys,
I built the Esb and CSG source packs from the trunk and unzipped them
checked weather they are build-able.
Apparently there are not. Both packs fails to build because of test
failures/skips and the reason for failures is tests are unable to
find 'SecVerifier.aar'
I'm guessing this may
Hi all,
$subject was started focusing following issues with the old implementation.
- Ease of maintainability in the long run
- All the core functions were separated into groups called modules.
- Error messages and site configs were separated into *.json configs.
- URL
Hi,
I think SecVerifier.aar is produced at products/integration. You have to
build it too.
On Fri, May 4, 2012 at 2:29 PM, Ramith Jayasinghe ram...@wso2.com wrote:
HI Guys,
I built the Esb and CSG source packs from the trunk and unzipped them
checked weather they are build-able.
On Fri, May 4, 2012 at 2:33 PM, Ruchira Wageesha ruch...@wso2.com wrote:
Hi all,
$subject was started focusing following issues with the old implementation.
- Ease of maintainability in the long run
- All the core functions were separated into groups called modules.
- Error
HI Achala,
Im trying to build the source pack (e.g.
wso2brs-1.2.0-SNAPSHOT-src.zip, wso2csg-1.0.0-alpha-src.zip ). So
maven can't find the SecVerifier.aar, which is configured using a
property in pom.xml ( i.e. sec.verifier.dir).
So there needs to be a way to ship this file with the packs?
If the fix breaks manager, it is not the proper fix. Can both of you
co-ordinate and figure out the proper fix?
The fix for Manager should have been checked with the dashboard, specially
since it was changing something in shindig.
On Fri, May 4, 2012 at 2:28 PM, Muhammed Shariq sha...@wso2.com
On Fri, May 4, 2012 at 2:28 PM, Muhammed Shariq sha...@wso2.com wrote:
On Fri, May 4, 2012 at 12:44 PM, Achala Aponso ach...@wso2.com wrote:
Hi,
The dashboard is not working due to the above commit.
So basically the dashboard component depends on the older version of
google-collect? In
Hi,
AFAIR there was an issue with SecVerifier.aar being copied from 3.2.0
distribution. (Not sure if its the same issue you facing). Try building
core/distribution/3.2.0 first.
thanks,
On Fri, May 4, 2012 at 2:42 PM, Ramith Jayasinghe ram...@wso2.com wrote:
HI Achala,
Im trying to build the
hi,
Also we will be using this structure for GS 2.0 jaggery App as well.
We can add some much MVC structure for GS 2.0
On Fri, May 4, 2012 at 2:40 PM, Nuwan Bandara nu...@wso2.com wrote:
On Fri, May 4, 2012 at 2:33 PM, Ruchira Wageesha ruch...@wso2.com wrote:
Hi all,
$subject was
Hi,
I built the Esb and CSG source packs from the trunk and unzipped them
checked weather they are build-able.
What do you mean??
Did you build the source without tests ? by any chance.
--Pradeep
___
Dev mailing list
Dev@wso2.org
On Fri, May 4, 2012 at 2:08 PM, Ranga Siriwardena ra...@wso2.com wrote:
Hi,
In 3.2.0 branch we have aws.java.sdk orbit bundle and it is not there in
the trunk. Any specific reason for this issue?
We need this bundle for EC2 auto-scaling stuff. So shall we add this to
trunk?
It should be
This is a totally different issue. He is building source packs, not the
code in the svn. So, the SecVerifier will not be found using relative
paths. You have to get it as a Maven dependency. The POMs have to be fixed.
On Fri, May 4, 2012 at 3:14 PM, Dimuthu Leelarathne dimut...@wso2.comwrote:
Hi Chathuranga,
This is not a problem with Bamboo, rather a problem with us. Let me explain
this further. This issue comes only if there is a p2-profile-gen failure.
The build abruptly stops and does not proceed even when we have -fn option
in Bamboo.
Since we have written this p2-profile-gen
---
Developer-Studio Eclipse-Tools #103 was successful.
---
This build was manually triggered by BambooBuilder.
carbon-p2-plugin in following pom files under platform/trunk/prodcuts have
been included as follows
artifactIdcarbon-p2-plugin/artifactId
version1.5-SNAPSHOT/version
I'm going to replace all those with ,
artifactIdcarbon-p2-plugin/artifactId
Hi,
I have fixed this issue now. Basically changed the dashboard common bundle
import version to refer to the old google-collect bundle. Also in Manager
we only use the dashboard server feature, so I had to add
the google-collect:1.0.0.wso2v2 bundle as a bundleDef in dashboard server
feature.
---
WSO2 Carbon platform #157 failed.
---
This build occurred because it is a dependant of
WSO2CARBON-CARBONCOREKERNELBUILD-214.
No failed tests found, a
Hi All,
Today we had another demo.
Participants were: Azeez, Srinath, Dimuthu, Damitha, Sameera, Pradeep,
Ranga, Lahiru, Sajith and myself.
First we gave a brief overview of the autoscaling architecture. Then we
started the demo.
We were able to demo end-end (LB - Controller -- Agent) scenario
+1 Go ahead with this.
Thanks,
Sameera.
On Fri, May 4, 2012 at 5:28 PM, Chethiya Abeysinghe cheth...@wso2.comwrote:
carbon-p2-plugin in following pom files under platform/trunk/prodcuts have
been included as follows
artifactIdcarbon-p2-plugin/artifactId
Hi Folks,
Do we need to start-up BAM as mandotory requirements, cos when i try to
invoke API info it gives following error..seems like it tries to connect
with BAM to publish some statistics
*(Product i am trying is APIManager -wso2am-1.0.0-M3)*
[2012-05-04 23:39:06,613] INFO -
---
WSO2 Carbon platform #158 was successful.
---
This build occurred because it is a dependant of
WSO2CARBON-CARBONCOREKERNELBUILD-215.
2029 tests in total.
Yes as of M3. But you have 2 options.
1. Remove the BAM handler from API configuration. This will stop pushing
events into BAM. Thus get rid of bellow error.
2. Or Just start the BAM server as per the README.txt says
Getting BAM configured should not take more than 5 mins.
On Sat, May 5, 2012
Hi Sumedha,
Thax for your kind response, it works after guide your steps, btw I do
have a few concerns over the exposed API End point,
i.e
let say I wanna access Youtube feed as follows in e.g curl -H
Authorization :Bearer 9nEQnijLZ0Gi0gZ6a3pZICktVUca*
Hi All,
Guess I need some help in understanding the real cause for issue
CARBON-12902 [3]. The issue can be easily re-producible in IS, Carbon
and ESB with following steps,
1. Start server
2. Login to management console
3. Restart the server without closing browser
4. Try to access a link in
Hi,
On Sat, May 5, 2012 at 7:18 AM, Amila Jayasekara ami...@wso2.com wrote:
Hi All,
Guess I need some help in understanding the real cause for issue
CARBON-12902 [3]. The issue can be easily re-producible in IS, Carbon
and ESB with following steps,
1. Start server
2. Login to management
On Sat, May 5, 2012 at 1:32 AM, Sumedha Rubasinghe sume...@wso2.com wrote:
On Sat, May 5, 2012 at 1:24 AM, Samisa Abeysinghe sam...@wso2.com wrote:
On Sat, May 5, 2012 at 12:57 AM, Sumedha Rubasinghe sume...@wso2.comwrote:
Yes as of M3. But you have 2 options.
1. Remove the BAM handler
Hi,
We wanted to track tenant manager inside a synapse mediator when we were
adding new modifications to Autoscaler component. How we can do it.I tried
it by adding scr reference to service component but it failed(As normal way
we did for other components - add scr to realmservice and then get
http://docs.wso2.org/display/ESB403/Enrich+Mediator
--
*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:
42 matches
Mail list logo
