Hi Subash,
What is the status of this error? Would you be able to have a look?
Thanks,
Sameera.
On Sun, Mar 4, 2012 at 7:48 PM, Subash Chaturanga wrote:
>
>
> On Sun, Mar 4, 2012 at 7:26 PM, Senaka Fernando wrote:
>
>> Hi Subash,
>>
>> Let's try to do a build on a clean repo tomorrow and see
On Mon, Mar 5, 2012 at 8:27 AM, Pradeep Fernando wrote:
> Hi,
>
> I was looking in to the $subject for last couple of days. Right now
> transaction manager is tightly couples to the servlet container (tomcat).
> Atomikos get initialized through a tomcat listener. And the Transaction
> Factory get
On Mon, Mar 5, 2012 at 12:33 PM, Rajika Kumarasiri wrote:
> It seems the Cassandra version that you are using tightly couple into the
> an older version of the thrift. In that case we will have to maintain both.
I checked Cassandra next version 1.1.x series and it depends on libthrift
0.7.0 the
It seems the Cassandra version that you are using tightly couple into the
an older version of the thrift. In that case we will have to maintain both.
Rajika
On Mon, Mar 5, 2012 at 11:52 AM, Deependra Ariyadewa wrote:
>
>
> On Mon, Mar 5, 2012 at 11:41 AM, Rajika Kumarasiri wrote:
>
>>
>>> There
On Mon, Mar 5, 2012 at 11:41 AM, Rajika Kumarasiri wrote:
>
>> There is a dependency mismatch when I try to start Cassandra in Carbon
>> core with libthrift 0.8.0 ( carbon trunk libthrift version) but it works
>> fine with libthrift 0.6.1. Please advice me how to resolve this issue and
>> let me
Hi Deep,
I'd suggest that we stabilize build first, do this change, and do a
complete build to ensure nothing breaks, and then commit, lest this would
potentially introduce more instability. There was an offline discussion
with Azeez et al on the same $subject.
Thanks,
Senaka.
On Mon, Mar 5, 2012
>
>
> There is a dependency mismatch when I try to start Cassandra in Carbon
> core with libthrift 0.8.0 ( carbon trunk libthrift version) but it works
> fine with libthrift 0.6.1. Please advice me how to resolve this issue and
> let me know if you have any concern regarding above version changes.
Um took an up in webapp-mgt now and seems to build fine. I had already
built the kernal (i.e. https://svn.wso2.org/repos/wso2/trunk/carbon)
On Mon, Mar 5, 2012 at 11:10 AM, Afkham Azeez wrote:
> I think you don't have a proper kernel update
>
> On Mon, Mar 5, 2012 at 11:04 AM, Muhammed Shariq
Hi All,
I need to upgrade following dependencies in Carbon trunk to support
Cassandra 1.x.x.
concurrentlinkedhashmap-lru version 1.1 to 1.2
high-scale-lib version 1.0 to 1.1.2
antlr version 2.7.7 to 3.2
Also I need to add following dependency to trunk.
jamm version 0.2.5
There is a dependency
I think you don't have a proper kernel update
On Mon, Mar 5, 2012 at 11:04 AM, Muhammed Shariq wrote:
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile
> (default-com
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile
(default-compile) on project org.wso2.carbon.webapp.mgt: Compilation
failure: Compilation failure:
[ERROR]
/home/shariq/src/tru
Hi Isuru,
On Mon, Mar 5, 2012 at 8:09 AM, Isuru Suriarachchi wrote:
> Hi Kishanthan,
>
> As we are done with the context.xml support and other Tomcat samples,
> please trigger a build and provide a pack as M2 today.
>
+1, will do it today.
Thanks,
Kishanthan.
>
> Thanks,
> ~Isuru
>
> --
> Isu
Hi All,
As a milestone item for Jaggery M4, I have added the support of directory
based app deployment. this has been done, with some changes to Axis2 Kernal
and Carbon Core. Earlier convention was that when we were registering an
Axis2 deployer that it
is mandatory to specify a corresponding file
Hi Chathuri,
setting the default version to the latest supported version will solve our
issue.
Thanks,
Ishan.
On Sun, Mar 4, 2012 at 4:49 PM, Chathuri Wimalasena wrote:
> Hi Ishan,
>
> On Sat, Mar 3, 2012 at 5:17 PM, Ishan Jayawardena wrote:
>
>> Hi Chathuri,
>> I would like to elaborate on this
On Mon, Mar 5, 2012 at 8:27 AM, Pradeep Fernando wrote:
> Hi,
>
> I was looking in to the $subject for last couple of days. Right now
> transaction manager is tightly couples to the servlet container (tomcat).
> Atomikos get initialized through a tomcat listener. And the Transaction
> Factory get
On Sun, Mar 4, 2012 at 7:49 PM, Pradeep Fernando wrote:
> Hi,
>
> IMHO , we should make product builds independent from each other. That is,
> a product should be able to build on its own, (NO pom inheritance) . We can
> introduce a aggregate pom, to maintain the same user experience. (you build
Hi,
I was looking in to the $subject for last couple of days. Right now
transaction manager is tightly couples to the servlet container (tomcat).
Atomikos get initialized through a tomcat listener. And the Transaction
Factory get initialized by the tomcat itself. After that within the
dataservices
Hi Kishanthan,
As we are done with the context.xml support and other Tomcat samples,
please trigger a build and provide a pack as M2 today.
Thanks,
~Isuru
--
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/
lean . enterpris
---
Carbon-Kernel > Carbon-Products > #35 failed.
---
This build occurred because it is a dependant of
WSO2CARBONKERNEL-GRAPHITEBUILD-113.
16/30 tests failed, no
---
Carbon-Kernel > Carbon-Products > #34 failed.
---
This build occurred because it is a dependant of
WSO2CARBONKERNEL-GRAPHITEBUILD-112.
16/30 tests failed, no
Hi,
IMHO , we should make product builds independent from each other. That is,
a product should be able to build on its own, (NO pom inheritance) . We can
introduce a aggregate pom, to maintain the same user experience. (you build
from product level, you get all the products.)
With the above kind
On Sun, Mar 4, 2012 at 7:26 PM, Senaka Fernando wrote:
> Hi Subash,
>
> Let's try to do a build on a clean repo tomorrow and see whether this can
> be reproduced. If we cannot, we can clean the repo of the builder and try.
> I too did not get this when I last tried, but I have a feeling that my r
Hi again,
I also had a look into the log. Looks like P2 profile generation of nearly
all products are failing. Lets also double check on all recent changes
involving the introduction of commons.io as a dependency and/or changes to
the version of commons.io in the poms, if this is reproducible. I'd
---
Carbon-Kernel > Carbon-Products > #33 failed.
---
Code has been updated by charith.
16/30 tests failed, no failures were new.
http://builder4.us1.wso2.org:88
Hi Subash,
Let's try to do a build on a clean repo tomorrow and see whether this can
be reproduced. If we cannot, we can clean the repo of the builder and try.
I too did not get this when I last tried, but I have a feeling that my repo
might have things that have accumulated. Also, please build wi
Hi Ishan,
On Sat, Mar 3, 2012 at 5:17 PM, Ishan Jayawardena wrote:
> Hi Chathuri,
> I would like to elaborate on this issue[1]. I think we have to support
> defining/editing namespaces separately because namespaces do not
> belong to the "Properties" view of an element(because they are neither
>
26 matches
Mail list logo
