Author: svn-site-role
Date: Sat Jun 6 09:01:52 2020
New Revision: 1878539
Log:
Site checkin for project Apache Maven Site
Modified:
maven/website/content/guides/introduction/introduction-to-plugins.html
maven/website/content/guides/introduction/introduction-to-profiles.html
maven/website/content/guides/introduction/introduction-to-the-pom.html
maven/website/content/guides/mini/guide-building-for-different-environments.html
maven/website/content/guides/mini/guide-configuring-maven.html
maven/website/content/guides/mini/guide-creating-archetypes.html
maven/website/content/guides/mini/guide-encryption.html
maven/website/content/guides/mini/guide-maven-classloading.html
maven/website/content/guides/mini/guide-new-committers.html
maven/website/content/guides/mini/guide-snippet-macro.html
maven/website/content/guides/mini/guide-using-one-source-directory.html
maven/website/content/guides/mini/guide-using-toolchains.html
maven/website/content/maven-site-1.0-site.jar
Modified: maven/website/content/guides/introduction/introduction-to-plugins.html
==============================================================================
--- maven/website/content/guides/introduction/introduction-to-plugins.html
(original)
+++ maven/website/content/guides/introduction/introduction-to-plugins.html Sat
Jun 6 09:01:52 2020
@@ -141,10 +141,10 @@
<p>Plugins are the central feature of Maven that allow for the reuse of common
build logic across multiple projects. They do this by executing an
"action" (i.e. creating a WAR file or compiling unit tests) in the
context of a project's description - the Project Object Model (POM). Plugin
behavior can be customized through a set of unique parameters which are exposed
by a description of each plugin goal (or Mojo).</p>
<p>One of the simplest plugins in Maven is the Clean Plugin. The <a
href="../../plugins/maven-clean-plugin/">Maven Clean plugin</a>
(maven-clean-plugin) is responsible for removing the target directory of a
Maven project. When you run "mvn clean", Maven executes the
"clean" goal as defined in the Clean plug-in, and the target
directory is removed. The Clean plugin <a
href="../../plugins/maven-clean-plugin/clean-mojo.html">defines a parameter</a>
which can be used to customize plugin behavior, this parameter is called
outputDirectory and it defaults to
${project.build.directory}.</p></section><section>
<h3><a
name="What_is_a_Mojo_.28And_Why_the_H---_is_it_Named_.27Mojo.27.29.3F"></a>What
is a Mojo (<i>And Why the H--- is it Named 'Mojo'</i>)?</h3>
-<p>A Mojo is really just a goal in Maven, and plug-ins consist of any number
of goals (Mojos). Mojos can be defined as annotated Java classes or Beanshell
script. A Mojo specifies metadata about a goal: a goal name, which phase of the
lifecycle it fits into, and the parameters it is expecting.</p>
+<p>A Mojo is really just a <b>goal</b> in Maven, and plug-ins consist of any
number of goals (Mojos). Mojos can be defined as annotated Java classes or
Beanshell script. A Mojo specifies metadata about a goal: a goal name, which
phase of the lifecycle it fits into, and the parameters it is expecting.</p>
<p>MOJO is a play on POJO (Plain-old-Java-object), substituting
"Maven" for "Plain". Mojo is also an interesting word (see
<a class="externalLink"
href="http://www.answers.com/mojo&r=67";>definition</a>). From <a
class="externalLink" href="http://www.wikipedia.org";>Wikipedia</a>, a
"mojo" is defined as: "...a small bag worn by a person under the
clothes (also known as a mojo hand). Such bags were thought to have
supernatural powers, such as protecting from evil, bringing good luck,
etc."</p></section><section>
<h3><a name="What_is_the_Build_Lifecycle.3F_.28Overview.29"></a>What is the
Build Lifecycle? (Overview)</h3>
-<p>The build lifecycle is a series of common stages through which all project
builds naturally progress. Plugin goals are bound to specific stages in the
lifecycle.</p></section></section><section>
+<p>The build lifecycle is a series of common <b>stage</b>s through which all
project builds naturally progress. Plugin goals are bound to specific stages in
the lifecycle.</p></section></section><section>
<h2><a name="Resources"></a>Resources</h2>
<ol style="list-style-type: decimal">
<li><a href="/plugin-developers/index.html">Plugin Development Center</a></li>
Modified:
maven/website/content/guides/introduction/introduction-to-profiles.html
==============================================================================
--- maven/website/content/guides/introduction/introduction-to-profiles.html
(original)
+++ maven/website/content/guides/introduction/introduction-to-profiles.html Sat
Jun 6 09:01:52 2020
@@ -430,20 +430,23 @@ mvn groupId:artifactId:goal -Ddebug=fals
<p>From the last example of profiles in the <code>pom.xml</code>, you'll
notice that there are two profiles named <code>appserverConfig-dev</code> and
<code>appserverConfig-dev-2</code> which has been given different values for
properties. If we go ahead and execute:</p>
<div class="source"><pre class="prettyprint linenums"> mvn
help:active-profiles -Denv=dev</pre></div>
<p>The result will be a bulleted list of the id of the profile with an
activation property of "env=dev" together with the source where it
was declared. See sample below.</p>
-<div class="source"><pre class="prettyprint linenums">The following profiles
are active:
+<div>
+<pre>The following profiles are active:
- appserverConfig-dev (source: pom)</pre></div>
<p>Now if we have a profile declared in <code>settings.xml</code> (refer to
the sample of profile in <code>settings.xml</code>) and that have been set to
be an active profile and execute:</p>
<div class="source"><pre class="prettyprint linenums"> mvn
help:active-profiles</pre></div>
<p>The result should be something like this</p>
-<div class="source"><pre class="prettyprint linenums">The following profiles
are active:
+<div>
+<pre>The following profiles are active:
- appserverConfig (source: settings.xml)</pre></div>
<p>Even though we don't have an activation property, a profile has been listed
as active. Why? Like we mentioned before, a profile that has been set as an
active profile in the <code>settings.xml</code> is automatically activated.</p>
<p>Now if we have something like a profile in the <code>settings.xml</code>
that has been set as an active profile and also triggered a profile in the POM.
Which profile do you think will have an effect on the build?</p>
<div class="source"><pre class="prettyprint linenums"> mvn
help:active-profiles -P appserverConfig-dev</pre></div>
<p>This will list the activated profiles:</p>
-<div class="source"><pre class="prettyprint linenums">The following profiles
are active:
+<div>
+<pre>The following profiles are active:
- appserverConfig-dev (source: pom)
- appserverConfig (source: settings.xml)</pre></div>
Modified: maven/website/content/guides/introduction/introduction-to-the-pom.html
==============================================================================
--- maven/website/content/guides/introduction/introduction-to-the-pom.html
(original)
+++ maven/website/content/guides/introduction/introduction-to-the-pom.html Sat
Jun 6 09:01:52 2020
@@ -375,7 +375,8 @@ Brett Porter" />
<h5><a name="The_Scenario"></a>The Scenario</h5>
<p>However, that would work if the parent project was already installed in our
local repository or was in that specific directory structure (parent
<code>pom.xml</code> is one directory higher than that of the module's
<code>pom.xml</code>).</p>
<p>But what if the parent is not yet installed and if the directory structure
is as in the following example?</p>
-<div class="source"><pre class="prettyprint linenums">.
+<div>
+<pre>.
|-- my-module
| `-- pom.xml
`-- parent
@@ -417,7 +418,8 @@ Brett Porter" />
<version>1</version>
</project></pre></div>
<p><b>directory structure</b></p>
-<div class="source"><pre class="prettyprint linenums">.
+<div>
+<pre>.
|-- my-module
| `-- pom.xml
`-- pom.xml</pre></div></section><section>
@@ -440,7 +442,8 @@ Brett Porter" />
<h4><a name="Example_4">Example 4</a></h4><section>
<h5><a name="The_Scenario"></a>The Scenario</h5>
<p>But what if we change the directory structure to the following:</p>
-<div class="source"><pre class="prettyprint linenums">.
+<div>
+<pre>.
|-- my-module
| `-- pom.xml
`-- parent
@@ -486,7 +489,8 @@ Brett Porter" />
<version>1</version>
</project></pre></div>
<p>and this <b>directory structure</b></p>
-<div class="source"><pre class="prettyprint linenums">.
+<div>
+<pre>.
|-- my-module
| `-- pom.xml
`-- parent
Modified:
maven/website/content/guides/mini/guide-building-for-different-environments.html
==============================================================================
---
maven/website/content/guides/mini/guide-building-for-different-environments.html
(original)
+++
maven/website/content/guides/mini/guide-building-for-different-environments.html
Sat Jun 6 09:01:52 2020
@@ -183,8 +183,7 @@ src/
<li><code>environment.test.properties</code> - This is the variant for the
test environment.</li>
<li><code>environment.prod.properties</code> - This is basically the same as
the test variant and will be used in the production environment.
<p>In the project descriptor, you need to configure the different profiles.
Only the test profile is showed here.</p>
-<div>
-<pre> <profiles>
+<div class="source"><pre class="prettyprint linenums"> <profiles>
<profile>
<id>test</id>
<build>
Modified: maven/website/content/guides/mini/guide-configuring-maven.html
==============================================================================
--- maven/website/content/guides/mini/guide-configuring-maven.html (original)
+++ maven/website/content/guides/mini/guide-configuring-maven.html Sat Jun 6
09:01:52 2020
@@ -174,8 +174,7 @@
<p>You can specify your user configuration in
<code>${user.home}/.m2/settings.xml</code>. A <a
href="../../maven-settings/settings.html">full reference</a> to the
configuration file is available. This section will show how to make some common
configurations. Note that the file is not required - defaults will be used if
it is not found.</p><section>
<h3><a name="Configuring_your_Local_Repository"></a>Configuring your Local
Repository</h3>
<p>The location of your local repository can be changed in your user
configuration. The default value is
<code>${user.home}/.m2/repository/</code>.</p>
-<div>
-<pre><settings>
+<div class="source"><pre class="prettyprint linenums"><settings>
...
<localRepository>/path/to/local/repo/</localRepository>
...
@@ -195,8 +194,7 @@
<p>Repositories to deploy to are defined in a project in the
<code><distributionManagement></code> section. However, you cannot put
your username, password, or other security settings in that project. For that
reason, you should add a server definition to your own settings with an
<code>id</code> that matches that of the deployment repository in the
project.</p>
<p>In addition, some repositories may require authorization to download from,
so the corresponding settings can be specified in a <code>server</code> element
in the same way.</p>
<p>Which settings are required will depend on the type of repository you are
deploying to. As of the first release, only SCP deployments and file
deployments are supported by default, so only the following SCP configuration
is needed:</p>
-<div>
-<pre><settings>
+<div class="source"><pre class="prettyprint linenums"><settings>
...
<servers>
<server>
Modified: maven/website/content/guides/mini/guide-creating-archetypes.html
==============================================================================
--- maven/website/content/guides/mini/guide-creating-archetypes.html (original)
+++ maven/website/content/guides/mini/guide-creating-archetypes.html Sat Jun 6
09:01:52 2020
@@ -200,7 +200,8 @@
<li><code><modules></code> : Modules definition</li></ul>
<p>At this point one can only specify individual files to be created but not
empty directories.</p>
<p>Thus the quickstart archetype shown above defines the following directory
structure:</p>
-<div class="source"><pre class="prettyprint linenums">
+<div>
+<pre>
archetype
|-- pom.xml
`-- src
Modified: maven/website/content/guides/mini/guide-encryption.html
==============================================================================
--- maven/website/content/guides/mini/guide-encryption.html (original)
+++ maven/website/content/guides/mini/guide-encryption.html Sat Jun 6 09:01:52
2020
@@ -193,7 +193,8 @@ Robert Scholte" />
<div class="source"><pre class="prettyprint linenums">mvn
--encrypt-master-password <password></pre></div>
<p><i>Note:</i> Since Maven 3.2.1 the password argument should no longer be
used (see <a href="#Tips">Tips</a> below for more information). Maven will
prompt for the password. Earlier versions of Maven will not prompt for a
password, so it must be typed on the command-line in plaintext.</p>
<p>This command will produce an encrypted version of the password, something
like</p>
-<div class="source"><pre class="prettyprint
linenums">{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+9EF1iFQyJQ=}</pre></div>
+<div>
+<pre>{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+9EF1iFQyJQ=}</pre></div>
<p>Store this password in the
<code>${user.home}/.m2/settings-security.xml</code>; it should look like</p>
<div class="source"><pre class="prettyprint linenums"><settingsSecurity>
<master>{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+9EF1iFQyJQ=}</master>
@@ -204,7 +205,8 @@ Robert Scholte" />
<div class="source"><pre class="prettyprint linenums">mvn --encrypt-password
<password></pre></div>
<p><i>Note:</i>Just like <code>--encrypt-master-password</code> the password
argument should no longer be used since Maven 3.2.1 (see <a href="#Tips">Tips
below for more information.</a>).</p>
<p>This command produces an encrypted version of it, something like</p>
-<div class="source"><pre class="prettyprint
linenums">{COQLCE6DU6GtcS5P=}</pre></div>
+<div>
+<pre>{COQLCE6DU6GtcS5P=}</pre></div>
<p>Copy and paste it into the servers section of your
<code>settings.xml</code> file. This will look like:</p>
<div class="source"><pre class="prettyprint linenums"><settings>
...
@@ -252,9 +254,11 @@ Robert Scholte" />
<h4><a
name="Escaping_curly-brace_literals_in_your_password_.28Since:_Maven_2.2.0.29"></a>Escaping
curly-brace literals in your password <i>(Since: Maven 2.2.0)</i></h4>
<p>At times, you might find that your password (or the encrypted form of it)
contains '{' or '}' as a literal value. If you added such a password as-is to
your settings.xml file, you would find that Maven does strange things with it.
Specifically, Maven treats all the characters preceding the '{' literal, and
all the characters after the '}' literal, as comments. Obviously, this is not
the behavior you want. What you really need is a way of <b>escaping</b> the
curly-brace literals in your password.</p>
<p>You can do this with the widely used '\' escape character. If your password
looks like this:</p>
-<div class="source"><pre class="prettyprint
linenums">jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+{EF1iFQyJQ=</pre></div>
+<div>
+<pre>jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+{EF1iFQyJQ=</pre></div>
<p>Then, the value you would add to your settings.xml looks like this:</p>
-<div class="source"><pre class="prettyprint
linenums">{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+\{EF1iFQyJQ=}</pre></div></section><section>
+<div>
+<pre>{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+\{EF1iFQyJQ=}</pre></div></section><section>
<h4><a name="Password_Security"></a>Password Security</h4>
<p>Editing <code>settings.xml</code> and running the above commands can still
leave your password stored locally in plaintext. You may want to check the
following locations:</p>
<ul>
Modified: maven/website/content/guides/mini/guide-maven-classloading.html
==============================================================================
--- maven/website/content/guides/mini/guide-maven-classloading.html (original)
+++ maven/website/content/guides/mini/guide-maven-classloading.html Sat Jun 6
09:01:52 2020
@@ -174,8 +174,7 @@ Anders Kristian Andersen" />
<h3><a name="a1._System_Classloader"></a>1. <a
name="System_Classloader">System Classloader</a></h3>
<p>Maven uses the <a class="externalLink"
href="https://codehaus-plexus.github.io/plexus-classworlds/";>Plexus
Classworlds</a> classloading framework with which we create our classloader
graph. If you look in your <code>${maven.home}/boot</code> directory you will
see a single JAR which is the Classworlds JAR we use to boot the classloader
graph. The Classworlds JAR is the only element of the Java
<code>CLASSPATH</code> and Classworlds then builds the other classloaders or
realms in Classworlds terminology.</p>
<p>An Ant script like this will show the contents of the system
classloader:</p>
-<div>
-<pre> <target name="info">
+<div class="source"><pre class="prettyprint linenums"> <target
name="info">
<echo>java.class.path=${java.class.path}</echo>
</target></pre></div></section><section>
<h3><a name="a2._Core_Classloader"></a>2. <a name="Core_Classloader">Core
Classloader</a></h3>
@@ -184,8 +183,7 @@ Anders Kristian Andersen" />
<h3><a name="a3._Plugin_Classloaders"></a>3. <a
name="Plugin_Classloaders">Plugin Classloaders</a></h3>
<p>After that, each plugin has its own classloader that is a child of Maven's
core classloader. The classes in this classloader are taken from the
dependencies in the plugin's dependency list.</p>
<p>Users can add dependencies to this classloader by adding dependencies to a
plugin in the <code><a
href="/ref/current/maven-model/maven.html#class_plugin">plugins/plugin</a></code>
section of their project <code>pom.xml</code>. Here is a sample of adding
<code>ant-nodeps</code> to the plugin classloader of the Antrun Plugin and
hereby enabling the use of additional/optional Ant tasks:</p>
-<div>
-<pre> <plugin>
+<div class="source"><pre class="prettyprint linenums">
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.3</version>
Modified: maven/website/content/guides/mini/guide-new-committers.html
==============================================================================
--- maven/website/content/guides/mini/guide-new-committers.html (original)
+++ maven/website/content/guides/mini/guide-new-committers.html Sat Jun 6
09:01:52 2020
@@ -123,7 +123,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h2><a name="Guide_for_new_commiters"></a>Guide for new commiters</h2>
+<h2><a name="Guide_for_new_committers"></a>Guide for new committers</h2>
<p>First thing is to sort out some administrative tasks. Before your account
is created and commit access granted you must complete and fax back to Apache
the <a class="externalLink"
href="http://www.apache.org/licenses/#clas";>Committer's License
Agreement</a>.</p>
<p>While this process is sorting itself out it is recommended that you peruse
the various guides provided by Apache. All the guides are located in the <a
class="externalLink" href="http://www.apache.org/dev/";>Development
Infrastructure Information</a>.</p>
<p>Of particular interest is the <a class="externalLink"
href="http://www.apache.org/dev/committers.html";>Committer's FAQ</a> and the <a
class="externalLink"
href="http://www.apache.org/dev/new-committers-guide.html";>New Committer's
Guide</a>.</p>
Modified: maven/website/content/guides/mini/guide-snippet-macro.html
==============================================================================
--- maven/website/content/guides/mini/guide-snippet-macro.html (original)
+++ maven/website/content/guides/mini/guide-snippet-macro.html Sat Jun 6
09:01:52 2020
@@ -150,16 +150,14 @@
<p>See the Doxia <a href="/doxia/macros/index.html#Snippet_Macro">Macros
Guide</a> for more information and examples.</p><section>
<h3><a name="Snippets_in_Sources"></a>Snippets in Sources</h3><section>
<h4><a name="Java"></a>Java</h4>
-<div>
-<pre> // START SNIPPET: snip-id
+<div class="source"><pre class="prettyprint linenums"> // START SNIPPET:
snip-id
public static void main( String[] args )
{
System.out.println( "Hello World!" );
}
// END SNIPPET: snip-id</pre></div></section><section>
<h4><a name="XML"></a>XML</h4>
-<div>
-<pre> <!-- START SNIPPET: snip-id -->
+<div class="source"><pre class="prettyprint linenums"> <!-- START SNIPPET:
snip-id -->
<navigation-rule>
<from-view-id>/logon.jsp</from-view-id>
<navigation-case>
@@ -169,8 +167,7 @@
</navigation-rule>
<!-- END SNIPPET: snip-id --></pre></div></section><section>
<h4><a name="JSP"></a>JSP</h4>
-<div>
-<pre> <%-- START SNIPPET: snip-id --%>
+<div class="source"><pre class="prettyprint linenums"> <%-- START SNIPPET:
snip-id --%>
<ul>
<li><a
href="newPerson!input.action">Create</a> a new
person</li>
<li><a href="listPeople.action">List</a> all
people</li>
@@ -178,13 +175,11 @@
<%-- END SNIPPET: snip-id --%></pre></div></section></section><section>
<h3><a name="Snippets_in_Documentation"></a>Snippets in
Documentation</h3><section>
<h4><a name="APT"></a>APT</h4>
-<div>
-<pre> %{snippet|id=snip-id|url=http://svn.example.com/path/to/Sample.java}
+<div class="source"><pre class="prettyprint linenums">
%{snippet|id=snip-id|url=http://svn.example.com/path/to/Sample.java}
%{snippet|id=snip-id|url=file:///path/to/Sample.java}</pre></div>
<p>As of doxia-core version 1.0-alpha-9, a 'file' parameter is also available.
If a full path is not specified, the location is assumed to be relative to
${basedir}.</p>
-<div>
-<pre> ~~ Since doxia-core 1.0-alpha-9
+<div class="source"><pre class="prettyprint linenums"> ~~ Since doxia-core
1.0-alpha-9
%{snippet|id=abc|file=src/main/webapp/index.jsp}</pre></div>
<ul>
<li>Macros in apt <b>must not</b> be indented.</li>
Modified:
maven/website/content/guides/mini/guide-using-one-source-directory.html
==============================================================================
--- maven/website/content/guides/mini/guide-using-one-source-directory.html
(original)
+++ maven/website/content/guides/mini/guide-using-one-source-directory.html Sat
Jun 6 09:01:52 2020
@@ -159,8 +159,7 @@
+- module/
+- Module.java</pre></div>
<p>First, you set up your <code>pom.xml</code> at the top level not to produce
anything, but to include the other modules we plan to create:</p>
-<div>
-<pre><project>
+<div class="source"><pre class="prettyprint linenums"><project>
<artifactId>my-parent</artifactId>
<packaging>pom</packaging>
...
@@ -170,8 +169,7 @@
</modules>
</project></pre></div>
<p>Next, the modules themselves are created. Here is the
<code>core/pom.xml</code> file you should create. The one in the
<code>module</code> subdirectory will be similar.</p>
-<div>
-<pre><project>
+<div class="source"><pre class="prettyprint linenums"><project>
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>my-groupId</groupId>
Modified: maven/website/content/guides/mini/guide-using-toolchains.html
==============================================================================
--- maven/website/content/guides/mini/guide-using-toolchains.html (original)
+++ maven/website/content/guides/mini/guide-using-toolchains.html Sat Jun 6
09:01:52 2020
@@ -201,27 +201,27 @@ Karl Heinz Marbaise" />
<td align="center">jdk</td>
<td align="left"><code><a class="externalLink"
href="https://www.mojohaus.org/animal-sniffer/animal-sniffer-maven-plugin/";>animal-sniffer-maven-plugin</a></code></td>
<td align="left">1.3</td>
-<td align="left">Codehaus Mojo</td></tr>
+<td align="left">MojoHaus</td></tr>
<tr class="a">
<td align="center">jdk</td>
<td align="left"><code><a class="externalLink"
href="https://www.mojohaus.org/cassandra-maven-plugin/";>cassandra-maven-plugin</a></code></td>
<td align="left">0.7.0-1</td>
-<td align="left">Codehaus Mojo</td></tr>
+<td align="left">MojoHaus</td></tr>
<tr class="b">
<td align="center">jdk</td>
<td align="left"><code><a class="externalLink"
href="https://www.mojohaus.org/exec-maven-plugin/";>exec-maven-plugin</a></code></td>
<td align="left">1.1.1</td>
-<td align="left">Codehaus Mojo</td></tr>
+<td align="left">MojoHaus</td></tr>
<tr class="a">
<td align="center">jdk</td>
<td align="left"><code><a class="externalLink"
href="https://www.mojohaus.org/jdiff-maven-plugin/";>jdiff-maven-plugin</a></code></td>
<td align="left">1.0-beta-1-SNAPSHOT</td>
-<td align="left">Codehaus Mojo</td></tr>
+<td align="left">MojoHaus</td></tr>
<tr class="b">
<td align="center">jdk</td>
<td align="left"><code><a class="externalLink"
href="https://www.mojohaus.org/keytool/keytool-maven-plugin/";>keytool-maven-plugin</a></code></td>
<td align="left">1.4</td>
-<td align="left">Codehaus Mojo</td></tr>
+<td align="left">MojoHaus</td></tr>
<tr class="a">
<td align="center">protobuf</td>
<td align="left"><code><a class="externalLink"
href="http://sergei-ivanov.github.io/maven-protoc-plugin/examples/protobuf-toolchain.html";>maven-protoc-plugin</a></code></td>
Modified: maven/website/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
