On Thu, 27 Oct 2022 at 22:46, Gary Gregory wrote:
>
> Would you mind creating a ticket for the proper Maven plugin?
https://issues.apache.org/jira/browse/MCHANGES-413
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
The tag in the repo is wrong:
git clone https://gitbox.apache.org/repos/asf/commons-compress.git --branch
commons-compress-1.22-RC1 commons-compress-1.22-RC1
Cloning into 'commons-compress-1.22-RC1'...
fatal: Remote branch commons-compress-1.22-RC1 not found in upstream origin
Gary
On 2022/10/2
The branch release-1.22 is where I’m staging the release before merging back to
master. The tag was accidentally named “commons-compress-1.22” which I aliased
to the RC1 tag, but it appears I might not have pushed the second tag. I’ll fix
the tag later today, though in the meantime, you can use
When preparing the 1.1 RC for [numbers] I pushed my tags using:
git push --tags
This seems to have pushed an old tag NUMBERS_1_0_B1_RC1 made by Matt
Juntunen a few days before the official beta RC1 tag. This is pointing
at a different commit from the tags used for the beta release:
commons-numbe
We have fixed quite a few bugs and added some significant enhancements
since Apache Commons Numbers 1.0 was released, so I would like to
release Apache Commons Numbers 1.1.
Apache Commons Numbers 1.1 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/numbers/1.1-R
Hi Matt,
[x] +1 Release these artifacts
Thanks for confirming the tag name.
Build passing successfully using that tag, running `mvn clean test install
site` on
nothing to commit, working tree clean
kinow@ranma:~/Development/java/apache/commons-compress$ mvn -v
Apache Maven 3.8.5 (3599d3414f04
Hi Alex,
[x] +1 Release these artifacts
Built from tag, with `mvn clean test install site` using
Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
Maven home: /opt/apache-maven-3.8.5
Java version: 17.0.4, vendor: Private Build, runtime:
/usr/lib/jvm/java-17-openjdk-amd64
Default lo
I included the wrong link to the changes report. It is here:
https://home.apache.org/~aherbert/commons-numbers-1.1-RC1-site/changes-report.html
Note that this custom site is only required as the commons-release-plugin
does not stage the multi-module site, so it is done manually for review.
I not
Ah good spot Alex. I believe we can sort out these site issues after the
release if needed (in case the site is rendered correctly after the
release/deploy).
Bruno
On Sat, 29 Oct 2022, 9:55 am Alex Herbert, wrote:
> I included the wrong link to the changes report. It is here:
>
>
> https://home
