So without release plugin, I could perform the release now. Using that plugin I now get this: mvn release:perform [INFO] Scanning for projects... [INFO] [INFO] ------------< org.codehaus.mojo:servicedocgen-maven-plugin >------------ [INFO] Building Maven Service Documentation Generator Plugin 1.0.0-beta-6-SNAPSHOT [INFO] ----------------------------[ maven-plugin ]---------------------------- [INFO] [INFO] --- maven-release-plugin:3.0.0-M1:perform (default-cli) @ servicedocgen-maven-plugin --- [INFO] phase verify-release-configuration [INFO] starting perform goal, composed of 3 phases: verify-completed-prepare-phases, checkout-project-from-scm, run-perform-goals [INFO] [perform] 1/3 verify-completed-prepare-phases [ERROR] No SCM URL was provided to perform the release from [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE
Seems I will have to redo from scratch once more. What really sucks is that that plugin automatically pushes all comits and tags even if the build failed so I am polluting the git with rubbish. Is there still some supporter left of release plugin here who might have some hints or rationale why it should be a good idea to actually use that plugin? Cheers Jörg joerg.h...@googlemail.com schrieb am Freitag, 28. Mai 2021 um 10:21:23 UTC+2: > gotcha: > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD SUCCESS > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 57.268 s > [INFO] Finished at: 2021-05-28T10:17:56+02:00 > [INFO] > ------------------------------------------------------------------------ > > Quite some difference. > A long time ago I suggested to provide settings for devonfw-ide ( > https://github.com/devonfw/ide) to avoid all such inconvenience, > pitfalls, etc. > It allows to automate setup of tools (java, maven, eclipse, etc.) for a > project in a sandbox in a fully automated manner. You can define versions > of java, maven, eclipse via some properties maintained in a git repo > alongside with the IDE settings like Eclipse formatter, etc. > Nobody at mojohaus was interested. Maybe a time to revisit. > > Cheers > Jörg > > joerg.h...@googlemail.com schrieb am Freitag, 28. Mai 2021 um 10:11:05 > UTC+2: > >> https://issues.apache.org/jira/browse/WAGON-568 >> >> joerg.h...@googlemail.com schrieb am Freitag, 28. Mai 2021 um 10:06:24 >> UTC+2: >> >>> Hi, >>> >>> from the logs and errors, I can clearly see that the hashes (sha1 and >>> md5) are not uploaded and therefore OSSRH is rejecting the release and >>> cannot close it successfully due to missing hashes. >>> This has nothing to do with GPG or my DSL provider. So IMHO the root >>> cause is that maven for some reason fails to upload these hashes: >>> [WARNING] Failed to upload checksum >>> org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha1: >>> >>> null >>> [WARNING] Failed to upload checksum >>> org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.md5: >>> >>> null >>> >>> BTW: fast.com shows me that I have 50 Mbps Download and 14 MBps Upload. >>> I am working all day with this DSL connection both private and professional >>> and do not see any such issues so IMHO a problem of availability of OSSRH >>> what is AFAIK already a known issue. >>> >>> So at least to make some progress, I will try to deploy the release to >>> OSSRH manually without using release plugin and see if that makes any >>> difference... >>> I am maintaining many other OSS projects outside mojohaus and do not >>> face such strange issues with deployment failing but outside mojohaus I >>> never use release plugin because IMHO it sucks. >>> >>> Cheers >>> Jörg >>> >>> Ben M. schrieb am Donnerstag, 27. Mai 2021 um 23:15:14 UTC+2: >>> >>>> OK, let's start with updating some gpg instructions: >>>> https://github.com/mojohaus/mojohaus.github.io/pull/38 >>>> >>>> Unless I do a release, I probably cannot help you any further. Sorry! >>>> :( >>>> BUT… I noticed slow upload/download speeds from Germany as well. In >>>> case you are a Deutsche Telekom customer as I am, just open a ticket. You >>>> will get a refund on each month this happens. According to press it is a >>>> peering problem on the part of Deutsche Telekom. >>>> >>>> Ben M. schrieb am Donnerstag, 27. Mai 2021 um 22:41:21 UTC+2: >>>> >>>>> Wow, the "how to release" page is extremely outdated. >>>>> >>>>> DSA keys… they are deprecated for years now and we are moving from RSA >>>>> to ECC now. >>>>> >>>>> About the run time… I did a dry run of release:prepare and found: >>>>> [INFO] [prepare dry-run] 17/17 end-release >>>>> [INFO] Release preparation simulation complete. >>>>> [INFO] >>>>> ------------------------------------------------------------------------ >>>>> [INFO] BUILD SUCCESS >>>>> [INFO] >>>>> ------------------------------------------------------------------------ >>>>> [INFO] Total time: 32.543 s >>>>> [INFO] Finished at: 2021-05-27T22:39:41+02:00 >>>>> [INFO] >>>>> ------------------------------------------------------------------------ >>>>> >>>>> I will ping some other committers and ask about what to do in your >>>>> case. >>>>> >>>>> joerg.h...@googlemail.com schrieb am Donnerstag, 27. Mai 2021 um >>>>> 21:50:04 UTC+2: >>>>> >>>>>> Hi Bean, >>>>>> >>>>>> thanks for your response and your suggestion. >>>>>> I updated parent to the latest release 61: >>>>>> >>>>>> https://github.com/mojohaus/servicedocgen-maven-plugin/commit/ca831c4821200ea162174533cf7293d433b03c53 >>>>>> >>>>>> After rerunning the release process I ended up with the exact same >>>>>> behaviour. >>>>>> >>>>>> BTW: >>>>>> [INFO] BUILD SUCCESS >>>>>> [INFO] >>>>>> ------------------------------------------------------------------------ >>>>>> [INFO] Total time: 01:25 h >>>>>> [INFO] Finished at: 2021-05-27T21:38:28+02:00 >>>>>> >>>>>> IMHO almost 1,5h is extraordinary slow for the release of a simple >>>>>> mojo. >>>>>> Something wrong with OSSRH nexus? >>>>>> >>>>>> It seems that release plugins hates me as I hat it. >>>>>> Is mojohaus still following the manifesto or have we changed to a >>>>>> collaboration of agile sub-projects where only the results count? >>>>>> So if nobody forces me to follow the official process and to use >>>>>> release-maven-plugin, I can do the release with "devon release" from >>>>>> devonfw-ide or I can also try to automate it via github actions. >>>>>> >>>>>> Kind regards >>>>>> Jörg >>>>>> Ben M. schrieb am Donnerstag, 27. Mai 2021 um 19:22:54 UTC+2: >>>>>> >>>>>>> Have you tried updating the parent pom? >>>>>>> I think you will need more recent versions of some plugins, >>>>>>> especially the deploy and gpg plugins. >>>>>>> >>>>>>> joerg.h...@googlemail.com schrieb am Donnerstag, 27. Mai 2021 um >>>>>>> 16:48:39 UTC+2: >>>>>>> >>>>>>>> Dear mojohaus experts, >>>>>>>> >>>>>>>> after a long while I want to build a release of one of my mojos. >>>>>>>> I tried to exactly follow the instructions: >>>>>>>> https://www.mojohaus.org/development/performing-a-release.html >>>>>>>> >>>>>>>> Whilst running mvn release:perform I saw log message like this: >>>>>>>> Uploading to ossrh-staging: >>>>>>>> http://oss.sonatype.org/service/local/staging/deploy/maven2/org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar >>>>>>>> [WARNING] Failed to upload checksum >>>>>>>> org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha1: >>>>>>>> >>>>>>>> null >>>>>>>> [WARNING] Failed to upload checksum >>>>>>>> org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.md5: >>>>>>>> >>>>>>>> null >>>>>>>> >>>>>>>> However, build gave me SUCCESS so I closed the repo in OSSRH. >>>>>>>> That now failed with this error: >>>>>>>> Requires one-of SHA-1: >>>>>>>> /org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha1, >>>>>>>> >>>>>>>> MD5: >>>>>>>> /org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.md5, >>>>>>>> >>>>>>>> SHA-256: >>>>>>>> /org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha256, >>>>>>>> >>>>>>>> SHA-512: >>>>>>>> /org/codehaus/mojo/servicedocgen-maven-plugin/1.0.0-beta-4/servicedocgen-maven-plugin-1.0.0-beta-4.jar.sha512 >>>>>>>> >>>>>>>> Can someone give me a hint what I might be doing wrong? >>>>>>>> >>>>>>>> Thanks & cheers >>>>>>>> Jörg >>>>>>>> >>>>>>> -- You received this message because you are subscribed to the Google Groups "mojohaus-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to mojohaus-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/f79dbfad-4909-4aba-ac0c-27ffe1888de1n%40googlegroups.com.
