Hi Jeffery, the yaafi-crypto pom seemed completely outdated, I cleaned it up, try again!
- the RC should be 1.0.8. - Could you double check the generated target/*.asc files ? (gpg --verify x.asc x shows correct signature). Best regards, Georg Von: Jeffery Painter <[email protected]> An: Turbine Developers List <[email protected]> Datum: 06.11.2018 20:12 Betreff: Re: Antwort: Re: turbine core 4.0.1 release schedule Hi Georg, Following the steps from: https://svn.apache.org/repos/asf/turbine/fulcrum/trunk/README.txt For yaafi-crypto and I get an error on the last step. Maybe you can help me figure out if I did something wrong. I ran the following commands: 1. mvn clean site install -Papache-release 2. mvn release:clean 3. mvn release:prepare -P apache-release 4. mvn release:perform on step 4, I get an error that basically says I am not authorized... any ideas? [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.583 s [INFO] [INFO] Finished at: 2018-11-06T14:07:54-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] [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging. [INFO] [ERROR] [INFO] [ERROR] For more information about the errors and possible solutions, please read the following articles: [INFO] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException - Jeff On 2/21/18 3:06 AM, Georg Kallidis wrote: > Hi Jeff, > > some "advice" .. currently the "cheatsheet" I use for a release is checked > in here: > https://svn.apache.org/repos/asf/turbine/fulcrum/trunk/README.txt - which > is also the Apache Fulcrum starting page on GitHub > https://github.com/apache/turbine-fulcrum (until we provide a readme.md). > The document should work for Windows and for *nix systems, with some > hints, if no GPG agent is running or not (Windows). Commands may run > without explicit gpg flags. > > For site publication in general check > https://svn.apache.org/repos/asf/turbine/fulcrum/trunk/security/README - > this should be moved elsewhere and > find more hints especially for Turbine site building (lower part with > references) here: > https://svn.apache.org/repos/asf/turbine/core/trunk/README.txt ( > https://github.com/apache/turbine-core). > > You may find there most of what is needed. > > - Georg > > > > Von: Jeffery Painter <[email protected]> > An: [email protected] > Datum: 16.02.2018 13:19 > Betreff: Re: turbine core 4.0.1 release schedule > > > > Hi Georg, > > I would like to learn more about the release process. I will do some > homework this weekend to see what is involved. I have never done it > before, so I may need some advice and guidance along the way. I think > the next big step would be Java 8 as you mention, and I would be up for > helping make that transition happen. > > -- > Jeff > > On 02/16/2018 03:40 AM, Georg Kallidis wrote: >> Hi Jeff, >> >> that´s great! We have to talk through this really .. >> >> Following is, what IMO taking place in the next two, three weeks, based > on >> what could be expected from current state: >> >> Thomas is in the process of preparing Intake, after this I would remove >> the two SNAPSHOTS (one of them already now resolved) in turbine core and >> prepare the release. Building the site may take some more time, but this >> could postponed or prepared all along. And yes, then we are able to >> release the archetype lastly! Do you want to volunteer for the release >> process? No other issues ASAIK! >> >> After this is done the race is opened for the Turbine (Java) 8 IMO! We >> might declare this just plain text - details following .. as reading our >> mailing list we agree on this matter. I have added some comments/hints > in >> pom dependencies, what might be done (+ release of Torque 4.1, which >> requires Java 8). More disrupting changes, which would mean e.g. an > entire >> new configuration building, are probably tasks requiring some more >> (combined) effort. I think Thomas already made some efforts to migrate > to >> velocity 2. But you might have some more insightful thoughts you would >> like to share! We should not forget about changing/adding more structure >> ton the repo (writeable GIT, another branch?). >> >> Best regards, Georg >> >> >> >> >> Von: Jeffery Painter <[email protected]> >> An: Turbine Developers List <[email protected]> >> Datum: 15.02.2018 17:39 >> Betreff: turbine core 4.0.1 release schedule >> >> >> >> >> Hello everyone, >> >> I am pretty deep into building out a detailed tutorial on getting >> started with Turbine 4.0 in Eclipse using the Maven archetype (I am >> quite sure it is a book now instead of a simple tutorial). I was >> wondering when we can expect final releases of Turbine core and the new >> turbine-webapp archetype? >> >> Once Thomas releases intake 1.2.3, is there anything else preventing >> releasing turbine 4.0.1 and subsequently turbine-webapp-4.0 version > 1.0.2? >> Let me know if there is anything I can do to help :-) I am working from >> snapshots at the moment, and it isn't reasonable for me to enlist others >> to test out my walk through until these are released. I would also love >> to share it with you guys for feedback if/when you have time. >> >> Thanks, >> Jeff >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > [Anhang "signature.asc" gelöscht von Georg Kallidis/CeDiS/FU-Berlin/DE]
smime.p7s
Description: S/MIME Cryptographic Signature
