[Maven-plugins-cvs] cvs commit: maven-plugins HOWTO_RELEASE.txt

[Lukas T. <luk...@us...>]

lukas_theussl    06/04/24 23:10:35

  Modified:    .        HOWTO_RELEASE.txt
  Log:
  Small corrections.
  
  Revision  Changes    Path
  1.2       +8 -5      maven-plugins/HOWTO_RELEASE.txt
  
  Index: HOWTO_RELEASE.txt
  ===================================================================
  RCS file: /cvsroot/maven-plugins/maven-plugins/HOWTO_RELEASE.txt,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- HOWTO_RELEASE.txt	25 Apr 2006 05:19:54 -0000	1.1
  +++ HOWTO_RELEASE.txt	25 Apr 2006 06:10:35 -0000	1.2
  @@ -43,12 +43,10 @@
   Set "maven.repo.list" to the correct deployment location on the command line:
   
   To deploy the snapshot:
  -maven -Dmaven.repo.list=maven.plugins.sf.releases plugin:repository-deploy
  -
  -To deploy the release:
   maven -Dmaven.repo.list=maven.plugins.sf.snapshots plugin:repository-deploy
   
  -Appending -SNAPSHOT to the currentVersion will automatically deploy to the snapshot repo.
  +To deploy the release:
  +maven -Dmaven.repo.list=maven.plugins.sf.releases plugin:repository-deploy
   
   
   PUBLISH THE SITE TO SOURCEFORGE
  @@ -74,8 +72,13 @@
   Then deploy it
   maven -Dmaven.repo.remote=http://maven-plugins.sourceforge.net/repository site:sshdeploy
   
  +NOTE: If you are using the maven-site-plugin >= 1.7 you will also have to use -Dmaven.site.failonerror=false.
  +The reason for that is that on the sourceforge server, remote users don't have the right to change the
  +permission for the root site directory (htdocs on sourceforge), so the corresponding chmod command will fail.
  +See http://jira.codehaus.org/browse/MPSITE-34.
  +
   
  -EMAIL RELEASE ANNOUCEMENT
  +EMAIL RELEASE ANNOUNCEMENT
   -------------------------
   The site step generates it, and this is how standalone: