[COLLECTIONS] Is the changes.xml file automatically updated by pull merge?

[Claude Warren]

-- 
LinkedIn: http://www.linkedin.com/in/claudewarren

Re: [COLLECTIONS] Is the changes.xml file automatically updated by pull merge?

[Alex Herbert]

No. Just add it as a second commit after merge.

On Sun, 12 May 2024, 11:12 Claude Warren,  wrote:

> --
> LinkedIn: http://www.linkedin.com/in/claudewarren
>

Re: [COLLECTIONS] Is the changes.xml file automatically updated by pull merge?

[Gary Gregory]

I usually update changes.xml right after I merge a PR.

Gary

On Sun, May 12, 2024, 6:12 AM Claude Warren  wrote:

> --
> LinkedIn: http://www.linkedin.com/in/claudewarren
>

[CANCEL][VOTE] Release Apache Commons Logging 1.3.2 based on RC2

[Gary Gregory]

I am canceling this RC to fix the release notes.

RC3 coming up...

Gary

On Sun, May 12, 2024, 1:13 AM Piotr P. Karwasz 
wrote:

> Hi Gary,
>
> On Sat, 11 May 2024 at 19:55, Gary Gregory  wrote:
> > Details of changes since 1.3.1 are in the release notes:
> >
> https://dist.apache.org/repos/dist/dev/commons/logging/1.3.2-RC2/RELEASE-NOTES.txt
> >
> https://dist.apache.org/repos/dist/dev/commons/logging/1.3.2-RC2/site/changes-report.html
>
> The `RELEASE-NOTES.txt` file contains the changes for 1.3.1 twice and
> does not contain the changes for 1.3.2.
>
> Piotr
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

[VOTE] Release Apache Commons Logging 1.3.2 based on RC3

[Gary Gregory]

[The only difference with RC2 is the release notes text file]

We have fixed a few bugs and added enhancements since Apache Commons
Logging 1.3.1 was released, so I would like to release Apache Commons
Logging 1.3.2.

Apache Commons Logging 1.3.2 RC3 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/logging/1.3.2-RC3
(svn revision 69111)

The Git tag commons-logging-1.3.2-RC3 commit for this RC is
51ee80926c25ad32cb50700996edf56ef9bb901b which you can browse here:

https://gitbox.apache.org/repos/asf?p=commons-logging.git;a=commit;h=51ee80926c25ad32cb50700996edf56ef9bb901b
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-logging.git
--branch commons-logging-1.3.2-RC3 commons-logging-1.3.2-RC3

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1728/commons-logging/commons-logging/1.3.2/

These are the artifacts and their hashes:

#Release SHA-512s
#Sun May 12 12:28:47 UTC 2024
commons-logging-1.3.2-adapters.jar=ca7783d5658395a34a1cfdaac0717563d4211cbe331f56a639527edf40824ef47b14bc5b194f329f0119d0ce582bd527f32fa0dd5971fbe6947bc35cdf292de0
commons-logging-1.3.2-api.jar=c973a826ad20c0c890ed405632320b3fed1d969079205f69a49327cec282d1cc1223fa0b5646a5de84e31a209c060a5ad6614f38c558482c9bbe2ab0a99d54e0
commons-logging-1.3.2-bin.tar.gz=13fa96d0e119c4e671e17cd391fbbe869642e0c769b6a91ebc29b918c3cd1c173d9e0ac18400d41848b611adbaee2386932121dcef3ab0937a78ecf73dbab4fc
commons-logging-1.3.2-bin.zip=46479bbcdb6c204e97bd006072ce610ac2b0200cb8657b78dfbfa027a293a7746c32ef74bf118eafe0919e81e78ff15354d2124a87a959300e56452a33d0d5b3
commons-logging-1.3.2-bom.json=140a60c1bc7960ffd0e4eb733efc8733778a0228adeaff2dd4d9ee6ffd7bc4f5eb7f6152b18f3d5c662e4041c56cfcd1d4f103c628a9177d5cb475db463c1aea
commons-logging-1.3.2-bom.xml=0f2e5b2b45ed7d22ea5d03b6641b1518e98cf1ff4b641b475ececfe91ca5ea65877d18a4c647116944e71a55ce68a20dc93c3b1b98faa50d2d5b0d1c22a4ac56
commons-logging-1.3.2-javadoc.jar=d8635955b27887aecb7ad3956b4a51c3e543ea85f1dd65eb7bdc7bcac2db417d48321a0a09faf6f8a369b818c4a55810c8ae6f298895aa49571291bd49c448f8
commons-logging-1.3.2-sources.jar=8f83cb0fbdbed75eb0cbac0d53c91bc484e19034640536d376f26706d02427c9db8f64048bf76deaba14f1b4494611755b4cd89830a630f67b43890048a87650
commons-logging-1.3.2-src.tar.gz=9c3a43d0507c16e08d35052e84326206d3cfbfa7c1cb6e6a9d739e7eada92febe3c332185c42220ce12b68b7b95e0ba8bfdcaa233571eca7ec395663f7a262ea
commons-logging-1.3.2-src.zip=933d741489788ba8287e189f4d4b7840623866ba0d7e689d3e2ddf8038926e8bfd7bfbf327542edf1468cd1cf3307a27dc71c971b423902b53c15bc9c8546ec2
commons-logging-1.3.2-test-sources.jar=4264e97c1f0fba85280daa9ca62d233c16e0f626c79606a9dd4db6276fc5da2e5dfc7810af7bbb35308a62f707480f25cc89e9f6c25ef935b3c0e6d8569272c7
commons-logging-1.3.2-tests.jar=fc8a0217379e71e4aee34cfb19eeebf5fab93fb3566eda798ce211adbe46b13e829f89f16665dd613ba31984ef9d78802a9f0b7b1a0a3706b33c7ce3696fc4da
commons-logging_commons-logging-1.3.2.spdx.json=b43a2bcf3b232ba7bbf9c0173e2c1beb4f229dcb6345430d7b67bc4400faf6eb4055b150bed96b44ddb486cbcd68a2f1a7a9a894d416d10c1a37ec3b089a07cb

