svn commit: r1020699 - in /websites/staging/maven/trunk/content: ./ guides/getting-started/index.html maven-site-1.0-site.jar

[bu...@apache.org]

Author: buildbot
Date: Sat Nov 11 14:39:45 2017
New Revision: 1020699

Log:
Staging update by buildbot for maven

Modified:
    websites/staging/maven/trunk/content/   (props changed)
    websites/staging/maven/trunk/content/guides/getting-started/index.html
    websites/staging/maven/trunk/content/maven-site-1.0-site.jar

Propchange: websites/staging/maven/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Nov 11 14:39:45 2017
@@ -1 +1 @@
-1814952
+1814953

Modified: websites/staging/maven/trunk/content/guides/getting-started/index.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/getting-started/index.html (original)
+++ websites/staging/maven/trunk/content/guides/getting-started/index.html Sat Nov 11 14:39:45 2017
@@ -368,13 +368,7 @@ Results :
 <div class="source"><pre class="prettyprint linenums">mvn site</pre></div>
 <p>There are plenty of other standalone goals that can be executed as well, for example:</p>
 <div class="source"><pre class="prettyprint linenums">mvn clean</pre></div>
-<p>This will remove the <tt>target</tt> directory with all the build data before starting so that it is fresh.</p>
-<p>Perhaps you'd like to generate an IntelliJ IDEA descriptor for the project?</p>
-<div class="source"><pre class="prettyprint linenums">mvn idea:idea</pre></div>
-<p>This can be run over the top of a previous IDEA project - it will update the settings rather than starting fresh.</p>
-<p>If you are using Eclipse IDE, just call:</p>
-<div class="source"><pre class="prettyprint linenums">mvn eclipse:eclipse</pre></div>
-<p><b>Note:</b> some familiar goals from Maven 1.0 are still there - such as <tt>jar:jar</tt>, but they might not behave like you'd expect. Presently, <tt>jar:jar</tt> will not recompile sources - it will simply just create a JAR from the <tt>target/classes</tt> directory, under the assumption everything else had already been done.</p></div>
+<p>This will remove the <tt>target</tt> directory with all the build data before starting so that it is fresh.</p></div>
 <div class="section">
 <h3><a name="What_is_a_SNAPSHOT_version">What is a SNAPSHOT version?</a></h3>
 <p>Notice the value of the <b>version</b> tag in the <tt>pom.xml</tt> file shown below has the suffix: <tt>-SNAPSHOT</tt>.</p>
@@ -908,9 +902,7 @@ command.line.prop=${command.line.prop}</
 <p>How does this work? Firstly, the parent POM created (called <tt>app</tt>), has a packaging of <tt>pom</tt> and a list of modules defined. This tells Maven to run all operations over the set of projects instead of just the current one (to override this behaviour, you can use the <tt>--non-recursive</tt> command line option).</p>
 <p>Next, we tell the WAR that it requires the <tt>my-app</tt> JAR. This does a few things: it makes it available on the classpath to any code in the WAR (none in this case), it makes sure the JAR is always built before the WAR, and it indicates to the WAR plugin to include the JAR in its library directory.</p>
 <p>You may have noticed that <tt>junit-4.11.jar</tt> was a dependency, but didn't end up in the WAR. The reason for this is the <tt>&lt;scope&gt;test&lt;/scope&gt;</tt> element - it is only required for testing, and so is not included in the web application as the compile time dependency <tt>my-app</tt> is.</p>
-<p>The final step was to include a parent definition. This is different to the <tt>extend</tt> element you may be familiar with from Maven 1.0: this ensures that the POM can always be located even if the project is distributed separately from its parent by looking it up in the repository.</p>
-<p>You might like to generate your IDEA workspace again from the top level directory...</p>
-<div class="source"><pre class="prettyprint linenums">mvn idea:idea</pre></div></div></div>
+<p>The final step was to include a parent definition. This is different to the <tt>extend</tt> element you may be familiar with from Maven 1.0: this ensures that the POM can always be located even if the project is distributed separately from its parent by looking it up in the repository.</p></div></div>
         </div>
       </div>
     </div>

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