[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Kernel_4.0.0 > #34 has FAILED. Change made by hasini.

[Bamboo]

---
WSO2 Carbon BRANCH > Kernel_4.0.0 > #34 failed.
---
Code has been updated by hasini.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-KER000-34/


--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
hasini (135506):

>Fixing https://wso2.org/jira/browse/CARBON-13740



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Products_4.0.0 > #30 has FAILED (1 tests failed, no failures were new). Change made by prabatha.

[Bamboo]

---
WSO2 Carbon BRANCH > Products_4.0.0 > #30 failed.
---
Code has been updated by prabatha.
1/4 tests failed, no failures were new.

http://wso2.org/bamboo/browse/WCB001-PRO000-30/


--
Failing Jobs
--
  - Default Job (Default Stage): 1 of 4 tests failed.



--
Code Changes
--
prabatha (135502):

>simplifying the query model and improving excel datasource support



--
Tests
--
Existing Test Failures (1)
   - StratosManagerTestServerManager: Start server

--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] C-App synchronization in a Carbon cluster

[Kishanthan Thangarajah]

On Sat, Jul 28, 2012 at 6:43 PM, Isuru Suriarachchi  wrote:

>
>
> On Sat, Jul 28, 2012 at 4:06 AM, Samisa Abeysinghe wrote:
>
>> Charitha - good catch!
>>
>> Isuru, thanks for the quick fix!!
>>
>> AS folks, can we please do a preliminary verification of the fix done by
>> Isuru, before it hits the formal QA cycle?
>>
>
> On a separate thread, I've already asked Kicha to test this including all
> possible scenarios..
>

Yes, i'm in the process of testing those scenarios.

>
> Thanks,
> ~Isuru
>
>
>>
>>
>> On Fri, Jul 27, 2012 at 10:55 AM, Isuru Suriarachchi wrote:
>>
>>>
>>>
>>> On Thu, Jul 26, 2012 at 2:55 PM, Afkham Azeez  wrote:
>>>


 On Thu, Jul 26, 2012 at 12:17 AM, Isuru Suriarachchi wrote:

> Oh.. I was planning to create different directories for different
> tenants inside repository/carbonapps. But looks like I've missed that. 
> I'll
> fix it and let you know..


 Tenants have their own temp directory right? If so, why can't we use
 those directories to store these?

>>>
>>> Yes, that's better than having another set of tenant spaces under
>>> repository/carbonapps. So I fixed it that way and tested with ST and
>>> tenants. I'm going to commit it now.
>>>
>>> Charitha, please test it with GD on/off as well on next pack.
>>>
>>> Thanks,
>>> ~Isuru
>>>
>>>


