Update the README

git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@744435 13f79535-47bb-0310-9956-ffa450edef68

1 files changed, 9 insertions, 2 deletions

diff --git a/maven-plugins/trunk/maven-eclipse-compiler/README b/maven-plugins/trunk/maven-eclipse-compiler/README
index 64d58dd57b..1ff74b8e49 100644
--- a/maven-plugins/trunk/maven-eclipse-compiler/README
+++ b/maven-plugins/trunk/maven-eclipse-compiler/README
@@ -21,7 +21,10 @@ followed by:
 

 mvn release:perform

 

-While running these will prompt you for the names fro the tag, release version etc.

+That will automatically create an SVN tag from the release, update the version 

+numbers in the pom.xml files in the trunk and tag, and deploy the artifacts to the

+staging repository defined by the <deploy.altRepository> in your Maven settings.xml.

+While running it will prompt you for the names for the tag, release version etc.

 

 In your maven settings.xml file you must have a server defined named "apache.releases",

 and a profile named "release". For example:

@@ -49,8 +52,12 @@ and a profile named "release". For example:
     </profile>

   </profiles>

 

+Call a vote to release the module, eg: http://apache.markmail.org/message/6jnlfxbx7uklt5nv

+

+After a successfule vote copy the staging artifacts to the live repository, eg: 

+

+cp -p -v -R  maven-eclipse-compiler-1.0/org/apache/tuscany/maven/plugins/ /x1/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/tuscany/maven/plugins

 

-