You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by kh...@apache.org on 2015/04/10 20:24:18 UTC
svn commit: r1672722 - in /maven/site/trunk/content/apt/developers:
release/maven-project-release-procedure.apt
website/deploy-component-reference-documentation.apt
Author: khmarbaise
Date: Fri Apr 10 18:24:17 2015
New Revision: 1672722
URL: http://svn.apache.org/r1672722
Log:
Changed the JIRA location for the release template
Fixed link error in deploy-component-reference-documentation.apt
Added a note about chaning into target/checkout folder in case of
release preparation.
Modified:
maven/site/trunk/content/apt/developers/release/maven-project-release-procedure.apt
maven/site/trunk/content/apt/developers/website/deploy-component-reference-documentation.apt
Modified: maven/site/trunk/content/apt/developers/release/maven-project-release-procedure.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/content/apt/developers/release/maven-project-release-procedure.apt?rev=1672722&r1=1672721&r2=1672722&view=diff
==============================================================================
--- maven/site/trunk/content/apt/developers/release/maven-project-release-procedure.apt (original)
+++ maven/site/trunk/content/apt/developers/release/maven-project-release-procedure.apt Fri Apr 10 18:24:17 2015
@@ -2,8 +2,9 @@
Releasing A Maven Project
-----
Jason van Zyl
+ Karl Heinz Marbaise
-----
- 2014-03-12
+ 2015-04-10
-----
~~ Licensed to the Apache Software Foundation (ASF) under one
@@ -85,10 +86,10 @@ Subject: [VOTE] Release Apache Maven XXX
Hi,
We solved N issues:
-http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=XXX&styleName=Html&version=XXX
+https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=XXXXXX&version=YYYYYYY
There are still a couple of issues left in JIRA:
-http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=XXX&status=1
+https://issues.apache.org/jira/issues/?jql=project%20%3D%20XXXXXXXXXX%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
Staging repo:
https://repository.apache.org/content/repositories/maven-[YOUR REPOSITORY ID]/
Modified: maven/site/trunk/content/apt/developers/website/deploy-component-reference-documentation.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/content/apt/developers/website/deploy-component-reference-documentation.apt?rev=1672722&r1=1672721&r2=1672722&view=diff
==============================================================================
--- maven/site/trunk/content/apt/developers/website/deploy-component-reference-documentation.apt (original)
+++ maven/site/trunk/content/apt/developers/website/deploy-component-reference-documentation.apt Fri Apr 10 18:24:17 2015
@@ -54,7 +54,7 @@ How components reference documentation p
component name and <<<xxx>>> can be:
* the component type, like <<<shared>>>, <<<plugins>>>, <<<skins>>>, ... (see
- {{/shared-archives/}}, {{/plugins-archives/}}, {{/skins/archives/}})
+ {{/shared-archives/}}, {{/plugins-archives/}}, {{/skins-archives/}})
* the component name for standalone components, like <<<archetype>>>, <<<plugin-tools>>>, <<<surefire>>>, <<<wagon>>>, ...
(see {{/archetype-archives/}}, {{/plugin-tools-archives/}}, {{/surefire-archives/}}, {{/wagon-archives/}})
@@ -65,6 +65,8 @@ How components reference documentation p
[[0]] prerequisite: eventually build the component if it has not been done previously, or some reports may miss build or integration information:
+ Notice: In cases where you have prepared a release you can simple change into <<<target/checkout>>> folder and continue with 2.
+
+----------+
mvn -Prun-its install
+----------+