Skip to content

Latest commit

 

History

History
36 lines (29 loc) · 1.73 KB

README.md

File metadata and controls

36 lines (29 loc) · 1.73 KB

mavendeployplugin

Maven plugin for deployment of Tomcat web application

How to create new version of plugin

  1. Let's say git repository is cloned into local folder C:\cc-deploy-maven-plugin.
  2. Clone repository to separate folder, e.g. C:\mvn-repo.
  3. Switch to mvn-repo branch in that folder.
  4. Go back to folder C:\cc-deploy-maven-plugin
  5. First, change the version mvn versions:set -DnewVersion=1.29 versions:commit
  6. Then, if no new modules were added run mvn clean install -DmvnRepo=C:\\mvn-repo (here and lower: \ is escaped for Cygwin).
  7. If a new module was added, then do this:
    1. Run mvn clean install -DmvnRepoNewModule=C:\\mvn-repo.
    2. Revert changed files in mvn-repo folder. Don't revert (i.e. delete) new ones.
    3. Rename maven-metadata-local* to mavent-metadata*.
    4. Run the same line as for the case when no new modules were added.
  8. Go to folder C:\mvn-repo.
  9. Add new files to commit, then commit and push mvn-repo branch to server.

Maven: how to build and install locally, without uploading to remote repository

mvn clean install

Plugin configuration

parameter description required
deploy.warName name of the folder where plugin will be uploaded to, usually it should be ${project.build.finalName} yes
deploy.hostName hostname to connect to via SSH yes
deploy.port SSH port no, default value is 22
deploy.userName SSH username yes
deploy.sshKeyFile SSH key file yes
deploy.remoteWebApps remote folder where upload files to yes
deploy.nginxCacheDir remote folder which must be cleaned after any changes were made yes
touchWebXml whether WEB-INF/web.xml must be touched after remote files were uploaded/removed/overwritten no, default true