> On 31. Jul 2020, at 07:46, Julian Reschke <[email protected]> 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 <[email protected] >>>> <mailto:[email protected]>> 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
