[Pljava-dev] Some tips to keep mvn -X output to manageable size

The output from mvn -X can be very helpful in understanding
build issues, but it can also be so long it's tedious to look
through. Here are some tips:

1. The *first* time you run mvn, it downloads *tons* of build
dependencies into your local Maven repository, and all the
download progress messages are included in your output.
(Also, if you ever clean out or remove your local repository,
the same thing happens again on the *next* mvn run after that.)

So tip #1: run mvn once at first (or once right after emptying
the repo), then run mvn -X clean install *again* and save the
output that time, not the first time.

2. If the build issue is in the native code (pljava-so subproject),
run a full mvn clean install in the top pljava directory once,
then cd pljava-so and from then on run mvn -X clean install
only there, so your output only covers that part of the build.
Once that is succeeding, cd .. and retry a full build for
adventure's sake.

-Chap
_______________________________________________
Pljava-dev mailing list
Pljava-dev(at)lists(dot)pgfoundry(dot)org
http://lists.pgfoundry.org/mailman/listinfo/pljava-dev