Author: buildbot
Date: Sat Oct 11 22:11:49 2014
New Revision: 925433
Log:
Staging update by buildbot for maven
Modified:
websites/staging/maven/trunk/content/ (props changed)
websites/staging/maven/trunk/content/guides/plugin/guide-java-plugin-development.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 Oct 11 22:11:49 2014
@@ -1 +1 @@
-1631113
+1631132
Modified:
websites/staging/maven/trunk/content/guides/plugin/guide-java-plugin-development.html
==============================================================================
---
websites/staging/maven/trunk/content/guides/plugin/guide-java-plugin-development.html
(original)
+++
websites/staging/maven/trunk/content/guides/plugin/guide-java-plugin-development.html
Sat Oct 11 22:11:49 2014
@@ -521,16 +521,7 @@ public class GreetingMojo extends Abstra
<pre><myURL>http://maven.apache.org</myURL></pre></div></div>
<div class="section">
<h5><a name="Plain_Text"></a>Plain Text</h5>
-<p>This includes variables typed <tt>char</tt>, <tt>Character</tt>,
<tt>StringBuffer</tt>, and <tt>String</tt>. When reading the configuration, the
text in the XML file is used as the value to be assigned to the parameter. For
<tt>char</tt> and <tt>Character</tt> parameters, only the first character of
the text is used.</p></div></div>
-<div class="section">
-<h4><a name="Parameter_Types_With_Multiple_Values"></a>Parameter Types With
Multiple Values</h4>
-<p>Listed below are the various types of composite objects which can be used
as parameters in your mojos, along with any rules on how the values in the POM
are interpreted. In general, the class of the object created to hold the
parameter value (as well as the class for each element within the parameter
value) is determined as follows (the first step which yields a valid class is
used):</p>
-<ol style="list-style-type: decimal">
-<li>If the XML element contains an <tt>implementation</tt> hint attribute,
that is used</li>
-<li>If the XML tag contains a <tt>.</tt>, try that as a fully qualified class
name</li>
-<li>Try the XML tag (with capitalized first letter) as a class in the same
package as the mojo/object being configured</li>
-<li>For arrays, use the component type of the array (for example, use
<tt>String</tt> for a <tt>String[]</tt> parameter); for collections and maps,
use the class specified in the mojo configuration for the collection or map;
use <tt>String</tt> for entries in a collection and values in a map</li></ol>
-<p>Once the type for the element is defined, the text in the XML file is
converted to the appropriate type of object</p>
+<p>This includes variables typed <tt>char</tt>, <tt>Character</tt>,
<tt>StringBuffer</tt>, and <tt>String</tt>. When reading the configuration, the
text in the XML file is used as the value to be assigned to the parameter. For
<tt>char</tt> and <tt>Character</tt> parameters, only the first character of
the text is used.</p></div>
<div class="section">
<h5><a name="Enums"></a>Enums</h5>
<p>Enumeration type parameters can also be used. First you need to define your
enumeration type and afterwards you can use the enumeration type in the
parameter definition:</p>
@@ -546,6 +537,9 @@ public class GreetingMojo extends Abstra
*/
@Parameter
private Color myColor;</pre></div>
+<p>So lets have a look like you can use such enumeration in your pom
configuration:</p>
+<div class="source">
+<pre><myColor>GREEN</myColor></pre></div>
<p>You can also use elements from the enumeration type as defaultValues like
the following:</p>
<div class="source">
<pre> public enum Color {
@@ -558,7 +552,16 @@ public class GreetingMojo extends Abstra
* My Enum
*/
@Parameter(defaultValue = "GREEN")
- private Color myColor;</pre></div></div>
+ private Color myColor;</pre></div></div></div>
+<div class="section">
+<h4><a name="Parameter_Types_With_Multiple_Values"></a>Parameter Types With
Multiple Values</h4>
+<p>Listed below are the various types of composite objects which can be used
as parameters in your mojos, along with any rules on how the values in the POM
are interpreted. In general, the class of the object created to hold the
parameter value (as well as the class for each element within the parameter
value) is determined as follows (the first step which yields a valid class is
used):</p>
+<ol style="list-style-type: decimal">
+<li>If the XML element contains an <tt>implementation</tt> hint attribute,
that is used</li>
+<li>If the XML tag contains a <tt>.</tt>, try that as a fully qualified class
name</li>
+<li>Try the XML tag (with capitalized first letter) as a class in the same
package as the mojo/object being configured</li>
+<li>For arrays, use the component type of the array (for example, use
<tt>String</tt> for a <tt>String[]</tt> parameter); for collections and maps,
use the class specified in the mojo configuration for the collection or map;
use <tt>String</tt> for entries in a collection and values in a map</li></ol>
+<p>Once the type for the element is defined, the text in the XML file is
converted to the appropriate type of object</p>
<div class="section">
<h5><a name="Arrays"></a>Arrays</h5>
<p>Array type parameters are configured by specifying the parameter multiple
times. Example:</p>
Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
