On Wed, Jan 4, 2012 at 4:38 PM, Afkham Azeez wrote:
>
>
> On Wed, Jan 4, 2012 at 4:35 PM, Samisa Abeysinghe wrote:
>
>> I looked into some of the errors reported by Sonar and looks like it is a
>> good idea to fix them all.
>>
>> Can some Java geeks please look into this and comment on the fact
On Wed, Jan 4, 2012 at 4:35 PM, Samisa Abeysinghe wrote:
> I looked into some of the errors reported by Sonar and looks like it is a
> good idea to fix them all.
>
> Can some Java geeks please look into this and comment on the fact if it is
> a good idea to trust Sonar and just fix them all and m
I looked into some of the errors reported by Sonar and looks like it is a
good idea to fix them all.
Can some Java geeks please look into this and comment on the fact if it is
a good idea to trust Sonar and just fix them all and make it to count zero
warnings.
On Wed, Jan 4, 2012 at 3:05 PM, Sami
On Wed, Jan 4, 2012 at 2:59 PM, Charith Wickramarachchi wrote:
>
>
> On Wed, Jan 4, 2012 at 9:53 AM, Charith Wickramarachchi
> wrote:
>
>>
>>
>> On Tue, Jan 3, 2012 at 2:20 PM, Charith Wickramarachchi > > wrote:
>>
>>>
>>>
>>> On Tue, Jan 3, 2012 at 1:40 PM, Srinath Perera wrote:
>>>
Hi Sam
On Wed, Jan 4, 2012 at 9:53 AM, Charith Wickramarachchi wrote:
>
>
> On Tue, Jan 3, 2012 at 2:20 PM, Charith Wickramarachchi
> wrote:
>
>>
>>
>> On Tue, Jan 3, 2012 at 1:40 PM, Srinath Perera wrote:
>>
>>> Hi Samisa,
>>>
>>> Sonar runs on top of the source code, and Charith is working on it
>>>
Are you guys planning to graduate possible components after the
stabilization effort?.
Danushka
On Tue, Jan 3, 2012 at 3:15 PM, Afkham Azeez wrote:
> -1. That breaks the one-checkout & one-build concept. The building by
> parts is fine, but building from the root pom level is also essential. If
On Tue, Jan 3, 2012 at 2:20 PM, Charith Wickramarachchi wrote:
>
>
> On Tue, Jan 3, 2012 at 1:40 PM, Srinath Perera wrote:
>
>> Hi Samisa,
>>
>> Sonar runs on top of the source code, and Charith is working on it making
>> sonar work with our build. He will give details.
>>
>>
> Hi Samisa,
>
> Bas
Hi Pradeep,
I would like to insist that what we run from Bamboo is only mvn clean
install, not anything specific. Retinale is that Bamboo must build what
others are building. So I am -1 on a Bamboo profile.
--Srinath
On Tue, Jan 3, 2012 at 3:09 PM, Pradeep Fernando wrote:
> Hi all,
>
> Had a c
Hi
There will be alternatives in bamboo level, such as we can control the
building process* via the dependency management*, the solution will work as
follows
1. Once the first job finishes all the product jobs starts
running.
means as Pradeep mention the target * (*
Another thing is , if the above config is working fine then -> one checkout
one build is working fine.
we are not changing any of the defaults. you just have to do mvn clean
install to build all the products.
thanks,
--Pradeep
___
Carbon-dev mailing li
Hi,
We are creating unnecessary dependencies among modules. ESB product build
should not block subsequent product builds.
To have a working product we should have product pack, it should pass all
the integration test bound to that.
At the end of the day we need working product packs. With the cur
There is another problem in running all the product builds in parallel on
the same machine; integration tests will fail due to port binding
exceptions. To overcomes this, we need to change the integration tests in
each product to start servers with portoffsets unique to each product.
On Tue, Jan 3
-1. That breaks the one-checkout & one-build concept. The building by parts
is fine, but building from the root pom level is also essential. If we
don't do that, we will never know when the one-checkout one-build fails.
Basically, once this stabilization is done, there can be no failures at
product
Hi all,
Had a chat with Dushan. Now we are building the carbon source from the root
pom. The build is almost woking fine. (it fails at the product level).
The problem with this setup is, even though some products are building
fine, it has dependencies among product builds.
Ex. due to a docGen is
On Tue, Jan 3, 2012 at 1:40 PM, Srinath Perera wrote:
> Hi Samisa,
>
> Sonar runs on top of the source code, and Charith is working on it making
> sonar work with our build. He will give details.
>
>
Hi Samisa,
Basically what we use is sonar maven plugin where it runs the maven goal
sonar after
Hi Samisa,
Sonar runs on top of the source code, and Charith is working on it making
sonar work with our build. He will give details.
--Srinath
On Tue, Jan 3, 2012 at 1:36 PM, Samisa Abeysinghe wrote:
> When bamboo builds this, where would be the packs?
>
> Have we pointed those to be picked b
When bamboo builds this, where would be the packs?
Have we pointed those to be picked by Sonar?
On Tue, Jan 3, 2012 at 1:34 PM, Srinath Perera wrote:
> Current known failures in trunk are at
>
> WSO2 Stratos Manager - Distribution ... FAILURE [15.341s]
> SQS module
>
> There are two
Current known failures in trunk are at
WSO2 Stratos Manager - Distribution ... FAILURE [15.341s]
SQS module
There are two mails @ carbon-dev on those.
--Srinath
On Tue, Jan 3, 2012 at 1:12 PM, Afkham Azeez wrote:
>
>
> On Tue, Jan 3, 2012 at 11:39 AM, Samisa Abeysinghe wrote:
>>
>
On Tue, Jan 3, 2012 at 11:39 AM, Samisa Abeysinghe wrote:
> I see that all of past 25 builds are broken.
>
> What is the plan to get this to get to work all green? What is the ETA?
> Who/How many are building this?
>
I have been continuously building the trunk, and it has been succeeding up
to p
I see that all of past 25 builds are broken.
What is the plan to get this to get to work all green? What is the ETA?
Who/How many are building this?
Thanks,
Samisa...
Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Carbon
20 matches
Mail list logo
