1 / 6

AutoDeploy Parse

AutoDeploy Parse. Developer checks out main project's project.xml. Developer runs 'maven parseproject' to download project and all dependencies. Developer modifies dependency projects and main project as needed. Developer commits changes to update all file versions.

reid
Download Presentation

AutoDeploy Parse

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AutoDeploy Parse • Developer checks out main project's project.xml. • Developer runs 'maven parseproject' to download project and all dependencies. • Developer modifies dependency projects and main project as needed. • Developer commits changes to update all file versions. • Developer cleans projects by running 'maven -Dgoal=clean multiproject:goal.

  2. AutoDeploy Catalog • Developer runs 'maven ccscm:catalog'. • Cvs status command is run against entire project and redirected to a file. • Maven plugin parses status file using Java Perl-style regular expressions (Apache Oro library). • Maven plugin writes self-referencing xml file catalog using JDOM with: • Tag name (if provided) • File names, versions, sizes, md5, and modtime info • Cvs repository information such as the server, repository, and module • This step is optional if continuing.

  3. AutoDeploy Version • Developer runs 'maven -DccScm.project.version=3.4 ccscm:version-project'. • Maven plugin writes the project.xml file with a new version number for project: • Use map for version • Increment previous version • User specified version • Maven plugin checks in the project.xml file and get the Cvs version. • Maven plugin rewrites the file catalog the same as in the previous slide. • Maven plugin checks in the file catalog. • All the project files will be tagged by the Maven plugin if one is provided.

  4. AutoDeploy Map • Developer runs 'maven ccscm:createmap'. • Maven plugin gets the file catalog version from a user property or from Cvs status. • Maven plugin parses project.xml file using Java JDOM library. • Determines current project name and version; writes to 'last' project map section. • Creates 'projects' map section for project with more project info, the file catalog version, and the name, group, and version for all dependencies. • 'Last' map section is used for higher level projects to grab the last build of a dependency. • The map can be used recursively through all dependencies if the dependencies were mapped as well.

  5. AutoDeploy Parent • On parent projects, we run the version step using the map to get the 'last' version of dependencies: 'maven -DccScm.use.map=yes ccscm:version-project' • If parent project is also to be versioned, need to run version and mapping step without using map first to update last map for project itself. • Three ways to version(highest to lowest level of priority): • ccScm.dep.ver.{artifactId} • ccScm.map.file • ccScm.project.version • Setting ccScm.dep.ver.{artifactId} property for project name overrides the version from the mapping, so the version and mapping step for the parent is no longer necessary.

More Related