Maybe it works with mvn verify -Dbnd.indexer.localURLs=ALLOWED
(https://github.com/bndtools/bnd/tree/master/maven/bnd-indexer-maven-plugin#configuration-properties) Have not tried it out myself, though.... Konrad > On 12. Jan 2021, at 11:40, Robert Munteanu <[email protected]> wrote: > > On Tue, 2021-01-12 at 10:53 +0100, Konrad Windszus wrote: >> Hi Robert, >> That is a shame, we had that with other artifacts in the past. I will >> try to get a fix for that in Maven Central. >> The file listing the wrong versions is >> https://repo1.maven.org/maven2/javax/jcr/jcr/maven-metadata.xml < >> https://repo1.maven.org/maven2/javax/jcr/jcr/maven-metadata.xml>. >> >> I am wondering why TravisCI is fine (but that is using the Google >> Mirrror at >> https://maven-central.storage-download.googleapis.com/maven2/ < >> https://maven-central.storage-download.googleapis.com/maven2/>, but >> even that one has a wrong version in >> https://maven-central.storage-download.googleapis.com/maven2/javax/jcr/jcr/maven-metadata.xml >> < >> https://maven-central.storage-download.googleapis.com/maven2/javax/jcr/jcr/maven-metadata.xml >>> ). >> >> I opened https://issues.sonatype.org/browse/MVNCENTRAL-6449 < >> https://issues.sonatype.org/browse/MVNCENTRAL-6449> for this. >> >> I fear that there is a bug in Nexus which leads to destroying the >> metadata. If there is not a fix for this soon, there must be an easy >> way to disable this functionality (via a Maven profile) and I need to >> investigate another way to check if the bundles resolve. > > Right, as it stands the source release cannot be built. I assume there > is no shortcut in the indexer plugin to point it directly to an > artifact, which would've fixed the problem without external > intervention. > >> Thanks, >> Konrad >> >> >>> On 12. Jan 2021, at 10:09, Robert Munteanu <[email protected]> >>> wrote: >>> >>> 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 >>> >> > >
