You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-commits@maven.apache.org by bu...@apache.org on 2016/02/13 12:33:34 UTC
svn commit: r980307 - in /websites/staging/maven/trunk/content: ./
developers/java6.html maven-site-1.0-site.jar
Author: buildbot
Date: Sat Feb 13 11:33:34 2016
New Revision: 980307
Log:
Staging update by buildbot for maven
Modified:
websites/staging/maven/trunk/content/ (props changed)
websites/staging/maven/trunk/content/developers/java6.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 Feb 13 11:33:34 2016
@@ -1 +1 @@
-1730177
+1730184
Modified: websites/staging/maven/trunk/content/developers/java6.html
==============================================================================
--- websites/staging/maven/trunk/content/developers/java6.html (original)
+++ websites/staging/maven/trunk/content/developers/java6.html Sat Feb 13 11:33:34 2016
@@ -457,8 +457,8 @@
<p>A plugin/component can start using Java 6 features and/or dependencies when the need arises. If there are issues that have already been fixed, but not yet released, the current trunk of the plugin/component must be released first, targeting Java 5. In the announcement for such a final Java 5 version of the plugin/component, we inform the users that this is the last version that will work with Java 5.</p>
<div class="section">
<h3><a name="In_JIRA"></a>In JIRA</h3>
-<p>When a plugin/component decides to switch to Java 6, you should set the description field for the versions in JIRA for the plugin/component, so that it is clear which version works with which version of Java. Mark the last Java 5 compatible version with "Last version to work with Java 5", see <a href="#issues.apache.orgjirabrowseMCHECKSTYLEfixforversion20631">example</a>. Mark the first version that requires Java 6 "This version requires Java 6", see <a href="#issues.apache.orgjirabrowseMCHECKSTYLEfixforversion20762">example</a>.</p>
-<p>Create an issue "Require Java 6" and schedule it for the first Java 6 version, see <a href="#issues.apache.orgjirabrowseMCHECKSTYLE-277">example</a>. Reference this issue when you check in the code changes (see below) into version control</p></div>
+<p>When a plugin/component decides to switch to Java 6, you should set the description field for the versions in JIRA for the plugin/component, so that it is clear which version works with which version of Java. Mark the last Java 5 compatible version with "Last version to work with Java 5", see <a class="externalLink" href="https://issues.apache.org/jira/browse/MCHECKSTYLE/fixforversion/20631">example</a>. Mark the first version that requires Java 6 "This version requires Java 6", see <a class="externalLink" href="https://issues.apache.org/jira/browse/MCHECKSTYLE/fixforversion/20762">example</a>.</p>
+<p>Create an issue "Require Java 6" and schedule it for the first Java 6 version, see <a class="externalLink" href="https://issues.apache.org/jira/browse/MCHECKSTYLE-277">example</a>. Reference this issue when you check in the code changes (see below) into version control</p></div>
<div class="section">
<h3><a name="On_the_plugincomponent_site"></a>On the plugin/component site</h3>
<p>Specify the Java requirements in <tt>index.apt.vm</tt>: "This plugin/component requires Java ${javaVersion}.", see <a class="externalLink" href="https://svn.apache.org/viewvc/maven/plugins/trunk/maven-checkstyle-plugin/src/site/apt/index.apt.vm?r1=1650811&r2=1652771&pathrev=1658048">example</a>. We need to use the variable ${javaVersion} here, because ${maven.compiler.source} does not work in a site.</p></div>
Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.