You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-commits@maven.apache.org by sv...@apache.org on 2020/10/03 18:32:05 UTC

svn commit: r1882222 - in /maven/website/content: guides/introduction/introduction-to-the-standard-directory-layout.html maven-site-1.0-site.jar

Author: svn-site-role
Date: Sat Oct  3 18:32:05 2020
New Revision: 1882222

Log:
Site checkin for project Apache Maven Site

Modified:
    maven/website/content/guides/introduction/introduction-to-the-standard-directory-layout.html
    maven/website/content/maven-site-1.0-site.jar

Modified: maven/website/content/guides/introduction/introduction-to-the-standard-directory-layout.html
==============================================================================
--- maven/website/content/guides/introduction/introduction-to-the-standard-directory-layout.html (original)
+++ maven/website/content/guides/introduction/introduction-to-the-standard-directory-layout.html Sat Oct  3 18:32:05 2020
@@ -145,8 +145,8 @@
         <main id="bodyColumn"  class="span10" >
 <section>
 <h2><a name="Introduction_to_the_Standard_Directory_Layout"></a>Introduction to the Standard Directory Layout</h2>
-<p>Having a common directory layout would allow for users familiar with one Maven project to immediately feel at home in another Maven project. The advantages are analogous to adopting a site-wide look-and-feel.</p>
-<p>The next section documents the directory layout expected by Maven and the directory layout created by Maven. Please try to conform to this structure as much as possible; however, if you can't these settings can be overridden via the project descriptor.</p>
+<p>Having a common directory layout allows users familiar with one Maven project to immediately feel at home in another Maven project. The advantages are analogous to adopting a site-wide look-and-feel.</p>
+<p>The next section documents the directory layout expected by Maven and the directory layout created by Maven. Try to conform to this structure as much as possible. However, if you can't, these settings can be overridden via the project descriptor.</p>
 <table border="1" class="table table-striped">
 <tr class="a">
 <td align="left"><code>src/main/java</code></td>
@@ -192,7 +192,7 @@
 <p>The <code>target</code> directory is used to house all output of the build.</p>
 <p>The <code>src</code> directory contains all of the source material for building the project, its site and so on. It contains a subdirectory for each type: <code>main</code> for the main build artifact, <code>test</code> for the unit test code and resources, <code>site</code> and so on.</p>
 <p>Within artifact producing source directories (ie. <code>main</code> and <code>test</code>), there is one directory for the language <code>java</code> (under which the normal package hierarchy exists), and one for <code>resources</code> (the structure which is copied to the target classpath given the default resource definition).</p>
-<p>If there are other contributing sources to the artifact build, they would be under other subdirectories: for example <code>src/main/antlr</code> would contain Antlr grammar definition files.</p></section>
+<p>If there are other contributing sources to the artifact build, they would be under other subdirectories. For example <code>src/main/antlr</code> would contain Antlr grammar definition files.</p></section>
         </main>
       </div>
     </div>

Modified: maven/website/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.