(axis-axis2-java-core) branch dependabot/maven/org.apache.maven.plugins-maven-clean-plugin-3.4.1 created (now 27790c067c)

[github-bot]

This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch 
dependabot/maven/org.apache.maven.plugins-maven-clean-plugin-3.4.1
in repository https://gitbox.apache.org/repos/asf/axis-axis2-java-core.git


  at 27790c067c Bump org.apache.maven.plugins:maven-clean-plugin from 3.4.0 
to 3.4.1

No new revisions were added by this update.

(axis-axis2-java-core) branch master updated: More release process updates

[robertlazarski]

This is an automated email from the ASF dual-hosted git repository.

robertlazarski pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/axis-axis2-java-core.git


The following commit(s) were added to refs/heads/master by this push:
 new 4896a31ff9 More release process updates
4896a31ff9 is described below

commit 4896a31ff9a5907935775d1368a1e4131bcb27d4
Author: Robert Lazarski 
AuthorDate: Wed Feb 19 10:41:38 2025 -1000

More release process updates
---
 src/site/markdown/release-process.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/src/site/markdown/release-process.md 
b/src/site/markdown/release-process.md
index c3384a4793..2c1de667e1 100644
--- a/src/site/markdown/release-process.md
+++ b/src/site/markdown/release-process.md
@@ -23,6 +23,8 @@ Release Process
 Release process overview
 
 
+### Update: Since the 1.8.x series we have released from git master without 
branches. Skip to Performing a Release. We may or may not use branches again in 
the future. 
+
 ### Cutting a branch
 
 *   When a release is ready to go, release manager (RM) puts
@@ -185,7 +187,7 @@ The created artifacts i.e. zip files can be checked with, 
for example, sha512sum
 mvn release:perform
 
 3.  Login to Nexus and close the staging repository. For more details about 
this step, see
-
[here](https://maven.apache.org/developers/release/maven-project-release-procedure.html).
+
[here](https://maven.apache.org/developers/release/maven-project-release-procedure.html)
 and [here](https://infra.apache.org/publishing-maven-artifacts.html#promote).
 
 4.  Execute the `target/checkout/etc/dist.py` script to upload the source and 
binary distributions to the development area of the https://dist.apache.org/repos/dist/";> repository. 
 

(axis-axis2-java-core) branch master updated: More release process updates

[robertlazarski]

This is an automated email from the ASF dual-hosted git repository.

robertlazarski pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/axis-axis2-java-core.git


The following commit(s) were added to refs/heads/master by this push:
 new cead5e5bd6 More release process updates
cead5e5bd6 is described below

commit cead5e5bd634460dbe672248cd81d332a6f722c5
Author: Robert Lazarski 
AuthorDate: Wed Feb 19 08:26:40 2025 -1000

More release process updates
---
 src/site/markdown/release-process.md | 12 ++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/src/site/markdown/release-process.md 
b/src/site/markdown/release-process.md
index a6a8158f5d..c3384a4793 100644
--- a/src/site/markdown/release-process.md
+++ b/src/site/markdown/release-process.md
@@ -105,9 +105,15 @@ Verify that the code meets the basic requirements for 
being releasable:
 
 mvn clean install -Papache-release
 
-3.  Check that the source distribution is buildable.
+You may also execute a dry run of the release process: mvn release:prepare 
-DdryRun=true. In a dry run, the generated zip files will still be labled as 
SNAPSHOT. After this, you need to clean up using the following command: mvn 
release:clean
 
-4.  Check that the source tree is buildable with an empty local Maven 
repository.
+3. Check that the Maven site can be generated and deployed successfully, and 
that it has the expected content.
+
+To generate the entire documentation in one place, complete with working 
inter-module links, execute the site-deploy phase (and check the files under 
target/staging). A quick and reliable way of doing that is to use the following 
command: mvn -Dmaven.test.skip=true clean package site-deploy
+
+4.  Check that the source distribution is buildable.
+
+5.  Check that the source tree is buildable with an empty local Maven 
repository.
 
 If any problems are detected, they should be fixed on the trunk (except for 
issues specific to the
 release branch) and then merged to the release branch.
@@ -200,6 +206,8 @@ The created artifacts i.e. zip files can be checked with, 
for example, sha512sum
 Now go to the `target/scmpublish-checkout` directory (relative to 
`target/checkout`) and check that there
 are no unexpected changes to the site. Then commit the changes.
 
+The root dir of axis-site has a .asf.yaml file, referenced here at 
target/scmpublish-checkout/.asf.yaml, that is  https://github.com/apache/infrastructure-asfyaml/blob/main/README.md";> 
documented here. 
+
 7.  Start the release vote by sending a mail to `java-...@axis.apache.org`.
 The mail should mention the following things: