Hi again
After the same problem appeared again this weekend I have done some
more testing but still do not have any idea why the problem appears
because locally everything works as expected (even with the exact same
jar used on the server).
However I think I have found a solution for:
On Fri, Mar 18, 2011 at 6:23 AM, Rupert Westenthaler <rwes...@apache.org> wrote:
> Is it possible to make the loggings of the sling launcher used for the
> integration tests available? I was not able to find it on the web
> interface. This would be the only possibility to understand what
> happened in that specific case.
by adding to the CommandLine used by the JarExectutor the arguments
//add "-f -" argument to redirect logging to the command
cl.addArgument("-f");
cl.addArgument("-");
the loggings should be available in the console log accessible via the
hudson server.
If nobody objects I will commit this change to redirect the loggings
of the executed jar the the console on monday.
best
Rupert
--
| Rupert Westenthaler rupert.westentha...@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
