Because I know Andrea would be curious; it was *not faster* on repeated builds:
04:43: mvn clean install --builder smart -T8 04:58: mvn clean install --builder smart -T 2C 04:57: mvn clean install -T 2C 04:40: mvn clean install -T8 So not much fun, unless it is more stable. -- Jody Garnett On Thu, 9 Apr 2020 at 17:05, Jody Garnett <jody.garn...@gmail.com> wrote: > If you are interested: > > cd $M2_HOME/lib/ext > curl -O > https://repo1.maven.org/maven2/io/takari/maven/takari-smart-builder/0.4.0/takari-smart-builder-0.4.0.jar > > mvn clean install --builder smart -T 2C > > In addition to being thread safe it is faster > -- > Jody Garnett > > > On Thu, 9 Apr 2020 at 16:47, Jody Garnett <jody.garn...@gmail.com> wrote: > >> I have a PR fox address plugin repository inconsistency: >> https://github.com/geotools/geotools/pull/2871 >> >> Interestingly the Mac OS CI check on that build was able to reproduce >> your issues: >> >> *[ERROR] Failed to execute goal >> org.apache.maven.plugins:maven-install-plugin:2.4:install (default-install) >> on project xmlcodegen: Failed to install metadata >> org.geotools.maven/maven-metadata.xml: Error updating group repository >> metadata: in epilog non whitespace content is not allowed but got s >> (position: END_TAG seen ...</metadata>\ns... @11:2) -> [Help 1]* >> >> >> Searching shows this issue historically was from two threads deploying >> the same module (this seems unlikely). Apparently the local maven >> repository is not thread safe and there are workarounds using >> https://github.com/takari/takari-local-repository ... >> >> This is not a very satisfying answer. >> -- >> Jody Garnett >> >> >> On Thu, 9 Apr 2020 at 15:52, Jody Garnett <jody.garn...@gmail.com> wrote: >> >>> I was able to suppress this warning in JarCollector using: >>> https://github.com/geotools/geotools/pull/2870 >>> It does not seem significant to your build failure. >>> >>> I was able to do a full -Dall build locally and did. not run into your >>> error. Do you have any more details? I do not want to mess with >>> pluginRepository definitions if it is not needed. >>> -- >>> Jody Garnett >>> >>> >>> On Thu, 9 Apr 2020 at 08:05, Ian Turton <ijtur...@gmail.com> wrote: >>> >>>> So I'm seeing the following error building the new 23.0 release >>>> artifacts >>>> >>>> [ERROR] Failed to execute goal >>>> org.apache.maven.plugins:maven-install-plugin:2.4:install (default-install) >>>> on project jar-collector: Failed to install metadata >>>> org.geotools.maven/maven-metadata.xml: Error updating group repository >>>> metadata: in epilog non whitespace content is not allowed but got s >>>> (position: END_TAG seen ...</metadata>\ns... @11:2) -> [Help 1] >>>> [ERROR] >>>> >>>> I can't however work out what the actual error is, Jody is this related >>>> to moving the repos somehow? >>>> >>>> Or is it related to the warnings (that I don't recall seeing before): >>>> >>>> [INFO] --- maven-plugin-plugin:3.6.0:descriptor (default-descriptor) @ >>>> jar-collector --- >>>> [INFO] Using 'UTF-8' encoding to read mojo source files. >>>> [WARNING] org.geotools.maven.JarCollector#jarName: >>>> [WARNING] The syntax >>>> [WARNING] @parameter expression="${property}" >>>> [WARNING] is deprecated, please use >>>> [WARNING] @parameter property="property" >>>> [WARNING] instead. >>>> [WARNING] org.geotools.maven.JarCollector#outputDirectory: >>>> [WARNING] The syntax >>>> [WARNING] @parameter expression="${property}" >>>> [WARNING] is deprecated, please use >>>> [WARNING] @parameter property="property" >>>> [WARNING] instead. >>>> [WARNING] org.geotools.maven.JarCollector#project: >>>> [WARNING] The syntax >>>> [WARNING] @parameter expression="${property}" >>>> [WARNING] is deprecated, please use >>>> [WARNING] @parameter property="property" >>>> [WARNING] instead. >>>> [INFO] java-javadoc mojo extractor found 1 mojo descriptor. >>>> [INFO] java-annotations mojo extractor found 0 mojo descriptor. >>>> >>>> Ian >>>> >>>> On Thu, 9 Apr 2020 at 15:01, Jody Garnett <jody.garn...@gmail.com> >>>> wrote: >>>> >>>>> I see, Ian please be aware that the deployment repositories have >>>>> changed :) >>>>> >>>>> I did not get a chance to address the package issues for GeoServer >>>>> mentioned on email. >>>>> — >>>>> Jody >>>>> >>>>> On Thu, Apr 9, 2020 at 2:58 AM Ian Turton <ijtur...@gmail.com> wrote: >>>>> >>>>>> I'm kicking off the release chain using >>>>>> >>>>>> GeoServer 6549c85312853ecb22b51d258423c983f22617cd >>>>>> GeoWebCache - a31bcff2bd98e40c2dc5d176efe3b64b38d11429 >>>>>> GeoTools - 9dca3294fe372826163e25e46a3a1ae7a26a8684 >>>>>> >>>>>> I'll keep people informed on the lists as I go, I expect to have >>>>>> artifacts ready to test this afternoon for GeoTools. >>>>>> >>>>>> Ian >>>>>> -- >>>>>> Ian Turton >>>>>> _______________________________________________ >>>>>> Geowebcache-devel mailing list >>>>>> geowebcache-de...@lists.sourceforge.net >>>>>> https://lists.sourceforge.net/lists/listinfo/geowebcache-devel >>>>>> >>>>> -- >>>>> -- >>>>> Jody Garnett >>>>> >>>> >>>> >>>> -- >>>> Ian Turton >>>> >>>
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
