Hi,
I tried to run 'mvn eclipse:eclipse' under 'products/manager', it
failed with "Request to merge when 'filtering' is not identical."
error.
Seems like this was caused by a change in the maven-eclipse-plugin
itself [1]. As suggested at [1], I could successfully build with
maven-eclipse-plugin 2
On Sun, Jan 8, 2012 at 11:25 AM, Harshana Martin wrote:
> Hi Senaka,
>
> On Tue, Dec 20, 2011 at 9:21 AM, Senaka Fernando wrote:
>
>> Hi Samisa,
>>
>> The info reports plugin is what broke the javadoc generation in carbon.
>> We tried various combinations last week but was not able to fix this.
Hi Senaka,
On Tue, Dec 20, 2011 at 9:21 AM, Senaka Fernando wrote:
> Hi Samisa,
>
> The info reports plugin is what broke the javadoc generation in carbon. We
> tried various combinations last week but was not able to fix this. What we
> understood that is Maven 3 was not picking the plugin defi
On Sun, Jan 8, 2012 at 10:00 AM, Afkham Azeez wrote:
>
>
> On Sun, Jan 8, 2012 at 9:10 AM, Charith Wickramarachchi
> wrote:
>
>>
>>
>> On Sun, Jan 8, 2012 at 6:24 AM, Afkham Azeez wrote:
>>
>>> The only way to reduce the possibility of this happening is to start
>>> servers with random portOffs
On Sun, Jan 8, 2012 at 9:10 AM, Charith Wickramarachchi wrote:
>
>
> On Sun, Jan 8, 2012 at 6:24 AM, Afkham Azeez wrote:
>
>> The only way to reduce the possibility of this happening is to start
>> servers with random portOffsets. Even then there could be clashes. Can we
>> stop the 3.2 build for
On Sun, Jan 8, 2012 at 6:24 AM, Afkham Azeez wrote:
> The only way to reduce the possibility of this happening is to start
> servers with random portOffsets. Even then there could be clashes. Can we
> stop the 3.2 build for the moment?
>
>
3.2.0 Build is running on a Remote machine using the Remo
The only way to reduce the possibility of this happening is to start
servers with random portOffsets. Even then there could be clashes. Can we
stop the 3.2 build for the moment?
--
Afkham Azeez
Sent from my phone
On Jan 8, 2012 12:39 AM, "Harshana Martin" wrote:
> Hi Azeez,
>
> On Sun, Jan 8, 20
Hi Azeez,
On Sun, Jan 8, 2012 at 12:30 AM, Afkham Azeez wrote:
> There is another Carbon server running it seems.
Yes. I think we need to think about this, since we have both trunk and
3.2.0 builds could go in parallel.
Due to this, build was hanged for few hours and i had to cancel the job.
There is another Carbon server running it seems.
Caused by: java.net.BindException: Address already in use 07-Jan-2012
00:22:08 at sun.nio.ch.Net.bind(Native Method)07-Jan-2012
00:22:08 at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:126)
On Sat, Jan 7, 2012
---
WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #84 failed (rerun once).
---
This build was manually triggered from the stage: Default Stage by
BambooBuil
---
WSO2 Carbon 3.2.0 > WSO2 Carbon - Platform 3.2.0 > #93 failed.
---
This build was triggered at the scheduled time of 12:00 AM
No failed tests found, a possibl
11 matches
Mail list logo
