You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by Konrad Windszus <ko...@gmx.de> on 2021/01/11 19:44:28 UTC
Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven Plugin
1.1.6
Hi,
A candidate for the Jackrabbit Filevault 3.4.8 release is available at:
https://dist.apache.org/repos/dist/dev/jackrabbit/filevault/3.4.8/
The release candidate is a zip archive of the sources in:
https://github.com/apache/jackrabbit-filevault/tree/jackrabbit-filevault-3.4.8/
The release notes in JIRA are at https://issues.apache.org/jira/projects/JCRVLT/versions/12348445
The SHA1 checksum of the archive is 669663e26d9fe7364a2735bcf237b4719ba1879d.
The SHA512 checksum of the archive is c2e0024af08ec640ba6a725944392dca4ab36b6106b4418f98a67c4d0c8ba2b601c49627d83d8541b3d5c04824d5fce1479b727510d22d9a4b14c11af6621f90
The command for running automated checks against this release candidate is:
$ sh check-release.sh filevault 3.4.8 669663e26d9fe7364a2735bcf237b4719ba1879d
A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachejackrabbit-1534
=====
Also a candidate for the Jackrabbit FileVault Package Maven Plugin 1.1.6 release is available at:
https://dist.apache.org/repos/dist/dev/jackrabbit/filevault-package-maven-plugin/1.1.6/
The release candidate is a zip archive of the sources in:
https://github.com/apache/jackrabbit-filevault-package-maven-plugin/tree/filevault-package-maven-plugin-1.1.6/
The release notes in JIRA are at https://issues.apache.org/jira/projects/JCRVLT/versions/12348444
The SHA1 checksum of the archive is d5c8785cdf5a9d6e069e8af1cc3542b6acee5677
The SHA512 checksum of the archive is bb11177aaa59b9d69ad06d7b63e965c4bba70e6433577292c4a32d7431198840b9f6e83c6b374c0cf9b5409224a03b413d9e0e68057346a51c01d915b301e3a5
The command for running automated checks against this release candidate is:
$ sh check-release.sh filevault-plugin 1.1.6 d5c8785cdf5a9d6e069e8af1cc3542b6acee5677
*** As FileVault Package Maven Plugin 1.1.6 depends on the FileVault 3.4.8 you need to install FileVault 3.4.8 to your local Maven repository (e.g. via mvn install) before being able to run the checks ***
A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachejackrabbit-1535
=====
Please vote on releasing both packages as Apache Jackrabbit Filevault 3.4.8 and FileVault Package Maven Plugin 1.1.6.
The vote is open for a minimum of 72 hours during business days and passes
if a majority of at least three +1 Jackrabbit PMC votes are cast.
The vote fails if not enough votes are cast after 1 week (5 business days).
[ ] +1 Release these packages as Apache Jackrabbit Filevault 3.4.8 and FileVault Package Maven Plugin 1.1.6
[ ] -1 Do not release these packages because...
Thanks in advance for voting,
Konrad
Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven
Plugin 1.1.6
Posted by Konrad Windszus <ko...@gmx.de>.
Hi Julian
> On 14. Jan 2021, at 16:00, Julian Reschke <ju...@gmx.de> wrote:
>
> Am 11.01.2021 um 20:44 schrieb Konrad Windszus:
>> Hi,
>> ...
>
> Hi Konrad!
>
> The subject line of this mail should be prefixed with "[VOTE]"...
Noted, I unfortunately missed it this time.
>
>> A candidate for the Jackrabbit Filevault 3.4.8 release is available at:
>>
>> https://dist.apache.org/repos/dist/dev/jackrabbit/filevault/3.4.8/
>>
>> The release candidate is a zip archive of the sources in:
>> https://github.com/apache/jackrabbit-filevault/tree/jackrabbit-filevault-3.4.8/
>>
>> The release notes in JIRA are at https://issues.apache.org/jira/projects/JCRVLT/versions/12348445
>>
>> The SHA1 checksum of the archive is 669663e26d9fe7364a2735bcf237b4719ba1879d.
>> The SHA512 checksum of the archive is c2e0024af08ec640ba6a725944392dca4ab36b6106b4418f98a67c4d0c8ba2b601c49627d83d8541b3d5c04824d5fce1479b727510d22d9a4b14c11af6621f90
>>
>> The command for running automated checks against this release candidate is:
>> $ sh check-release.sh filevault 3.4.8 669663e26d9fe7364a2735bcf237b4719ba1879d
>> ...
>
>
> Tried that, and I'm getting:
>
>> [INFO] Downloading from apache.releases.https: https://repository.apache.org/service/local/staging/deploy/maven2/javax/jcr/jcr/maven-metadata.xml <https://repository.apache.org/service/local/staging/deploy/maven2/javax/jcr/jcr/maven-metadata.xml>
>> [WARNING] Could not transfer metadata javax.jcr:jcr/maven-metadata.xml from/to apache.releases.https (https://repository.apache.org/service/local/staging/deploy/maven2 <https://repository.apache.org/service/local/staging/deploy/maven2>): Authentication failed for https://repository.apache.org/service/local/staging/deploy/maven2/javax/jcr/jcr/maven-metadata.xml <https://repository.apache.org/service/local/staging/deploy/maven2/javax/jcr/jcr/maven-metadata.xml> 401 Unauthorized
>> [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
>> at aQute.bnd.maven.indexer.plugin.IndexerMojo$RepositoryURLResolver.resolver (IndexerMojo.java:343)
>> at aQute.bnd.maven.indexer.plugin.IndexerMojo.execute (IndexerMojo.java:177)
>> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
>> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
>> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
>> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
>> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
>> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
>> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
>> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
>> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke (Method.java:498)
>> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
>> at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
>> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
>> at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
>> [INFO] ------------------------------------------------------------------------
>
This was already reported by Robert and is due to incorrect metadata in Maven Central which should be fixed soon: https://issues.sonatype.org/browse/MVNCENTRAL-6449 <https://issues.sonatype.org/browse/MVNCENTRAL-6449>. I will let you know once Sonatype fixed the issue.
Konrad
> Best regards, Julian
> <jackrabbit-filevault-3.4.8.log>
Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven
Plugin 1.1.6
Posted by Julian Reschke <ju...@gmx.de>.
Am 11.01.2021 um 20:44 schrieb Konrad Windszus:
> Hi,
> ...
Hi Konrad!
The subject line of this mail should be prefixed with "[VOTE]"...
> A candidate for the Jackrabbit Filevault 3.4.8 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/filevault/3.4.8/
>
> The release candidate is a zip archive of the sources in:
> https://github.com/apache/jackrabbit-filevault/tree/jackrabbit-filevault-3.4.8/
>
> The release notes in JIRA are at https://issues.apache.org/jira/projects/JCRVLT/versions/12348445
>
> The SHA1 checksum of the archive is 669663e26d9fe7364a2735bcf237b4719ba1879d.
> The SHA512 checksum of the archive is c2e0024af08ec640ba6a725944392dca4ab36b6106b4418f98a67c4d0c8ba2b601c49627d83d8541b3d5c04824d5fce1479b727510d22d9a4b14c11af6621f90
>
> The command for running automated checks against this release candidate is:
> $ sh check-release.sh filevault 3.4.8 669663e26d9fe7364a2735bcf237b4719ba1879d
> ...
Tried that, and I'm getting:
> [INFO] Downloading from apache.releases.https: https://repository.apache.org/service/local/staging/deploy/maven2/javax/jcr/jcr/maven-metadata.xml
> [WARNING] Could not transfer metadata javax.jcr:jcr/maven-metadata.xml from/to apache.releases.https (https://repository.apache.org/service/local/staging/deploy/maven2): Authentication failed for https://repository.apache.org/service/local/staging/deploy/maven2/javax/jcr/jcr/maven-metadata.xml 401 Unauthorized
> [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
> at aQute.bnd.maven.indexer.plugin.IndexerMojo$RepositoryURLResolver.resolver (IndexerMojo.java:343)
> at aQute.bnd.maven.indexer.plugin.IndexerMojo.execute (IndexerMojo.java:177)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
> [INFO] ------------------------------------------------------------------------
Best regards, Julian
Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven
Plugin 1.1.6
Posted by Konrad Windszus <ko...@gmx.de>.
> I can +1 FileVault 3.4.8; the other one doesn't validate for me on
> Cygwin (due to scm problem I currently can't investigate -- same as last
> time).
>
> Best regards, Julian
Once you find some time please raise an issue with further details, then I can look into that and hopefully fix it.
Konrad
Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven
Plugin 1.1.6
Posted by Julian Reschke <ju...@gmx.de>.
Am 20.01.2021 um 13:51 schrieb Konrad Windszus:
> Gentle nudge....
> Still one more vote missing...
> ...
I can +1 FileVault 3.4.8; the other one doesn't validate for me on
Cygwin (due to scm problem I currently can't investigate -- same as last
time).
Best regards, Julian
Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven
Plugin 1.1.6
Posted by Konrad Windszus <ko...@gmx.de>.
Gentle nudge....
Still one more vote missing...
Konrad
> On 18. Jan 2021, at 08:58, Konrad Windszus <ko...@gmx.de> wrote:
>
> I need one more vote.
> Thanks,
> Konrad
>
>
>> On 11. Jan 2021, at 20:44, Konrad Windszus <ko...@gmx.de> wrote:
>>
>> Hi,
>>
>> A candidate for the Jackrabbit Filevault 3.4.8 release is available at:
>>
>> https://dist.apache.org/repos/dist/dev/jackrabbit/filevault/3.4.8/
>>
>> The release candidate is a zip archive of the sources in:
>> https://github.com/apache/jackrabbit-filevault/tree/jackrabbit-filevault-3.4.8/
>>
>> The release notes in JIRA are at https://issues.apache.org/jira/projects/JCRVLT/versions/12348445
>>
>> The SHA1 checksum of the archive is 669663e26d9fe7364a2735bcf237b4719ba1879d.
>> The SHA512 checksum of the archive is c2e0024af08ec640ba6a725944392dca4ab36b6106b4418f98a67c4d0c8ba2b601c49627d83d8541b3d5c04824d5fce1479b727510d22d9a4b14c11af6621f90
>>
>> The command for running automated checks against this release candidate is:
>> $ sh check-release.sh filevault 3.4.8 669663e26d9fe7364a2735bcf237b4719ba1879d
>>
>> A staged Maven repository is available for review at:
>> https://repository.apache.org/content/repositories/orgapachejackrabbit-1534
>>
>> =====
>>
>> Also a candidate for the Jackrabbit FileVault Package Maven Plugin 1.1.6 release is available at:
>> https://dist.apache.org/repos/dist/dev/jackrabbit/filevault-package-maven-plugin/1.1.6/
>>
>> The release candidate is a zip archive of the sources in:
>> https://github.com/apache/jackrabbit-filevault-package-maven-plugin/tree/filevault-package-maven-plugin-1.1.6/
>>
>> The release notes in JIRA are at https://issues.apache.org/jira/projects/JCRVLT/versions/12348444
>>
>> The SHA1 checksum of the archive is d5c8785cdf5a9d6e069e8af1cc3542b6acee5677
>> The SHA512 checksum of the archive is bb11177aaa59b9d69ad06d7b63e965c4bba70e6433577292c4a32d7431198840b9f6e83c6b374c0cf9b5409224a03b413d9e0e68057346a51c01d915b301e3a5
>>
>> The command for running automated checks against this release candidate is:
>> $ sh check-release.sh filevault-plugin 1.1.6 d5c8785cdf5a9d6e069e8af1cc3542b6acee5677
>>
>>
>> *** As FileVault Package Maven Plugin 1.1.6 depends on the FileVault 3.4.8 you need to install FileVault 3.4.8 to your local Maven repository (e.g. via mvn install) before being able to run the checks ***
>>
>> A staged Maven repository is available for review at:
>> https://repository.apache.org/content/repositories/orgapachejackrabbit-1535
>>
>> =====
>>
>> Please vote on releasing both packages as Apache Jackrabbit Filevault 3.4.8 and FileVault Package Maven Plugin 1.1.6.
>> The vote is open for a minimum of 72 hours during business days and passes
>> if a majority of at least three +1 Jackrabbit PMC votes are cast.
>> The vote fails if not enough votes are cast after 1 week (5 business days).
>>
>> [ ] +1 Release these packages as Apache Jackrabbit Filevault 3.4.8 and FileVault Package Maven Plugin 1.1.6
>> [ ] -1 Do not release these packages because...
>>
>> Thanks in advance for voting,
>> Konrad
>
Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven
Plugin 1.1.6
Posted by Konrad Windszus <ko...@gmx.de>.
I need one more vote.
Thanks,
Konrad
> On 11. Jan 2021, at 20:44, Konrad Windszus <ko...@gmx.de> wrote:
>
> Hi,
>
> A candidate for the Jackrabbit Filevault 3.4.8 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/filevault/3.4.8/
>
> The release candidate is a zip archive of the sources in:
> https://github.com/apache/jackrabbit-filevault/tree/jackrabbit-filevault-3.4.8/
>
> The release notes in JIRA are at https://issues.apache.org/jira/projects/JCRVLT/versions/12348445
>
> The SHA1 checksum of the archive is 669663e26d9fe7364a2735bcf237b4719ba1879d.
> The SHA512 checksum of the archive is c2e0024af08ec640ba6a725944392dca4ab36b6106b4418f98a67c4d0c8ba2b601c49627d83d8541b3d5c04824d5fce1479b727510d22d9a4b14c11af6621f90
>
> The command for running automated checks against this release candidate is:
> $ sh check-release.sh filevault 3.4.8 669663e26d9fe7364a2735bcf237b4719ba1879d
>
> A staged Maven repository is available for review at:
> https://repository.apache.org/content/repositories/orgapachejackrabbit-1534
>
> =====
>
> Also a candidate for the Jackrabbit FileVault Package Maven Plugin 1.1.6 release is available at:
> https://dist.apache.org/repos/dist/dev/jackrabbit/filevault-package-maven-plugin/1.1.6/
>
> The release candidate is a zip archive of the sources in:
> https://github.com/apache/jackrabbit-filevault-package-maven-plugin/tree/filevault-package-maven-plugin-1.1.6/
>
> The release notes in JIRA are at https://issues.apache.org/jira/projects/JCRVLT/versions/12348444
>
> The SHA1 checksum of the archive is d5c8785cdf5a9d6e069e8af1cc3542b6acee5677
> The SHA512 checksum of the archive is bb11177aaa59b9d69ad06d7b63e965c4bba70e6433577292c4a32d7431198840b9f6e83c6b374c0cf9b5409224a03b413d9e0e68057346a51c01d915b301e3a5
>
> The command for running automated checks against this release candidate is:
> $ sh check-release.sh filevault-plugin 1.1.6 d5c8785cdf5a9d6e069e8af1cc3542b6acee5677
>
>
> *** As FileVault Package Maven Plugin 1.1.6 depends on the FileVault 3.4.8 you need to install FileVault 3.4.8 to your local Maven repository (e.g. via mvn install) before being able to run the checks ***
>
> A staged Maven repository is available for review at:
> https://repository.apache.org/content/repositories/orgapachejackrabbit-1535
>
> =====
>
> Please vote on releasing both packages as Apache Jackrabbit Filevault 3.4.8 and FileVault Package Maven Plugin 1.1.6.
> The vote is open for a minimum of 72 hours during business days and passes
> if a majority of at least three +1 Jackrabbit PMC votes are cast.
> The vote fails if not enough votes are cast after 1 week (5 business days).
>
> [ ] +1 Release these packages as Apache Jackrabbit Filevault 3.4.8 and FileVault Package Maven Plugin 1.1.6
> [ ] -1 Do not release these packages because...
>
> Thanks in advance for voting,
> Konrad
Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven
Plugin 1.1.6
Posted by Julian Reschke <ju...@gmx.de>.
Am 15.01.2021 um 08:33 schrieb Konrad Windszus:
> Hi Julian,
>>
>> check-release for FileVault Package Maven Plugin 1.1.6 fails, as it
>> assumes that FV 3.4.8 is already released. (same problem as for the last
>> release)
>>
> I explicitly mentioned that in my release vote email:
>
>
>> *** As FileVault Package Maven Plugin 1.1.6 depends on the FileVault 3.4.8 you need to install FileVault 3.4.8 to your local Maven repository (e.g. via mvn install) before being able to run the checks ***
>
> Did it work after installing it to the local repo?
I would prefer not to install something locally which might not be
released with that version. IMHO it would be much better if you just did
two independant releases.
(and no, I didn't try with the local install yet)
Best regards, Julian
Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven
Plugin 1.1.6
Posted by Konrad Windszus <ko...@gmx.de>.
Hi Julian,
>
> check-release for FileVault Package Maven Plugin 1.1.6 fails, as it
> assumes that FV 3.4.8 is already released. (same problem as for the last
> release)
>
I explicitly mentioned that in my release vote email:
> *** As FileVault Package Maven Plugin 1.1.6 depends on the FileVault 3.4.8 you need to install FileVault 3.4.8 to your local Maven repository (e.g. via mvn install) before being able to run the checks ***
Did it work after installing it to the local repo?
Thanks,
Konrad
Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven
Plugin 1.1.6
Posted by Julian Reschke <ju...@gmx.de>.
Am 15.01.2021 um 07:45 schrieb Konrad Windszus:
> Sonatype fixed the issue in Maven Central
> (https://issues.sonatype.org/browse/MVNCENTRAL-6449
> <https://issues.sonatype.org/browse/MVNCENTRAL-6449>) so now you should
> be able to build locally without any mirror.
> Please try again and sorry for the issue.
>
> Cheers,
> Konrad
> ...
Thanks.
With that, check-release for Jackrabbit FileVault 3.4.8 passes (so +1 to
release that).
check-release for FileVault Package Maven Plugin 1.1.6 fails, as it
assumes that FV 3.4.8 is already released. (same problem as for the last
release)
Best regards, Julian
Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven
Plugin 1.1.6
Posted by Konrad Windszus <ko...@gmx.de>.
Sonatype fixed the issue in Maven Central (https://issues.sonatype.org/browse/MVNCENTRAL-6449 <https://issues.sonatype.org/browse/MVNCENTRAL-6449>) so now you should be able to build locally without any mirror.
Please try again and sorry for the issue.
Cheers,
Konrad
> On 12. Jan 2021, at 10:53, Konrad Windszus <ko...@gmx.de> 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.
> Thanks,
> Konrad
>
>
>> On 12. Jan 2021, at 10:09, Robert Munteanu <rombert@apache.org <ma...@apache.org>> 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 <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
>>
>
Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven
Plugin 1.1.6
Posted by Robert Munteanu <ro...@apache.org>.
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 also works. However, it assumes that the jars are installed
locally and that might not be the chase. The page your referenced also
mentions mvn urls, but looking at the code I am not sure it would do
what we need.
Thanks,
Robert
> Konrad
>
> > On 12. Jan 2021, at 11:40, Robert Munteanu <ro...@apache.org>
> > 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 <ro...@apache.org>
> > > > 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
> > > >
> > >
> >
> >
>
Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven
Plugin 1.1.6
Posted by Konrad Windszus <ko...@gmx.de>.
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 <ro...@apache.org> 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 <ro...@apache.org>
>>> 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
>>>
>>
>
>
Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven
Plugin 1.1.6
Posted by Robert Munteanu <ro...@apache.org>.
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 <ro...@apache.org>
> > 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
> >
>
Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven
Plugin 1.1.6
Posted by Konrad Windszus <ko...@gmx.de>.
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.
Thanks,
Konrad
> On 12. Jan 2021, at 10:09, Robert Munteanu <ro...@apache.org> 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
>
Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven
Plugin 1.1.6
Posted by Robert Munteanu <ro...@apache.org>.
On Thu, 2021-01-14 at 16:07 +0100, Julian Reschke wrote:
> Yes, but that shouldn't be needed.
It is not needed anymore, the build now succeeds out of the box.
So here's my +1, with
[INFO] ------------------------------------------------------------------------
[INFO] Apache Maven 3.6.3 (SUSE 3.6.3-2.5)
[INFO] OS name: "linux", version: "5.10.4-1-default", arch: "amd64", family: "unix"
[INFO] Java version: 11.0.9.1, vendor: Oracle Corporation, runtime: /usr/lib64/jvm/java-11-openjdk-11
[INFO] MAVEN_OPTS:
[INFO] ------------------------------------------------------------------------
[INFO] ALL CHECKS OK
[INFO] ------------------------------------------------------------------------
Thanks,
Robert
Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven
Plugin 1.1.6
Posted by Julian Reschke <ju...@gmx.de>.
Am 12.01.2021 um 10:59 schrieb Robert Munteanu:
> On Tue, 2021-01-12 at 09:45 +0000, 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 configured.
Yes, but that shouldn't be needed.
Best regards, Julian
Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven
Plugin 1.1.6
Posted by Robert Munteanu <ro...@apache.org>.
On Tue, 2021-01-12 at 09:45 +0000, 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 configured.
Thanks,
Robert
RE: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven
Plugin 1.1.6
Posted by Stefan Seifert <St...@diva-e.com>.
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 <ro...@apache.org>
>Sent: Tuesday, January 12, 2021 10:09 AM
>To: dev@jackrabbit.apache.org
>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
Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven
Plugin 1.1.6
Posted by Robert Munteanu <ro...@apache.org>.
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
Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven
Plugin 1.1.6
Posted by Marcel Reutegger <mr...@adobe.com>.
On 11.01.21, 20:44, "Konrad Windszus" <ko...@gmx.de> wrote:
> Please vote on releasing both packages as Apache Jackrabbit Filevault
> 3.4.8 and FileVault Package Maven Plugin 1.1.6. The vote is open for a
> minimum of 72 hours during business days and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast. The vote fails if not
> enough votes are cast after 1 week (5 business days).
All checks OK.
+1 Release these packages as Apache Jackrabbit Filevault 3.4.8 and FileVault
Package Maven Plugin 1.1.6
As mentioned by Julian earlier, I would also prefer if the two releases
were independent.
Regards
Marcel
Re: Release Jackrabbit FileVault 3.4.8 and FileVault Package Maven
Plugin 1.1.6
Posted by Konrad Windszus <ko...@gmx.de>.
Here is my +1
Konrad
> On 11. Jan 2021, at 20:44, Konrad Windszus <ko...@gmx.de> wrote:
>
> Hi,
>
> A candidate for the Jackrabbit Filevault 3.4.8 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/filevault/3.4.8/
>
> The release candidate is a zip archive of the sources in:
> https://github.com/apache/jackrabbit-filevault/tree/jackrabbit-filevault-3.4.8/
>
> The release notes in JIRA are at https://issues.apache.org/jira/projects/JCRVLT/versions/12348445
>
> The SHA1 checksum of the archive is 669663e26d9fe7364a2735bcf237b4719ba1879d.
> The SHA512 checksum of the archive is c2e0024af08ec640ba6a725944392dca4ab36b6106b4418f98a67c4d0c8ba2b601c49627d83d8541b3d5c04824d5fce1479b727510d22d9a4b14c11af6621f90
>
> The command for running automated checks against this release candidate is:
> $ sh check-release.sh filevault 3.4.8 669663e26d9fe7364a2735bcf237b4719ba1879d
>
> A staged Maven repository is available for review at:
> https://repository.apache.org/content/repositories/orgapachejackrabbit-1534
>
> =====
>
> Also a candidate for the Jackrabbit FileVault Package Maven Plugin 1.1.6 release is available at:
> https://dist.apache.org/repos/dist/dev/jackrabbit/filevault-package-maven-plugin/1.1.6/
>
> The release candidate is a zip archive of the sources in:
> https://github.com/apache/jackrabbit-filevault-package-maven-plugin/tree/filevault-package-maven-plugin-1.1.6/
>
> The release notes in JIRA are at https://issues.apache.org/jira/projects/JCRVLT/versions/12348444
>
> The SHA1 checksum of the archive is d5c8785cdf5a9d6e069e8af1cc3542b6acee5677
> The SHA512 checksum of the archive is bb11177aaa59b9d69ad06d7b63e965c4bba70e6433577292c4a32d7431198840b9f6e83c6b374c0cf9b5409224a03b413d9e0e68057346a51c01d915b301e3a5
>
> The command for running automated checks against this release candidate is:
> $ sh check-release.sh filevault-plugin 1.1.6 d5c8785cdf5a9d6e069e8af1cc3542b6acee5677
>
>
> *** As FileVault Package Maven Plugin 1.1.6 depends on the FileVault 3.4.8 you need to install FileVault 3.4.8 to your local Maven repository (e.g. via mvn install) before being able to run the checks ***
>
> A staged Maven repository is available for review at:
> https://repository.apache.org/content/repositories/orgapachejackrabbit-1535
>
> =====
>
> Please vote on releasing both packages as Apache Jackrabbit Filevault 3.4.8 and FileVault Package Maven Plugin 1.1.6.
> The vote is open for a minimum of 72 hours during business days and passes
> if a majority of at least three +1 Jackrabbit PMC votes are cast.
> The vote fails if not enough votes are cast after 1 week (5 business days).
>
> [ ] +1 Release these packages as Apache Jackrabbit Filevault 3.4.8 and FileVault Package Maven Plugin 1.1.6
> [ ] -1 Do not release these packages because...
>
> Thanks in advance for voting,
> Konrad
[RESULT][VOTE] Release Jackrabbit FileVault 3.4.8 and FileVault
Package Maven Plugin 1.1.6
Posted by Konrad Windszus <ko...@gmx.de>.
Hi,
The vote has passed with
+1 (binding) from Marcel, Robert and myself
+1 (non-binding) from Stefan
Thanks for voting. I will copy this release to the Jackrabbit dist directory and promote the artifacts to the central Maven repository.
Konrad
> On 11. Jan 2021, at 20:44, Konrad Windszus <ko...@gmx.de> wrote:
>
> Hi,
>
> A candidate for the Jackrabbit Filevault 3.4.8 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/filevault/3.4.8/
>
> The release candidate is a zip archive of the sources in:
> https://github.com/apache/jackrabbit-filevault/tree/jackrabbit-filevault-3.4.8/
>
> The release notes in JIRA are at https://issues.apache.org/jira/projects/JCRVLT/versions/12348445
>
> The SHA1 checksum of the archive is 669663e26d9fe7364a2735bcf237b4719ba1879d.
> The SHA512 checksum of the archive is c2e0024af08ec640ba6a725944392dca4ab36b6106b4418f98a67c4d0c8ba2b601c49627d83d8541b3d5c04824d5fce1479b727510d22d9a4b14c11af6621f90
>
> The command for running automated checks against this release candidate is:
> $ sh check-release.sh filevault 3.4.8 669663e26d9fe7364a2735bcf237b4719ba1879d
>
> A staged Maven repository is available for review at:
> https://repository.apache.org/content/repositories/orgapachejackrabbit-1534
>
> =====
>
> Also a candidate for the Jackrabbit FileVault Package Maven Plugin 1.1.6 release is available at:
> https://dist.apache.org/repos/dist/dev/jackrabbit/filevault-package-maven-plugin/1.1.6/
>
> The release candidate is a zip archive of the sources in:
> https://github.com/apache/jackrabbit-filevault-package-maven-plugin/tree/filevault-package-maven-plugin-1.1.6/
>
> The release notes in JIRA are at https://issues.apache.org/jira/projects/JCRVLT/versions/12348444
>
> The SHA1 checksum of the archive is d5c8785cdf5a9d6e069e8af1cc3542b6acee5677
> The SHA512 checksum of the archive is bb11177aaa59b9d69ad06d7b63e965c4bba70e6433577292c4a32d7431198840b9f6e83c6b374c0cf9b5409224a03b413d9e0e68057346a51c01d915b301e3a5
>
> The command for running automated checks against this release candidate is:
> $ sh check-release.sh filevault-plugin 1.1.6 d5c8785cdf5a9d6e069e8af1cc3542b6acee5677
>
>
> *** As FileVault Package Maven Plugin 1.1.6 depends on the FileVault 3.4.8 you need to install FileVault 3.4.8 to your local Maven repository (e.g. via mvn install) before being able to run the checks ***
>
> A staged Maven repository is available for review at:
> https://repository.apache.org/content/repositories/orgapachejackrabbit-1535
>
> =====
>
> Please vote on releasing both packages as Apache Jackrabbit Filevault 3.4.8 and FileVault Package Maven Plugin 1.1.6.
> The vote is open for a minimum of 72 hours during business days and passes
> if a majority of at least three +1 Jackrabbit PMC votes are cast.
> The vote fails if not enough votes are cast after 1 week (5 business days).
>
> [ ] +1 Release these packages as Apache Jackrabbit Filevault 3.4.8 and FileVault Package Maven Plugin 1.1.6
> [ ] -1 Do not release these packages because...
>
> Thanks in advance for voting,
> Konrad