Message-ID: <229834210.817.1386920837724.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_816_1968103793.1386920837724" ------=_Part_816_1968103793.1386920837724 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
A problem every former Ant or Maven 1 users have probably faced in the p= ast (if not please give me your trick!!) is to try to figure out the execut= ion order of a given goal or task of a third party build. Basically, you ha= d to trace down every dependencies or pray the guy had respected some conve= ntions. What a waste of time! Afterall, any project build always goes throu= ght the same phases, ie compiling, testing, packaging, ... Why not st= andardize those phase and their execution order?=20
As you have learned in the Maven, not just another build tool, Maven 2 revo= lves around the concept of build patterns.