Hi folks,
We have fixed a few bugs since Apache Commons JCS 3.2 was released, so I would
like to release Apache Commons JCS 3.2.1.
Apache Commons JCS 3.2.1 rc1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1 (svn revision
68312)
The Git tag common
My vote:
> Am 04.04.2024 um 16:49 schrieb Thomas Vandahl :
>
> Hi folks,
>
> We have fixed a few bugs since Apache Commons JCS 3.2 was released, so I
> would like to release Apache Commons JCS 3.2.1.
>
> [X] +1 Release these artifacts
> [ ] +0 OK, but...
> [ ] -0 OK, but really should fix..
Hi Thomas,
The build is not working for me. Are you able to tell me what could be
wrong with my environment, please?
commit 0b20664b6c60b025cfe0e95c33e86f3239822a12 (HEAD, tag:
commons-jcs3-3.2.1-rc1)
Author: Thomas Vandahl
Date: Thu Apr 4 14:47:16 2024 +0200
[maven-release-plugin] prepar
Hi Thomas,
Thank you for preparing a release candidate.
Something looks confusing in the source tree:
In git master marked as version 3.2.2-SNAPSHOT, all of the Maven
modules follow the normal naming convention where directory names are
artifact IDs, for example, "commons-jcs3-core":
https://git
Note that the parent pom is way behind in versions but I am not sure
it matters here (aside from not getting JPMS modules almost for free).
Gary
On Thu, Apr 4, 2024 at 3:48 PM Bruno Kinoshita wrote:
>
> Hi Thomas,
>
> The build is not working for me. Are you able to tell me what could be
> wrong
I think it is better to keep the release notes as a _history_ instead
of only the latest. This lets you see what you're getting when
migrating from several versions back.
Gary
On Thu, Apr 4, 2024 at 10:52 AM Thomas Vandahl wrote:
>
> Hi folks,
>
> We have fixed a few bugs since Apache Commons JC
FWIW, I can run the default goal, IOW, just `mvn` on the command line.
Running `mvn clean install site` runs successfully using:
openjdk version "17.0.10" 2024-01-16
OpenJDK Runtime Environment Homebrew (build 17.0.10+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.10+0, mixed mode, sharing)
Ap
This:
(file://${basedir}/internal-repository):
makes it look like a variable interpolation issue, maybe.
Can you try with Maven 3.9.6 (the latest).
Gary
On Thu, Apr 4, 2024 at 3:48 PM Bruno Kinoshita wrote:
>
> Hi Thomas,
>
> The build is not working for me. Are you able to tell me what coul
Another note:
The changes.xml contains XML not supported by the VM file, for
example, all of the JIRA issue IDs are lost.
Gary
On Thu, Apr 4, 2024 at 10:52 AM Thomas Vandahl wrote:
>
> Hi folks,
>
> We have fixed a few bugs since Apache Commons JCS 3.2 was released, so I
> would like to releas
After being successful on macOS, I am seeing the following _repeatable_
failures on Windows 10 running the default Maven goal (just `mvn`):
...
[INFO] Running
org.apache.commons.jcs3.utils.discovery.UDPDiscoverySenderEncryptedUnitTest
[ERROR] Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Tim
We have fixed a few bugs since Apache Commons IO 2.16.0 was released,
so I would like to release Apache Commons IO 2.16.1.
Apache Commons IO 2.16.1 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/io/2.16.1-RC1 (svn
revision 68319)
The Git tag commons-io-2.16.1
+1
Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
Maven home: /opt/apache-maven-3.8.5
Java version: 17.0.10, vendor: Private Build, runtime:
/usr/lib/jvm/java-17-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.15.0-101-generic", arch: "amd
I am canceling this vote to merge https://github.com/apache/commons-io/pull/609
RC2 is coming soon.
Gary
On Thu, Apr 4, 2024 at 4:54 PM Gary Gregory wrote:
>
> We have fixed a few bugs since Apache Commons IO 2.16.0 was released,
> so I would like to release Apache Commons IO 2.16.1.
>
> Apache
[ The difference with RC1 is https://github.com/apache/commons-io/pull/609 ]
We have fixed a few bugs since Apache Commons IO 2.16.0 was released,
so I would like to release Apache Commons IO 2.16.1.
Apache Commons IO 2.16.1 RC2 is available for review here:
https://dist.apache.org/repos/dist
Hi Gary,
> Am 04.04.2024 um 21:58 schrieb Gary Gregory :
>
> Hi Thomas,
>
> Thank you for preparing a release candidate.
>
> Something looks confusing in the source tree:
>
> In git master marked as version 3.2.2-SNAPSHOT, all of the Maven
> modules follow the normal naming convention where di
Hi Gary,
> Am 04.04.2024 um 21:59 schrieb Gary Gregory :
>
> Note that the parent pom is way behind in versions but I am not sure
> it matters here (aside from not getting JPMS modules almost for free).
Yes, again: intentional. This being a bug fix release for 3.2, I did not want
to change too
Hi Gary,
> Am 04.04.2024 um 22:05 schrieb Gary Gregory :
>
> I think it is better to keep the release notes as a _history_ instead
> of only the latest. This lets you see what you're getting when
> migrating from several versions back.
I don't quite get your point, I'm afraid. Isn't this what th
Hi Gary,
> Am 04.04.2024 um 22:22 schrieb Gary Gregory :
>
> Another note:
>
> The changes.xml contains XML not supported by the VM file, for
> example, all of the JIRA issue IDs are lost.
>
I see working JIRA links in
https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/site/changes-
18 matches
Mail list logo
