This is an automated email from the ASF dual-hosted git repository.

khmarbaise pushed a commit to branch BADGES
in repository https://gitbox.apache.org/repos/asf/maven-enforcer.git

commit cb014e1cd061ab27b7667b859d48b28e3eeb30cd
Author: Karl Heinz Marbaise <[email protected]>
AuthorDate: Sat Jan 13 17:19:30 2018 +0100

    Removed README.TXT and moved content to README.md
---
 README.TXT | 24 ------------------------
 README.md  |  2 +-
 2 files changed, 1 insertion(+), 25 deletions(-)

diff --git a/README.TXT b/README.TXT
deleted file mode 100644
index 71e0c62..0000000
--- a/README.TXT
+++ /dev/null
@@ -1,24 +0,0 @@
-Deploying web site
--------------------
-You can use the deploySite(.sh|.bat) script
-Without any profile, the site will be deployed to 
http://maven.apache.org/enforcer-archives/enforcer-${project.version}
-sh ./deploySite.sh -Preporting
-
-To deploy main version http://maven.apache.org/enforcer, use
-sh ./deploySite.sh -Preporting -Psite-release
-
-Note you can add arguments to the script to pass your svn credentials:
--Dusername=
--Dpassword=
-
-Workflow for site when releasing
---------------------------------
-Once release staged, you can publish a staged site.
-cd target/checkout
-sh ./deploySite.sh -Preporting
-content will be in 
http://maven.apache.org/enforcer-archives/enforcer-${project.version}
-
-Once vote passed, redeploy main site:
-cd target/checkout (or use the version tag)
-sh ./deploySite.sh -Preporting -Psite-release
-
diff --git a/README.md b/README.md
index 7fd7e79..23878cc 100644
--- a/README.md
+++ b/README.md
@@ -20,7 +20,7 @@ Test
 ## Deploying web site
 
 You can use the `deploySite.sh` or `deploySite.bat` script
-Without any profile, the site will be deployed to 
`https://maven.apache.org/enforcer-archives/enforcer-${project.version}`
+without any profile, the site will be deployed to 
`https://maven.apache.org/enforcer-archives/enforcer-${project.version}`
 
 ```
 sh ./deploySite.sh -Preporting

-- 
To stop receiving notification emails like this one, please contact
[email protected].

Reply via email to