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 2020/07/28 09:48:11 UTC
[VOTE] Release Apache Jackrabbit FileVault 3.4.6 & Apache Jackrabbit
FileVault - Package Maven Plugin 1.1.4
Hi,
A candidate for the Jackrabbit FileVault 3.4.6 release is available at:
https://dist.apache.org/repos/dist/dev/jackrabbit/filevault/3.4.6/ <https://dist.apache.org/repos/dist/dev/jackrabbit/filevault/3.4.6/>
The release candidate is a zip archive of the sources in:
https://github.com/apache/jackrabbit-filevault/tree/jackrabbit-filevault-3.4.6 <https://github.com/apache/jackrabbit-filevault/tree/jackrabbit-filevault-3.4.6>
The SHA1 checksum of the archive is ed203dca0f3e6b13aee753fbddd83fea14eef092
The SHA-512 checksum of the archive is 6174d50596de206fef8dea09d0e03316cf6054096165758c33c0ade9b9d5e4a38a4b54abdddc2b0ed7f8e666ae6c4a8f9a8d2a883bb02f0a56bfad04e0b0e432
The command for running automated checks against this release candidate is:
$ sh check-release.sh filevault 3.4.6 ed203dca0f3e6b13aee753fbddd83fea14eef092
A candidate for the Jackrabbit FileVault Package Maven Plugin 1.1.4 release is available at:
https://dist.apache.org/repos/dist/dev/jackrabbit/filevault-package-maven-plugin/1.1.4/ <https://dist.apache.org/repos/dist/dev/jackrabbit/filevault-package-maven-plugin/1.1.4/>
The release candidate is a zip archive of the sources in:
https://svn.apache.org/repos/asf/jackrabbit/commons/filevault-package-maven-plugin/tags/filevault-package-maven-plugin-1.1.4/ <https://svn.apache.org/repos/asf/jackrabbit/commons/filevault-package-maven-plugin/tags/filevault-package-maven-plugin-1.1.4/>
The SHA1 checksum of the archive is 007b00f60356bdf796beaf3ace1f239f9698f0ed
The SHA-512 checksum of the archive is 53e4ff0f0eac482d5007a3037a0d13fe557cae278f884749b14946b1133c488617b8e4daccb13f43fbaec4d3a290a9f1f9e216ace1d1fd19c0e112c33d95a911
The command for running automated checks against this release candidate is:
$ sh check-release.sh filevault-plugin 1.1.4 007b00f60356bdf796beaf3ace1f239f9698f0ed
A staged Maven repository containing both release candidates is available for review at:
https://repository.apache.org/content/repositories/orgapachejackrabbit-1520 <https://repository.apache.org/content/repositories/orgapachejackrabbit-1520>
The release notes can be found at
https://issues.apache.org/jira/projects/JCRVLT/versions/12347797 <https://issues.apache.org/jira/projects/JCRVLT/versions/12347797> and
https://issues.apache.org/jira/projects/JCRVLT/versions/12347848 <https://issues.apache.org/jira/projects/JCRVLT/versions/12347848>
Please vote on releasing these packages as Apache Jackrabbit FileVault 3.4.6 and Apache Jackrabbit FileVault Package Maven Plugin 1.1.4
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
[ ] -1 Do not release these packages because...
Thanks,
Konrad
P.S, Due to the Git migration the check script at has been updated: https://dist.apache.org/repos/dist/dev/jackrabbit/check-release.sh <https://dist.apache.org/repos/dist/dev/jackrabbit/check-release.sh>
Re: [VOTE] Release Apache Jackrabbit FileVault 3.4.6 & Apache
Jackrabbit FileVault - Package Maven Plugin 1.1.4
Posted by Tobias Bocanegra <tr...@adobe.com>.
Hi,
Thanks for releasing!
Here's my vote:
[X] +1 Release these packages
With:
[INFO] ------------------------------------------------------------------------
[INFO] Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; 2019-04-05T04:00:29+09:00)
[INFO] OS name: "mac os x", version: "10.15.6", arch: "x86_64", family: "mac"
[INFO] Java version: 1.8.0_221, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/jdk1.8.0_221.jdk/Contents/Home/jre
[INFO] MAVEN_OPTS:
[INFO] ------------------------------------------------------------------------
[INFO] ALL CHECKS OK
[INFO] ------------------------------------------------------------------------
Regards, Toby
On 28 Jul 2020, at 18:48, Konrad Windszus <ko...@gmx.de>> wrote:
Hi,
A candidate for the Jackrabbit FileVault 3.4.6 release is available at:
https://dist.apache.org/repos/dist/dev/jackrabbit/filevault/3.4.6/
The release candidate is a zip archive of the sources in:
https://github.com/apache/jackrabbit-filevault/tree/jackrabbit-filevault-3.4.6
The SHA1 checksum of the archive is ed203dca0f3e6b13aee753fbddd83fea14eef092
The SHA-512 checksum of the archive is 6174d50596de206fef8dea09d0e03316cf6054096165758c33c0ade9b9d5e4a38a4b54abdddc2b0ed7f8e666ae6c4a8f9a8d2a883bb02f0a56bfad04e0b0e432
The command for running automated checks against this release candidate is:
$ sh check-release.sh filevault 3.4.6 ed203dca0f3e6b13aee753fbddd83fea14eef092
A candidate for the Jackrabbit FileVault Package Maven Plugin 1.1.4 release is available at:
https://dist.apache.org/repos/dist/dev/jackrabbit/filevault-package-maven-plugin/1.1.4/
The release candidate is a zip archive of the sources in:
https://svn.apache.org/repos/asf/jackrabbit/commons/filevault-package-maven-plugin/tags/filevault-package-maven-plugin-1.1.4/
The SHA1 checksum of the archive is 007b00f60356bdf796beaf3ace1f239f9698f0ed
The SHA-512 checksum of the archive is 53e4ff0f0eac482d5007a3037a0d13fe557cae278f884749b14946b1133c488617b8e4daccb13f43fbaec4d3a290a9f1f9e216ace1d1fd19c0e112c33d95a911
The command for running automated checks against this release candidate is:
$ sh check-release.sh filevault-plugin 1.1.4 007b00f60356bdf796beaf3ace1f239f9698f0ed
A staged Maven repository containing both release candidates is available for review at:
https://repository.apache.org/content/repositories/orgapachejackrabbit-1520
The release notes can be found at
https://issues.apache.org/jira/projects/JCRVLT/versions/12347797 and
https://issues.apache.org/jira/projects/JCRVLT/versions/12347848
Please vote on releasing these packages as Apache Jackrabbit FileVault 3.4.6 and Apache Jackrabbit FileVault Package Maven Plugin 1.1.4
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
[ ] -1 Do not release these packages because...
Thanks,
Konrad
P.S, Due to the Git migration the check script at has been updated: https://dist.apache.org/repos/dist/dev/jackrabbit/check-release.sh
Re: [VOTE] Release Apache Jackrabbit FileVault 3.4.6 & Apache
Jackrabbit FileVault - Package Maven Plugin 1.1.4
Posted by Konrad Windszus <ko...@gmx.de>.
> On 31. Jul 2020, at 07:46, Julian Reschke <ju...@gmx.de> wrote:
>
> Am 30.07.2020 um 20:22 schrieb Julian Reschke:
>> Am 30.07.2020 um 20:07 schrieb Konrad Windszus:
>>> Hi Julian,
>>>
>>>> On 30. Jul 2020, at 19:52, Julian Reschke <julian.reschke@gmx.de
>>>> <ma...@gmx.de>> wrote:
>>>>
>>>> Am 30.07.2020 um 19:35 schrieb Julian Reschke:
>>>>> ...
>>>>> That would fix the immediate issue (I assume), but is somehow risky
>>>>> because then it get's harder to understand what actually is checked.
>>>>>
>>>>> I get that in this case we have a combined vote for these two releases,
>>>>> and that they are only released in tandem or not at all.
>>>>>
>>>>> But what if one of these had a dependency on something that happens to
>>>>> be in the staging repo right now, but which is not part of the vote?
>>>>>
>>>>> It might be better if check-release actually installed the artefact
>>>>> locally. I already tried that by changing the MVN_ARGS in the script,
>>>>> but couldn't get that working.
>>>>>
>>>>> Best regards, Julian
>>>>
>>>> So I did manually install 3.4.6 and then ran the check for the maven
>>>> plugin; log output attached.
>>>>
>>>> Two problems:
>>>>
>>>> 1) Tests fail:
>>>>
>>>>> [INFO] T E S T S
>>>>> [INFO] -------------------------------------------------------
>>>>> [INFO] Running
>>>>> org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT
>>>>>
>>>>> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time
>>>>> elapsed: 0.17 s <<< FAILURE! - in
>>>>> org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT
>>>>>
>>>>> [ERROR]
>>>>> org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT.multi_module_build_succeeds
>>>>> Time elapsed: 0.085 s <<< ERROR!
>>>>> org.apache.maven.it.VerificationException:
>>>>> Exit code was non-zero: 1; command line and log =
>>>>> bin\mvn -e --batch-mode
>>>>> -Dmaven.repo.local=C:\Users\jre\.m2\repository clean test
>>>>> Der Befehl "mvn" ist entweder falsch geschrieben oder
>>>>> konnte nicht gefunden werden.
>>>>>
>>>>> at
>>>>> org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT.multi_module_build_succeeds(AnalyzeClassesMultiModuleIT.java:33)
>>>>>
>>>>>
>>> Do you haven Maven (mvn) in your PATH?
>>
>> mvn is a symbolic link in /usr/local/bin, which is in my PATH.
>>
>> That said, it might not work the way it's called because I'm on cygwin.
>> ...
>
> ...so I tried to check out the plugin from source control to test it
> directly. The mail says:
>
>> The release candidate is a zip archive of the sources in:
>> https://svn.apache.org/repos/asf/jackrabbit/commons/filevault-package-maven-plugin/tags/filevault-package-maven-plugin-1.1.4/
>
I fixed the mail template now
> However, that tag does not exist as the source moved to git, right?
>
> Went over to
> <https://jackrabbit.apache.org/filevault-package-maven-plugin/>, but
> that says "svn", too...
That is still the site for the last release 1.1.2 (when it was still in SVN), the new site at http://jackrabbit.apache.org/filevault-package-maven-plugin-archives/1.1.3-SNAPSHOT/ <http://jackrabbit.apache.org/filevault-package-maven-plugin-archives/1.1.3-SNAPSHOT/> has the correct link.
>
> Best regards, Julian
Re: [VOTE] Release Apache Jackrabbit FileVault 3.4.6 & Apache
Jackrabbit FileVault - Package Maven Plugin 1.1.4
Posted by Julian Reschke <ju...@gmx.de>.
Am 30.07.2020 um 20:22 schrieb Julian Reschke:
> Am 30.07.2020 um 20:07 schrieb Konrad Windszus:
>> Hi Julian,
>>
>>> On 30. Jul 2020, at 19:52, Julian Reschke <julian.reschke@gmx.de
>>> <ma...@gmx.de>> wrote:
>>>
>>> Am 30.07.2020 um 19:35 schrieb Julian Reschke:
>>>> ...
>>>> That would fix the immediate issue (I assume), but is somehow risky
>>>> because then it get's harder to understand what actually is checked.
>>>>
>>>> I get that in this case we have a combined vote for these two releases,
>>>> and that they are only released in tandem or not at all.
>>>>
>>>> But what if one of these had a dependency on something that happens to
>>>> be in the staging repo right now, but which is not part of the vote?
>>>>
>>>> It might be better if check-release actually installed the artefact
>>>> locally. I already tried that by changing the MVN_ARGS in the script,
>>>> but couldn't get that working.
>>>>
>>>> Best regards, Julian
>>>
>>> So I did manually install 3.4.6 and then ran the check for the maven
>>> plugin; log output attached.
>>>
>>> Two problems:
>>>
>>> 1) Tests fail:
>>>
>>>> [INFO] T E S T S
>>>> [INFO] -------------------------------------------------------
>>>> [INFO] Running
>>>> org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT
>>>>
>>>> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time
>>>> elapsed: 0.17 s <<< FAILURE! - in
>>>> org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT
>>>>
>>>> [ERROR]
>>>> org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT.multi_module_build_succeeds
>>>> Time elapsed: 0.085 s <<< ERROR!
>>>> org.apache.maven.it.VerificationException:
>>>> Exit code was non-zero: 1; command line and log =
>>>> bin\mvn -e --batch-mode
>>>> -Dmaven.repo.local=C:\Users\jre\.m2\repository clean test
>>>> Der Befehl "mvn" ist entweder falsch geschrieben oder
>>>> konnte nicht gefunden werden.
>>>>
>>>> at
>>>> org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT.multi_module_build_succeeds(AnalyzeClassesMultiModuleIT.java:33)
>>>>
>>>>
>> Do you haven Maven (mvn) in your PATH?
>
> mvn is a symbolic link in /usr/local/bin, which is in my PATH.
>
> That said, it might not work the way it's called because I'm on cygwin.
> ...
...so I tried to check out the plugin from source control to test it
directly. The mail says:
> The release candidate is a zip archive of the sources in:
> https://svn.apache.org/repos/asf/jackrabbit/commons/filevault-package-maven-plugin/tags/filevault-package-maven-plugin-1.1.4/
However, that tag does not exist as the source moved to git, right?
Went over to
<https://jackrabbit.apache.org/filevault-package-maven-plugin/>, but
that says "svn", too...
Best regards, Julian
Re: [VOTE] Release Apache Jackrabbit FileVault 3.4.6 & Apache
Jackrabbit FileVault - Package Maven Plugin 1.1.4
Posted by Julian Reschke <ju...@gmx.de>.
Am 31.07.2020 um 06:05 schrieb Tobias Bocanegra:
> I see the same:
>
> [INFO] Verifying jackrabbit-filevault-3.4.6-src.zip...
> gpg: assuming signed data in
> './filevault/3.4.6/jackrabbit-filevault-3.4.6-src.zip'
> gpg: Signature made Tue Jul 28 14:55:53 2020 JST
> gpg: using RSA key D7742D58455ECC7C
> gpg: Good signature from "Konrad Windszus <kwin@apache.org
> <ma...@apache.org>>" [ultimate]
> [INFO] OK: jackrabbit-filevault-3.4.6-src.zip.asc
> openssl:Error: '' is an invalid command.
>
> There was an error in the script. I fixed it, and how it works correctly:
Thanks.
Best regards, Julian
Re: [VOTE] Release Apache Jackrabbit FileVault 3.4.6 & Apache
Jackrabbit FileVault - Package Maven Plugin 1.1.4
Posted by Tobias Bocanegra <tr...@adobe.com>.
I see the same:
[INFO] Verifying jackrabbit-filevault-3.4.6-src.zip...
gpg: assuming signed data in './filevault/3.4.6/jackrabbit-filevault-3.4.6-src.zip'
gpg: Signature made Tue Jul 28 14:55:53 2020 JST
gpg: using RSA key D7742D58455ECC7C
gpg: Good signature from "Konrad Windszus <kw...@apache.org>>" [ultimate]
[INFO] OK: jackrabbit-filevault-3.4.6-src.zip.asc
openssl:Error: '' is an invalid command.
There was an error in the script. I fixed it, and how it works correctly:
[INFO] 3. Verify checksums and signatures
[INFO]
[INFO] Verifying jackrabbit-filevault-3.4.6-src.zip...
gpg: assuming signed data in './filevault/3.4.6/jackrabbit-filevault-3.4.6-src.zip'
gpg: Signature made Tue Jul 28 14:55:53 2020 JST
gpg: using RSA key D7742D58455ECC7C
gpg: Good signature from "Konrad Windszus <kw...@apache.org>>" [ultimate]
[INFO] OK: jackrabbit-filevault-3.4.6-src.zip.asc
[INFO] OK: jackrabbit-filevault-3.4.6-src.zip.sha1
[INFO] OK: jackrabbit-filevault-3.4.6-src.zip.sha512
[INFO]
[INFO] 3. Verify checksums and signatures
[INFO]
[INFO] Verifying filevault-package-maven-plugin-1.1.4-source-release.zip...
gpg: assuming signed data in './filevault-package-maven-plugin/1.1.4/filevault-package-maven-plugin-1.1.4-source-release.zip'
gpg: Signature made Tue Jul 28 16:43:49 2020 JST
gpg: using RSA key D7742D58455ECC7C
gpg: Good signature from "Konrad Windszus <kw...@apache.org>>" [ultimate]
[INFO] OK: filevault-package-maven-plugin-1.1.4-source-release.zip.asc
[INFO] OK: filevault-package-maven-plugin-1.1.4-source-release.zip.sha512
[INFO]
Regards, Toby
On 31 Jul 2020, at 03:28, Konrad Windszus <ko...@gmx.de>> wrote:
Regarding "Can you please check whether you see the same gpg/openssl issues in your log?"
Yes, that message is totally expected. As I said already: My key is not signed yet! Therefore GPG emits a message related to that.
IMHO that should not make the check fail though (and in fact it doesn't) because it is equal to the key from the KEYS file.
"You should get your key linked to the Apache web of trust<http://www.apache.org/dev/release-signing.html#apache-wot>. Once other people have signed your key, you can update the KEYS file with the signatures you’ve received."
(https://jackrabbit.apache.org/filevault/howto_release.html#Appendix_A:_Create_and_add_your_key_to_the_Jackrabbit_KEYS_file).
I will try to get it signed by someone else, but IMHO this is just a nice to have, not mandatory!
Konrad
Re: [VOTE] Release Apache Jackrabbit FileVault 3.4.6 & Apache
Jackrabbit FileVault - Package Maven Plugin 1.1.4
Posted by Konrad Windszus <ko...@gmx.de>.
Regarding "Can you please check whether you see the same gpg/openssl issues in your log?"
Yes, that message is totally expected. As I said already: My key is not signed yet! Therefore GPG emits a message related to that.
IMHO that should not make the check fail though (and in fact it doesn't) because it is equal to the key from the KEYS file.
"You should get your key linked to the Apache web of trust <http://www.apache.org/dev/release-signing.html#apache-wot>. Once other people have signed your key, you can update the KEYS file with the signatures you’ve received."
(https://jackrabbit.apache.org/filevault/howto_release.html#Appendix_A:_Create_and_add_your_key_to_the_Jackrabbit_KEYS_file <https://jackrabbit.apache.org/filevault/howto_release.html#Appendix_A:_Create_and_add_your_key_to_the_Jackrabbit_KEYS_file>).
I will try to get it signed by someone else, but IMHO this is just a nice to have, not mandatory!
Konrad
Re: [VOTE] Release Apache Jackrabbit FileVault 3.4.6 & Apache
Jackrabbit FileVault - Package Maven Plugin 1.1.4
Posted by Julian Reschke <ju...@gmx.de>.
Am 30.07.2020 um 20:22 schrieb Julian Reschke:
> Am 30.07.2020 um 20:07 schrieb Konrad Windszus:
>> Hi Julian,
>>
>>> On 30. Jul 2020, at 19:52, Julian Reschke <julian.reschke@gmx.de
>>> <ma...@gmx.de>> wrote:
>>>
>>> Am 30.07.2020 um 19:35 schrieb Julian Reschke:
>>>> ...
>>>> That would fix the immediate issue (I assume), but is somehow risky
>>>> because then it get's harder to understand what actually is checked.
>>>>
>>>> I get that in this case we have a combined vote for these two releases,
>>>> and that they are only released in tandem or not at all.
>>>>
>>>> But what if one of these had a dependency on something that happens to
>>>> be in the staging repo right now, but which is not part of the vote?
>>>>
>>>> It might be better if check-release actually installed the artefact
>>>> locally. I already tried that by changing the MVN_ARGS in the script,
>>>> but couldn't get that working.
>>>>
>>>> Best regards, Julian
>>>
>>> So I did manually install 3.4.6 and then ran the check for the maven
>>> plugin; log output attached.
>>>
>>> Two problems:
>>>
>>> 1) Tests fail:
>>>
>>>> [INFO] T E S T S
>>>> [INFO] -------------------------------------------------------
>>>> [INFO] Running
>>>> org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT
>>>>
>>>> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time
>>>> elapsed: 0.17 s <<< FAILURE! - in
>>>> org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT
>>>>
>>>> [ERROR]
>>>> org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT.multi_module_build_succeeds
>>>> Time elapsed: 0.085 s <<< ERROR!
>>>> org.apache.maven.it.VerificationException:
>>>> Exit code was non-zero: 1; command line and log =
>>>> bin\mvn -e --batch-mode
>>>> -Dmaven.repo.local=C:\Users\jre\.m2\repository clean test
>>>> Der Befehl "mvn" ist entweder falsch geschrieben oder
>>>> konnte nicht gefunden werden.
>>>>
>>>> at
>>>> org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT.multi_module_build_succeeds(AnalyzeClassesMultiModuleIT.java:33)
>>>>
>>>>
>> Do you haven Maven (mvn) in your PATH?
>
> mvn is a symbolic link in /usr/local/bin, which is in my PATH.
>
> That said, it might not work the way it's called because I'm on cygwin.
> ...
Ok, so the Cygwin symlink does not work.
Addinf apache-maven-.../bin to the PATH indeed changes the behavior.
Instead of failing as above the first test is now hanging:
> [INFO] -------------------------------------------------------
> [INFO] T E S T S
> [INFO] -------------------------------------------------------
> [INFO] Running org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT
jstack says:
> 2020-07-31 09:05:51
> Full thread dump Java HotSpot(TM) 64-Bit Server VM (25.221-b11 mixed mode):
>
> "Thread-9" #44 prio=5 os_prio=0 tid=0x000000001decc800 nid=0x3fac runnable [0x00000000242bf000]
> java.lang.Thread.State: RUNNABLE
> at java.io.FileInputStream.readBytes(Native Method)
> at java.io.FileInputStream.read(FileInputStream.java:255)
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
> - locked <0x00000000edd6c2d0> (a java.io.InputStreamReader)
> at java.io.InputStreamReader.read(InputStreamReader.java:184)
> at java.io.BufferedReader.fill(BufferedReader.java:161)
> at java.io.BufferedReader.readLine(BufferedReader.java:324)
> - locked <0x00000000edd6c2d0> (a java.io.InputStreamReader)
> at java.io.BufferedReader.readLine(BufferedReader.java:389)
> at org.apache.maven.surefire.shade.common.org.apache.maven.shared.utils.cli.StreamPumper.run(StreamPumper.java:89)
>
> "Thread-8" #43 prio=5 os_prio=0 tid=0x000000001decb800 nid=0x2ac runnable [0x00000000241be000]
> java.lang.Thread.State: RUNNABLE
> at java.io.FileInputStream.readBytes(Native Method)
> at java.io.FileInputStream.read(FileInputStream.java:255)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:284)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
> - locked <0x00000000edd48b18> (a java.io.BufferedInputStream)
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
> - locked <0x00000000edd69690> (a java.io.InputStreamReader)
> at java.io.InputStreamReader.read(InputStreamReader.java:184)
> at java.io.BufferedReader.fill(BufferedReader.java:161)
> at java.io.BufferedReader.readLine(BufferedReader.java:324)
> - locked <0x00000000edd69690> (a java.io.InputStreamReader)
> at java.io.BufferedReader.readLine(BufferedReader.java:389)
> at org.apache.maven.surefire.shade.common.org.apache.maven.shared.utils.cli.StreamPumper.run(StreamPumper.java:89)
>
> "Thread-7" #42 prio=5 os_prio=0 tid=0x000000001decb000 nid=0x2038 waiting on condition [0x00000000240bf000]
> java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x00000000ed56c458> (a java.util.concurrent.Semaphore$NonfairSync)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
> at java.util.concurrent.Semaphore.acquire(Semaphore.java:312)
> at org.apache.maven.plugin.surefire.booterclient.lazytestprovider.TestLessInputStream.awaitNextCommand(TestLessInputStream.java:165)
> at org.apache.maven.plugin.surefire.booterclient.lazytestprovider.TestLessInputStream.beforeNextCommand(TestLessInputStream.java:136)
> at org.apache.maven.plugin.surefire.booterclient.lazytestprovider.AbstractCommandStream.read(AbstractCommandStream.java:100)
> at org.apache.maven.surefire.shade.common.org.apache.maven.shared.utils.cli.StreamFeeder.feed(StreamFeeder.java:123)
> at org.apache.maven.surefire.shade.common.org.apache.maven.shared.utils.cli.StreamFeeder.run(StreamFeeder.java:60)
>
> "ThreadedStreamConsumer" #40 daemon prio=5 os_prio=0 tid=0x000000001deca000 nid=0x16cc waiting on condition [0x0000000023fbf000]
> java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x00000000edcfa2c8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
> at java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:403)
> at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:83)
> at java.lang.Thread.run(Thread.java:748)
>
> "ping-timer-10s" #39 daemon prio=5 os_prio=0 tid=0x000000001dec8800 nid=0x3f3c waiting on condition [0x000000002253e000]
> java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x00000000ed256948> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
> at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093)
> at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
> at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
>
> "timeout-check-timer" #37 daemon prio=5 os_prio=0 tid=0x000000001dec8000 nid=0xb9c waiting on condition [0x000000001eb9f000]
> java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x00000000ed27f1c0> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
> at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093)
> at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
> at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
>
> "resolver-5" #17 daemon prio=5 os_prio=0 tid=0x000000001b7f4000 nid=0x1d28 waiting on condition [0x000000002158f000]
> java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x000000008083c200> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
> at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
> at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
>
> "resolver-4" #16 daemon prio=5 os_prio=0 tid=0x000000001b7ed000 nid=0x20dc waiting on condition [0x000000002148e000]
> java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x000000008083c200> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
> at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
> at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
>
> "resolver-3" #15 daemon prio=5 os_prio=0 tid=0x000000001b7ee000 nid=0x3d58 waiting on condition [0x000000002138f000]
> java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x000000008083c200> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
> at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
> at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
>
> "resolver-2" #14 daemon prio=5 os_prio=0 tid=0x000000001b7f2000 nid=0x3f68 waiting on condition [0x000000001ffdf000]
> java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x000000008083c200> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
> at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
> at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
>
> "resolver-1" #13 daemon prio=5 os_prio=0 tid=0x000000001b7f0800 nid=0x35f0 waiting on condition [0x000000001fc8f000]
> java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x000000008083c200> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
> at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
> at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
>
> "Service Thread" #10 daemon prio=9 os_prio=0 tid=0x0000000019a5f000 nid=0x1e4c runnable [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
>
> "C1 CompilerThread3" #9 daemon prio=9 os_prio=2 tid=0x0000000019a35800 nid=0x3fd4 waiting on condition [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
>
> "C2 CompilerThread2" #8 daemon prio=9 os_prio=2 tid=0x0000000019a31800 nid=0x3e80 waiting on condition [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
>
> "C2 CompilerThread1" #7 daemon prio=9 os_prio=2 tid=0x0000000019a2d000 nid=0x2e50 waiting on condition [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
>
> "C2 CompilerThread0" #6 daemon prio=9 os_prio=2 tid=0x0000000019a2a800 nid=0x2e14 waiting on condition [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
>
> "Attach Listener" #5 daemon prio=5 os_prio=2 tid=0x0000000019a29800 nid=0x31cc waiting on condition [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
>
> "Signal Dispatcher" #4 daemon prio=9 os_prio=2 tid=0x0000000019a28000 nid=0x35b0 runnable [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
>
> "Finalizer" #3 daemon prio=8 os_prio=1 tid=0x0000000019a20800 nid=0x2c98 in Object.wait() [0x0000000019fff000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000080775a28> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:144)
> - locked <0x0000000080775a28> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:165)
> at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:216)
>
> "Reference Handler" #2 daemon prio=10 os_prio=2 tid=0x0000000017c2c800 nid=0x21bc in Object.wait() [0x0000000019eff000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000080b29a20> (a java.lang.ref.Reference$Lock)
> at java.lang.Object.wait(Object.java:502)
> at java.lang.ref.Reference.tryHandlePending(Reference.java:191)
> - locked <0x0000000080b29a20> (a java.lang.ref.Reference$Lock)
> at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:153)
>
> "main" #1 prio=5 os_prio=0 tid=0x00000000028ce800 nid=0x3030 runnable [0x0000000002abe000]
> java.lang.Thread.State: RUNNABLE
> at java.lang.ProcessImpl.waitForInterruptibly(Native Method)
> at java.lang.ProcessImpl.waitFor(ProcessImpl.java:449)
> at org.apache.maven.surefire.shade.common.org.apache.maven.shared.utils.cli.CommandLineUtils$1.call(CommandLineUtils.java:279)
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:617)
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:285)
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:248)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1217)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1063)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:889)
> 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)
>
> "VM Thread" os_prio=2 tid=0x0000000017c28800 nid=0x3760 runnable
>
> "GC task thread#0 (ParallelGC)" os_prio=0 tid=0x0000000002ad7800 nid=0x2c14 runnable
>
> "GC task thread#1 (ParallelGC)" os_prio=0 tid=0x0000000002ad9000 nid=0x32a4 runnable
>
> "GC task thread#2 (ParallelGC)" os_prio=0 tid=0x0000000002ada800 nid=0x2f8c runnable
>
> "GC task thread#3 (ParallelGC)" os_prio=0 tid=0x0000000002adc000 nid=0x396c runnable
>
> "GC task thread#4 (ParallelGC)" os_prio=0 tid=0x0000000002ade800 nid=0x1338 runnable
>
> "GC task thread#5 (ParallelGC)" os_prio=0 tid=0x0000000002adf800 nid=0x1c74 runnable
>
> "GC task thread#6 (ParallelGC)" os_prio=0 tid=0x0000000002ae4000 nid=0x3fc0 runnable
>
> "GC task thread#7 (ParallelGC)" os_prio=0 tid=0x0000000002ae5000 nid=0x3438 runnable
>
> "VM Periodic Task Thread" os_prio=2 tid=0x0000000019a61000 nid=0x36ec waiting on condition
>
> JNI global references: 213
I assume this really has nothing to do with the vault maven plugin, but
that's what happens here, so I really can't cast a vote.
Best regards, Julian
Re: [VOTE] Release Apache Jackrabbit FileVault 3.4.6 & Apache
Jackrabbit FileVault - Package Maven Plugin 1.1.4
Posted by Julian Reschke <ju...@gmx.de>.
Am 30.07.2020 um 20:07 schrieb Konrad Windszus:
> Hi Julian,
>
>> On 30. Jul 2020, at 19:52, Julian Reschke <julian.reschke@gmx.de
>> <ma...@gmx.de>> wrote:
>>
>> Am 30.07.2020 um 19:35 schrieb Julian Reschke:
>>> ...
>>> That would fix the immediate issue (I assume), but is somehow risky
>>> because then it get's harder to understand what actually is checked.
>>>
>>> I get that in this case we have a combined vote for these two releases,
>>> and that they are only released in tandem or not at all.
>>>
>>> But what if one of these had a dependency on something that happens to
>>> be in the staging repo right now, but which is not part of the vote?
>>>
>>> It might be better if check-release actually installed the artefact
>>> locally. I already tried that by changing the MVN_ARGS in the script,
>>> but couldn't get that working.
>>>
>>> Best regards, Julian
>>
>> So I did manually install 3.4.6 and then ran the check for the maven
>> plugin; log output attached.
>>
>> Two problems:
>>
>> 1) Tests fail:
>>
>>> [INFO] T E S T S
>>> [INFO] -------------------------------------------------------
>>> [INFO] Running
>>> org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT
>>> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time
>>> elapsed: 0.17 s <<< FAILURE! - in
>>> org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT
>>> [ERROR]
>>> org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT.multi_module_build_succeeds
>>> Time elapsed: 0.085 s <<< ERROR!
>>> org.apache.maven.it.VerificationException:
>>> Exit code was non-zero: 1; command line and log =
>>> bin\mvn -e --batch-mode
>>> -Dmaven.repo.local=C:\Users\jre\.m2\repository clean test
>>> Der Befehl "mvn" ist entweder falsch geschrieben oder
>>> konnte nicht gefunden werden.
>>>
>>> at
>>> org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT.multi_module_build_succeeds(AnalyzeClassesMultiModuleIT.java:33)
>>>
> Do you haven Maven (mvn) in your PATH?
mvn is a symbolic link in /usr/local/bin, which is in my PATH.
That said, it might not work the way it's called because I'm on cygwin.
>> but then also
>>
>> 2) there seems to be a problem with the checksum checks (only visible in
>> the log):
>>
>>> [INFO]
>>> [INFO] 3. Verify checksums and signatures
>>> [INFO]
>>> [INFO] Verifying
>>> filevault-package-maven-plugin-1.1.4-source-release.zip...
>>> gpg: die unterzeichneten Daten sind wohl in
>>> './filevault-package-maven-plugin/1.1.4/filevault-package-maven-plugin-1.1.4-source-release.zip'
>>> gpg: Unterschrift vom Di, 28. Jul 2020 08:43:49 MEZ mittels
>>> RSA-Schlüssel ID 455ECC7C
>>> gpg: Korrekte Unterschrift von "Konrad Windszus <kwin@apache.org
>>> <ma...@apache.org>>"
>>> gpg: WARNUNG: Dieser Schlüssel trägt keine vertrauenswürdige Signatur!
>>> gpg: Es gibt keinen Hinweis, daß die Signatur wirklich dem
>>> vorgeblichen Besitzer gehört.
>>> Haupt-Fingerabdruck = B91A B7D2 121D C6B0 A61A A182 D774 2D58 455E CC7C
>>> [INFO] OK: filevault-package-maven-plugin-1.1.4-source-release.zip.asc
>>> openssl:Error: '' is an invalid command.
>>>
>>> Standard commands
>>> asn1parse ca ciphers cms
>>> crl crl2pkcs7 dgst dh
>>> dhparam dsa dsaparam ec
>>> ecparam enc engine errstr
>>> gendh gendsa genpkey genrsa
>>> nseq ocsp passwd pkcs12
>>> pkcs7 pkcs8 pkey pkeyparam
>>> pkeyutl prime rand req
>>> rsa rsautl s_client s_server
>>> s_time sess_id smime speed
>>> spkac srp ts verify
>>> version x509
>>>
>>> Message Digest commands (see the `dgst' command for more details)
>>> md2 md4 md5 mdc2
>>> rmd160 sha sha1
>>>
>>> Cipher commands (see the `enc' command for more details)
>>> aes-128-cbc aes-128-ecb aes-192-cbc aes-192-ecb
>>> aes-256-cbc aes-256-ecb base64 bf
>>> bf-cbc bf-cfb bf-ecb bf-ofb
>>> camellia-128-cbc camellia-128-ecb camellia-192-cbc camellia-192-ecb
>>> camellia-256-cbc camellia-256-ecb cast cast-cbc
>>> cast5-cbc cast5-cfb cast5-ecb cast5-ofb
>>> des des-cbc des-cfb des-ecb
>>> des-ede des-ede-cbc des-ede-cfb des-ede-ofb
>>> des-ede3 des-ede3-cbc des-ede3-cfb des-ede3-ofb
>>> des-ofb des3 desx idea
>>> idea-cbc idea-cfb idea-ecb idea-ofb
>>> rc2 rc2-40-cbc rc2-64-cbc rc2-cbc
>>> rc2-cfb rc2-ecb rc2-ofb rc4
>>> rc4-40 rc5 rc5-cbc rc5-cfb
>>> rc5-ecb rc5-ofb seed seed-cbc
>>> seed-cfb seed-ecb seed-ofb zlib
>>>
>>> [INFO] OK:
>>> filevault-package-maven-plugin-1.1.4-source-release.zip.sha512
>>
> My key is in https://dist.apache.org/repos/dist/release/jackrabbit/KEYS
> <https://dist.apache.org/repos/dist/release/jackrabbit/KEYS> (https://
> <https://downloads.apache.org/jackrabbit/KEYS>downloads.apache.org/jackrabbit/KEYS
> <http://downloads.apache.org/jackrabbit/KEYS>)
> You have to trust those keys, because they are not (yet) signed by
> anyone else.
> According to
> https://jackrabbit.apache.org/filevault/howto_release.html#Appendix_A:_Create_and_add_your_key_to_the_Jackrabbit_KEYS_file
> <https://jackrabbit.apache.org/filevault/howto_release.html#Appendix_A:_Create_and_add_your_key_to_the_Jackrabbit_KEYS_file> or
> https://jackrabbit.apache.org/jcr/creating-releases.html#Appendix_A:_Create_and_add_your_key_to_the_Jackrabbit_KEYS_file
> <https://jackrabbit.apache.org/jcr/creating-releases.html#Appendix_A:_Create_and_add_your_key_to_the_Jackrabbit_KEYS_file> this
> is enough.
> I would suggest to mark all keys being listed in
> https://dist.apache.org/repos/dist/release/jackrabbit/KEYS
> <https://dist.apache.org/repos/dist/release/jackrabbit/KEYS> as trusted,
> as only with ASF credentials someone could upload them there.
>
> I am still wondering why these issues never come up with the previous
> releases.....
When I voted for earlier releases, they worked for me. I don't think I
ever voted on the plugin.
The latter issue apparently is eaten by the check-release script; it may
have been present before. I only checked the log because of the failure.
So we really have multiple issues to solve.
Can you please check whether you see the same gpg/openssl issues in your
log?
Best regards, Julian
Re: [VOTE] Release Apache Jackrabbit FileVault 3.4.6 & Apache
Jackrabbit FileVault - Package Maven Plugin 1.1.4
Posted by Konrad Windszus <ko...@gmx.de>.
Hi Julian,
> On 30. Jul 2020, at 19:52, Julian Reschke <ju...@gmx.de> wrote:
>
> Am 30.07.2020 um 19:35 schrieb Julian Reschke:
>> ...
>> That would fix the immediate issue (I assume), but is somehow risky
>> because then it get's harder to understand what actually is checked.
>>
>> I get that in this case we have a combined vote for these two releases,
>> and that they are only released in tandem or not at all.
>>
>> But what if one of these had a dependency on something that happens to
>> be in the staging repo right now, but which is not part of the vote?
>>
>> It might be better if check-release actually installed the artefact
>> locally. I already tried that by changing the MVN_ARGS in the script,
>> but couldn't get that working.
>>
>> Best regards, Julian
>
> So I did manually install 3.4.6 and then ran the check for the maven
> plugin; log output attached.
>
> Two problems:
>
> 1) Tests fail:
>
>> [INFO] T E S T S
>> [INFO] -------------------------------------------------------
>> [INFO] Running org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT
>> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.17 s <<< FAILURE! - in org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT
>> [ERROR] org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT.multi_module_build_succeeds Time elapsed: 0.085 s <<< ERROR!
>> org.apache.maven.it.VerificationException:
>> Exit code was non-zero: 1; command line and log =
>> bin\mvn -e --batch-mode -Dmaven.repo.local=C:\Users\jre\.m2\repository clean test
>> Der Befehl "mvn" ist entweder falsch geschrieben oder
>> konnte nicht gefunden werden.
>>
>> at org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT.multi_module_build_succeeds(AnalyzeClassesMultiModuleIT.java:33)
>>
Do you haven Maven (mvn) in your PATH?
> but then also
>
> 2) there seems to be a problem with the checksum checks (only visible in
> the log):
>
>> [INFO]
>> [INFO] 3. Verify checksums and signatures
>> [INFO]
>> [INFO] Verifying filevault-package-maven-plugin-1.1.4-source-release.zip...
>> gpg: die unterzeichneten Daten sind wohl in './filevault-package-maven-plugin/1.1.4/filevault-package-maven-plugin-1.1.4-source-release.zip'
>> gpg: Unterschrift vom Di, 28. Jul 2020 08:43:49 MEZ mittels RSA-Schlüssel ID 455ECC7C
>> gpg: Korrekte Unterschrift von "Konrad Windszus <kwin@apache.org <ma...@apache.org>>"
>> gpg: WARNUNG: Dieser Schlüssel trägt keine vertrauenswürdige Signatur!
>> gpg: Es gibt keinen Hinweis, daß die Signatur wirklich dem vorgeblichen Besitzer gehört.
>> Haupt-Fingerabdruck = B91A B7D2 121D C6B0 A61A A182 D774 2D58 455E CC7C
>> [INFO] OK: filevault-package-maven-plugin-1.1.4-source-release.zip.asc
>> openssl:Error: '' is an invalid command.
>>
>> Standard commands
>> asn1parse ca ciphers cms
>> crl crl2pkcs7 dgst dh
>> dhparam dsa dsaparam ec
>> ecparam enc engine errstr
>> gendh gendsa genpkey genrsa
>> nseq ocsp passwd pkcs12
>> pkcs7 pkcs8 pkey pkeyparam
>> pkeyutl prime rand req
>> rsa rsautl s_client s_server
>> s_time sess_id smime speed
>> spkac srp ts verify
>> version x509
>>
>> Message Digest commands (see the `dgst' command for more details)
>> md2 md4 md5 mdc2
>> rmd160 sha sha1
>>
>> Cipher commands (see the `enc' command for more details)
>> aes-128-cbc aes-128-ecb aes-192-cbc aes-192-ecb
>> aes-256-cbc aes-256-ecb base64 bf
>> bf-cbc bf-cfb bf-ecb bf-ofb
>> camellia-128-cbc camellia-128-ecb camellia-192-cbc camellia-192-ecb
>> camellia-256-cbc camellia-256-ecb cast cast-cbc
>> cast5-cbc cast5-cfb cast5-ecb cast5-ofb
>> des des-cbc des-cfb des-ecb
>> des-ede des-ede-cbc des-ede-cfb des-ede-ofb
>> des-ede3 des-ede3-cbc des-ede3-cfb des-ede3-ofb
>> des-ofb des3 desx idea
>> idea-cbc idea-cfb idea-ecb idea-ofb
>> rc2 rc2-40-cbc rc2-64-cbc rc2-cbc
>> rc2-cfb rc2-ecb rc2-ofb rc4
>> rc4-40 rc5 rc5-cbc rc5-cfb
>> rc5-ecb rc5-ofb seed seed-cbc
>> seed-cfb seed-ecb seed-ofb zlib
>>
>> [INFO] OK: filevault-package-maven-plugin-1.1.4-source-release.zip.sha512
>
My key is in https://dist.apache.org/repos/dist/release/jackrabbit/KEYS <https://dist.apache.org/repos/dist/release/jackrabbit/KEYS> (https:// <https://downloads.apache.org/jackrabbit/KEYS>downloads.apache.org/jackrabbit/KEYS <http://downloads.apache.org/jackrabbit/KEYS>)
You have to trust those keys, because they are not (yet) signed by anyone else.
According to https://jackrabbit.apache.org/filevault/howto_release.html#Appendix_A:_Create_and_add_your_key_to_the_Jackrabbit_KEYS_file <https://jackrabbit.apache.org/filevault/howto_release.html#Appendix_A:_Create_and_add_your_key_to_the_Jackrabbit_KEYS_file> or https://jackrabbit.apache.org/jcr/creating-releases.html#Appendix_A:_Create_and_add_your_key_to_the_Jackrabbit_KEYS_file <https://jackrabbit.apache.org/jcr/creating-releases.html#Appendix_A:_Create_and_add_your_key_to_the_Jackrabbit_KEYS_file> this is enough.
I would suggest to mark all keys being listed in https://dist.apache.org/repos/dist/release/jackrabbit/KEYS <https://dist.apache.org/repos/dist/release/jackrabbit/KEYS> as trusted, as only with ASF credentials someone could upload them there.
I am still wondering why these issues never come up with the previous releases.....
Konrad
> Best regards, Julian
> <filevault-package-maven-plugin-1.1.4.log>
Re: [VOTE] Release Apache Jackrabbit FileVault 3.4.6 & Apache
Jackrabbit FileVault - Package Maven Plugin 1.1.4
Posted by Julian Reschke <ju...@gmx.de>.
Am 30.07.2020 um 19:35 schrieb Julian Reschke:
> ...
> That would fix the immediate issue (I assume), but is somehow risky
> because then it get's harder to understand what actually is checked.
>
> I get that in this case we have a combined vote for these two releases,
> and that they are only released in tandem or not at all.
>
> But what if one of these had a dependency on something that happens to
> be in the staging repo right now, but which is not part of the vote?
>
> It might be better if check-release actually installed the artefact
> locally. I already tried that by changing the MVN_ARGS in the script,
> but couldn't get that working.
>
> Best regards, Julian
So I did manually install 3.4.6 and then ran the check for the maven
plugin; log output attached.
Two problems:
1) Tests fail:
> [INFO] T E S T S
> [INFO] -------------------------------------------------------
> [INFO] Running org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.17 s <<< FAILURE! - in org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT
> [ERROR] org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT.multi_module_build_succeeds Time elapsed: 0.085 s <<< ERROR!
> org.apache.maven.it.VerificationException:
> Exit code was non-zero: 1; command line and log =
> bin\mvn -e --batch-mode -Dmaven.repo.local=C:\Users\jre\.m2\repository clean test
> Der Befehl "mvn" ist entweder falsch geschrieben oder
> konnte nicht gefunden werden.
>
> at org.apache.jackrabbit.filevault.maven.packaging.it.AnalyzeClassesMultiModuleIT.multi_module_build_succeeds(AnalyzeClassesMultiModuleIT.java:33)
>
but then also
2) there seems to be a problem with the checksum checks (only visible in
the log):
> [INFO]
> [INFO] 3. Verify checksums and signatures
> [INFO]
> [INFO] Verifying filevault-package-maven-plugin-1.1.4-source-release.zip...
> gpg: die unterzeichneten Daten sind wohl in './filevault-package-maven-plugin/1.1.4/filevault-package-maven-plugin-1.1.4-source-release.zip'
> gpg: Unterschrift vom Di, 28. Jul 2020 08:43:49 MEZ mittels RSA-Schlüssel ID 455ECC7C
> gpg: Korrekte Unterschrift von "Konrad Windszus <kw...@apache.org>"
> gpg: WARNUNG: Dieser Schlüssel trägt keine vertrauenswürdige Signatur!
> gpg: Es gibt keinen Hinweis, daß die Signatur wirklich dem vorgeblichen Besitzer gehört.
> Haupt-Fingerabdruck = B91A B7D2 121D C6B0 A61A A182 D774 2D58 455E CC7C
> [INFO] OK: filevault-package-maven-plugin-1.1.4-source-release.zip.asc
> openssl:Error: '' is an invalid command.
>
> Standard commands
> asn1parse ca ciphers cms
> crl crl2pkcs7 dgst dh
> dhparam dsa dsaparam ec
> ecparam enc engine errstr
> gendh gendsa genpkey genrsa
> nseq ocsp passwd pkcs12
> pkcs7 pkcs8 pkey pkeyparam
> pkeyutl prime rand req
> rsa rsautl s_client s_server
> s_time sess_id smime speed
> spkac srp ts verify
> version x509
>
> Message Digest commands (see the `dgst' command for more details)
> md2 md4 md5 mdc2
> rmd160 sha sha1
>
> Cipher commands (see the `enc' command for more details)
> aes-128-cbc aes-128-ecb aes-192-cbc aes-192-ecb
> aes-256-cbc aes-256-ecb base64 bf
> bf-cbc bf-cfb bf-ecb bf-ofb
> camellia-128-cbc camellia-128-ecb camellia-192-cbc camellia-192-ecb
> camellia-256-cbc camellia-256-ecb cast cast-cbc
> cast5-cbc cast5-cfb cast5-ecb cast5-ofb
> des des-cbc des-cfb des-ecb
> des-ede des-ede-cbc des-ede-cfb des-ede-ofb
> des-ede3 des-ede3-cbc des-ede3-cfb des-ede3-ofb
> des-ofb des3 desx idea
> idea-cbc idea-cfb idea-ecb idea-ofb
> rc2 rc2-40-cbc rc2-64-cbc rc2-cbc
> rc2-cfb rc2-ecb rc2-ofb rc4
> rc4-40 rc5 rc5-cbc rc5-cfb
> rc5-ecb rc5-ofb seed seed-cbc
> seed-cfb seed-ecb seed-ofb zlib
>
> [INFO] OK: filevault-package-maven-plugin-1.1.4-source-release.zip.sha512
Best regards, Julian
Re: [VOTE] Release Apache Jackrabbit FileVault 3.4.6 & Apache
Jackrabbit FileVault - Package Maven Plugin 1.1.4
Posted by Tobias Bocanegra <tr...@adobe.com>.
Hi,
I first tested FileVault, which succeeded w/o problems.
Then I tested the plugin, which failed because of the missing 3.4.6.
Then I run `mvn clean install` in the `target/jackrabbit-filevault-3.4.6/svn/jackrabbit-filevault-3.4.6` directory.
After that, the check release succeeded for the plugin as well.
Regards, Toby
> On 31 Jul 2020, at 02:35, Julian Reschke <ju...@gmx.de> wrote:
>
> Am 30.07.2020 um 18:36 schrieb Konrad Windszus:
>>
>>
>>> On 30. Jul 2020, at 16:35, Julian Reschke <julian.reschke@gmx.de
>>> <ma...@gmx.de>> wrote:
>>>
>>> So, when taking the vote instructions literally, I should veto
>>> the release...
>>
>> The vote instructions in my email do not say anything about failed
>> execution of check-release.sh, but vote however you want to.
>>
>> I already gave updated instructions that should hopefully fix the issue
>> (I haven't heard back from you whether that fixed the issue)
>> If you still veto the release due to that that is up to you.
>
> I didn't veto it, I just did not vote *for* it because I didn't have
> time to workaround the issue (yet).
>
> Toby: as you voted +1 already, how did *you* verify the second release?
> Did you have 3.4.6 installed localled?
>
> IIUC, I would have to git clone vault at 3.4.6, and run "mvn install",
> and then would be able to run the check for the plugin?
>
>> But we should probably all think about what would be a good reason to
>> veto a release.
>> Missed instructions on how to check the release are IMHO not a very
>> convincing reasons....
>>
>> Back to the topic: I would recommend to adjust the check-release.sh that
>> also the staging repo is transparently added as new remote repo for the
>> Maven execution.
>> WDYT?
>>
>> Konrad
>
> That would fix the immediate issue (I assume), but is somehow risky
> because then it get's harder to understand what actually is checked.
>
> I get that in this case we have a combined vote for these two releases,
> and that they are only released in tandem or not at all.
>
> But what if one of these had a dependency on something that happens to
> be in the staging repo right now, but which is not part of the vote?
>
> It might be better if check-release actually installed the artefact
> locally. I already tried that by changing the MVN_ARGS in the script,
> but couldn't get that working.
>
> Best regards, Julian
Re: [VOTE] Release Apache Jackrabbit FileVault 3.4.6 & Apache
Jackrabbit FileVault - Package Maven Plugin 1.1.4
Posted by Julian Reschke <ju...@gmx.de>.
Am 30.07.2020 um 18:36 schrieb Konrad Windszus:
>
>
>> On 30. Jul 2020, at 16:35, Julian Reschke <julian.reschke@gmx.de
>> <ma...@gmx.de>> wrote:
>>
>> So, when taking the vote instructions literally, I should veto
>> the release...
>
> The vote instructions in my email do not say anything about failed
> execution of check-release.sh, but vote however you want to.
>
> I already gave updated instructions that should hopefully fix the issue
> (I haven't heard back from you whether that fixed the issue)
> If you still veto the release due to that that is up to you.
I didn't veto it, I just did not vote *for* it because I didn't have
time to workaround the issue (yet).
Toby: as you voted +1 already, how did *you* verify the second release?
Did you have 3.4.6 installed localled?
IIUC, I would have to git clone vault at 3.4.6, and run "mvn install",
and then would be able to run the check for the plugin?
> But we should probably all think about what would be a good reason to
> veto a release.
> Missed instructions on how to check the release are IMHO not a very
> convincing reasons....
>
> Back to the topic: I would recommend to adjust the check-release.sh that
> also the staging repo is transparently added as new remote repo for the
> Maven execution.
> WDYT?
>
> Konrad
That would fix the immediate issue (I assume), but is somehow risky
because then it get's harder to understand what actually is checked.
I get that in this case we have a combined vote for these two releases,
and that they are only released in tandem or not at all.
But what if one of these had a dependency on something that happens to
be in the staging repo right now, but which is not part of the vote?
It might be better if check-release actually installed the artefact
locally. I already tried that by changing the MVN_ARGS in the script,
but couldn't get that working.
Best regards, Julian
Re: [VOTE] Release Apache Jackrabbit FileVault 3.4.6 & Apache
Jackrabbit FileVault - Package Maven Plugin 1.1.4
Posted by Konrad Windszus <ko...@gmx.de>.
> On 30. Jul 2020, at 16:35, Julian Reschke <ju...@gmx.de> wrote:
>
> So, when taking the vote instructions literally, I should veto
> the release...
The vote instructions in my email do not say anything about failed execution of check-release.sh, but vote however you want to.
I already gave updated instructions that should hopefully fix the issue (I haven't heard back from you whether that fixed the issue)
If you still veto the release due to that that is up to you.
But we should probably all think about what would be a good reason to veto a release.
Missed instructions on how to check the release are IMHO not a very convincing reasons....
Back to the topic: I would recommend to adjust the check-release.sh that also the staging repo is transparently added as new remote repo for the Maven execution.
WDYT?
Konrad
Re: [VOTE] Release Apache Jackrabbit FileVault 3.4.6 & Apache
Jackrabbit FileVault - Package Maven Plugin 1.1.4
Posted by Julian Reschke <ju...@gmx.de>.
Am 30.07.2020 um 15:48 schrieb Konrad Windszus:
> There is only one vote for both.
> If that fails none of the two will be released.
> This approach was followed for all FileVault releases done by me up till now I am wondering why this never came up for the previous releases.
>
> Having two different votes is much more effort, and I don't see a reason for that additional effort.
>
> WDYT?
> Konrad
Ok, understood, so there is one vote only.
But then, we need people to actually test the releases, and we need the
instructions to be accurate.
I followed the instructions, and the second run of check-release fails
for me. So, when taking the vote instructions literally, I should veto
the release...
Best regards, Julian
Re: [VOTE] Release Apache Jackrabbit FileVault 3.4.6 & Apache
Jackrabbit FileVault - Package Maven Plugin 1.1.4
Posted by Konrad Windszus <ko...@gmx.de>.
There is only one vote for both.
If that fails none of the two will be released.
This approach was followed for all FileVault releases done by me up till now I am wondering why this never came up for the previous releases.
Having two different votes is much more effort, and I don't see a reason for that additional effort.
WDYT?
Konrad
> On 30. Jul 2020, at 15:45, Julian Reschke <ju...@gmx.de> wrote:
>
> Am 30.07.2020 um 13:20 schrieb Konrad Windszus:
>> Hi Julian,
>> can you give a bit more context?
>> I released both 3.4.6 and the Maven plugin 1.1.4 together because the latter depends on the former.
>> So you have to first build and install 3.4.6 and then the Maven plugin.
>
> Is check-release supposed to do that install?
>
> I don't think so, so you would need to adjust the check instructions.
>
> And even if this works, coupling the two releases is IMHI problematic...
> What would happen if the first vote fails, and the second passes?
>
> Best regards, Julian
Re: [VOTE] Release Apache Jackrabbit FileVault 3.4.6 & Apache
Jackrabbit FileVault - Package Maven Plugin 1.1.4
Posted by Julian Reschke <ju...@gmx.de>.
Am 30.07.2020 um 13:20 schrieb Konrad Windszus:
> Hi Julian,
> can you give a bit more context?
> I released both 3.4.6 and the Maven plugin 1.1.4 together because the latter depends on the former.
> So you have to first build and install 3.4.6 and then the Maven plugin.
Is check-release supposed to do that install?
I don't think so, so you would need to adjust the check instructions.
And even if this works, coupling the two releases is IMHI problematic...
What would happen if the first vote fails, and the second passes?
Best regards, Julian
Re: [VOTE] Release Apache Jackrabbit FileVault 3.4.6 & Apache
Jackrabbit FileVault - Package Maven Plugin 1.1.4
Posted by Konrad Windszus <ko...@gmx.de>.
Hi Julian,
can you give a bit more context?
I released both 3.4.6 and the Maven plugin 1.1.4 together because the latter depends on the former.
So you have to first build and install 3.4.6 and then the Maven plugin.
Hope this helps,
Konrad
> On 30. Jul 2020, at 12:51, Julian Reschke <ju...@gmx.de> wrote:
>
> Am 28.07.2020 um 11:48 schrieb Konrad Windszus:
>> ...
>
> The check for the filevault plugin fails here:
>
>> [INFO] Scanning for projects...
>> Downloading from central: https://repo.maven.apache.org/maven2/org/apache/jackrabbit/vault/parent/3.4.6/parent-3.4.6.pom
>> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
>> [FATAL] Non-resolvable parent POM for org.apache.jackrabbit:filevault-package-maven-plugin:1.1.4: Could not find artifact org.apache.jackrabbit.vault:parent:pom:3.4.6 in central (https://repo.maven.apache.org/maven2) and 'parent.relativePath' points at no local POM @ line 23, column 13
>
> How is this supposed to work when 3.4.6 is not released yet?
>
> Best regards, Julian
Re: [VOTE] Release Apache Jackrabbit FileVault 3.4.6 & Apache
Jackrabbit FileVault - Package Maven Plugin 1.1.4
Posted by Julian Reschke <ju...@gmx.de>.
Am 28.07.2020 um 11:48 schrieb Konrad Windszus:
> ...
The check for the filevault plugin fails here:
> [INFO] Scanning for projects...
> Downloading from central: https://repo.maven.apache.org/maven2/org/apache/jackrabbit/vault/parent/3.4.6/parent-3.4.6.pom
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-resolvable parent POM for org.apache.jackrabbit:filevault-package-maven-plugin:1.1.4: Could not find artifact org.apache.jackrabbit.vault:parent:pom:3.4.6 in central (https://repo.maven.apache.org/maven2) and 'parent.relativePath' points at no local POM @ line 23, column 13
How is this supposed to work when 3.4.6 is not released yet?
Best regards, Julian
Re: [VOTE] Release Apache Jackrabbit FileVault 3.4.6 & Apache
Jackrabbit FileVault - Package Maven Plugin 1.1.4
Posted by Konrad Windszus <ko...@gmx.de>.
+1
Konrad
> On 28. Jul 2020, at 11:48, Konrad Windszus <ko...@gmx.de> wrote:
>
> Hi,
>
> A candidate for the Jackrabbit FileVault 3.4.6 release is available at:
> https://dist.apache.org/repos/dist/dev/jackrabbit/filevault/3.4.6/ <https://dist.apache.org/repos/dist/dev/jackrabbit/filevault/3.4.6/>
>
> The release candidate is a zip archive of the sources in:
> https://github.com/apache/jackrabbit-filevault/tree/jackrabbit-filevault-3.4.6 <https://github.com/apache/jackrabbit-filevault/tree/jackrabbit-filevault-3.4.6>
>
> The SHA1 checksum of the archive is ed203dca0f3e6b13aee753fbddd83fea14eef092
> The SHA-512 checksum of the archive is 6174d50596de206fef8dea09d0e03316cf6054096165758c33c0ade9b9d5e4a38a4b54abdddc2b0ed7f8e666ae6c4a8f9a8d2a883bb02f0a56bfad04e0b0e432
>
> The command for running automated checks against this release candidate is:
> $ sh check-release.sh filevault 3.4.6 ed203dca0f3e6b13aee753fbddd83fea14eef092
>
>
> A candidate for the Jackrabbit FileVault Package Maven Plugin 1.1.4 release is available at:
> https://dist.apache.org/repos/dist/dev/jackrabbit/filevault-package-maven-plugin/1.1.4/ <https://dist.apache.org/repos/dist/dev/jackrabbit/filevault-package-maven-plugin/1.1.4/>
>
> The release candidate is a zip archive of the sources in:
> https://svn.apache.org/repos/asf/jackrabbit/commons/filevault-package-maven-plugin/tags/filevault-package-maven-plugin-1.1.4/ <https://svn.apache.org/repos/asf/jackrabbit/commons/filevault-package-maven-plugin/tags/filevault-package-maven-plugin-1.1.4/>
>
> The SHA1 checksum of the archive is 007b00f60356bdf796beaf3ace1f239f9698f0ed
> The SHA-512 checksum of the archive is 53e4ff0f0eac482d5007a3037a0d13fe557cae278f884749b14946b1133c488617b8e4daccb13f43fbaec4d3a290a9f1f9e216ace1d1fd19c0e112c33d95a911
>
> The command for running automated checks against this release candidate is:
> $ sh check-release.sh filevault-plugin 1.1.4 007b00f60356bdf796beaf3ace1f239f9698f0ed
>
>
> A staged Maven repository containing both release candidates is available for review at:
> https://repository.apache.org/content/repositories/orgapachejackrabbit-1520 <https://repository.apache.org/content/repositories/orgapachejackrabbit-1520>
>
> The release notes can be found at
> https://issues.apache.org/jira/projects/JCRVLT/versions/12347797 <https://issues.apache.org/jira/projects/JCRVLT/versions/12347797> and
> https://issues.apache.org/jira/projects/JCRVLT/versions/12347848 <https://issues.apache.org/jira/projects/JCRVLT/versions/12347848>
>
> Please vote on releasing these packages as Apache Jackrabbit FileVault 3.4.6 and Apache Jackrabbit FileVault Package Maven Plugin 1.1.4
>
> 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
> [ ] -1 Do not release these packages because...
>
> Thanks,
> Konrad
>
> P.S, Due to the Git migration the check script at has been updated: https://dist.apache.org/repos/dist/dev/jackrabbit/check-release.sh <https://dist.apache.org/repos/dist/dev/jackrabbit/check-release.sh>
Re: [VOTE] Release Apache Jackrabbit FileVault 3.4.6 & Apache
Jackrabbit FileVault - Package Maven Plugin 1.1.4
Posted by Robert Munteanu <ro...@apache.org>.
Thanks, Konrad. I replied on that thread.
Robert
On Mon, 2020-08-03 at 12:04 +0200, Konrad Windszus wrote:
> Hi Robert,
>
> Regarding:
> Note that, just like Toby, I had to manually install filevault 3.4.6
> to
> make the plug-in build pass. It would be great to have this work out-
> of-the-box.
>
> Please check
> https://lists.apache.org/thread.html/r1bc7a7cda0dc76d504fb85fe05864c987ecdf7465c1fcfb92553640f%40%3Cdev.jackrabbit.apache.org%3E
> <
> https://lists.apache.org/thread.html/r1bc7a7cda0dc76d504fb85fe05864c987ecdf7465c1fcfb92553640f@%3Cdev.jackrabbit.apache.org%3E
> >
>
> Thanks,
> Konrad
>
> > On 3. Aug 2020, at 11:55, Robert Munteanu <ro...@apache.org>
> > wrote:
> >
> > On Tue, 2020-07-28 at 11:48 +0200, Konrad Windszus wrote:
> > > Please vote on releasing these packages as Apache Jackrabbit
> > > FileVault 3.4.6 and Apache Jackrabbit FileVault Package Maven
> > > Plugin
> > > 1.1.4
> >
> > +1
> >
> > [INFO] ------------------------------------------------------------
> > ------------
> > [INFO] Apache Maven 3.6.3 (SUSE 3.6.3-2.4)
> > [INFO] OS name: "linux", version: "5.7.9-1-default", arch: "amd64",
> > family: "unix"
> > [INFO] Java version: 11.0.8, vendor: N/A, runtime:
> > /usr/lib64/jvm/java-11-openjdk-11
> > [INFO] MAVEN_OPTS:
> > [INFO] ------------------------------------------------------------
> > ------------
> > [INFO] ALL CHECKS
> > OK
> > [INFO] ------------------------------------------------------------
> > ------------
> >
> > Note that, just like Toby, I had to manually install filevault
> > 3.4.6 to
> > make the plug-in build pass. It would be great to have this work
> > out-
> > of-the-box.
> >
> > Thanks,
> > Robert
> >
Re: [VOTE] Release Apache Jackrabbit FileVault 3.4.6 & Apache
Jackrabbit FileVault - Package Maven Plugin 1.1.4
Posted by Konrad Windszus <ko...@gmx.de>.
Hi Robert,
Regarding:
Note that, just like Toby, I had to manually install filevault 3.4.6 to
make the plug-in build pass. It would be great to have this work out-
of-the-box.
Please check https://lists.apache.org/thread.html/r1bc7a7cda0dc76d504fb85fe05864c987ecdf7465c1fcfb92553640f%40%3Cdev.jackrabbit.apache.org%3E <https://lists.apache.org/thread.html/r1bc7a7cda0dc76d504fb85fe05864c987ecdf7465c1fcfb92553640f@%3Cdev.jackrabbit.apache.org%3E>
Thanks,
Konrad
> On 3. Aug 2020, at 11:55, Robert Munteanu <ro...@apache.org> wrote:
>
> On Tue, 2020-07-28 at 11:48 +0200, Konrad Windszus wrote:
>> Please vote on releasing these packages as Apache Jackrabbit
>> FileVault 3.4.6 and Apache Jackrabbit FileVault Package Maven Plugin
>> 1.1.4
>
> +1
>
> [INFO] ------------------------------------------------------------------------
> [INFO] Apache Maven 3.6.3 (SUSE 3.6.3-2.4)
> [INFO] OS name: "linux", version: "5.7.9-1-default", arch: "amd64", family: "unix"
> [INFO] Java version: 11.0.8, vendor: N/A, runtime: /usr/lib64/jvm/java-11-openjdk-11
> [INFO] MAVEN_OPTS:
> [INFO] ------------------------------------------------------------------------
> [INFO] ALL CHECKS OK
> [INFO] ------------------------------------------------------------------------
>
> Note that, just like Toby, I had to manually install filevault 3.4.6 to
> make the plug-in build pass. It would be great to have this work out-
> of-the-box.
>
> Thanks,
> Robert
>
Re: [VOTE] Release Apache Jackrabbit FileVault 3.4.6 & Apache
Jackrabbit FileVault - Package Maven Plugin 1.1.4
Posted by Robert Munteanu <ro...@apache.org>.
On Tue, 2020-07-28 at 11:48 +0200, Konrad Windszus wrote:
> Please vote on releasing these packages as Apache Jackrabbit
> FileVault 3.4.6 and Apache Jackrabbit FileVault Package Maven Plugin
> 1.1.4
+1
[INFO] ------------------------------------------------------------------------
[INFO] Apache Maven 3.6.3 (SUSE 3.6.3-2.4)
[INFO] OS name: "linux", version: "5.7.9-1-default", arch: "amd64", family: "unix"
[INFO] Java version: 11.0.8, vendor: N/A, runtime: /usr/lib64/jvm/java-11-openjdk-11
[INFO] MAVEN_OPTS:
[INFO] ------------------------------------------------------------------------
[INFO] ALL CHECKS OK
[INFO] ------------------------------------------------------------------------
Note that, just like Toby, I had to manually install filevault 3.4.6 to
make the plug-in build pass. It would be great to have this work out-
of-the-box.
Thanks,
Robert
Re: [VOTE] Release Apache Jackrabbit FileVault 3.4.6 & Apache
Jackrabbit FileVault - Package Maven Plugin 1.1.4
Posted by Konrad Windszus <ko...@gmx.de>.
We need one more vote.
Anyone?
> On 28. Jul 2020, at 11:48, Konrad Windszus <ko...@gmx.de> wrote:
>
> Hi,
>
> A candidate for the Jackrabbit FileVault 3.4.6 release is available at:
> https://dist.apache.org/repos/dist/dev/jackrabbit/filevault/3.4.6/ <https://dist.apache.org/repos/dist/dev/jackrabbit/filevault/3.4.6/>
>
> The release candidate is a zip archive of the sources in:
> https://github.com/apache/jackrabbit-filevault/tree/jackrabbit-filevault-3.4.6 <https://github.com/apache/jackrabbit-filevault/tree/jackrabbit-filevault-3.4.6>
>
> The SHA1 checksum of the archive is ed203dca0f3e6b13aee753fbddd83fea14eef092
> The SHA-512 checksum of the archive is 6174d50596de206fef8dea09d0e03316cf6054096165758c33c0ade9b9d5e4a38a4b54abdddc2b0ed7f8e666ae6c4a8f9a8d2a883bb02f0a56bfad04e0b0e432
>
> The command for running automated checks against this release candidate is:
> $ sh check-release.sh filevault 3.4.6 ed203dca0f3e6b13aee753fbddd83fea14eef092
>
>
> A candidate for the Jackrabbit FileVault Package Maven Plugin 1.1.4 release is available at:
> https://dist.apache.org/repos/dist/dev/jackrabbit/filevault-package-maven-plugin/1.1.4/ <https://dist.apache.org/repos/dist/dev/jackrabbit/filevault-package-maven-plugin/1.1.4/>
>
> The release candidate is a zip archive of the sources in:
> https://svn.apache.org/repos/asf/jackrabbit/commons/filevault-package-maven-plugin/tags/filevault-package-maven-plugin-1.1.4/ <https://svn.apache.org/repos/asf/jackrabbit/commons/filevault-package-maven-plugin/tags/filevault-package-maven-plugin-1.1.4/>
>
> The SHA1 checksum of the archive is 007b00f60356bdf796beaf3ace1f239f9698f0ed
> The SHA-512 checksum of the archive is 53e4ff0f0eac482d5007a3037a0d13fe557cae278f884749b14946b1133c488617b8e4daccb13f43fbaec4d3a290a9f1f9e216ace1d1fd19c0e112c33d95a911
>
> The command for running automated checks against this release candidate is:
> $ sh check-release.sh filevault-plugin 1.1.4 007b00f60356bdf796beaf3ace1f239f9698f0ed
>
>
> A staged Maven repository containing both release candidates is available for review at:
> https://repository.apache.org/content/repositories/orgapachejackrabbit-1520 <https://repository.apache.org/content/repositories/orgapachejackrabbit-1520>
>
> The release notes can be found at
> https://issues.apache.org/jira/projects/JCRVLT/versions/12347797 <https://issues.apache.org/jira/projects/JCRVLT/versions/12347797> and
> https://issues.apache.org/jira/projects/JCRVLT/versions/12347848 <https://issues.apache.org/jira/projects/JCRVLT/versions/12347848>
>
> Please vote on releasing these packages as Apache Jackrabbit FileVault 3.4.6 and Apache Jackrabbit FileVault Package Maven Plugin 1.1.4
>
> 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
> [ ] -1 Do not release these packages because...
>
> Thanks,
> Konrad
>
> P.S, Due to the Git migration the check script at has been updated: https://dist.apache.org/repos/dist/dev/jackrabbit/check-release.sh <https://dist.apache.org/repos/dist/dev/jackrabbit/check-release.sh>