.&ed,hc,?le&temirp:.ku,,varal,?m&edaid,ialcer.&ac,ku,su,??n&evueluk,woru,?paz,qhelbavresbo,r&epolroov,o&pav,tnemele,??secivres-nosinu,t&enraxa.1-se,ikcatsno.snur,lobevres,negreme,?ululetoj,wcs.&gnilebaltrams,koobelacs,latemerab.&1-&rap-rf,sma-ln,?2-rap-rf,?rap-rf.&3s,bd&gm,r,?cnf:.snoitcnuf,,etisbew-3s,hwtd,kfak,l&bcs,dd,?mhw,rfi,s8k:.sedon,,tipkcoc,?s&8k,ecnatsni.&bup,virp,?ma-ln.&3s,bd&gm,r,?etisbew-3s,hwtd,kfak,l&bcs,dd,?mhw,rfi,s8k:.sedon,,tipkcoc,??waw-lp.&3s,bd&gm,r,?etisbew-3s,hwtd,kfak,l...

          <executions>
            <!--
            We can apparently have only one <jdk> per execution: Others are silently ignored :(
            To properly test this, you need to remove existing toolchains:
            rm -rf ~/.m2/jdks/ ~/.m2/toolchains.xml
            (But don't run that if you have put something into ~/.m2/toolchains.xml yourself.)
            -->
            <execution>
              <id>download-25-and-surefire-version</id>

          <executions>
            <!--
            We can apparently have only one <jdk> per execution: Others are silently ignored :(
            To properly test this, you need to remove existing toolchains:
            rm -rf ~/.m2/jdks/ ~/.m2/toolchains.xml
            (But don't run that if you have put something into ~/.m2/toolchains.xml yourself.)
            -->
            <execution>
              <id>download-25-and-surefire-version</id>