On Sun, Jul 17, 2022 at 12:49 AM Andreas Veithen-Knowles <
andreas.veit...@gmail.com> wrote:

> How is it that the generated site has links to the 1.8.1 and 1.8.2 release
> notes, although they don't appear in site.xml (
> https://github.com/apache/axis-axis2-java-core/blob/v1.8.2/src/site/site.xml#L60
> )?
>
> Andreas
>
>
I'm glad you mentioned this. This particular issue is that since this step
is not mentioned in
https://axis.apache.org/axis2/java/core/release-process.html.

It is one of about five mysteries that I fixed manually. That issue is #1
in the list below. FYI, I am exclusively on Linux. If anyone has ideas on
the rest, please comment.

I do not expect any of these as showstoppers but rather a TODO list of
fixes. Note that we currently have enough votes to proceed with 1.8.2.

1) The site.xml edits for release notes are not mentioned in
release-process.html.  Will fix in Git.

2) The python script dist.py breaks in several ways on Linux. I am not a
python user. It is not compatible with python3. On python 2 I get a "File
exists" error. Nevertheless it is not a bad choice and the best option is
to fix it.

3) The corba and osgi modules do not build cleanly for javadoc. They need
to be removed from apidocs/pom.xml. We should consider removing corba
entirely.

4) Linux kernel limitation, "Argument list too long" error when running "mvn
-X scm-publish:publish-scm -Dscmpublish.skipCheckin=true" .

5) Link broken:
https://docs.sonatype.org/display/Repository/Closing+a+Staging+Repository.
Will fix in Git with new link:
https://help.sonatype.com/repomanager2/staging-releases/managing-staging-repositories

Reply via email to