Got it. Thank you. That makes good sense. Onwards! On Mon, Jun 1, 2020 at 3:51 PM Tilman Hausherr <[email protected]> wrote:
> Yes, we use this to test compiling on jenkins with a jdk6 system while > running the build on a jdk8 system, at the request of Simon Steiner. > > It worked fine for a long time, although currently it doesn't. (Because > it works only with some maven versions) > > Tilman > > Am 01.06.2020 um 21:01 schrieb Tim Allison: > > Do we need this line? Are we getting benefit from specifying a different > > jdk via JAVA_HOME that we wouldn't get from letting maven use the active > > "alternative"? > > > > Anyways, all good. Sorry for the noise. > > > > On Mon, Jun 1, 2020 at 2:43 PM Tim Allison <[email protected]> wrote: > > > >> User error...I recently reimaged my laptop and forgot to set JAVA_HOME, > >> which needs to be picked up here: > >> > >> <jdk.path>${env.JAVA_HOME}</jdk.path> > >> > >> for use here: > >> > >> <executable>${jdk.path}/bin/javac</executable> > >> > >> > >> On Mon, Jun 1, 2020 at 2:37 PM Tim Allison <[email protected]> wrote: > >> > >>> I get the same behavior (compiler failing at fontbox) with Java 11 on > >>> ubuntu. I'm sure this is user error, but it is weird. > >>> > >>> Apache Maven 3.6.3 > >>> Maven home: /usr/share/maven > >>> Java version: 11.0.7, vendor: AdoptOpenJDK, runtime: > >>> /usr/lib/jvm/adoptopenjdk-11-hotspot-amd64 > >>> Default locale: en_US, platform encoding: UTF-8 > >>> OS name: "linux", version: "5.4.0-33-generic", arch: "amd64", family: > >>> "unix" > >>> > >>> On Mon, Jun 1, 2020 at 2:24 PM Tim Allison <[email protected]> > wrote: > >>> > >>>> Thank you, Tilman. > >>>> > >>>> Apache Maven 3.6.3 > >>>> Maven home: /usr/share/maven > >>>> Java version: 1.8.0_252, vendor: AdoptOpenJDK, runtime: > >>>> /usr/lib/jvm/adoptopenjdk-8-hotspot-amd64/jre > >>>> Default locale: en_US, platform encoding: UTF-8 > >>>> OS name: "linux", version: "5.4.0-33-generic", arch: "amd64", family: > >>>> "unix" > >>>> > >>>> I specified 3.8.0 and 3.8.1 and still got the following...with no > useful > >>>> information...or...where do I look for useful information? > >>>> > >>>> [INFO] > >>>> > ------------------------------------------------------------------------ > >>>> [INFO] Reactor Summary for PDFBox reactor 2.0.20-SNAPSHOT: > >>>> [INFO] > >>>> [INFO] PDFBox parent ...................................... SUCCESS [ > >>>> 2.719 s] > >>>> [INFO] Apache FontBox ..................................... FAILURE [ > >>>> 1.304 s] > >>>> [INFO] Apache XmpBox ...................................... SKIPPED > >>>> [INFO] Apache PDFBox ...................................... SKIPPED > >>>> [INFO] Apache Preflight ................................... SKIPPED > >>>> [INFO] Apache Preflight application ....................... SKIPPED > >>>> [INFO] Apache PDFBox Debugger ............................. SKIPPED > >>>> [INFO] Apache PDFBox tools ................................ SKIPPED > >>>> [INFO] Apache PDFBox application .......................... SKIPPED > >>>> [INFO] Apache PDFBox Debugger application ................. SKIPPED > >>>> [INFO] Apache PDFBox examples ............................. SKIPPED > >>>> [INFO] PDFBox reactor ..................................... SKIPPED > >>>> [INFO] > >>>> > ------------------------------------------------------------------------ > >>>> [INFO] BUILD FAILURE > >>>> [INFO] > >>>> > ------------------------------------------------------------------------ > >>>> [INFO] Total time: 5.190 s > >>>> [INFO] Finished at: 2020-06-01T14:21:11-04:00 > >>>> [INFO] > >>>> > ------------------------------------------------------------------------ > >>>> [ERROR] Failed to execute goal > >>>> org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile > >>>> (default-compile) on project fontbox: Compilation failure -> [Help 1] > >>>> [ERROR] > >>>> [ERROR] To see the full stack trace of the errors, re-run Maven with > the > >>>> -e switch. > >>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging. > >>>> [ERROR] > >>>> [ERROR] For more information about the errors and possible solutions, > >>>> please read the following articles: > >>>> [ERROR] [Help 1] > >>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > >>>> [ERROR] > >>>> [ERROR] After correcting the problems, you can resume the build with > the > >>>> command > >>>> [ERROR] mvn <args> -rf :fontbox > >>>> > >>>> On Mon, Jun 1, 2020 at 1:07 PM Tilman Hausherr <[email protected] > > > >>>> wrote: > >>>> > >>>>> Am 01.06.2020 um 18:51 schrieb Tim Allison: > >>>>>> I'm having problems building...likely user error. > >>>>>> > >>>>>> On ubuntu with Java 8, maven 3.6.3, `mvn clean install` on the > >>>>> commandline: > >>>>>> fontbox fails to build "maven-compiler-plugin" Compilation failure > >>>>> with no > >>>>>> warnings or info on what failed even with -e -X. > >>>>> Which java 8? I remember this came with early jdk8 versions, or when > >>>>> java wasn't there. > >>>>> > >>>>> Another possibility would be to update the maven-compiler-plugin to > >>>>> 3.8.0. > >>>>> > >>>>> > >>>>>> > >>>>>> On a mac with Java 8, I'm getting test failures > >>>>> testFlattenPDFBOX563() and > >>>>>> testFlattenPDFBOX2469Filled(). If I disable those tests, I am able > to > >>>>>> build it. > >>>>> > >>>>> I've disabled them now, likely small rendering differences. > >>>>> > >>>>> Tilman > >>>>> > >>>>>> All is good for now, but weird... > >>>>>> > >>>>>> On Sat, May 30, 2020 at 7:37 AM Andreas Lehmkuehler < > [email protected] > >>>>>> > >>>>>> wrote: > >>>>>> > >>>>>>> @Tim > >>>>>>> Cool, yes, please! I'm going to postpone the release for a couple > of > >>>>> days > >>>>>>> depending on the results. > >>>>>>> > >>>>>>> Thanks in advance! > >>>>>>> > >>>>>>> Andreas > >>>>>>> > >>>>>>> Am 30.05.20 um 12:59 schrieb Tim Allison: > >>>>>>>> I can run the tests on Monday w results by the end of the day EDT > if > >>>>>>>> desired. > >>>>>>>> > >>>>>>>> On Sat, May 30, 2020 at 5:53 AM Andreas Lehmkuehler < > >>>>> [email protected]> > >>>>>>>> wrote: > >>>>>>>> > >>>>>>>>> Hi, > >>>>>>>>> > >>>>>>>>> I just realized that we didn't run Tims tests yet. I've had a > >>>>> look at > >>>>>>> the > >>>>>>>>> tickets and most of them are not related to text extraction. The > >>>>>>> remaining > >>>>>>>>> are > >>>>>>>>> mostly dealing with corner cases so that we should be save. > >>>>>>>>> > >>>>>>>>> WDYT, are we save enough or do we need to run the tests before > >>>>> cutting > >>>>>>> the > >>>>>>>>> release? > >>>>>>>>> > >>>>>>>>> Andreas > >>>>>>>>> > >>>>>>>>> Am 26.05.20 um 08:02 schrieb Andreas Lehmkuehler: > >>>>>>>>>> I'm planning to cut the release on next Monday 1st of June. > >>>>>>>>>> > >>>>>>>>>> Andreas > >>>>>>>>>> > >>>>>>>>>> Am 20.05.20 um 08:15 schrieb Andreas Lehmkuehler: > >>>>>>>>>>> Hi, > >>>>>>>>>>> > >>>>>>>>>>> how about cutting a 2.0.20 release in 2 or 3 weeks from now? > >>>>>>>>>>> > >>>>>>>>>>> Andreas > >>>>>>>>>>> > >>>>>>>>>>> > >>>>> --------------------------------------------------------------------- > >>>>>>>>>>> To unsubscribe, e-mail: [email protected] > >>>>>>>>>>> For additional commands, e-mail: [email protected] > >>>>>>>>>>> > >>>>>>>>>> > >>>>> --------------------------------------------------------------------- > >>>>>>>>>> To unsubscribe, e-mail: [email protected] > >>>>>>>>>> For additional commands, e-mail: [email protected] > >>>>>>>>>> > >>>>>>>>> > >>>>> --------------------------------------------------------------------- > >>>>>>>>> To unsubscribe, e-mail: [email protected] > >>>>>>>>> For additional commands, e-mail: [email protected] > >>>>>>>>> > >>>>>>>>> > >>>>>>> > --------------------------------------------------------------------- > >>>>>>> To unsubscribe, e-mail: [email protected] > >>>>>>> For additional commands, e-mail: [email protected] > >>>>>>> > >>>>>>> > >>>>> > >>>>> --------------------------------------------------------------------- > >>>>> To unsubscribe, e-mail: [email protected] > >>>>> For additional commands, e-mail: [email protected] > >>>>> > >>>>> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
