the idea with component documentation publication with LATEST then svn cp is at http://maven.apache.org/developers/website/deploy-component-reference-documentation.html
it's the other side of maven.apache.org publication Regards, Hervé Le mardi 3 décembre 2013 20:22:42 Robert Scholte a écrit : > The usage of the version was the initial idea when switching to > svnpubsub[1]. > However, the commit of a new site can take a lot of time, depending on the > size of the project ( I've seen 1h+ ). > By using -LATEST, it'll only take a lot of time during the first > publication. Every next release will be an update. > I've already updated the description for the deployments of maven-plugin > sites, I'll fix this one as well. > > Robert > > [1] http://maven.apache.org/developers/website/deploy-maven-website.html > > Op Tue, 03 Dec 2013 15:32:49 +0100 schreef Igor Fedorenko > > <[email protected]>: > > ... and another question. > > > > Verifier pom forces shared-archives/maven-verifier-LATEST documentation > > site path [1], so I had to explicitly override that from command line to > > get the site staged at shared-archives/maven-verifier-1.5 as required by > > release documentation [2]. Are we expected to specify manually site > > location manually during release or the pom and/or documentation need to > > be updated? > > > > > > [1] > > http://svn.apache.org/viewvc/maven/shared/trunk/maven-verifier/pom.xml?ann > > otate=1547285 [2] > > http://maven.apache.org/developers/release/maven-shared-release.html > > > > -- > > Regards, > > Igor > > > > On 12/3/2013, 0:18, Igor Fedorenko wrote: > >> Thank you, Olivier, it'd have taken me forever to figure this out by > >> myself! > >> > >> (I had troubles with svn authentication earlier today and accidentally > >> committed modified pom.xml while I was troubleshooting it). > >> > >> -- > >> Regards, > >> Igor > >> > >> On 12/2/2013, 23:31, Olivier Lamy wrote: > >>> It looks the pom contains the wrong scm information: > >>> https://svn.apache.org/repos/asf/maven/shared/trunk/maven-verifier/pom.x > >>> ml > >>> > >>> <scm> > >>> > >>> <connection>scm:svn:http://svn.apache.org/repos/asf/maven/shared/tags/ma > >>> ven-verifier-1.5</connection> > >>> > >>> > >>> <developerConnection>scm:svn:https://svn.apache.org/repos/asf/maven/shar > >>> ed/tags/maven-verifier-1.5</developerConnection> > >>> > >>> > >>> <url>http://svn.apache.org/viewvc/maven/shared/tags/maven-verifier-1.5</ > >>> url>>>> > >>> </scm> > >>> > >>> must be trunk. > >>> > >>> log says: > >>> /bin/sh -c cd /code/maven-verifier && svn --non-interactive copy > >>> --file > >>> /var/folders/9n/d3xsnbqx0y9cfz4n9spt1vym0000gn/T/maven-scm-1817316767.co > >>> mmit > >>> > >>> --revision 1547210 > >>> https://svn.apache.org/repos/asf/maven/shared/tags/maven-verifier-1.5 > >>> https://svn.apache.org/repos/asf/maven/shared/tags/maven-verifier-1.5 > >>> > >>> the first path doesn't exist as it's read from the pom. > >>> > >>> On 3 December 2013 14:48, Igor Fedorenko <[email protected]> wrote: > >>>> I am trying to stage maven-verifier 1.5 but having some troubles > >>>> creating the release tag during "release:prepare". The error message I > >>>> get shows some odd SVN URL, but I am not sure where it comes from. > >>>> Here > >>>> is the error > >>>> > >>>> [INFO] Checking in modified POMs... > >>>> [INFO] Executing: /bin/sh -c cd /code/maven-verifier && svn > >>>> --non-interactive commit --file > >>>> /var/folders/9n/d3xsnbqx0y9cfz4n9spt1vym0000gn/T/maven-scm-2080488481.c > >>>> ommit > >>>> > >>>> --targets > >>>> /var/folders/9n/d3xsnbqx0y9cfz4n9spt1vym0000gn/T/maven-scm-654334978372 > >>>> 7626565-targets > >>>> > >>>> [INFO] Working directory: /code/maven-verifier > >>>> [INFO] Tagging release with the label maven-verifier-1.5... > >>>> [INFO] Executing: /bin/sh -c cd /code/maven-verifier && svn > >>>> --non-interactive copy --file > >>>> /var/folders/9n/d3xsnbqx0y9cfz4n9spt1vym0000gn/T/maven-scm-1817316767.c > >>>> ommit > >>>> > >>>> --revision 1547210 > >>>> https://svn.apache.org/repos/asf/maven/shared/tags/maven-verifier-1.5 > >>>> https://svn.apache.org/repos/asf/maven/shared/tags/maven-verifier-1.5 > >>>> [INFO] Working directory: /code/maven-verifier > >>>> [INFO] > >>>> ----------------------------------------------------------------------- > >>>> - > >>>> [INFO] BUILD FAILURE > >>>> [INFO] > >>>> ----------------------------------------------------------------------- > >>>> - > >>>> [INFO] Total time: 10.799s > >>>> [INFO] Finished at: Mon Dec 02 17:14:59 EST 2013 > >>>> [INFO] Final Memory: 13M/245M > >>>> [INFO] > >>>> ----------------------------------------------------------------------- > >>>> - > >>>> [ERROR] Failed to execute goal > >>>> org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare > >>>> (default-cli) on > >>>> project maven-verifier: Unable to tag SCM > >>>> [ERROR] Provider message: > >>>> [ERROR] The svn tag command failed. > >>>> [ERROR] Command output: > >>>> [ERROR] svn: E160013: > >>>> '/repos/asf/!svn/rvr/1547210/maven/shared/tags/maven-verifier-1.5' > >>>> path not > >>>> found > >>>> > >>>> Does anyone have suggestions how to troubleshoot this? > >>>> > >>>> -- > >>>> Regards, > >>>> Igor > >>>> > >>>> --------------------------------------------------------------------- > >>>> 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
