The idea was to have a versioned one under http://maven.apache.org/maven-release-archives/maven-release-2.5 Then just svn cp to the current destination. But I believe had the good idea to just use something like http://maven.apache.org/maven-release-archives/maven-release-LATEST (to avoid toooooo lonnnngg commit when staging a release) and then svn cp that. But I think the update has not been applied in the maven-release project
On 5 March 2014 22:29, Benson Margulies <[email protected]> wrote: > I followed the instructions in the README.TXT, but the site remains > under http://maven.apache.org/maven-release-archives/maven-release-2.5/, > and is not promoted to the main location. > > So I followed the instructions in > https://maven.apache.org/developers/website/deploy-component-reference-documentation.html > manually. Olivier, was this your intention when you set up > deploySite.sh? -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
