Jenkins was wedged on there anyway, so I rebooted the VM. You should be good to
go again.
I'm not aware of any easy way to be able to kill that test from Jenkins, but
perhaps you could try this:
http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#forkedProcessTimeoutInSeconds
-
Because of [1] and the input here in this mail thread, I added a "jdk1.7"
profile which is enabled by default on Java 7. With this profile, we use
JAXB api 2.2 und JAXB impl 2.2.5. With this, I got rid of the
NullpointerExceptions in multiple tests running with Java 7 [2].
Unfortunately we got some
We have again and again a problem to get our Windows build running after one of
our tests fails [1]. It looks like the test took to long. The process itself is
still existing and prevents Jenkins in the next build to delete the
camel-core-XXX.jar artifact. This is the reason for all next build f
Hi,
Forwarding to the users list.
On 26/03/12 15:36, Zemin Hu wrote:
Hi,
I have couple of RESTful web service that I want to use Camel as integration
point. I had a brief review for restlet which is supposed to be the
solution, but from I have seen, it's not straight forward to use:
1. straight
Hi,
I have couple of RESTful web service that I want to use Camel as integration
point. I had a brief review for restlet which is supposed to be the
solution, but from I have seen, it's not straight forward to use:
1. straight forward support/constrcut RESTful dynamic URL for both
and :
http://ho
