svn commit: r1743934 - in /maven/site/trunk/content: apt/plugin-developers/common-bugs.apt markdown/docs/3.3.1/release-notes.md markdown/reference/maven-classloading.md

[hb...@apache.org]

Author: hboutemy
Date: Sun May 15 18:05:12 2016
New Revision: 1743934

URL: http://svn.apache.org/viewvc?rev=1743934&view=rev
Log:
updated Jira url

Modified:
    maven/site/trunk/content/apt/plugin-developers/common-bugs.apt
    maven/site/trunk/content/markdown/docs/3.3.1/release-notes.md
    maven/site/trunk/content/markdown/reference/maven-classloading.md

Modified: maven/site/trunk/content/apt/plugin-developers/common-bugs.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/content/apt/plugin-developers/common-bugs.apt?rev=1743934&r1=1743933&r2=1743934&view=diff
==============================================================================
--- maven/site/trunk/content/apt/plugin-developers/common-bugs.apt (original)
+++ maven/site/trunk/content/apt/plugin-developers/common-bugs.apt Sun May 15 18:05:12 2016
@@ -181,7 +181,7 @@ File path = new File( new URI( url.toExt
   class accepts malformed URLs which will make the constructor of <<<URI>>> throw an exception. And indeed, class
   loaders from Sun JREs up to Java 1.4 will deliver malformed URLs when queried for a resource. Likewise, the class
   loaders employed by Maven 2.x deliver malformed resource URLs regardless of the JRE version (see
-  {{{http://jira.codehaus.org/browse/MNG-3607}MNG-3607}}).
+  {{{https://issues.apache.org/jira/browse/MNG-3607}MNG-3607}}).
 
   For all these reasons, it is recommended to use
   <<<{{{http://commons.apache.org/io/api-release/org/apache/commons/io/FileUtils.html#toFile(java.net.URL)}FileUtils.toFile()}}>>>
@@ -462,7 +462,7 @@ public MyMojo extends AbstractMojo
   Up to Maven 2.0.5, version 1.1 of the artifact <<<plexus-utils>>> was included in the Maven core class loader which
   is shared with the plugin class realm. This effectively prevented plugins from using another/newer version of
   <<<plexus-utils>>>. This has been solved starting with Maven 2.0.6 by shading (most of) the classes from
-  <<<plexus-utils>>> (see {{{http://jira.codehaus.org/browse/MNG-2892}MNG-2892}}).
+  <<<plexus-utils>>> (see {{{https://issues.apache.org/jira/browse/MNG-2892}MNG-2892}}).
 
   In short, plugins that strictly require a newer version of <<<plexus-utils>>> also require Maven 2.0.6 as a minimum.
   Hence, a POM snippet for a Maven plugin like shown below is misleading:

Modified: maven/site/trunk/content/markdown/docs/3.3.1/release-notes.md
URL: http://svn.apache.org/viewvc/maven/site/trunk/content/markdown/docs/3.3.1/release-notes.md?rev=1743934&r1=1743933&r2=1743934&view=diff
==============================================================================
--- maven/site/trunk/content/markdown/docs/3.3.1/release-notes.md (original)
+++ maven/site/trunk/content/markdown/docs/3.3.1/release-notes.md Sun May 15 18:05:12 2016
@@ -226,7 +226,7 @@ mvn exec:java@second-cli
 
 So now you can define more than one configuration for command line executions.
    
- * The Maven team has decided to [drop support for Win9x in launch scripts](https://jira.codehaus.org/browse/MNG-5776)
+ * The Maven team has decided to [drop support for Win9x in launch scripts](https://issues.apache.org/jira/browse/MNG-5776)
    at long last. Yeah.
 
 
@@ -241,10 +241,10 @@ and migrated afterwards to the Apache Ma
 [5]: ../../docs/history.html
 
 [maven-toolchains-plugin]: http://maven.apache.org/plugins/maven-toolchains-plugin/
-[MNG-3891]: https://jira.codehaus.org/browse/MNG-3891
-[MNG-5745]: https://jira.codehaus.org/browse/MNG-5745
-[MNG-5754]: https://jira.codehaus.org/browse/MNG-5754
-[MNG-5771]: https://jira.codehaus.org/browse/MNG-5771
-[MNG-5767]: https://jira.codehaus.org/browse/MNG-5767
-[MNG-5768]: https://jira.codehaus.org/browse/MNG-5768
-[MNG-5780]: https://jira.codehaus.org/browse/MNG-5780
+[MNG-3891]: https://issues.apache.org/jira/browse/MNG-3891
+[MNG-5745]: https://issues.apache.org/jira/browse/MNG-5745
+[MNG-5754]: https://issues.apache.org/jira/browse/MNG-5754
+[MNG-5771]: https://issues.apache.org/jira/browse/MNG-5771
+[MNG-5767]: https://issues.apache.org/jira/browse/MNG-5767
+[MNG-5768]: https://issues.apache.org/jira/browse/MNG-5768
+[MNG-5780]: https://issues.apache.org/jira/browse/MNG-5780

Modified: maven/site/trunk/content/markdown/reference/maven-classloading.md
URL: http://svn.apache.org/viewvc/maven/site/trunk/content/markdown/reference/maven-classloading.md?rev=1743934&r1=1743933&r2=1743934&view=diff
==============================================================================
--- maven/site/trunk/content/markdown/reference/maven-classloading.md (original)
+++ maven/site/trunk/content/markdown/reference/maven-classloading.md Sun May 15 18:05:12 2016
@@ -75,7 +75,7 @@ For projects without build extensions, s
 
 For projects that use build extensions, plugin classloaders are wired to project classloaders. This gives plugin code access to both Maven API packages and packages exported by the project build extensions. Maven will create one and only one classlaoder for each unique plugin+dependencies+buid-extensions combination.
 
-All plugin classloaders use ClassWorlds bootstrap classloader as the parent. This provides relatively clean and therefore consistent plugin classpath, while still allowing plugins access to `-javaagent` classes (see [MNG-4747](http://jira.codehaus.org/browse/MNG-4747)).
+All plugin classloaders use ClassWorlds bootstrap classloader as the parent. This provides relatively clean and therefore consistent plugin classpath, while still allowing plugins access to `-javaagent` classes (see [MNG-4747](https://issues.apache.org/jira/browse/MNG-4747)).
 
 Reporting plugins are wired differently still, but reporting plugins are a special case and are outside of the scope of this document.