References: <56C41C5B.9000809@lucee.org> <56C4D516.9010403@hogranch.com>
 <56C4D8C4.4010809@anastigmatix.net> <56C50E87.4070008@lucee.org>
 <56C51150.1070708@anastigmatix.net> <56C54EE0.2080905@lucee.org>
 <56C553C3.40408@lucee.org> <56C556BD.1010907@anastigmatix.net>
 <56C55824.1060502@lucee.org> <56C564F4.1050909@anastigmatix.net>
 <56C5E1B3.8090204@lucee.org> <56C5E795.4080405@anastigmatix.net>
From: Chapman Flack <chap@anastigmatix.net>
Message-ID: <56C5EA23.2010306@anastigmatix.net>
Date: Thu, 18 Feb 2016 10:58:27 -0500
MIME-Version: 1.0
In-Reply-To: <56C5E795.4080405@anastigmatix.net>
Subject: [Pljava-dev] Some tips to keep mvn -X output to manageable size
Content-Type: text/plain; charset="us-ascii"

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@lists.pgfoundry.org
http://lists.pgfoundry.org/mailman/listinfo/pljava-dev