I have tested this with 'mvn' and 'mvn -V -Prelease -Ptest-deploy -P
jacoco -P japicmp clean package site deploy' using:

openjdk version "21.0.3" 2024-04-16
OpenJDK Runtime Environment Homebrew (build 21.0.3)
OpenJDK 64-Bit Server VM Homebrew (build 21.0.3, mixed mode, sharing)

Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: /usr/local/Cellar/maven/3.9.6/libexec
Java version: 21.0.3, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk/21.0.3/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "14.4.1", arch: "x86_64", family: "mac"

Darwin  23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:11:05
PDT 2024; root:xnu-10063.101.17~1/RELEASE_X86_64 x86_64

Details of changes since 1.3.1 are in the release notes:

https://dist.apache.org/repos/dist/dev/commons/logging/1.3.2-RC3/RELEASE-NOTES.txt

https://dist.apache.org/repos/dist/dev/commons/logging/1.3.2-RC3/site/changes-report.html

Site:

https://dist.apache.org/repos/dist/dev/commons/logging/1.3.2-RC3/site/index.html
(note some *relative* links are broken and the 1.3.2 directories
are not yet created - these will be OK once the site is deployed.)

JApiCmp Report (compared to 1.3.1):

https://dist.apache.org/repos/dist/dev/commons/logging/1.3.2-RC3/site/japicmp.html

RAT Report:

https://dist.apache.org/repos/dist/dev/commons/logging/1.3.2-RC3/site/rat-report.html

KEYS:
  https://downloads.apache.org/commons/KEYS

Please review the release candidate and vote.
This vote will close no sooner than 72 hours from now.

  [ ] +1 Release these artifacts
  [ ] +0 OK, but...
  [ ] -0 OK, but really should fix...
  [ ] -1 I oppose this release because...

Thank you,

Gary Gregory,
Release Manager (using key 86fdc7e2a11262cb)

For following is intended as a helper and refresher for

[JCS] How to proceed? was: Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc2

[Thomas Vandahl]

Hi folks,

how shall we proceed with the release process? We have tests which rely on a 
working multicast configuration. This seems to be a serious obstacle. I can 
exclude the tests so that the build should be runnable by anyone. Downside is, 
that we don't test the feature anymore. 

I'm a bit at a loss on how to tackle this problem. I'm open for suggestions. 
Please help!

Bye, Thomas 

