svn commit: r1878064 - in /maven/website/content: maven-jsr330.html maven-site-1.0-site.jar

[sv...@apache.org]

Author: svn-site-role
Date: Sat May 23 16:41:16 2020
New Revision: 1878064

Log:
Site checkin for project Apache Maven Site

Modified:
    maven/website/content/maven-jsr330.html
    maven/website/content/maven-site-1.0-site.jar

Modified: maven/website/content/maven-jsr330.html
==============================================================================
--- maven/website/content/maven-jsr330.html (original)
+++ maven/website/content/maven-jsr330.html Sat May 23 16:41:16 2020
@@ -160,8 +160,8 @@ under the License.
 <section>
 <h2><a name="Why_JSR-330.3F"></a>Why JSR-330?</h2>
 <p>Maven has a long history of using dependency injection (DI) by way of <a class="externalLink" href="https://codehaus-plexus.github.io/">Plexus</a>, so the intent of using <a class="externalLink" href="https://www.jcp.org/en/jsr/detail?id=330">JSR-330</a> is to replace a custom DI mechanism with something standard. The implementation Maven uses - since 3.0-beta-3 - is named <a class="externalLink" href="https://eclipse.org/sisu/">Sisu</a> and is based on <a class="externalLink" href="https://code.google.com/p/google-guice/">Guice 3.x</a>, which directly supports JSR-330.</p>
-<p>If you are using <a class="externalLink" href="https://codehaus-plexus.github.io/plexus-containers/">Plexus annotations and APIs</a> currently, there is no rush to switch and no big bang conversions are necessary: Plexus, JSR-330 and Guice APIs all happily co-exist within Maven's core and you can choose to use JSR-330 when you wish. There are hundreds of components written using the Plexus APIs, particularly components and plugins compatible with Maven 2, then those APIs will be supported forever, or at least until Maven fully drops Maven 2 support.</p>
-<p>If you want to use JSR-330, you must understand that your code won't be compatible with Maven 2 or 3.0.x but only with Maven 3.1.0+: even if JSR-330 is available in core since Maven 3.0-beta-3, it was made available to plugins and extensions only in Maven 3.1.0 (see <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5343">MNG-5343</a> for more details).</p>
+<p>If you are using <a class="externalLink" href="https://codehaus-plexus.github.io/plexus-containers/">Plexus annotations and APIs</a> currently, there is no rush to switch and no big bang conversions are necessary: Plexus, JSR-330 and Guice APIs all happily co-exist within Maven's core and you can choose to use JSR-330 when you wish. There are hundreds of components written using the Plexus APIs.</p>
+<p>If you want to use JSR-330, you must understand that your code won't be compatible with Maven 3.0.x but only with Maven 3.1.0 and later. Even though JSR-330 has been available in core since Maven 3.0-beta-3, it was made available to plugins and extensions only in Maven 3.1.0 (see <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5343">MNG-5343</a> for more details).</p>
 <p>If you are interested the background of moving from Plexus to Guice and JSR-330, you can refer to the following articles:</p>
 <ul>
 

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