Modified: maven/site/trunk/src/site/apt/guides/introduction/introduction-to-archetypes.apt URL: http://svn.apache.org/viewcvs/maven/site/trunk/src/site/apt/guides/introduction/introduction-to-archetypes.apt?rev=331045&r1=331044&r2=331045&view=diff ============================================================================== --- maven/site/trunk/src/site/apt/guides/introduction/introduction-to-archetypes.apt (original) +++ maven/site/trunk/src/site/apt/guides/introduction/introduction-to-archetypes.apt Sat Nov 5 15:06:14 2005 @@ -20,21 +20,21 @@ 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 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 captured in an archetype so that pieces + 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 that existing project. You can do anything like this with archetypes. 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 organizations + 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. * What makes up an Archetype? Archetypes are packaged up in a JAR and they consist of the archetype metadata which describes the contents of archetype and a set of {{{http://jakarta.apache.org/velocity}Velocity}} templates which make up the prototype - project. If you would like to know how to make your archetypes please refer to our + project. If you would like to know how to make your own archetypes please refer to our {{{../mini/guide-creating-archetypes.html}Guide to creating archetypes}}.
Modified: maven/site/trunk/src/site/apt/guides/introduction/introduction-to-dependency-management.apt URL: http://svn.apache.org/viewcvs/maven/site/trunk/src/site/apt/guides/introduction/introduction-to-dependency-management.apt?rev=331045&r1=331044&r2=331045&view=diff ============================================================================== --- maven/site/trunk/src/site/apt/guides/introduction/introduction-to-dependency-management.apt (original) +++ maven/site/trunk/src/site/apt/guides/introduction/introduction-to-dependency-management.apt Sat Nov 5 15:06:14 2005 @@ -8,7 +8,7 @@ Introduction to dependency management - Dependency management is one of the features of Maven that is best know to users and is one of the areas where + Dependency management is one of the features of Maven that is best known to users and is one of the areas where Maven excels. There is not much difficulty in managing dependencies for a single a project, but when you start getting into dealing with multi-module projects and applications that consist of tens or hundreds of modules this is where Maven can help you a great deal in maintaining a high degree of control and stability. Modified: maven/site/trunk/src/site/apt/guides/introduction/introduction-to-profiles.apt URL: http://svn.apache.org/viewcvs/maven/site/trunk/src/site/apt/guides/introduction/introduction-to-profiles.apt?rev=331045&r1=331044&r2=331045&view=diff ============================================================================== --- maven/site/trunk/src/site/apt/guides/introduction/introduction-to-profiles.apt (original) +++ maven/site/trunk/src/site/apt/guides/introduction/introduction-to-profiles.apt Sat Nov 5 15:06:14 2005 @@ -218,7 +218,7 @@ tests pass, since the path you've provided allows the test plugin to install and test this web application. - <However>, when your your colleague attempts to build to <<integration-test>>, + <However>, when your colleague attempts to build to <<integration-test>>, his build fails spectacularly, complaining that it cannot resolve the plugin configuration parameter \<appserverHome\>, or worse, that the value of that parameter - literally $\{appserver.home\} - is invalid (if it warns you at all). @@ -282,7 +282,7 @@ </profiles> +---+ - This profile looks quite similar to the one from last example, with a few + This profile looks quite similar to the one from the last example, with a few important exceptions: it's plainly geared toward a development environment, and it has an activation section that will trigger its inclusion when the system properties contain "env=dev". So, executing: Modified: maven/site/trunk/src/site/fml/about.fml URL: http://svn.apache.org/viewcvs/maven/site/trunk/src/site/fml/about.fml?rev=331045&r1=331044&r2=331045&view=diff ============================================================================== --- maven/site/trunk/src/site/fml/about.fml (original) +++ maven/site/trunk/src/site/fml/about.fml Sat Nov 5 15:06:14 2005 @@ -6,11 +6,10 @@ <question>Tell me about the goals of Maven 2.0</question> <answer> <p> - You've seen - <a href="#what-is-maven">above</a> - the goals that Maven aims to achieve, however there have also - been questions about why Maven 2.0 is rewritten from the successful Maven 1.0. In summary, the main goals of - the new Maven 2.0 architecture are: + In addition to understanding the + <a href="./what-is-maven.html">Goals of Maven</a> + there have also been questions about why Maven 2.0 is rewritten from the successful Maven 1.0. + In summary, the main goals of the new Maven 2.0 architecture are: </p> <ul> <li>To be simple to use - it should be more obvious and consistent about how things are working</li> @@ -39,7 +38,7 @@ </p> <p> For instructions on checking out and building Maven 2.0, see - <a href="/maven2/developers/building.html">Building Maven 2.0</a> + <a href="./guides/development/guide-building-m2.html">Building Maven 2.0</a> . </p> <p>
