Re: [PATCH] Using --batch-mode in check-release.sh ?

On Tue, 2021-01-12 at 09:49 +, Marcel Reutegger wrote: > Hi, > > On 12.01.21, 10:46, "Robert Munteanu" wrote: > > Reading the output of check-release.sh is hard since recent > > versions of > > Maven will use escape sequences to generate colored output. I > > proposed > > that we use

Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven Plugin 1.1.6

On Tue, 2021-01-12 at 11:58 +0100, Konrad Windszus wrote: > 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 Yes, that

Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven Plugin 1.1.6

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 wrote: > > On Tue, 2021-01-12 at

Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven Plugin 1.1.6

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 <

Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven Plugin 1.1.6

On Tue, 2021-01-12 at 09:45 +, Stefan Seifert wrote: > 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 Good point, the build passes for me with repo.adobe.com

[jira] [Created] (JCRVLT-491) Broken Maven metadata on Maven Central should not prevent Maven build

Konrad Windszus created JCRVLT-491: -- Summary: Broken Maven metadata on Maven Central should not prevent Maven build Key: JCRVLT-491 URL: https://issues.apache.org/jira/browse/JCRVLT-491 Project:

Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven Plugin 1.1.6

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 .

Re: [PATCH] Using --batch-mode in check-release.sh ?

Hi, On 12.01.21, 10:46, "Robert Munteanu" wrote: > Reading the output of check-release.sh is hard since recent versions of > Maven will use escape sequences to generate colored output. I proposed > that we use --batch-mode to prevent that in the check-release.sh > script. +1 Regards Marcel

[PATCH] Using --batch-mode in check-release.sh ?

Hi, (This is a one-liner with potential wide impact, so sending to dev list). Reading the output of check-release.sh is hard since recent versions of Maven will use escape sequences to generate colored output. I proposed that we use --batch-mode to prevent that in the check-release.sh script.

RE: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven Plugin 1.1.6

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,

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