[cmake-developers] [PATCH] Tell CTest about Apache Maven warnings

[David Cole]

Thanks. Looks reasonable. Merged/pushed to next:
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=fcf3208ac10942344d4e7302ca8351758ba26978

Expect it in the next release.

thx,
David


On Fri, Mar 18, 2011 at 4:51 AM, Rolf Eike Beer <eike at sf-mail.de> wrote:
> Hi,
>
> we had a lot of fun debugging our nightly builds in the last couple of days.
> Part of our build process are some programs that get build using Apache Maven
> and are used to generate other files later on. It's something like this:
>
> ADD_CUSTOM_COMMAND(
>        OUTPUT ${artifact}
>        DEPENDS ${sources}
>        WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}
>        COMMAND ${MAVEN_EXECUTABLE} --quiet install
>        COMMENT "Building Java artifacts using Apache Maven..."
>        VERBATIM
> )
> ADD_CUSTOM_TARGET(${target} ALL DEPENDS ${artifact})
>
> And then some other ADD_CUSTOM_COMMANDS that depend on ${target}. When this
> was run on any of our desktops it worked fine, when we log in to the build
> machines it works fine, but when it runs with cron it doesn't work (not even
> on the Windows hosts). Since the first errors we got in CDash log were those
> of the target files that could not be generated because the maven output was
> missing we suspected some sort of dependency problem. It took us a while to
> find out that the dependencies were fine and Maven really wrote out some
> errors but CTest just didn't catch them. At the end it was just JAVA_HOME
> environment not being set when running with cron (easily fixed by "source
> /etc/profile" in the nightly script).
>
> To prevent other people wasting their time hunting bugs that are simply not
> there: here is a small patch that tells CTest to detect Mavens error and
> warning messages.
>
> Eike
>
> _______________________________________________
> cmake-developers mailing list
> cmake-developers at cmake.org
> http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
>
>