yes, the first issue is a svn-eu issue: I'll add a FAQ the second issue is more subtle: you got the solution, which is delete local svn checkout that needs a FAQ entry too
I'll do it tomorrow if nobody beats me at it notice you ran "mvn site-deploy", ie the phase, and scm-publish:publish-scm was bound to the phase in parent pom pro: more concise and classical cons: each time you run the command, the site gets generated (site phase) that's why I documented "mvn scm-publish:publish-scm" given your nice idea in install and deploy for multi-modules' installAtEnd, I think I should be able to integrate scm support in site:deploy this would simplify the commands and configuration but the site:deploy code will be more complex and for the moment, I didn't have time Regards, Hervé Le mardi 24 septembre 2013 21:56:46 Robert Scholte a écrit : > Hi, > > And again my site publication wasn't straight forward, but I think I'm > hitting a Europe-delay issue. > > After running 'mvn site-deploy -Preporting' for the first time, it ends > with a > [ERROR] Failed to check out from SCM: The svn command failed. svn: > E170000: URL > 'https://svn.apache.org/repos/infra/websites/production/maven/content/plugin > s-archives/maven-deploy-plugin-LATEST' doesn't exist > > A couple of seconds later I get the following notification: > Log: > Automatic svn path creation: > https://svn.apache.org/repos/infra/websites/production/maven/content/ plugin > s-archives/maven-deploy-plugin-LATEST > > This looks like the reason why waitBeforeTagging[1] was introduced for the > maven-release-plugin > > Since I'm not sure if scm-publish:publish-scm will work, I decided to run > 'mvn site-deploy -Preporting' again. > > After a lot of "svn add"'s I get the following message: > [ERROR] Failed to add new files to SCM: The svn command failed. svn: > E155007: 'E:\Users\Robert > Scholte\maven-sites\plugins-archives\maven-deploy-plugin-LATEST\apidocs' > is not a working copy > > By now I know that one solution is to start all over again: deleting > E:\Users\Robert Scholte\maven-sites\plugins-archives and run 'mvn > site-deploy -Preporting' for the third time. > > Now finally success. > > So I think we should add an optional delay to prevent the issue from my > first run. > I still don't understand what is the real issue with the second run. > > That's something about the process. > > The "Stage the Release"[2] chapter is missing a direct link to the page > explaining how to publish the site. > > Robert > > [1] > http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html > #waitBeforeTagging [2] > http://maven.apache.org/developers/release/maven-project-release-procedure.h > tml#Stage_the_Release > > > Op Sun, 22 Sep 2013 11:18:47 +0200 schreef Robert Scholte > > <[email protected]>: > > I will release the maven-deploy-plugin soon, so I can verify very well > > if that part is complete. > > > > Robert > > > > Op Sun, 22 Sep 2013 01:49:25 +0200 schreef Hervé BOUTEMY > > > > <[email protected]>: > >> I just published a documentation about CMS + svnpubsub for Maven, with > >> schema > >> for global overview of the differences and synchronization points > >> between Maven > >> site and components reference documentations [1] > >> > >> The documentation about Maven website is expected to be complete, but > >> components reference documentation still needs improvements for people > >> to > >> better understand how the configuration is done. It can even be subject > >> to > >> discussion, since not every component uses the same process for the > >> moment: > >> one of my intents by doing this documentation is to be able to discuss > >> with > >> Maven devs to define our target convention. But for the moment, it is > >> not > >> possible since I know a lot of people are lost in different cases (and > >> no, > >> there is no CMS when we publish component reference documentation). > >> > >> Please review and tell if anything is not clear > >> > >> Regards, > >> > >> Hervé > >> > >> [1] http://maven.apache.org/developers/website/deploy-maven-website.html > >> > >> --------------------------------------------------------------------- > >> 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] > > --------------------------------------------------------------------- > 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]
