camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller <christian.muel...@gmail.com>
Subject Re: Camel.trunk.fulltest - Build # 641 - Still Unstable
Date Sat, 07 Jan 2012 23:16:38 GMT
@Claus: Could you please have a look at r1228756. I think I found a more
reliable way to solve CAMEL-4814.
Instead of creating the properties file on the fly (which is error prone on
some OS) we could simply set the port number as system property in the
setUp or setUpBeforeClass method and let Springs
PropertyPlaceholderConfigurer resolve them.
What do you think?

Best,
Christian

On Sat, Jan 7, 2012 at 9:46 PM, Apache Jenkins Server <
jenkins@builds.apache.org> wrote:

> The Apache Jenkins build system has built Camel.trunk.fulltest (build #641)
>
> Status: Still Unstable
>
> Check console output at
> https://builds.apache.org/job/Camel.trunk.fulltest/641/ to view the
> results.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message