Hi Jeffery, .. stepping through your release you successfully got the tagged version into svn repo
https://svn.apache.org/repos/asf/turbine/fulcrum/tags/fulcrum-yaafi-crypto-1.0.7 . Check this again: https://www.apache.org/dev/release-signing.html#keys-policy - The release process may not find your public key .. it has to be here, but it isn't: https://dist.apache.org/repos/dist/release/turbine/KEYS. This is required, so that is missing. - I found your key on pgpkeys.mit.edu, that is OK (more info here: https://httpd.apache.org/dev/verification.html) - But check id.apache.org, that you saved your key fingerprint there also. Hope this helps! RC is 1.0.7, that is correct, my fault! Best regards, Georg Von: Jeffery Painter <[email protected]> An: [email protected] Datum: 07.11.2018 17:50 Betreff: Re: Fulcrum javadoc updates Hi Georg, I got to the same point in the release steps, and I am getting the same error message that I am not authorized to deploy the artifacts... is there something I need to do to gain access? FYI - I can log in to Nexus using my Apache credentials, but it currently shows that I have no staging repositories. Responding to your prior notes inline. >> gk: - the RC should be 1.0.8. The last release was 1.0.6, this would be 1.0.7 and after release it should then be 1.0.8-SNAPSHOT right? See: http://turbine.apache.org/fulcrum/fulcrum-yaafi-crypto/downloads.html >> gk: - Could you double check the generated target/*.asc files ? (gpg --verify >> x.asc x shows correct signature). FYI: My key was signed by Jean-Frederic, Christopher Schultz (from tomcat group) and a few others at ApacheCon. It is uploaded to the public key servers and included in Jean's webring. See - https://pgp.mit.edu/pks/lookup?op=vindex&search=0x207EE518D34FA936 painter@merlin:~/workspace-turbine/fulcrum/yaafi-crypto/target$ gpg --verify fulcrum-yaafi-crypto-1.0.7-javadoc.jar.asc gpg: assuming signed data in 'fulcrum-yaafi-crypto-1.0.7-javadoc.jar' gpg: Signature made Wed 07 Nov 2018 11:35:33 AM EST gpg: using RSA key F325EA8120E1E588FC5EC9A9207EE518D34FA936 gpg: Good signature from "Jeffery Painter <[email protected]>" [ultimate] gpg: aka "Jeffery Painter (CODE SIGNING KEY) <[email protected]>" [ultimate] Then repeat the steps 1..3 (all goes ok until step 4): $ mvn release:perform . . . [INFO] [INFO] Uploading to apache.releases.https: https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/fulcrum/fulcrum-yaafi-crypto/1.0.7/fulcrum-yaafi-crypto-1.0.7.pom [INFO] Progress (1): 2.0/3.5 kB [INFO] Progress (1): 3.5 kB [INFO] [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] BUILD FAILURE [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] Total time: 9.129 s [INFO] [INFO] Finished at: 2018-11-07T11:37:08-05:00 [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project fulcrum-yaafi-crypto: Failed to deploy artifacts: Could not transfer artifact org.apache.fulcrum:fulcrum-yaafi-crypto:jar:1.0.7 from/to apache.releases.https (https://repository.apache.org/service/local/staging/deploy/maven2): Failed to transfer file: https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/fulcrum/fulcrum-yaafi-crypto/1.0.7/fulcrum-yaafi-crypto-1.0.7.jar . Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1] [INFO] [ERROR] Thanks! Jeffery On 11/7/18 11:17 AM, Jeffery Painter wrote: > Hi Georg, > > I tried moving testcontainer and factory to Junit5 - not too hard, but > it will cause a cascade of changes that I think requires updating all > related packages to Junit5 at the same time.... seems like a big effort > and I don't have the time to invest on that right now :-( As soon as I > updated testcontainer, yaafi started complaining, etc. > > I took your lead on updates for yaafi-crypto pom changes and made them > across all fulcrum modules. I also simplified a small bit of code in > the yaafi-crypto hex conversion lib. > > I will try to package for release again and see how it goes! > > - > Jeffery > > > > On 11/7/18 6:02 AM, Georg Kallidis wrote: >> Hi Jeffery, >> >> thanks a lot for your efforts! I do my best to allow for enabling next >> steps -I may be able to check middle of next week for the latest. >> >> Where to begin? Factory and Testcontainer? >> >> - I considered to allow for Junit5 (+ Junit 4) in Fulcrum testcontainer >> release, may be we want this included or not? I think yes. >> - minor version for Fulcrum Factory (code could be done more in Java 8 >> syntax), check src/changes/changes.xml >> >> - Fulcrum Yaafi: Thomas mentioning "avalon" - yes it is "as it is", kind >> of stable, but the code is in attic (excalibur). Thomas may come up with >> some more helpful hints7suggestions (Spring?). Keeping this as it is for >> now.. >> >> - For the atticable Fulcrums, we may move them to a dormant folder (like >> commons) after a vote (list of candidates).. >> >> Best regards, Georg >> >> >> >> Von: Jeffery Painter <[email protected]> >> An: [email protected] >> Datum: 06.11.2018 19:19 >> Betreff: Re: Fulcrum javadoc updates >> >> >> >> Hello all, >> >> I think I have mostly finished making the fulcrum javadoc updates :-) >> >> "mvn clean site" works for all of the following now: >> >> fulcrum-commonsemail (attic?) >> fulcrum-configuration/impl (attic?) >> fulcrum-crypto >> fulcrum-factory >> fulcrum-hsqldb (attic?) >> fulcrum-intake >> fulcrum-jetty >> fulcrum-json (and all sub components) >> fulcrum-localization >> fulcrum-mimetype >> fulcrum-parser >> fulcrum-pbe (attic?) >> fulcrum-pool >> fulcrum-quartz >> fulcrum-naming (attic?) >> fulcrum-resourcemanager (attic?) >> fulcrum-script (attic?) >> fulcrum-security/api >> fulcrum-security/dist >> fulcrum-security/hibernate >> fulcrum-security/memory >> fulcrum-servicemanager >> fulcrum-spring (attic?) >> fulcrum-testcontainer >> fulcrum-upload >> fulcrum-xmlrpc (attic?) >> fulcrum-xslt (attic?) >> fulcrum-yaafi >> fulcrum-yaafi-crypto >> >> Needs some help: >> >> fulcrum-security/torque >> >> The generated Torque.OM classes are the only ones left with offending >> JavaDoc entries, I cleaned up the rest. I can run mvn javadoc:javadoc >> and it plays nicely with the exclusions I put into the pom.xml, however >> they are ignored when running full "mvn clean site". I haven't spent >> any more time investigating this. >> >> Does not complete or maybe move to attic... >> fulcrum-bsf (attic? no tests, site build does not work) >> >> Georg - whenever you are ready, I think we can start putting most of >> these up for release and voting. Let me know how I can help :-) >> >> >> Thanks! >> Jeff >> >> >> >> On 11/5/18 12:51 PM, Jeffery Painter wrote: >>> Progress update: >>> >>> "mvn clean package site" builds OK now for the following: >>> >>> fulcrum-crypto >>> fulcrum-factory >>> fulcrum-intake >>> fulcrum-json (and all sub components) >>> fulcrum-localization >>> fulcrum-mimetype >>> fulcrum-parser >>> fulcrum-pbe >>> fulcrum-pool >>> fulcrum-quartz >>> fulcrum-servicemanager >>> fulcrum-testcontainer >>> fulcrum-yaafi >>> fulcrum-yaafi-crypto >>> >>> >>> I still have to tackle fulcrum-security (lots of problems there) and >>> fulcrum-upload. Haven't looked beyond that yet. >>> >>> -- >>> Jeff >>> >>> >> [Anhang "signature.asc" gelöscht von Georg Kallidis/CeDiS/FU-Berlin/DE] >> > [Anhang "signature.asc" gelöscht von Georg Kallidis/CeDiS/FU-Berlin/DE]
smime.p7s
Description: S/MIME Cryptographic Signature