> Am 05.05.2024 um 19:20 schrieb Thomas Vandahl :
> 
> Hi Bruno,
> 
>> Am 02.05.2024 um 22:01 schrieb Bruno Kinoshita :
>> 
>> Tried building the project but alas I think my network has UDP multicast
>> issues?
>> 
>> [ERROR] Failures:
>> [ERROR]   UDPDiscoverySenderEncryptedUnitTest.testPassiveBroadcast:122
>> message not received
>> [ERROR]   UDPDiscoverySenderEncryptedUnitTest.testRemoveBroadcast:150
>> message not received
>> [ERROR]   UDPDiscoverySenderEncryptedUnitTest.testRequestBroadcast:175
>> message not received
>> [ERROR]   UDPDiscoverySenderUnitTest.testPassiveBroadcast:119 message not
>> received
>> [ERROR]   UDPDiscoverySenderUnitTest.testRemoveBroadcast:149 message not
>> received
>> [ERROR]   UDPDiscoverySenderUnitTest.testRequestBroadcast:176 message not
>> received
>> [ERROR]
>> UDPDiscoveryUnitTest.testSimpleUDPDiscoveryIPv4:49->simpleUDPDiscovery:131
>> Receiver count [0] should be the at least the number sent [10].
>> [INFO]
>> [ERROR] Tests run: 431, Failures: 7, Errors: 0, Skipped: 0
> 
> Yes, this means that multicast consistently does not work in your environment 
> - for whatever reason.
> There are several test tools available to check for configuration problems, 
> like for example this one: https://github.com/enclave-networks/multicast-test 
> 
> 
> Could you please give it a try?
> 
> Bye, Thomas


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [JCS] How to proceed? was: Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc2

[Gary Gregory]

I suggest the following:

- Refactor the failing test methods into a new test class.
- Document the environmental requirements in the new test's Javadoc.
Document how to skip this one test from the comment line in the
Javadoc: mvn ... -Dtest='!ClassNameTest'
- Document the above in the VOTE email and release notes.
- Perhaps also document the threshold in the VOTE what constitutes
acceptable coverage for RC: Java versions and OS types/versions.
- The RM then decides if the threshold is met based on the VOTE replies

Gary

On Sun, May 12, 2024 at 2:21 PM Thomas Vandahl  wrote:
>
> Hi folks,
>
> how shall we proceed with the release process? We have tests which rely on a 
> working multicast configuration. This seems to be a serious obstacle. I can 
> exclude the tests so that the build should be runnable by anyone. Downside 
> is, that we don't test the feature anymore.
>
> I'm a bit at a loss on how to tackle this problem. I'm open for suggestions. 
> Please help!
>
> Bye, Thomas
>
> > Am 05.05.2024 um 19:20 schrieb Thomas Vandahl :
> >
> > Hi Bruno,
> >
> >> Am 02.05.2024 um 22:01 schrieb Bruno Kinoshita :
> >>
> >> Tried building the project but alas I think my network has UDP multicast
> >> issues?
> >>
> >> [ERROR] Failures:
> >> [ERROR]   UDPDiscoverySenderEncryptedUnitTest.testPassiveBroadcast:122
> >> message not received
> >> [ERROR]   UDPDiscoverySenderEncryptedUnitTest.testRemoveBroadcast:150
> >> message not received
> >> [ERROR]   UDPDiscoverySenderEncryptedUnitTest.testRequestBroadcast:175
> >> message not received
> >> [ERROR]   UDPDiscoverySenderUnitTest.testPassiveBroadcast:119 message not
> >> received
> >> [ERROR]   UDPDiscoverySenderUnitTest.testRemoveBroadcast:149 message not
> >> received
> >> [ERROR]   UDPDiscoverySenderUnitTest.testRequestBroadcast:176 message not
> >> received
> >> [ERROR]
> >> UDPDiscoveryUnitTest.testSimpleUDPDiscoveryIPv4:49->simpleUDPDiscovery:131
> >> Receiver count [0] should be the at least the number sent [10].
> >> [INFO]
> >> [ERROR] Tests run: 431, Failures: 7, Errors: 0, Skipped: 0
> >
> > Yes, this means that multicast consistently does not work in your 
> > environment - for whatever reason.
> > There are several test tools available to check for configuration problems, 
> > like for example this one: 
> > https://github.com/enclave-networks/multicast-test 
> > 
> >
> > Could you please give it a try?
> >
> > Bye, Thomas
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [CLI] Deprecated options and helpformatting

[Gary Gregory]

How does it look now?

Would you check git master is OK, then I can cut a release candidate
later in the week.

Gary

On Sat, May 11, 2024 at 6:28 AM Claude Warren  wrote:
>
> Also, it appears that the deprecatedHandler is only tested on the string
> option processing.  if the application retains a list of Options and passes
> those in to be checked the deprecation check is not execute.
>
> On Sat, May 11, 2024 at 12:18 PM Claude Warren  wrote:
>
> > Greetings,
> >
> > I see that there is a deprecated option in cli 1.7.0, and that it has some
> > nice data.  But I don't see how to display the info in the help.
> >
> > It looks like the only option is to print "[Deprecated]" without any
> > information from the deprecated info.  I think the HelpPrinter needs a
> > function (similar to the command line deprecatedHandler) to convert the
> > object to a string that can be prefixed to the option help output where the
> > "[Deprecated]" is now.
> >
> > Does this make sense?
> >
> > Is there something I am overlooking that already does this?
> >
> > Claude
> >
> >
> >

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org