i've the same problem after clearing the relevant parts of my local maven repo. strange that the version is missing from the maven central metadata, as the artifacts itself are there: https://repo.maven.apache.org/maven2/javax/jcr/jcr/2.0/
on the public adobe repo the metadata is complete, that's maybe the reason it works for some https://repo.adobe.com/nexus/content/groups/public/javax/jcr/jcr/maven-metadata.xml stefan >-----Original Message----- >From: Robert Munteanu <[email protected]> >Sent: Tuesday, January 12, 2021 10:09 AM >To: [email protected] >Subject: Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven >Plugin 1.1.6 > >Hi, > >On Mon, 2021-01-11 at 20:44 +0100, Konrad Windszus wrote: >> The command for running automated checks against this release >> candidate is: >> $ sh check-release.sh filevault 3.4.8 >> 669663e26d9fe7364a2735bcf237b4719ba1879d > >I am unable to run the tests, or indeed build filevault master. > >With mvn clean verify in the project root I get > >[INFO] --- bnd-indexer-maven-plugin:5.2.0:index (index) @ >org.apache.jackrabbit.vault.target-osgi-environment --- >[ERROR] Failed to determine the artifact URI for artifact >javax.jcr:jcr:jar:2.0 >java.io.FileNotFoundException: Unable to index artifact >javax.jcr:jcr:jar:2.0. The repository local is not known to this resolver > >I am building with > >Apache Maven 3.6.3 (SUSE 3.6.3-2.5) >Maven home: /usr/share/maven >Java version: 11.0.9.1, vendor: Oracle Corporation, runtime: >/usr/lib64/jvm/java-11-openjdk-11 >Default locale: en_US, platform encoding: UTF-8 >OS name: "linux", version: "5.10.4-1-default", arch: "amd64", family: >"unix" > >Not sure if related, but the Maven central metadata does not seem to >include the 2.0 version in its listing > >https://repo.maven.apache.org/maven2/javax/jcr/jcr/maven-metadata.xml > ><metadata> > <groupId>javax.jcr</groupId> > <artifactId>jcr</artifactId> > <version>1.0</version> > <versioning> > <versions> > <version>1.0</version> > <version>1.0.1</version> > </versions> > </versioning> ></metadata> > >Does anyone else have this problem? > >Thanks, >Robert
