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> <56C5EA23.2010306@anastigmatix.net> <56C5ED52.2080004@lucee.org> From: Chapman Flack Message-ID: <56C5EFE5.7010200@anastigmatix.net> Date: Thu, 18 Feb 2016 11:23:01 -0500 MIME-Version: 1.0 In-Reply-To: <56C5ED52.2080004@lucee.org> Subject: Re: [Pljava-dev] Some tips to keep mvn -X output to manageable size Content-Type: text/plain; charset="us-ascii" On 02/18/2016 11:12 AM, Igal @ Lucee.org wrote: > On 2/18/2016 7:58 AM, Chapman Flack wrote: >> 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. > Sounds good. >> 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. > Is the problem now in pljava-so subproject? I'm not sure how do you see > that, so I wouldn't be able to tell by myself. No, I was just giving general tips (I changed the Subject: line). Your last build got past pljava-so and finished everything in fact. You could try loading it. (It still might or might not work.) I am still interested in those compiler warnings about int/jint and long/jlong widths and undeclared handlers. Those *are* in the pljava-so subproject, but I won't have anything new for you to try there until I have more of a chance to look. -Chap _______________________________________________ Pljava-dev mailing list Pljava-dev@lists.pgfoundry.org http://lists.pgfoundry.org/mailman/listinfo/pljava-dev