The logging output during a regular build of matterhorn is crazy. Many debug
statements, tons of warnings and errors are printed to the commandline, so
nobody is able to pay attention to the important pieces anymore.
In order to overcome this issue, I invested some time into figuring out how to
configure logging in general and for eclipselink in special during the tests. I
have now added these two properties to the surefire plugin configuration:
<eclipselink.logging.level>
<java.util.logging.config.file>
which configure the logging as if during runtime. By altering the
java.util.logging.config.file entry, we can have the build use a different
logging configuration at any time. I also made the modification to use the
jdk's java.util.logging binding rather than the slfj4-simple. This gets rid of
all the garbage solr is logging to the console while creating the search index
and during operations.
Christoph and I have also spent a considerable amount of time removing warning
output from checkstyle in all of the modules. Please make sure to check your
build after you make changes and get rid of any warnings that appear. In case
you are not happy with settings of either checkstyle or any other build plugin,
just bring your concerns to list so we can discuss them, make adjustments and
have everybody on board to keep our build clean.
Tobias
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
