Labels

.net (1) *nix (1) administration (1) Android (2) Axis2 (2) best practice (5) big-data (1) business-analysis (1) code re-use (1) continuous-integration (1) Cordova-PhoneGap (1) database (2) defect (1) design (3) Eclipse (7) education (1) groovy (2) https (2) Hudson (4) Java (1) JAX-RS (2) Jersey (3) Jetty (1) localization (1) m2eclipse (2) MapForce (1) Maven (12) MySQL (1) Nexus (4) notes (4) OO (1) Oracle (4) performance (1) Perl (1) PL/SQL (1) podcast (1) PostgreSQL (1) requirement (1) scripting (1) serialization (1) shell (1) SoapUI (1) SQL (1) SSH (2) stored procedure (1) STS (2) Subclipse (1) Subversion (3) TOAD (3) Tomcat (4) UML (2) unit-testing (2) WAMP (1) WAS (3) Windows (3) WP8 (2) WTP (2) XML (4) XSLT (1)

Thursday, January 12, 2012

Maven build lifecycle

How long can you use Maven without understanding the Maven build lifecycle?  Notes from Introduction to the Build Lifecycle for someone who has already used Maven for awhile:
  • Three built-in lifecycles: default, clean and site
  • Different build phases for each lifecycle
  • A goal represents a specific task, may be bound to zero or more build phases. A goal not bound to any build phase could be executed outside of the build lifecycle by direct invocation
  • goal = Ant task (roughly) = an action during the build
  • There is both a clean lifecycle and a clean phase 
  • If a build phase has no goals bound to it, that build phase will not execute
  • Each packaging (e.g. jar, war, etc.) contains a list of goals to bind to a particular phase
  • Plugins can provide/offer multiple goals for execution
  • If more than one goal is bound to a particular phase, the order used is that those from the packaging are executed first, followed by those configured in the POM

No comments:

Post a Comment