>
> Thanks,
> ~Isuru
>
>
> On Wed, Jul 25, 2012 at 10:31 PM, Charitha Kankanamge <
> chari...@wso2.com> wrote:
>
>> Hi,
>>
>> It seems we have not thought about MT aspects of this model. Now, the
>> carbonapps directory is taken out from repository/deployment/server and 
>> the
>> all CApps will be stored in common carbonapps directory regardless of the
>> tenant who deployed CApp. Because of this, any tenant can see others 
>> CApps
>> :( I came across this [1] issue in latest AS probably because of this
>> change.
>>
>>
>> [1]https://wso2.org/jira/browse/CARBON-13691
>>
>>
>> On Fri, Jul 6, 2012 at 6:05 PM, Isuru Suriarachchi wrote:
>>
>>>  Hi all,
>>>
>>> I'm trying to fix [1]. Here's the root cause for this issue..
>>>
>>> Imagine a Carbon cluster with 2 nodes where the svn based deployment
>>> synchronizer (DS) is configured. When a C-App is deployed to node1, it 
>>> is
>>> extracted and individual artifacts are copied into respective hot
>>> directories. When the DS runs for the first time, it copies the C-App 
>>> into
>>> node2 and it will be deployed there. When the DS runs again in node1, it
>>> will try to copy the individual artifacts to node2. But node2 already 
>>> has
>>> those artifacts as the C-App id already deployed in node2. Therefore an 
>>> svn
>>> conflict occurs.
>>>
>>> To resolve this issue, there are two possible options..
>>>
>>> 1. Keeping all artifacts coming from C-Apps out of the repository
>>> (repository/deployment/server)
>>> 2. Keeping the original C-App out of the repository
>>>
>>> Initially I tried option 1 above and programetically called the
>>> relevant deployers for individual artifacts. But this creates lot of
>>> problems with some artifacts (Ex: ESB stuff). Therefore, I'm trying to
>>> solve the initial problem using option 2 above.
>>>
>>> I've taken the carbonapps directory out
>>> of repository/deployment/server directory and kept it as
>>> repository/carbonapps (we can change this if needed). Still the 
>>> carbonapps
>>> directory has hot deployment capabilities. But it won't be synchronized 
>>> by
>>> the DS. So when a C-App is deployed into node 1, it will be extracted 
>>> and
>>> only the individual artifacts will be copied into the repository. When 
>>> the
>>> DS runs, all needed artifacts will be synced to node 2. Therefore,
>>> functionality wise, there won't be any issues on node 2.
>>>
>>> But if someone logs into the management console of node 2 and go to
>>> the C-App list, nothing will be listed. Is this something we have to 
>>> fix?
>>> Because anyway in a RW/RO cluster, user can't use the management 
>>> console of
>>> the slave node.
>>>
>>> WDYT??
>>>
>>> Thanks,
>>> ~Isuru
>>>
>>> [1] https://wso2.org/jira/browse/CARBON-13598
>>>
>>> --
>>> Isuru Suriarachchi
>>> Senior Technical Lead
>>> WSO2 Inc. http://wso2.com
>>> email : is...@wso2.com
>>> blog : http://isurues.wordpress.com/
>>>
>>> lean . enterprise . middleware
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>
>
> --
> Isuru Suriarachchi
> Senior Technical Lead
> WSO2 Inc. http://wso2.com
> email : is...@wso2.com
> blog : http://isurue

Re: [Dev] Most of the service stubs generation are failing in branch {was : [Bamboo-Build] WSO2 Carbon BRANCH > Platform_4.0.0 > #54 has FAILED. Change made by prabatha, shammi and ajithn.}

[Pradeep Fernando]

theres a separate mail. SupunM is looking in to this.

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

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Platform_4.0.0 > #54 has FAILED. Change made by prabatha, shammi and ajithn.

[Bamboo]

---
WSO2 Carbon BRANCH > Platform_4.0.0 > #54 failed.
---
Code has been updated by prabatha, shammi, ajithn.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA000-54/


--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
ajithn (135500):

>Fixed test failure

prabatha (135502):

>simplifying the query model and improving excel datasource support

shammi (135501):

>Adding CG to product profiles



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Kernel_4.0.0 > #32 has FAILED. Change made by supunm.

[Pradeep Fernando]

The actual error is at the service stub level. Eventhough they are marked
as success, they dont get generated at all. SupunM is working on this.

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

Re: [Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Kernel_4.0.0 > #33 has FAILED. Change made by pradeep.

[Pradeep Fernando]

Hi,
due to the axis2-client modification, the service stub generation
fails.please look in to this.

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

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Products_4.0.0 > #29 has FAILED (1 tests failed). Change made by shammi, ajithn and Isuru Udana Loku Narangoda.

[Bamboo]

---
WSO2 Carbon BRANCH > Products_4.0.0 > #29 failed.
---
This build was manually triggered by BambooBuilder.
1/4 tests failed.

http://wso2.org/bamboo/browse/WCB001-PRO000-29/


--
Failing Jobs
--
  - Default Job (Default Stage): 1 of 4 tests failed.



--
Code Changes
--
ajithn (135500):

>Fixed test failure

shammi (135501):

>Adding CG to product profiles

shammi (135499):

>Adding dependencies to builder profile



--
Tests
--
New Test Failures (1)
   - StratosManagerTestServerManager: Start server

--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Platform_4.0.0 > #53 has FAILED. Change made by shammi and Isuru Udana Loku Narangoda.

[Bamboo]

---
WSO2 Carbon BRANCH > Platform_4.0.0 > #53 failed.
---
This build was manually triggered by BambooBuilder.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA000-53/


--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
shammi (135497):

>Fixing new paths 

shammi (135499):

>Adding dependencies to builder profile

Isuru Udana Loku Narangoda (135498):

>fixing ESBJAVA-1346



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Kernel_4.0.0 > #33 has FAILED. Change made by pradeep.

[Bamboo]

---
WSO2 Carbon BRANCH > Kernel_4.0.0 > #33 failed.
---
Code has been updated by pradeep.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-KER000-33/


--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
pradeep (135486):

>fixing CARBON-13502

pradeep (135485):

>removing snapshots



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Kernel_4.0.0 > #32 has FAILED. Change made by supunm.

[Shammi Jayasinghe]

Hi ,

We are experiencing following compilation failure in branch. Please have a
look.

build   28-Jul-2012 10:40:19[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
(default-compile) on project org.wso2.carbon.authenticator.proxy:
Compilation failure: Compilation failure:
build   28-Jul-2012 10:40:19[ERROR]
/home/bamboo/Bamboo-3.4/source-repository/build-dir/WCB001-KER000-JOB1/core/org.wso2.carbon.authenticator.proxy/4.0.0/src/main/java/org/wso2/carbon/authenticator/proxy/AuthenticationAdminClient.java:[31,41]
package org.wso2.carbon.authenticator.stub does not exist
build   28-Jul-2012 10:40:19[ERROR]
/home/bamboo/Bamboo-3.4/source-repository/build-dir/WCB001-KER000-JOB1/core/org.wso2.carbon.authenticator.proxy/4.0.0/src/main/java/org/wso2/carbon/authenticator/proxy/AuthenticationAdminClient.java:[32,41]
package org.wso2.carbon.authenticator.stub does not exist
build   28-Jul-2012 10:40:19[ERROR]
/home/bamboo/Bamboo-3.4/source-repository/build-dir/WCB001-KER000-JOB1/core/org.wso2.carbon.authenticator.proxy/4.0.0/src/main/java/org/wso2/carbon/authenticator/proxy/AuthenticationAdminClient.java:[45,12]
cannot find symbol
build   28-Jul-2012 10:40:19[ERROR] symbol  : class AuthenticationAdminStub
build   28-Jul-2012 10:40:19[ERROR] location: class
org.wso2.carbon.authenticator.proxy.AuthenticationAdminClient
build   28-Jul-2012 10:40:19[ERROR]
/home/bamboo/Bamboo-3.4/source-repository/build-dir/WCB001-KER000-JOB1/core/org.wso2.carbon.authenticator.proxy/4.0.0/src/main/java/org/wso2/carbon/authenticator/proxy/AuthenticationAdminClient.java:[76,11]
cannot find symbol
build   28-Jul-2012 10:40:19[ERROR] symbol  : class RememberMeData
build   28-Jul-2012 10:40:19[ERROR] location: class
org.wso2.carbon.authenticator.proxy.AuthenticationAdminClient
build   28-Jul-2012 10:40:19[ERROR]
/home/bamboo/Bamboo-3.4/source-repository/build-dir/WCB001-KER000-JOB1/core/org.wso2.carbon.authenticator.proxy/4.0.0/src/main/java/org/wso2/carbon/authenticator/proxy/AuthenticationAdminClient.java:[54,19]
cannot find symbol
build   28-Jul-2012 10:40:19[ERROR] symbol  : class AuthenticationAdminStub
build   28-Jul-2012 10:40:19[ERROR] location: class
org.wso2.carbon.authenticator.proxy.AuthenticationAdminClient
build   28-Jul-2012 10:40:19[ERROR]
/home/bamboo/Bamboo-3.4/source-repository/build-dir/WCB001-KER000-JOB1/core/org.wso2.carbon.authenticator.proxy/4.0.0/src/main/java/org/wso2/carbon/authenticator/proxy/AuthenticationAdminClient.java:[79,12]
cannot find symbol
build   28-Jul-2012 10:40:19[ERROR] symbol  : class RememberMeData
build   28-Jul-2012 10:40:19[ERROR] location: class
org.wso2.carbon.authenticator.proxy.AuthenticationAdminClient



Thanks
Shammi
On Sat, Jul 28, 2012 at 11:10 PM, Bamboo  wrote:

>  [image: Failed]  WSO2 Carbon 
> BRANCH›
> Kernel_4.0.0  › 
> #32
> failed
>
> Code has been updated by supunm
> .
>
> No failed tests found, a possible compilation error.
>   Failing Jobs Job
> Duration Tests[image: Failed]  Default 
> Job (Default
> Stage)  56 minutes  No tests found  
> Logs|
> Artifacts  
> Code
> Changes   View
> full change details
> supunm 
> fix for 
> CARBON-13725
> 135480 View Online  | Add
> Comments 
>
> This message was sent by Atlassian Bamboo .
>
> If you wish to stop receiving these emails edit your user 
> profileor notify
> your administrator .
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards,*

Shammi Jayasinghe*
Senior Software Engineer; WSO2, Inc.; http://wso2.com,
mobile: +94 71 4493085
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Kernel_4.0.0 > #32 has FAILED. Change made by supunm.

[Bamboo]

---
WSO2 Carbon BRANCH > Kernel_4.0.0 > #32 failed.
---
Code has been updated by supunm.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-KER000-32/


--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
supunm (135480):

>fix for CARBON-13725



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Platform build failure

[Suhothayan Sriskandarajah]

org.wso2.carbon.agent model had been rename to data-bridge long time ago,
hence please fix the usage-agent to depend on data-bridge instead.

Suho


On Sat, Jul 28, 2012 at 1:41 PM, Rajith Siriwardena  wrote:

> hi
> by referring to Amilam 's previous thread i removed it
> from /usage/org.wso2.carbon.usage.agent/2.0.0/pom.xml.
>
>
> On Sat, Jul 28, 2012 at 7:54 AM, Rajith Siriwardena wrote:
>
>> [WARNING] The POM for
>> org.eclipse.osgi:org.eclipse.osgi.services:jar:3.2.0.v20090520-1800 is
>> invalid, transitive dependencies (if any) will not be available, enable
>> debug logging for more details
>> [WARNING] The POM for org.wso2.carbon:org.wso2.carbon.agent:jar:4.0.0 is
>> missing, no dependency information available
>> [WARNING] The POM for
>> org.eclipse.equinox:org.eclipse.equinox.http.servlet:jar:1.0.200.v20090520-1800
>> is invalid, transitive dependencies (if any) will not be available, enable
>> debug logging for more details
>>
>>
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 1:09.094s
>> [INFO] Finished at: Sat Jul 28 07:50:07 IST 2012
>> [INFO] Final Memory: 480M/1520M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal on project org.wso2.carbon.usage.agent:
>> Could not resolve dependencies for project
>> org.wso2.carbon:org.wso2.carbon.usage.agent:bundle:2.0.0: Failure to find
>> org.wso2.carbon:org.wso2.carbon.agent:jar:4.0.0 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]
>> [ERROR]
>>
>>
>>
>> --
>> Rajith Siriwardana
>> Intern, WSO2 Inc.,
>> Mobile: +94 712732184
>>
>>
>
>
> --
> Rajith Siriwardana
> Intern, WSO2 Inc.,
> Mobile: +94 712732184
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*S. Suhothayan
*
Software Engineer,
Data Technologies Team,
 *WSO2, Inc. **http://wso2.com
 *
*lean.enterprise.middleware.*

*email: **s...@wso2.com* * cell: (+94) 779 756 757
blog: **http://suhothayan.blogspot.com/* *
twitter: **http://twitter.com/suhothayan* *
linked-in: **http://lk.linkedin.com/in/suhothayan*
*
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] C-App synchronization in a Carbon cluster

[Isuru Suriarachchi]

On Sat, Jul 28, 2012 at 8:33 PM, Harshana Martin  wrote:

> Hi Isuru,
>
> I believe this new C-App deploymement location can be derived using tenant?
>
Yes.. It's CARBON_HOME/tmp/tenants//carbonapps/

Thanks,
~Isuru

> Otherwise the Dev Studio C-App deployment feature will be broken.
>
> Thanks and Regards,
> Harshana
> On Jul 28, 2012 8:14 PM, "Isuru Suriarachchi"  wrote:
>
>>
>>
>> On Sat, Jul 28, 2012 at 4:06 AM, Samisa Abeysinghe wrote:
>>
>>> Charitha - good catch!
>>>
>>> Isuru, thanks for the quick fix!!
>>>
>>> AS folks, can we please do a preliminary verification of the fix done by
>>> Isuru, before it hits the formal QA cycle?
>>>
>>
>> On a separate thread, I've already asked Kicha to test this including all
>> possible scenarios..
>>
>> Thanks,
>> ~Isuru
>>
>>
>>>
>>>
>>> On Fri, Jul 27, 2012 at 10:55 AM, Isuru Suriarachchi wrote:
>>>


 On Thu, Jul 26, 2012 at 2:55 PM, Afkham Azeez  wrote:

>
>
> On Thu, Jul 26, 2012 at 12:17 AM, Isuru Suriarachchi 
> wrote:
>
>> Oh.. I was planning to create different directories for different
>> tenants inside repository/carbonapps. But looks like I've missed that. 
>> I'll
>> fix it and let you know..
>
>
> Tenants have their own temp directory right? If so, why can't we use
> those directories to store these?
>

 Yes, that's better than having another set of tenant spaces under
 repository/carbonapps. So I fixed it that way and tested with ST and
 tenants. I'm going to commit it now.

 Charitha, please test it with GD on/off as well on next pack.

 Thanks,
 ~Isuru


>
>
>>
>> Thanks,
>> ~Isuru
>>
>>
>> On Wed, Jul 25, 2012 at 10:31 PM, Charitha Kankanamge <
>> chari...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> It seems we have not thought about MT aspects of this model. Now,
>>> the carbonapps directory is taken out from repository/deployment/server 
>>> and
>>> the all CApps will be stored in common carbonapps directory regardless 
>>> of
>>> the tenant who deployed CApp. Because of this, any tenant can see others
>>> CApps :( I came across this [1] issue in latest AS probably because of 
>>> this
>>> change.
>>>
>>>
>>> [1]https://wso2.org/jira/browse/CARBON-13691
>>>
>>>
>>> On Fri, Jul 6, 2012 at 6:05 PM, Isuru Suriarachchi 
>>> wrote:
>>>
  Hi all,

 I'm trying to fix [1]. Here's the root cause for this issue..

 Imagine a Carbon cluster with 2 nodes where the svn based
 deployment synchronizer (DS) is configured. When a C-App is deployed to
 node1, it is extracted and individual artifacts are copied into 
 respective
 hot directories. When the DS runs for the first time, it copies the 
 C-App
 into node2 and it will be deployed there. When the DS runs again in 
 node1,
 it will try to copy the individual artifacts to node2. But node2 
 already
 has those artifacts as the C-App id already deployed in node2. 
 Therefore an
 svn conflict occurs.

 To resolve this issue, there are two possible options..

 1. Keeping all artifacts coming from C-Apps out of the repository
 (repository/deployment/server)
 2. Keeping the original C-App out of the repository

 Initially I tried option 1 above and programetically called the
 relevant deployers for individual artifacts. But this creates lot of
 problems with some artifacts (Ex: ESB stuff). Therefore, I'm trying to
 solve the initial problem using option 2 above.

 I've taken the carbonapps directory out
 of repository/deployment/server directory and kept it as
 repository/carbonapps (we can change this if needed). Still the 
 carbonapps
 directory has hot deployment capabilities. But it won't be 
 synchronized by
 the DS. So when a C-App is deployed into node 1, it will be extracted 
 and
 only the individual artifacts will be copied into the repository. When 
 the
 DS runs, all needed artifacts will be synced to node 2. Therefore,
 functionality wise, there won't be any issues on node 2.

 But if someone logs into the management console of node 2 and go to
 the C-App list, nothing will be listed. Is this something we have to 
 fix?
 Because anyway in a RW/RO cluster, user can't use the management 
 console of
 the slave node.

 WDYT??

 Thanks,
 ~Isuru

 [1] https://wso2.org/jira/browse/CARBON-13598

 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Platform_4.0.0 > #50 has FAILED. Change made by ajithn and buddhikac.

[Bamboo]

---
WSO2 Carbon BRANCH > Platform_4.0.0 > #50 failed.
---
Code has been updated by ajithn, buddhikac.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA000-50/


--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
buddhikac (135478):

>Fixing build issue.
>

ajithn (135479):

>Fixed test failures



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Platform_4.0.0 > #49 has FAILED. Change made by ajithn.

[Bamboo]

---
WSO2 Carbon BRANCH > Platform_4.0.0 > #49 failed.
---
Code has been updated by ajithn.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA000-49/


--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
ajithn (135476):

>Fixed test



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Products_4.0.0 > #26 has FAILED. Change made by amani.

[Bamboo]

---
WSO2 Carbon BRANCH > Products_4.0.0 > #26 failed.
---
Code has been updated by amani.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PRO000-26/


--
Failing Jobs
--
  - Default Job (Default Stage): 3 tests passed.



--
Code Changes
--
amani (135474):

>Adding pagination for archived log files.



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Platform Build Failure - branch : analytics

[Buddhika Chamith]

Fixed. Sorry for the inconvenience.

Regards
Buddhika

On Sat, Jul 28, 2012 at 4:03 PM, Kasun Indrasiri  wrote:

> Platform is updated.
>
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 3.512s
> [INFO] Finished at: Sat Jul 28 16:01:21 IST 2012
> [INFO] Final Memory: 28M/341M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
> (default-compile) on project org.wso2.carbon.analytics.hive: Compilation
> failure: Compilation failure:
> [ERROR]
> /home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/ServiceHolder.java:[27,46]
> package org.wso2.carbon.rssmanager.core.service does not exist
> [ERROR]
> /home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/ServiceHolder.java:[40,19]
> cannot find symbol
> [ERROR] symbol  : class RSSManagerService
> [ERROR] location: class org.wso2.carbon.analytics.hive.ServiceHolder
> [ERROR]
> /home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/ServiceHolder.java:[104,44]
> cannot find symbol
> [ERROR] symbol  : class RSSManagerService
> [ERROR] location: class org.wso2.carbon.analytics.hive.ServiceHolder
> [ERROR]
> /home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/ServiceHolder.java:[108,18]
> cannot find symbol
> [ERROR] symbol  : class RSSManagerService
> [ERROR] location: class org.wso2.carbon.analytics.hive.ServiceHolder
> [ERROR]
> /home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/internal/HiveServiceComponent.java:[42,46]
> package org.wso2.carbon.rssmanager.core.service does not exist
> [ERROR]
> /home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/internal/HiveServiceComponent.java:[202,40]
> cannot find symbol
> [ERROR] symbol  : class RSSManagerService
> [ERROR] location: class
> org.wso2.carbon.analytics.hive.internal.HiveServiceComponent
> [ERROR]
> /home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/internal/HiveServiceComponent.java:[210,42]
> cannot find symbol
> [ERROR] symbol  : class RSSManagerService
> [ERROR] location: class
> org.wso2.carbon.analytics.hive.internal.HiveServiceComponent
> [ERROR]
> /home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/impl/HiveExecutorServiceImpl.java:[20,39]
> cannot find symbol
> [ERROR] symbol  : class HiveContext
> [ERROR] location: package org.apache.hadoop.hive.metastore
> [ERROR]
> /home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/multitenancy/HiveAxis2ConfigObserver.java:[25,45]
> package org.wso2.carbon.rssmanager.core.entity does not exist
> [ERROR]
> /home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/multitenancy/HiveAxis2ConfigObserver.java:[26,45]
> package org.wso2.carbon.rssmanager.core.entity does not exist
> [ERROR]
> /home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/multitenancy/HiveAxis2ConfigObserver.java:[27,45]
> package org.wso2.carbon.rssmanager.core.entity does not exist
> [ERROR]
> /home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/multitenancy/HiveAxis2ConfigObserver.java:[28,45]
> package org.wso2.carbon.rssmanager.core.entity does not exist
> [ERROR]
> /home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/multitenancy/HiveAxis2ConfigObserver.java:[29,46]
> package org.wso2.carbon.rssmanager.core.service does not exist
> [ERROR]
> /home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/w

Re: [Dev] C-App synchronization in a Carbon cluster

[Harshana Martin]

Hi Isuru,

I believe this new C-App deploymement location can be derived using tenant?

Otherwise the Dev Studio C-App deployment feature will be broken.

Thanks and Regards,
Harshana
On Jul 28, 2012 8:14 PM, "Isuru Suriarachchi"  wrote:

>
>
> On Sat, Jul 28, 2012 at 4:06 AM, Samisa Abeysinghe wrote:
>
>> Charitha - good catch!
>>
>> Isuru, thanks for the quick fix!!
>>
>> AS folks, can we please do a preliminary verification of the fix done by
>> Isuru, before it hits the formal QA cycle?
>>
>
> On a separate thread, I've already asked Kicha to test this including all
> possible scenarios..
>
> Thanks,
> ~Isuru
>
>
>>
>>
>> On Fri, Jul 27, 2012 at 10:55 AM, Isuru Suriarachchi wrote:
>>
>>>
>>>
>>> On Thu, Jul 26, 2012 at 2:55 PM, Afkham Azeez  wrote:
>>>


 On Thu, Jul 26, 2012 at 12:17 AM, Isuru Suriarachchi wrote:

> Oh.. I was planning to create different directories for different
> tenants inside repository/carbonapps. But looks like I've missed that. 
> I'll
> fix it and let you know..


 Tenants have their own temp directory right? If so, why can't we use
 those directories to store these?

>>>
>>> Yes, that's better than having another set of tenant spaces under
>>> repository/carbonapps. So I fixed it that way and tested with ST and
>>> tenants. I'm going to commit it now.
>>>
>>> Charitha, please test it with GD on/off as well on next pack.
>>>
>>> Thanks,
>>> ~Isuru
>>>
>>>


>
> Thanks,
> ~Isuru
>
>
> On Wed, Jul 25, 2012 at 10:31 PM, Charitha Kankanamge <
> chari...@wso2.com> wrote:
>
>> Hi,
>>
>> It seems we have not thought about MT aspects of this model. Now, the
>> carbonapps directory is taken out from repository/deployment/server and 
>> the
>> all CApps will be stored in common carbonapps directory regardless of the
>> tenant who deployed CApp. Because of this, any tenant can see others 
>> CApps
>> :( I came across this [1] issue in latest AS probably because of this
>> change.
>>
>>
>> [1]https://wso2.org/jira/browse/CARBON-13691
>>
>>
>> On Fri, Jul 6, 2012 at 6:05 PM, Isuru Suriarachchi wrote:
>>
>>>  Hi all,
>>>
>>> I'm trying to fix [1]. Here's the root cause for this issue..
>>>
>>> Imagine a Carbon cluster with 2 nodes where the svn based deployment
>>> synchronizer (DS) is configured. When a C-App is deployed to node1, it 
>>> is
>>> extracted and individual artifacts are copied into respective hot
>>> directories. When the DS runs for the first time, it copies the C-App 
>>> into
>>> node2 and it will be deployed there. When the DS runs again in node1, it
>>> will try to copy the individual artifacts to node2. But node2 already 
>>> has
>>> those artifacts as the C-App id already deployed in node2. Therefore an 
>>> svn
>>> conflict occurs.
>>>
>>> To resolve this issue, there are two possible options..
>>>
>>> 1. Keeping all artifacts coming from C-Apps out of the repository
>>> (repository/deployment/server)
>>> 2. Keeping the original C-App out of the repository
>>>
>>> Initially I tried option 1 above and programetically called the
>>> relevant deployers for individual artifacts. But this creates lot of
>>> problems with some artifacts (Ex: ESB stuff). Therefore, I'm trying to
>>> solve the initial problem using option 2 above.
>>>
>>> I've taken the carbonapps directory out
>>> of repository/deployment/server directory and kept it as
>>> repository/carbonapps (we can change this if needed). Still the 
>>> carbonapps
>>> directory has hot deployment capabilities. But it won't be synchronized 
>>> by
>>> the DS. So when a C-App is deployed into node 1, it will be extracted 
>>> and
>>> only the individual artifacts will be copied into the repository. When 
>>> the
>>> DS runs, all needed artifacts will be synced to node 2. Therefore,
>>> functionality wise, there won't be any issues on node 2.
>>>
>>> But if someone logs into the management console of node 2 and go to
>>> the C-App list, nothing will be listed. Is this something we have to 
>>> fix?
>>> Because anyway in a RW/RO cluster, user can't use the management 
>>> console of
>>> the slave node.
>>>
>>> WDYT??
>>>
>>> Thanks,
>>> ~Isuru
>>>
>>> [1] https://wso2.org/jira/browse/CARBON-13598
>>>
>>> --
>>> Isuru Suriarachchi
>>> Senior Technical Lead
>>> WSO2 Inc. http://wso2.com
>>> email : is...@wso2.com
>>> blog : http://isurues.wordpress.com/
>>>
>>> lean . enterprise . middleware
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>
>
> --
> Isuru Suriar

Re: [Dev] C-App synchronization in a Carbon cluster

[Isuru Suriarachchi]

On Sat, Jul 28, 2012 at 4:06 AM, Samisa Abeysinghe  wrote:

> Charitha - good catch!
>
> Isuru, thanks for the quick fix!!
>
> AS folks, can we please do a preliminary verification of the fix done by
> Isuru, before it hits the formal QA cycle?
>

On a separate thread, I've already asked Kicha to test this including all
possible scenarios..

Thanks,
~Isuru


>
>
> On Fri, Jul 27, 2012 at 10:55 AM, Isuru Suriarachchi wrote:
>
>>
>>
>> On Thu, Jul 26, 2012 at 2:55 PM, Afkham Azeez  wrote:
>>
>>>
>>>
>>> On Thu, Jul 26, 2012 at 12:17 AM, Isuru Suriarachchi wrote:
>>>
 Oh.. I was planning to create different directories for different
 tenants inside repository/carbonapps. But looks like I've missed that. I'll
 fix it and let you know..
>>>
>>>
>>> Tenants have their own temp directory right? If so, why can't we use
>>> those directories to store these?
>>>
>>
>> Yes, that's better than having another set of tenant spaces under
>> repository/carbonapps. So I fixed it that way and tested with ST and
>> tenants. I'm going to commit it now.
>>
>> Charitha, please test it with GD on/off as well on next pack.
>>
>> Thanks,
>> ~Isuru
>>
>>
>>>
>>>

 Thanks,
 ~Isuru


 On Wed, Jul 25, 2012 at 10:31 PM, Charitha Kankanamge <
 chari...@wso2.com> wrote:

> Hi,
>
> It seems we have not thought about MT aspects of this model. Now, the
> carbonapps directory is taken out from repository/deployment/server and 
> the
> all CApps will be stored in common carbonapps directory regardless of the
> tenant who deployed CApp. Because of this, any tenant can see others CApps
> :( I came across this [1] issue in latest AS probably because of this
> change.
>
>
> [1]https://wso2.org/jira/browse/CARBON-13691
>
>
> On Fri, Jul 6, 2012 at 6:05 PM, Isuru Suriarachchi wrote:
>
>>  Hi all,
>>
>> I'm trying to fix [1]. Here's the root cause for this issue..
>>
>> Imagine a Carbon cluster with 2 nodes where the svn based deployment
>> synchronizer (DS) is configured. When a C-App is deployed to node1, it is
>> extracted and individual artifacts are copied into respective hot
>> directories. When the DS runs for the first time, it copies the C-App 
>> into
>> node2 and it will be deployed there. When the DS runs again in node1, it
>> will try to copy the individual artifacts to node2. But node2 already has
>> those artifacts as the C-App id already deployed in node2. Therefore an 
>> svn
>> conflict occurs.
>>
>> To resolve this issue, there are two possible options..
>>
>> 1. Keeping all artifacts coming from C-Apps out of the repository
>> (repository/deployment/server)
>> 2. Keeping the original C-App out of the repository
>>
>> Initially I tried option 1 above and programetically called the
>> relevant deployers for individual artifacts. But this creates lot of
>> problems with some artifacts (Ex: ESB stuff). Therefore, I'm trying to
>> solve the initial problem using option 2 above.
>>
>> I've taken the carbonapps directory out
>> of repository/deployment/server directory and kept it as
>> repository/carbonapps (we can change this if needed). Still the 
>> carbonapps
>> directory has hot deployment capabilities. But it won't be synchronized 
>> by
>> the DS. So when a C-App is deployed into node 1, it will be extracted and
>> only the individual artifacts will be copied into the repository. When 
>> the
>> DS runs, all needed artifacts will be synced to node 2. Therefore,
>> functionality wise, there won't be any issues on node 2.
>>
>> But if someone logs into the management console of node 2 and go to
>> the C-App list, nothing will be listed. Is this something we have to fix?
>> Because anyway in a RW/RO cluster, user can't use the management console 
>> of
>> the slave node.
>>
>> WDYT??
>>
>> Thanks,
>> ~Isuru
>>
>> [1] https://wso2.org/jira/browse/CARBON-13598
>>
>> --
>> Isuru Suriarachchi
>> Senior Technical Lead
>> WSO2 Inc. http://wso2.com
>> email : is...@wso2.com
>> blog : http://isurues.wordpress.com/
>>
>> lean . enterprise . middleware
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware


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


>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> Member; A

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Platform_4.0.0 > #48 has FAILED. Change made by amani.

[Bamboo]

---
WSO2 Carbon BRANCH > Platform_4.0.0 > #48 failed.
---
Code has been updated by amani.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA000-48/


--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
amani (135474):

>Adding pagination for archived log files.



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Platform_4.0.0 > #47 has FAILED. Change made by ajithn.

[Bamboo]

---
WSO2 Carbon BRANCH > Platform_4.0.0 > #47 failed.
---
Code has been updated by ajithn.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA000-47/


--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
ajithn (135458):

>increased the time that waiting for capp deploy



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Products_4.0.0 > #25 has FAILED. Change made by hiranya and ajithn.

[Bamboo]

---
WSO2 Carbon BRANCH > Products_4.0.0 > #25 failed.
---
Code has been updated by hiranya, ajithn.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PRO000-25/


--
Failing Jobs
--
  - Default Job (Default Stage): 3 tests passed.



--
Code Changes
--
hiranya (135456):

>Fixing a bug in the top 10 view of stats

hiranya (135453):

>Fixing a bug in top 10 view of subscriptions and a performance improvement in 
>the search function

ajithn (135458):

>increased the time that waiting for capp deploy



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Does CSG component creates roles in user store ?

[Suresh Attanayaka]

Hi,
Are these roles in the user store created by the CSG component ?

   - csg_unpublisher
   - csg_publisher

OT-Issue : https://wso2.org/jira/browse/CARBON-13737

Thanks,
-Suresh

-- 
Suresh Attanayake
Software Engineer; WSO2 Inc. http://wso2.com/
Blog : http://sureshatt.blogspot.com/
Twitter : https://twitter.com/sureshatt
LinkedIn : http://lk.linkedin.com/in/sureshatt
Mobile : +94755012060,+94770419136,+94710467976
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [API Store] Wrong and Very Expensive Mechanism used in getAPIsWithTag

[Senaka Fernando]

Hi all,

This came up in a discussion with Sanjiva et al, but there wasn't any
alternative proposed at that time. While working on service store stuff, I
noticed this once again. To ensure this gets fixed properly, I created an
issue mentioning a better way of doing the same, [1]. This is nothing new,
a test case was written in the Registry Kernel (long time back - I think
during the pre-carbon days) which does nearly the same thing. This is not
the best way, but its much much better than what we have today. Better if
this can be fixed for the release.

[1] https://wso2.org/jira/browse/APISTORE-526

Thanks,
Senaka.

-- 
*Senaka Fernando*
Member - Integration Technologies Management Committee;
Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org

E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando

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

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Platform_4.0.0 > #46 has FAILED. Change made by hiranya.

[Bamboo]

---
WSO2 Carbon BRANCH > Platform_4.0.0 > #46 failed.
---
Code has been updated by hiranya.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA000-46/


--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
hiranya (135456):

>Fixing a bug in the top 10 view of stats

hiranya (135453):

>Fixing a bug in top 10 view of subscriptions and a performance improvement in 
>the search function

hiranya (135454):

>Returning partially initialized API objects from the getAllAPIs for better UI 
>performance in Publisher



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Platform Build Failure - branch : analytics

[Kasun Indrasiri]

Platform is updated.

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 3.512s
[INFO] Finished at: Sat Jul 28 16:01:21 IST 2012
[INFO] Final Memory: 28M/341M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
(default-compile) on project org.wso2.carbon.analytics.hive: Compilation
failure: Compilation failure:
[ERROR]
/home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/ServiceHolder.java:[27,46]
package org.wso2.carbon.rssmanager.core.service does not exist
[ERROR]
/home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/ServiceHolder.java:[40,19]
cannot find symbol
[ERROR] symbol  : class RSSManagerService
[ERROR] location: class org.wso2.carbon.analytics.hive.ServiceHolder
[ERROR]
/home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/ServiceHolder.java:[104,44]
cannot find symbol
[ERROR] symbol  : class RSSManagerService
[ERROR] location: class org.wso2.carbon.analytics.hive.ServiceHolder
[ERROR]
/home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/ServiceHolder.java:[108,18]
cannot find symbol
[ERROR] symbol  : class RSSManagerService
[ERROR] location: class org.wso2.carbon.analytics.hive.ServiceHolder
[ERROR]
/home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/internal/HiveServiceComponent.java:[42,46]
package org.wso2.carbon.rssmanager.core.service does not exist
[ERROR]
/home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/internal/HiveServiceComponent.java:[202,40]
cannot find symbol
[ERROR] symbol  : class RSSManagerService
[ERROR] location: class
org.wso2.carbon.analytics.hive.internal.HiveServiceComponent
[ERROR]
/home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/internal/HiveServiceComponent.java:[210,42]
cannot find symbol
[ERROR] symbol  : class RSSManagerService
[ERROR] location: class
org.wso2.carbon.analytics.hive.internal.HiveServiceComponent
[ERROR]
/home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/impl/HiveExecutorServiceImpl.java:[20,39]
cannot find symbol
[ERROR] symbol  : class HiveContext
[ERROR] location: package org.apache.hadoop.hive.metastore
[ERROR]
/home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/multitenancy/HiveAxis2ConfigObserver.java:[25,45]
package org.wso2.carbon.rssmanager.core.entity does not exist
[ERROR]
/home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/multitenancy/HiveAxis2ConfigObserver.java:[26,45]
package org.wso2.carbon.rssmanager.core.entity does not exist
[ERROR]
/home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/multitenancy/HiveAxis2ConfigObserver.java:[27,45]
package org.wso2.carbon.rssmanager.core.entity does not exist
[ERROR]
/home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/multitenancy/HiveAxis2ConfigObserver.java:[28,45]
package org.wso2.carbon.rssmanager.core.entity does not exist
[ERROR]
/home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/multitenancy/HiveAxis2ConfigObserver.java:[29,46]
package org.wso2.carbon.rssmanager.core.service does not exist
[ERROR]
/home/kasun/development/wso2/wso2svn/carbon/platform/branches/4.0.0/components/analytics/org.wso2.carbon.analytics.hive/4.0.0/src/main/java/org/wso2/carbon/analytics/hive/impl/HiveExecutorServiceImpl.java:[311,16]
cannot find symbol
[ERROR] symbol  : variable HiveContext
[ERROR] location: class
org.wso2.carbon.analytics.hive.impl.HiveExecutorServiceImpl.ScriptCallable
[ERROR]
/home/kasun/deve

[Dev] Pagination Query Parameter in API Store

[Senaka Fernando]

Hi all,

In Beta2, the URI for the next page on the API Store is
https://10.0.0.14:9443/store/apis/list?currentPage=*2.0*. Are we still
using 1.0 and 2.0 to identify the currentPage in API Manager? Or was this
fixed? If not, please fix as it is ugly.

Thanks,
Senaka.

-- 
*Senaka Fernando*
Member - Integration Technologies Management Committee;
Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org

E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando

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

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Products_4.0.0 > #24 has FAILED. Change made by 5 authors.

[Bamboo]

---
WSO2 Carbon BRANCH > Products_4.0.0 > #24 failed.
---
Code has been updated by hiranya, prabatha, ajithn, ranga, shariq.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PRO000-24/


--
Failing Jobs
--
  - Default Job (Default Stage): 3 tests passed.



--
Code Changes
--
ajithn (135447):

>remove duplicate line

ranga (135445):

>Fixing scriptengine.version.mashup to 0.9.0-ALPHA1

hiranya (135444):

>Fixing a performance issue in getting API subscriptions by version



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Platform build failure

[Rajith Siriwardena]

hi
by referring to Amilam 's previous thread i removed it
from /usage/org.wso2.carbon.usage.agent/2.0.0/pom.xml.

On Sat, Jul 28, 2012 at 7:54 AM, Rajith Siriwardena  wrote:

> [WARNING] The POM for
> org.eclipse.osgi:org.eclipse.osgi.services:jar:3.2.0.v20090520-1800 is
> invalid, transitive dependencies (if any) will not be available, enable
> debug logging for more details
> [WARNING] The POM for org.wso2.carbon:org.wso2.carbon.agent:jar:4.0.0 is
> missing, no dependency information available
> [WARNING] The POM for
> org.eclipse.equinox:org.eclipse.equinox.http.servlet:jar:1.0.200.v20090520-1800
> is invalid, transitive dependencies (if any) will not be available, enable
> debug logging for more details
>
>
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 1:09.094s
> [INFO] Finished at: Sat Jul 28 07:50:07 IST 2012
> [INFO] Final Memory: 480M/1520M
> [INFO]
> 
> [ERROR] Failed to execute goal on project org.wso2.carbon.usage.agent:
> Could not resolve dependencies for project
> org.wso2.carbon:org.wso2.carbon.usage.agent:bundle:2.0.0: Failure to find
> org.wso2.carbon:org.wso2.carbon.agent:jar:4.0.0 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]
> [ERROR]
>
>
>
> --
> Rajith Siriwardana
> Intern, WSO2 Inc.,
> Mobile: +94 712732184
>
>


-- 
Rajith Siriwardana
Intern, WSO2 Inc.,
Mobile: +94 712732184
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Platform_4.0.0 > #45 has FAILED. Change made by prabatha, ajithn and shariq.

[Bamboo]

---
WSO2 Carbon BRANCH > Platform_4.0.0 > #45 failed.
---
Code has been updated by prabatha, ajithn, shariq.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA000-45/


--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
ajithn (135447):

>remove duplicate line

shariq (135451):

>Removing unused dependency.
>

prabatha (135449):

>improving update,create and delete functionalities



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Platform_4.0.0 > #44 has FAILED. Change made by hiranya and ranga.

[Bamboo]

---
WSO2 Carbon BRANCH > Platform_4.0.0 > #44 failed.
---
Code has been updated by hiranya, ranga.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA000-44/


--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
ranga (135445):

>Fixing scriptengine.version.mashup to 0.9.0-ALPHA1

hiranya (135444):

>Fixing a performance issue in getting API subscriptions by version



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Branch 4.0.0 build failure in Stratos usage-agent component

[Muhammed Shariq]

Removed the dependency to the old agent component ...

On Sat, Jul 28, 2012 at 10:22 AM, Ranga Siriwardena  wrote:

> Hi,
>
> $Subject.
>
> -- Forwarded message --
> From: WSO2 Carbon 3.2.2 Builder (US1) 
> Date: Sat, Jul 28, 2012 at 6:14 PM
> Subject: "WSO2 Carbon Continuous Build has FAILED
> /home/builder/carbon/platform/4.0.0"
> To: ra...@wso2.com
>
>
> [INFO] WSO2 Carbon - Autoscaler Feature .. SKIPPED
> [INFO] Autoscaler Service Module . SKIPPED
> [INFO] WSO2 Carbon - Autoscaler Feature .. SKIPPED
> [INFO] Tenant Aware Load Balancer Feature Aggregator Module  SKIPPED
> [INFO] WSO2 Carbon - Loadbalancer Endpoint Management Feature  SKIPPED
> [INFO] WSO2 Carbon - Gadget Generation Feature Aggregator Module  SKIPPED
> [INFO] WSO2 Carbon - Gadget Generation Server Feature  SKIPPED
> [INFO] WSO2 Carbon - Gadget Generation UI Feature  SKIPPED
> [INFO] WSO2 Carbon - Gadget Generation Feature ... SKIPPED
> [INFO] WSO2 Carbon - Cassandra Feature Aggregator Module . SKIPPED
> [INFO] WSO2 Carbon - Cassandra Explorer server Feature ... SKIPPED
> [INFO] WSO2 Carbon - Cassandra Explorer UI Feature ... SKIPPED
> [INFO] WSO2 Carbon - Cassandra Explorer Feature .. SKIPPED
> [INFO] WSO2 Carbon - Data Bridge - Cassandra Defn Storage Server Feature
>  SKIPPED
> [INFO] WSO2 Carbon - Data Bridge - Cassandra Defn Storage Aggregator
> Feature  SKIPPED
> [INFO] WSO2 Carbon - New Datasource Management Feature ... SKIPPED
> [INFO] WSO2 Jaggery Server - Features Aggregator Module .. SKIPPED
> [INFO] WSO2 Jaggery Server - Style Features .. SKIPPED
> [INFO] Jaggery Server Feature  SKIPPED
> [INFO] Jaggery Management UI Feature . SKIPPED
> [INFO] Jaggery aggregate Feature . SKIPPED
> [INFO] WSO2 Carbon - BAM Feature Aggregator Module ... SKIPPED
> [INFO] WSO2 Carbon - BAM Core Feature  SKIPPED
> [INFO] WSO2 Carbon - BAM Management UI Feature ... SKIPPED
> [INFO] WSO2 Carbon - Business Activity Monitoring Feature  SKIPPED
> [INFO] WSO2 Carbon - AppFactory Feature Aggregator Module  SKIPPED
> [INFO] WSO2 Carbon - AppFactory Server Feature ... SKIPPED
> [INFO] WSO2 Carbon - Platform Aggregator Pom . SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 57:42.630s
> [INFO] Finished at: Sat Jul 28 18:14:11 IST 2012
> [INFO] Final Memory: 1471M/1811M
> [INFO]
> 
> [ERROR] Failed to execute goal on project org.wso2.carbon.usage.agent:
> Could not resolve dependencies for project
> org.wso2.carbon:org.wso2.carbon.usage.agent:bundle:2.0.0: Could not find
> artifact org.wso2.carbon:org.wso2.carbon.agent:jar:4.0.0 in wso2-nexus (
> http://maven.wso2.org/nexus/content/groups/wso2-public/) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :org.wso2.carbon.usage.agent
>
>
> Thank You.
> Ranga.
>
> --
> Ranga Siriwardena
> Software Engineer
> WSO2 Inc.
>
>


-- 
Thanks,
Shariq.
Phone: +94 777 202 225
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Products_4.0.0 > #23 has FAILED. Change made by prabatha.

[Bamboo]

---
WSO2 Carbon BRANCH > Products_4.0.0 > #23 failed.
---
Code has been updated by prabatha.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PRO000-23/


--
Failing Jobs
--
  - Default Job (Default Stage): 3 tests passed.



--
Code Changes
--
prabatha (135440):

>removing the analyzer package properly from svn



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev