Message-ID: <1197491810.1423.1394432803114.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1422_957542275.1394432803113" ------=_Part_1422_957542275.1394432803113 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Raphael Pieroni is leading an effort to make Archetype a seamles= s and end-to-end tool for prototyping Maven projects. The work has been carried out over at the Mojo pr= oject (https://svn.codehaus.org/mojo/trunk/moj= o/mojo-sandbox/maven-archetypeng) but is approaching a state where it can be brought back to= Apache.=20
This code has been imported into the maven-sandbox at apache.= =20
We currently have a system where the creation of Archetypes is dead simp= le. Using default information you simply use "mvn archetype:create-fro= m-project" and it will generate your Archetype for you. Very simple. N= ext we are going to create a few simple additions that will allow this Arch= etype to be installed or deployed. We are also going to make some tools to = automatically ensure the Archetype created is intact. So the very first goa= l is to allow someone to generate Archetypes, verify them and deploy them. = So we are rapidly approaching ther reality where samples projects can be co= ntinuously integrated and periodically be deployed in Archetype form. This = is what Archetype was meant to be and Raphael has made this happen. Once th= e process is seamless we wil align all the package names with the Apache na= mespace and bring the code back to the Maven project. We are close. Many th= anks to Raphael!