Author: olamy
Date: Sat Feb 18 21:27:31 2012
New Revision: 1290880

URL: http://svn.apache.org/viewvc?rev=1290880&view=rev
improve README: note on how to test staged Tomcat maven artifacts


Modified: tomcat/maven-plugin/trunk/README.txt
URL: http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/README.txt?rev=1290880&r1=1290879&r2=1290880&view=diff
--- tomcat/maven-plugin/trunk/README.txt (original)
+++ tomcat/maven-plugin/trunk/README.txt Sat Feb 18 21:27:31 2012
@@ -1,23 +1,25 @@
+Build Apache Tomcat Maven Plugin
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=
+Snapshots deployment
To deploy a snaphot version to https://repository.apache.org/content/repositories/snapshots/, you must run : mvn clean deploy .
Note you need some configuration in ~/.m2/settings.xml:
- <id>apache.snapshots</id>
+ <id>apache.snapshots.https</id>
<username>your asf id</username>
- <!--password></password-->
- <!--privateKey>path to your private key</privateKey-->
- <!--passphrase></passphrase-->
- <filePermissions>664</filePermissions>
- <directoryPermissions>775</directoryPermissions>
+ <password>your asf paswword</password>

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.

-If you have a nice ssh key in ~/.ssh/ no need of configuring password, privateKey, passphrase.
+Site deployment

Checkstyle: this project use the Apache Maven checkstyle configuration for ide codestyle files see http://maven.apache.org/developers/committer-environment.html .

@@ -25,6 +27,18 @@ Site: to test site generation, just run:

To deploy site, use: mvn clean site-deploy -Preporting. The site will be deploy to http://tomcat.apache.org/maven-plugin-${project.version}

+Note you need some configuration in ~/.m2/settings.xml:
+ <server>
+ <id>apache.website</id>
+ <username>your asf id</username>
+ <filePermissions>664</filePermissions>
+ <directoryPermissions>775</directoryPermissions>
+ </server>
+If you have a nice ssh key in ~/.ssh/ no need of configuring password, privateKey, passphrase.
For release your ~/.m2/settings.xml must contains :

@@ -33,3 +47,14 @@ For release your ~/.m2/settings.xml must
<password>asf password</password>

+And run: mvn release:prepare release:perform -Dusername= -Dpassword= (username/password are you 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=
+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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org

Search Discussions

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupdev @
postedFeb 18, '12 at 9:27p
activeFeb 18, '12 at 9:27p

1 user in discussion

Olamy: 1 post



site design / logo © 2016 Grokbase