Author: kkolinko
Date: Sat Feb 18 23:18:49 2012
New Revision: 1290904
URL: http://svn.apache.org/viewvc?rev=1290904&view=rev
Log:
Correct several typos
Modified:
tomcat/maven-plugin/trunk/README.txt
Modified: tomcat/maven-plugin/trunk/README.txt
URL:
http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/README.txt?rev=1290904&r1=1290903&r2=1290904&view=diff
==============================================================================
--- tomcat/maven-plugin/trunk/README.txt (original)
+++ tomcat/maven-plugin/trunk/README.txt Sat Feb 18 23:18:49 2012
@@ -1,6 +1,6 @@
Build Apache Tomcat Maven Plugin
--------------------------------
-to build this project you must Apache Maven at least 2.2.1 .
+To build this project you must Apache Maven at least 2.2.1 .
mvn clean install will install the mojos without running integration tests.
As there are some hardcoded integration tests with http port 1973, ajp 2001
and 2008, you could have some port allocation issues (if you don't know why
those values ask olamy :-) )
mvn clean install -Prun-its will run integration tests too: to override the
default used htpp port you can use -Dits.http.port= -Dits.ajp.port=
@@ -15,17 +15,17 @@ Note you need some configuration in ~/.m
<password>your asf paswword</password>
</server
-NOTE: a Jenkins job deploy SNAPSHOT automatically
https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/.
-So no real to deploy manually, just commit and Jenkins will do the job for you.
+NOTE: a Jenkins job deploys SNAPSHOT automatically
https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/.
+So no real need to deploy manually, just commit and Jenkins will do the job
for you.
Site deployment
-----------------
-Checkstyle: this project use the Apache Maven checkstyle configuration for ide
codestyle files see
http://maven.apache.org/developers/committer-environment.html .
+Checkstyle: this project uses the Apache Maven checkstyle configuration for
ide codestyle files see
http://maven.apache.org/developers/committer-environment.html .
Site: to test site generation, just run: mvn site. If you want more reporting
(javadoc, pmd, checkstyle, jxr, changelog from jira entries), use: mvn site
-Preporting.
-To deploy site, use: mvn clean site-deploy -Preporting. The site will be
deploy to http://tomcat.apache.org/maven-plugin-${project.version}
+To deploy site, use: mvn clean site-deploy -Preporting. The site will be
deployed to http://tomcat.apache.org/maven-plugin-${project.version}
Note you need some configuration in ~/.m2/settings.xml:
<server>
@@ -47,14 +47,14 @@ For release your ~/.m2/settings.xml must
<password>asf password</password>
</server>
-And run: mvn release:prepare release:perform -Dusername= -Dpassword=
(username/password are you Apache svn authz)
+And run: mvn release:prepare release:perform -Dusername= -Dpassword=
(username/password are your Apache svn authz)
Test staged Tomcat artifacts
----------------------------
To test staging artifacts for a vote process.
* activate a profile: tc-staging
* pass staging repository as parameter: -DtcStagedReleaseUrl=
-* pass version tomcat version as parameter: -Dtomcat7Version=
+* pass tomcat version as parameter: -Dtomcat7Version=
Sample: mvn clean install -Prun-its -Ptc-staging
-DtcStagedReleaseUrl=https://repository.apache.org/content/repositories/orgapachetomcat-020/
-Dtomcat7Version=7.0.26
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
