Hi Martin, this time https://repository.apache.org/content/groups/snapshots/org/apache/sis/core/sis-metadata/0.8-jdk8-SNAPSHOT/ was hit:
sis-metadata-0.8-jdk8-20170718.214026-447.jar versus ...214027-447.jar my workaround was to manually download the files into my local .m2/ repository and rename them. It's a bit annoying but it works by now. Seems to be a problem with the maven build system. How are those timestamps and the sequence number generated? I have the current snapshot checked out. Is it some maven plugin? Can I reproduce and analyze such a deployment locally? Dieter. -----Original Message----- From: Martin Desruisseaux [mailto:[email protected]] Sent: Mittwoch, 19. Juli 2017 00:27 To: [email protected] Subject: Re: sis-referencing 0.8-jdk8-SNAPSHOT Indeed, the maven-metadata.xml content mismatched the actual filenames again. I launched another build, and the maven-metadata.xml content (0.8-jdk8-20170718.214118-447) now seems to matches the actual filenames. Would you have a chance to test? However given that the matches or mismatches seem to happen randomly, I worry that even if it work this time, it may break after any future build. If it happen again, I will ask on the Maven mailing list if this is a known issue. Martin Le 18/07/2017 à 15:34, Dieter Stüken a écrit : > Hmm... > > I'm just trying to use 0.8-jdk8-SNAPSHOT. Unfortunately I got some error like: > > The POM for > org.apache.sis.core:sis-referencing:jar:0.8-jdk8-20170717.215031-446 > is missing > > I'm not an expert with maven, but if I have a look at: > > https://repository.apache.org/content/groups/snapshots/org/apache/sis/ > core/sis-referencing/0.8-jdk8-SNAPSHOT > > I notice it is named: > > sis-referencing-0.8-jdk8-20170717.215030-446.jar<https://repository.ap > ache.org/content/groups/snapshots/org/apache/sis/core/sis-referencing/ > 0.8-jdk8-SNAPSHOT/sis-referencing-0.8-jdk8-20170717.215030-446.jar> > > while maven-metadata.xml refers to ...215031-446.jar > > Is there a "temporary" problem with the maven deployment? > Will see, if the problem vanishes with the next build tonight. > > Dieter.
