Author: svn-site-role
Date: Sun Apr 14 20:40:56 2024
New Revision: 1916990
Log:
Site checkin for project Apache Maven Site
Modified:
maven/website/content/guides/introduction/introduction-to-archetypes.html
maven/website/content/maven-site-1.0-site.jar
Modified:
maven/website/content/guides/introduction/introduction-to-archetypes.html
==============================================================================
--- maven/website/content/guides/introduction/introduction-to-archetypes.html
(original)
+++ maven/website/content/guides/introduction/introduction-to-archetypes.html
Sun Apr 14 20:40:56 2024
@@ -150,7 +150,7 @@
<h1>Introduction to Archetypes</h1></section><section>
<h1>What is Archetype?</h1>
<p>In short, Archetype is a Maven project templating toolkit. An archetype is
defined as <i>an original pattern or model from which all other things of the
same kind are made</i>. The name fits as we are trying to provide a system that
provides a consistent means of generating Maven projects. Archetype will help
authors create Maven project templates for users, and provides users with the
means to generate parameterized versions of those project templates.</p>
-<p>Using archetypes provides a great way to enable developers quickly in a way
consistent with best practices employed by your project or organization. Within
the Maven project, we use archetypes to try and get our users up and running as
quickly as possible by providing a sample project that demonstrates many of the
features of Maven, while introducing new users to the best practices employed
by Maven. In a matter of seconds, a new user can have a working Maven project
to use as a jumping board for investigating more of the features in Maven. We
have also tried to make the Archetype mechanism additive, and by that we mean
allowing portions of a project to be captured in an archetype so that pieces or
aspects of a project can be added to existing projects. A good example of this
is the Maven site archetype. If, for example, you have used the quick start
archetype to generate a working project, you can then quickly create a site for
that project by using the site archetype within tha
t existing project. You can do anything like this with archetypes.</p>
+<p>Using archetypes provides a great way to enable developers work quickly in
a way consistent with best practices employed by your project or organization.
Within the Maven project, we use archetypes to try and get our users up and
running as quickly as possible by providing a sample project that demonstrates
many of the features of Maven, while introducing new users to the best
practices employed by Maven. In a matter of seconds, a new user can have a
working Maven project to use as a jumping board for investigating more of the
features in Maven. We have also tried to make the Archetype mechanism additive,
and by that we mean allowing portions of a project to be captured in an
archetype so that pieces or aspects of a project can be added to existing
projects. A good example of this is the Maven site archetype. If, for example,
you have used the quick start archetype to generate a working project, you can
then quickly create a site for that project by using the site archetype withi
n that existing project. You can do anything like this with archetypes.</p>
<p>You may want to standardize J2EE development within your organization, so
you may want to provide archetypes for EJBs, or WARs, or for your web services.
Once these archetypes are created and deployed in your organization's
repository, they are available for use by all developers within your
organization.</p><section>
<h2>Using an Archetype</h2>
<p>To create a new project based on an Archetype, you need to call <code>mvn
archetype:generate</code> goal, like the following:</p>
Modified: maven/website/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
