Re: Releasing: Step 11: Deploy the current website same as Step 7: Stage the latest documentation ?

2009-06-14 Thread Benjamin Bentmann
Barrie Treloar wrote: (and for me the site:stage-deploy fails, I dont know whether site-deploy has the same problems - i cant recall) What exactly is the error with site:stage-deploy you observe? Problems with authentication? Did you configure your settings with a server entry for the

Re: Releasing: Step 11: Deploy the current website same as Step 7: Stage the latest documentation ?

2009-06-14 Thread Barrie Treloar
On Sun, Jun 14, 2009 at 9:34 PM, Benjamin Bentmannbenjamin.bentm...@udo.edu wrote: Barrie Treloar wrote: (and for me the site:stage-deploy fails, I dont know whether site-deploy has the same problems - i cant recall) What exactly is the error with site:stage-deploy you observe? Problems with

Releasing: Step 11: Deploy the current website same as Step 7: Stage the latest documentation ?

2009-06-13 Thread Barrie Treloar
11. Deploy the current website Note: Be sure to generate and deploy the site using the same version of the release. Typically, you need to check out the tag (or go to target/checkout) cd target\checkout mvn site-deploy -Preporting 7. Stage the latest documentation The plugin parent POM is

Re: Releasing: Step 11: Deploy the current website same as Step 7: Stage the latest documentation ?

2009-06-13 Thread Arnaud HERITIER
It's what I do. I log on people.apache.org, I remove the old site and copy the new one Arnaud On Sat, Jun 13, 2009 at 2:49 PM, Barrie Treloar baerr...@gmail.com wrote: 11. Deploy the current website Note: Be sure to generate and deploy the site using the same version of the release.

Re: Releasing: Step 11: Deploy the current website same as Step 7: Stage the latest documentation ?

2009-06-13 Thread Wendy Smoak
On Sat, Jun 13, 2009 at 5:49 AM, Barrie Treloarbaerr...@gmail.com wrote: But isn't the output of these the same content? So instead of re-running this couldn't I just copy the already deployed version in /www/maven.apache.org/plugins/maven-XXX-plugin-Y.Z to

Re: Releasing: Step 11: Deploy the current website same as Step 7: Stage the latest documentation ?

2009-06-13 Thread Vincent Siveton
Hi Barrie, 2009/6/13 Barrie Treloar baerr...@gmail.com: So instead of re-running this couldn't I just copy the already deployed version in /www/maven.apache.org/plugins/maven-XXX-plugin-Y.Z to /www/maven.apache.org/plugins/maven-XXX-plugin ? IMHO it is not the correct solution: mvn

Re: Releasing: Step 11: Deploy the current website same as Step 7: Stage the latest documentation ?

2009-06-13 Thread Barrie Treloar
On Sun, Jun 14, 2009 at 12:09 AM, Vincent Sivetonvincent.sive...@gmail.com wrote: Hi Barrie, 2009/6/13 Barrie Treloar baerr...@gmail.com: So instead of re-running this couldn't I just copy the already deployed version in /www/maven.apache.org/plugins/maven-XXX-plugin-Y.Z to

Re: Releasing: Step 11: Deploy the current website same as Step 7: Stage the latest documentation ?

2009-06-13 Thread Vincent Siveton
Hi Barrie, 2009/6/13 Barrie Treloar baerr...@gmail.com: IMHO it is not the correct solution: mvn site:deploy and mvn site:stage-deploy have different behaviours. Can you explain the differences? They generate the same content right? The differences are mainly about links. See this MPIR

Re: Releasing: Step 11: Deploy the current website same as Step 7: Stage the latest documentation ?

2009-06-13 Thread Barrie Treloar
On Sun, Jun 14, 2009 at 12:36 PM, Vincent Sivetonvincent.sive...@gmail.com wrote: Yes site deploy could fail as described in 7a. But since the content is not the same, I recommend you to use site and not copy dir. Cheers, Vincent [1]

Re: Releasing: Step 11: Deploy the current website same as Step 7: Stage the latest documentation ?

2009-06-13 Thread Wendy Smoak
On Sat, Jun 13, 2009 at 8:06 PM, Vincent Sivetonvincent.sive...@gmail.com wrote: 2009/6/13 Barrie Treloar baerr...@gmail.com: The differences are mainly about links. See this MPIR staging page [1] vs final [2] But that's a bug in the site plugin, right? It _ought_ to be the same content from