Re: svn commit: r1859859 [1/5] - in /commons/proper/jcs/trunk/commons-jcs-core/src: main/java/org/apache/commons/jcs/ main/java/org/apache/commons/jcs/access/ main/java/org/apache/commons/jcs/admin/ m

[Thomas Vandahl]

On 24.05.19 12:33, Gary Gregory wrote:
> -1
> 
> We are now on gitbox https://gitbox.apache.org/repos/asf/commons-jcs.git
> 

When did that happen? I don't remember an announcement or a vote.

Bye, Thomas


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

Re: svn commit: r1859859 [1/5] - in /commons/proper/jcs/trunk/commons-jcs-core/src: main/java/org/apache/commons/jcs/ main/java/org/apache/commons/jcs/access/ main/java/org/apache/commons/jcs/admin/ m

[Thomas Vandahl]

On 26.05.19 15:54, sebb wrote:
> Jan 2019
> 
> https://lists.apache.org/thread.html/053bb8f18e90800d918956f69364167b23c0cdca175568300b1108f6@%3Cdev.commons.apache.org%3E

Ok, I missed that one completely.
What do I have to do?

Bye, Thomas


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

Re: svn commit: r1859859 [1/5] - in /commons/proper/jcs/trunk/commons-jcs-core/src: main/java/org/apache/commons/jcs/ main/java/org/apache/commons/jcs/access/ main/java/org/apache/commons/jcs/admin/ m

[Thomas Vandahl]

On 27.05.19 10:21, sebb wrote:
> Either re-apply each of the commits in turn to Git.
Done.

Bye, Thomas

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

Re: [CONFIGURATION] Formatting braces

[Thomas Vandahl]

On 11.09.19 15:53, Gary Gregory wrote:
> public static final ConfigurationConsumer
> DEFAULT_INCLUDE_LISTENER = e -> { throw e; };
> 
> public static final ConfigurationConsumer
> NOOP_INCLUDE_LISTENER = e -> { /* noop */ };

+1 for these.

> I propose a reformatting to use the "{ on the same line" which means that
> blocks go from:
> 
> if (test)
> {
>// this
> }
> else
> {
>   // that
> }
> 
> to:
> 
> if (test) {
>// this
> } else {
>   // that
> }

-1 here. At least not for all components.

Bye, Thomas


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

Re: [all] Thoughts on build system maven -> gradle??

[Thomas Vandahl]

On 17.07.20 10:13, Claude Warren wrote:
> -1 from me.  I have a philosophical objection.

Same here: -1

> Much like HTTP's mod_rewrite[1] gradle's greatest strength is that it
> allows the developer to do so much in so many ways.  But its greatest
> weakness is that it allows the developer to do so much in so many ways.
> 
> My experience with Ant and Gradle is that in a fairly short period of time
> the build scripts become so complex that it takes a development team just
> to maintain them.
> 
> The greatest strength of Maven is that it requires developers to seriously
> work to do things outside of the "Maven way".  But its greatest weakness is
> that developers have to seriously work  to do things outside of the "Maven
> way".
> 
> My experience with Maven is that if the developer wants to do something
> outside of the "Maven way" it is difficult, but it also forces the
> developer to think about what they are doing.

Very well put. The "Maven way" is a concept that makes it easy for new
people to understand how a project is structured. If you know how a
Maven project works in principle, you can understand all others. This is
one of the greatest strengths of Maven IMO.

> With respect to this project, it is my opinion that we do not want to
> create a build system that is so complex that it becomes difficult for the
> uninitiated developer to contribute to the project.

Couldn't agree more.

Bye, Thomas

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

Re: svn commit: r1369332 - in /commons/proper/jcs/trunk/src/test/org/apache/jcs: ./ auxiliary/disk/block/ auxiliary/disk/file/ auxiliary/disk/indexed/ auxiliary/disk/jdbc/ auxiliary/disk/jdbc/mysql/ a

[Thomas Vandahl]

On 06.08.12 00:12, sebb wrote:
> On 4 August 2012 15:23,   wrote:
>> Author: tv
>> Date: Sat Aug  4 14:23:36 2012
>> New Revision: 1369332
>>
>> URL: http://svn.apache.org/viewvc?rev=1369332&view=rev
>> Log:
>> - Fixed lots of warnings and FindBugs issues
>> - Introduced carefully crafted @SuppressWarnings annotations
> 
> Please add a comment to each suppression to say why it is safe to ignore.

Will do. May take some time, though.

Bye, Thomas.


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

Re: [VOTE] Apache Commons as Sponsor for BeanShell in Incubator

[Thomas Vandahl]

On 09.10.12 15:12, Simone Tripodi wrote:
> So, I'm here to call for a vote for Commons PMC be the BeanShell
> Sponsor, please cast your votes
> 
> [X] +1

Bye, Thomas


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

Re: [all] moving to svnpubsub or CMS?

[Thomas Vandahl]

On 14.11.2012 08:40, Luc Maisonobe wrote:

Please, could someone who knows what to do step up?


Just a quick note that sites created by Maven can be published with 
svnpubsub using the  SCM Publish Maven Plugin 
(http://maven.apache.org/sandbox/plugins/asf-svnpubsub-plugin/). I guess 
this may keep the effort manageable (no further experience, though).


See especially the link 
http://maven.apache.org/sandbox/plugins/asf-svnpubsub-plugin/examples/importing-maven-site.html 
for how to do the initial import.


Bye, Thomas.



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

[VOTE] Release Apache Commons JCS 3.0 based on RC1

[Thomas Vandahl]

This has been a major overhaul of JCS with many adjustments for JDK 8+,
better concurrency and logging. Finally, I would like to
release Apache Commons JCS 3.0.

Apache Commons JCS 3.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/jcs/3.0-RC1 (svn
revision 40998)

The Git tag commons-jcs3-3.0-rc1 commit for this RC is
2c281fc779770f15f8d7cf4421a47eddbb422a1d which you can browse here:

https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=2c281fc779770f15f8d7cf4421a47eddbb422a1d

You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-jcs.git
--branch commons-jcs3-3.0-rc1 commons-jcs3-3.0-rc1

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1522/org/apache/commons/commons-jcs3/3.0/

These are the distribution artifacts and their hashes:

commons-jcs3-dist-3.0-src.zip=
7948c2ec95c034c86a794d7cf749b507ca697bd5c1041a1666405a0ffa99878ff93aba40f8fb257fc923b107b20c50fe4c941a631d06549751e5350b886590ef
commons-jcs3-dist-3.0-src.tar.gz=
f5aaec51851beff43605cc6392b8b428b347c4aa9014760f944281fb7e92db413f5a688276ad204522131597c691e797a68317f0625b05abc605a3407c4aa151
commons-jcs3-dist-3.0-bin.zip=
18da4ec7dc823f14b5cf8e9410d182fdb5c8fff1c6b2e66e5aecced882452e3498159acfb4c31d7b90203201ea8266aaf6d9f20bd637a73e03d3d3202ecc045c
commons-jcs3-dist-3.0-bin.tar.gz=
b09f11d7875ed3bb0fe704eba90436fd63b73427aca8960e408e8823a998a7f19f8aa4ec43dd50c0b29da228e9e3b8d5388dd4d8bfeb6f39eb84866792467160

These are the Maven artifacts and their hashes:

commons-jcs3-core-3.0-javadoc.jar=
9cde0fca72a48c8f02abe1ec488fb90d1089afdfed5de004a87d0dff07a9e472fc23a3712d935097468ddcb5daead2dd865a5f45d18e119ae271c780f6e6aa0e
commons-jcs3-core-3.0-sources.jar=
113d3a862f276aa4010aa31870c284fe1418859e8fc596ff26bb818e4cd70b7d592307a89012e4ea8170f6b5b2580abc620647128bdbaa864564a4c5b108f81d
commons-jcs3-core-3.0-test-sources.jar=
104536381ca3c82049ce2bd02fdb34d226ca0bb5741783af3a833412809ea3d3929d46a8bfd0db4e72b93938a28c1ed33c473c2f42c5ed6c918709bc946f2588
commons-jcs3-core-3.0-tests.jar=
5d6f4dabb316d7a6d186ae680fc561f1651ace5a2d4f08d1ef00d3331b32c216ea20863c9947e4092ce6b0e819d39e4e994678f4d4775a334d83d7c498439530
commons-jcs3-core-3.0.jar=
60aa6f6ef00dc5c0050da196bc7f3b2560bd002ec0f67b85f78a42571dbd400651456c26643c7f0123698405c07f8104bcd9fd67dea5788f5c348c48826833b2
commons-jcs3-jcache-extras-3.0-javadoc.jar=
2ed5254bfb88720cd7c8cdb49ba9749ab215d4671018d177dd8f3fd52dcd42c4f1dfeb0c7e0a81aac5a25e2a42a6d0e983f29134515d9681ea9c2e083d92595a
commons-jcs3-jcache-extras-3.0-sources.jar=
e0f8562ea8322efc03cf946ede568ccae7f32586dfd7cf8e6e06b27de6e787b5830342355da3354b7035194f6f54931a939fd6c7d76fc2753620bd09557f3501
commons-jcs3-jcache-extras-3.0-test-sources.jar=
080080deee43954d3bb55287c65df8b3507f14acc16759c62ffb56b852bd46633ae3d82c738627a9713e0718827a4657c2321f1f6814e345207c291a44e04ae8
commons-jcs3-jcache-extras-3.0-tests.jar=
9c3ea32d8f0b809eadf679559a1800f6d0d77ade0dec7755a5ed7b4872d735671c994a4cd2184e5da418a22bb19f97c0c8d51941f6a57ee93b1d3945bf32ce1b
commons-jcs3-jcache-extras-3.0.jar=
0fab536bd0fa49421332bd92c7c42d8329977a1b9d51354b7116103c75518030bf45b304304bcfa3a87d1e2e0c8ea8deb298a172d47e8e2f9ea06889bb8d3ad5
commons-jcs3-jcache-openjpa-3.0-javadoc.jar=
2471748e891c266964a755b05bfd525e6ad240a91ff7b2c88e80d5c40caba31ed14fee955a4e858b16915664902c76b337828b4e69e2e2e95267da4ca2dc53de
commons-jcs3-jcache-openjpa-3.0-sources.jar=
e1e62570e4d4dffb85fedefc1362c52872e95d78d20d4dcc83214ab32231f36e134ab3af53aef30f57f205e50c425004c3a749b830bbd589a5e9a58669c62d1c
commons-jcs3-jcache-openjpa-3.0-test-sources.jar=
716137ca51679ed09e3efeed6ae0619b0492a1f0579bf1d20eb20a3f5fa236c99c44b32f6fb21f512b55952d314f7fe579d6eb961e2ffd51f24ed7d4564cfb20
commons-jcs3-jcache-openjpa-3.0-tests.jar=
c7feaf654396380d1513be32a0873ad4408442a077de7f8b2341f067d672d1db7615dd902441ccb634406fa989fdf19384b0018637d4cea5fb7efd0455633cb3
commons-jcs3-jcache-openjpa-3.0.jar=
b279161f879f994a0d9e36861f2847b96d0b7f2658c9786ad219970019b233af6e585dd11f71b2981e8abfebda35dd63256e25a290b77cf6e5bbcdb603ba0dcb
commons-jcs3-jcache-3.0-cdi.jar=
0c5e8750a7ac7f1936429985fd0fb425f2ac33eb0ad851287a9ced00bbe5f6a5bff18cfb68854e8062b9e216b9083eb5527b399dd40fa9df1a3d06b97e3515e6
commons-jcs3-jcache-3.0-javadoc.jar=
a4877b8f0d91fbb382f1313415fd6191cb4379d7b5b6b151024fdff887a8c3a1bc08e17578a31a6311ac5457c5436ddb30e8d277c43338a6705cabedce9cee7b
commons-jcs3-jcache-3.0-nocdi.jar=
973eba23cd7df050b00c44819a2c2cb5bcc5b81ff1ac7c9a3d731e0e396315585087484f793afd742c82f7a845d98c5929e55ccd3dcfbea017f6a681cd654704
commons-jcs3-jcache-3.0-sources.jar=
79751991acdd11abe36fb9ecfc99c0cd9cbfd0b8c0b09dd7543a9dc07dbf3e15b8f8bc100795e7fb01199fb8eec7abfea539c257b9f46847fd4ffc3938e55d05
commons-jcs3-jcache-3.0-test-sources.jar=
982521c03bf2641cdcad9fe0bfb561b3c096f71f9bd4f772e8cfc7c360bb9e74a43b4bcd695c0ffb484959e9946006b3aa47000475f8b509cac61fafd4bbe9c9
commons-jcs3-jcache-3.0-tests.jar=
fd36177e9f6dae4afe8

Re: [VOTE] Release Apache Commons JCS 3.0 based on RC1

[Thomas Vandahl]

On 17.08.20 08:29, Thomas Vandahl wrote:
>   [X] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...

Bye, Thomas

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

REMINDER: [VOTE] Release Apache Commons JCS 3.0 based on RC1

[Thomas Vandahl]

Could I please ask for one more PMC vote?

TIA
Bye, Thomas

On 17.08.20 08:29, Thomas Vandahl wrote:
> This has been a major overhaul of JCS with many adjustments for JDK 8+,
> better concurrency and logging. Finally, I would like to
> release Apache Commons JCS 3.0.
[...]
> Please review the release candidate and vote.
> This vote will close no sooner that 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,
> 
> Bye, Thomas
> Release Manager (using key 88817402)

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

[RESULT] [VOTE] Release Apache Commons JCS 3.0 based on RC1

[Thomas Vandahl]

On 17.08.20 08:29, Thomas Vandahl wrote:
> This has been a major overhaul of JCS with many adjustments for JDK 8+,
> better concurrency and logging. Finally, I would like to
> release Apache Commons JCS 3.0.

More than 72 hours have now passed, and there have been the following
votes (in order of appearance):

+1 Thomas Vandahl (binding)
+1 Bruno P. Kinoshita (binding)
+1 Romain Manni-Bucau (non-binding)
+1 Sebb (binding)

The vote has therefore succeeded, and publication will take place soon.

Thanks to all voters.

Bye, Thomas

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

[ANNOUNCE] Apache Commons JCS 3.0 Released

[Thomas Vandahl]

The Apache Commons Team is pleased to announce the availability of
Apache Commons JCS 3.0

Apache Commons JCS is a distributed, versatile caching system.

This has been a major overhaul of JCS with many adjustments for JDK 8+,
better concurrency and logging.

Commons JCS 3.0 requires Java 8 or later.

The release notes can be reviewed at:
http://www.apache.org/dist/commons/jcs/RELEASE-NOTES.txt

Distribution packages can be downloaded from:
https://commons.apache.org/proper/commons-jcs/download_jcs.cgi

When downloading, please verify signatures using the KEYS file available
at: http://www.apache.org/dist/commons

More information and comprehensive documentation is available at:
https://commons.apache.org/proper/commons-jcs/

Maven artifacts are also available in the central Maven repository:
http://repo1.maven.org/maven2/org/apache/commons/jcs3

The Apache Commons Team


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

Re: [All] New repo for all proper components as submodules?

[Thomas Vandahl]

On 30.08.20 00:52, Gary Gregory wrote:

Hi All,

Any thoughts for or against creating a new git repository which would
contain all 'proper' Commons components as git submodules?

The idea is to be able to checkout all of Commons 'proper' in one go in one
place.


I understand this is in addition to the current repos?

Bye, Thomas

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

Re: [commons-jcs] branch master updated: Use for-each. Use final. Remove redundant modifiers.

[Thomas Vandahl]

Hi Gary,

On 21.11.20 19:22, ggreg...@apache.org wrote:

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

ggregory pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-jcs.git


The following commit(s) were added to refs/heads/master by this push:
  new 8429481  Use for-each. Use final. Remove redundant modifiers.
8429481 is described below

commit 842948113064884f60d7a0cbb1b5d33f67a89c32
Author: Gary Gregory 
AuthorDate: Sat Nov 21 13:22:05 2020 -0500


Busy bee you are. :-)
Thanks for cleaning up!

Bye, Thomas

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

[VOTE] Release Apache Commons JCS 3.1 based on RC1

[Thomas Vandahl]

Hi folks,

We have fixed quite a few bugs and added some significant enhancements since 
Apache Commons JCS 3.0 was released, so I would like to release Apache Commons 
JCS 3.1.

Apache Commons JCS 3.1 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1

The Git tag commons-jcs-3.1-rc1 commit for this RC is 
f370adb43aeef51a5456d93f13f2601f3b87c44a which you can browse here: 

https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=f370adb43aeef51a5456d93f13f2601f3b87c44a

You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch 
commons-jcs-3.1-rc1 commons-jcs-3.1-rc1

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1575/org/apache/commons/commons-jcs3/3.1/

These are the distribution artifacts and their hashes:

commons-jcs3-dist-3.1-bin.tar.gz
651d9adaa7495a5411baf2903f57e1471633ba1742ce4739dd5060f186ddecfb44afe9b528eac1d904ebc8bfe43654a455fe8a6ccb0a46449acf2830ad3a015e
commons-jcs3-dist-3.1-bin.zip 
5e53f4ddca4071aa9d13d88b17444afdcb71f513ab0cef1be4e5dd5162c477d101b50dbecb5a7624546fbd4985d1ca4024ab6f3ef1b06d6f0a3fbfea393ba861
commons-jcs3-dist-3.1-src.tar.gz
137639d251a52ebf61b15eb710b201c2d6f1b111c507596bd49ecee313ec1e51fd885ad869addebb337cceddb1eb9ab9e73e77baf705a7cbfaae3d9bd4251ec5
commons-jcs3-dist-3.1-src.zip
013f85fa8f291b4ea3f2b43858dd48bd3335a4092339971c8a6b16751ae7c539b031ac27897d800ee2e523d3e9edf776b7a8911a9adf8633e064b489ff8de2b9

I have tested this with ***'mvn clean install site'*** using: 
---
Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
Java version: 1.8.0_241, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk1.8.0_241.jdk/Contents/Home/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
---

Details of changes since 3.0 are in the release notes:

https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1/RELEASE-NOTES.txt

https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1/site/changes-report.html

Site:

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

JApiCmp Report (compared to 3.0):

https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1/site/commons-jcs3-core/japicmp.html

RAT Report:

https://dist.apache.org/repos/dist/dev/commons/jcs/COMMONS_JCS_3_1_RC1/site/commons-jcs3-core/rat-report.html

KEYS:
  https://www.apache.org/dist/commons/KEYS

Please review the release candidate and vote.
This vote will close no sooner that 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,

Thomas Vandahl (tv), 
Release Manager (using key 88817402)


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

Re: [VOTE] Release Apache Commons JCS 3.1 based on RC1

[Thomas Vandahl]

Yeah, sorry - typo.

> Am 23.12.2021 um 19:20 schrieb Thomas Vandahl :
> 
> The Git tag commons-jcs3-3.1-rc1 commit for this RC is 
> f370adb43aeef51a5456d93f13f2601f3b87c44a which you can browse here: 
>
> https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=f370adb43aeef51a5456d93f13f2601f3b87c44a
> 
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch 
> commons-jcs3-3.1-rc1 commons-jcs3-3.1-rc1

Sorry for the confusion.

Bye, Thomas


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

Re: [VOTE] Release Apache Commons JCS 3.1 based on RC1

[Thomas Vandahl]

My vote:

> Am 23.12.2021 um 19:20 schrieb Thomas Vandahl :
> 
>  [X] +1 Release these artifacts
>  [ ] +0 OK, but...
>  [ ] -0 OK, but really should fix...
>  [ ] -1 I oppose this release because...

Bye, Thomas 

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

Re: [VOTE] Release Apache Commons JCS 3.1 based on RC1

[Thomas Vandahl]

Hi Bruno.

> Am 24.12.2021 um 02:00 schrieb Bruno P. Kinoshita 
> :
> 
> [ERROR]   SerializerUnitTest.testReadWrite:116 [key:0] should not be null, 
> Region Name = blockRegion2

Can you reproduce the failure (because I can't)? Some of the concurrent tests 
are timing sensitive. If you can reproduce the failure situation, I would be 
very much interested in your test setup.

Bye, Thomas 


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

Re: [VOTE] Release Apache Commons JCS 3.1 based on RC1

[Thomas Vandahl]

> Am 28.12.2021 um 13:01 schrieb Bruno P. Kinoshita 
> :
> 
> `mvn clean test install site` took a few minutes, but it just finished 
> running. Below the error that just happened again on my environment (appears 
> to be consistent for me):
> 
> [INFO] Results:
> [INFO] 
> [ERROR] Failures: 
> [ERROR]   SerializerUnitTest.testReadWrite:116 [key:0] should not be null, 
> Region Name = blockRegion2

Can you send me the log file please (direct mail, supposed to be in target/) If 
the test fails consistently, please run just that test because the log file is 
being overwritten every time.

> [INFO] Apache Commons JCS :: Core . FAILURE [17:44 
> min]

=:-o That's actually a *lot* of time. My seven year old Macbook needs about 
four minutes for the same task. Maybe there's a timing issue.

Bye, Thomas 


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

Re: can we get rid of dependabot?

[Thomas Vandahl]

+1
Thank you, Phil. This thing is a P.I.T.A.

> Am 28.12.2021 um 19:20 schrieb Phil Steitz :
> 
> I can no longer effectively monitor commits@ due to the spam generated by 
> this tool.  I am afraid my eyeballs aren't the only ones going missing here 
> and that is a problem much more severe than any value provided by this tool, 
> IMO.
> 
> Phil

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

Re: [VOTE] Release Apache Commons JCS 3.1 based on RC1

[Thomas Vandahl]

> Am 29.12.2021 um 16:06 schrieb Gary Gregory :
> 
> Is this test failure being addressed?

Well, "addressed" is a big word for what I'm currently trying. "looked at" is 
closer to what happens.

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

[CANCEL][VOTE] Release Apache Commons JCS 3.1 based on RC1

[Thomas Vandahl]

> Am 23.12.2021 um 19:20 schrieb Thomas Vandahl :
> 
> Hi folks,
> 
> We have fixed quite a few bugs and added some significant enhancements since 
> Apache Commons JCS 3.0 was released, so I would like to release Apache 
> Commons JCS 3.1.

Thanks to Bruno we were able to find an issue that could cause serious 
performance degradation in EncryptingSerializer. I will fix this and cut an RC2 
rsn.

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

[VOTE] Release Apache Commons JCS 3.1 based on rc2

[Thomas Vandahl]

Hi folks,

We have fixed quite a few bugs and added some significant enhancements since 
Apache Commons JCS 3.0 was released, so I would like to release Apache Commons 
JCS 3.1.

Note that, although the core library of Log4j is an optional dependency to 
commons-jcs, we have addressed CVE-2021-44228 by updating log4j-api and 
log4j-core to version 2.17.1.

Apache Commons JCS 3.1 rc2 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/jcs/3.1-rc2 (svn revision 
51880)

The Git tag commons-jcs3-3.1-rc2 commit for this RC is 
5cd1ad02a8ddd196c9594fbb208d708440f87734 which you can browse here:

https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=5cd1ad02a8ddd196c9594fbb208d708440f87734
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch 
commons-jcs3-3.1-rc2 commons-jcs3-3.1-rc2

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1576/org/apache/commons/commons-jcs3/3.1/

These are the distribution artifacts and their hashes:

commons-jcs3-dist-3.1-bin.tar.gz
2d64ec75177934524353adcc7cccb92b05b4a5b6014f75b10f16dae2265954da0c0f4c0eb68013fee71d4ec53a49b02f7689de5fce6ff34ae90cd83705a56362
commons-jcs3-dist-3.1-bin.zip
cba57f84ce1e0654239b0ea72663c166e47cf582c0ffc4a2743fd583d35eabbbcb03576fb1aac3e425a48a5b55068c554ab13b3b210a4d50151f62fa9e79894c
commons-jcs3-dist-3.1-src.tar.gz
d76daa3e8449e711e91e3f3ec73dc00b212d10db28f0f9a726c4df35bb9578cc1649ee8c5f20159f8cda0f58c569fa5821c3736a3f65fc03cfff74da200b790d
commons-jcs3-dist-3.1-src.zip
1990533137ca75dbbfa702bb8dedb680e2f6d96d301cf263794d96da845c2c72072c1e84b6e50b7dd0588f96fd9512be0d7a61cd08463f1e01044a55a75b0ed5

I have tested this with ***'mvn clean verify site site:stage'*** using: 

Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
Java version: 1.8.0_311, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk1.8.0_311.jdk/Contents/Home/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"

Details of changes since 3.0 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/jcs/3.1-rc2/RELEASE-NOTES.txt

https://dist.apache.org/repos/dist/dev/commons/jcs/3.1-rc2/site/changes-report.html

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

JApiCmp Report (compared to 3.0):

https://dist.apache.org/repos/dist/dev/commons/jcs/3.1-rc2/site/commons-jcs3-core/japicmp.html

RAT Report:

https://dist.apache.org/repos/dist/dev/commons/jcs/3.1-rc2/site/commons-jcs3-core/rat-report.html

KEYS:
  https://www.apache.org/dist/commons/KEYS

Please review the release candidate and vote.
This vote will close no sooner that 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,

Thomas Vandahl (tv), 
Release Manager (using key 88817402)


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

Re: [VOTE] Release Apache Commons JCS 3.1 based on rc2

[Thomas Vandahl]

> Am 03.01.2022 um 18:24 schrieb Thomas Vandahl :
> 
> Hi folks,
> 
> We have fixed quite a few bugs and added some significant enhancements since 
> Apache Commons JCS 3.0 was released, so I would like to release Apache 
> Commons JCS 3.1.
> 
>  [X] +1 Release these artifacts
>  [ ] +0 OK, but...
>  [ ] -0 OK, but really should fix...
>  [ ] -1 I oppose this release because...

My vote.
Bye, Thomas 


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

Re: [VOTE] Release Apache Commons JCS 3.1 based on rc2

[Thomas Vandahl]

Hi Bruno,

> Am 05.01.2022 um 06:41 schrieb Bruno P. Kinoshita 
> :
> 
> I didn't have much time, so inspected only one file, randomly selected, from 
> the dist area. The src zip. @Thomas, I think the NOTICE has the date 2020? I 
> think that can be fixed later? Everything else looks OK in that file.

This is what the maven-remote-resources-plugin puts out, probably based on 
${project.build.outputTimestamp}. No idea where it comes from and who sets this.
Anyone?

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

Re: [VOTE] Release Apache Commons JCS 3.1 based on rc2

[Thomas Vandahl]

Hi Bruno,

> Am 05.01.2022 um 21:59 schrieb Bruno P. Kinoshita 
> :
> 
> Did you have an old NOTICE file in the directory where you built the jcs 
> release? I read the release instructions [1] and the code of 
> commons-release-plugin [2], and found nothing that appeared to replace files 
> or dates. The tag on GitHub is showing NOTICE.txt (with the extension) with 
> the correct dates. 

No, I haven’t. I completely rely on the files automatically generated by the 
plugin. If you look at the code of the plugin, you see the mentioned 
outputTimestamp property is being used. 
I found docs about this here: 
https://maven.apache.org/guides/mini/guide-reproducible-builds.html

> Maybe somebody else knows how that can happen.
The effective POM shows the following entry:
2020-01-22T15:10:15Z

Now we see why the year number in NOTICE is wrong. But who sets this?

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

[all] project.build.outputTimestamp set in org.apache:apache, was Re: [VOTE] Release Apache Commons JCS 3.1 based on rc2

[Thomas Vandahl]

Hi folks,

This may be of general interest, at least I had no idea about the consequences.
So I thought I’d share the result of my research.

> Am 06.01.2022 um 10:30 schrieb Thomas Vandahl :
> 
>> Maybe somebody else knows how that can happen.
> The effective POM shows the following entry:
> 2020-01-22T15:10:15Z
> 
> Now we see why the year number in NOTICE is wrong. But who sets this?

Found it. For the information of all interested parties, the following command

mvn org.apache.maven.plugins:maven-help-plugin:3.2.0:effective-pom 
-Dverbose=true

produces the line (among others)


2020-01-22T15:10:15Z
  

Re: [VOTE] Release Apache Commons JCS 3.1 based on rc2

[Thomas Vandahl]

Hi folks,

could I please have one more PMC vote? If you think that the outputTimestamp 
issue must be fixed before, then please vote -1 explicitly.

Bye, Thomas 

> Am 03.01.2022 um 18:24 schrieb Thomas Vandahl :
> 
> Hi folks,
> 
> We have fixed quite a few bugs and added some significant enhancements since 
> Apache Commons JCS 3.0 was released, so I would like to release Apache 
> Commons JCS 3.1.
> 
> Note that, although the core library of Log4j is an optional dependency to 
> commons-jcs, we have addressed CVE-2021-44228 by updating log4j-api and 
> log4j-core to version 2.17.1.
> 
> Apache Commons JCS 3.1 rc2 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/jcs/3.1-rc2 (svn revision 
> 51880)
> 
> The Git tag commons-jcs3-3.1-rc2 commit for this RC is 
> 5cd1ad02a8ddd196c9594fbb208d708440f87734 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=5cd1ad02a8ddd196c9594fbb208d708440f87734
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch 
> commons-jcs3-3.1-rc2 commons-jcs3-3.1-rc2
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1576/org/apache/commons/commons-jcs3/3.1/
> 
> These are the distribution artifacts and their hashes:
> 
> commons-jcs3-dist-3.1-bin.tar.gz
> 2d64ec75177934524353adcc7cccb92b05b4a5b6014f75b10f16dae2265954da0c0f4c0eb68013fee71d4ec53a49b02f7689de5fce6ff34ae90cd83705a56362
> commons-jcs3-dist-3.1-bin.zip
> cba57f84ce1e0654239b0ea72663c166e47cf582c0ffc4a2743fd583d35eabbbcb03576fb1aac3e425a48a5b55068c554ab13b3b210a4d50151f62fa9e79894c
> commons-jcs3-dist-3.1-src.tar.gz
> d76daa3e8449e711e91e3f3ec73dc00b212d10db28f0f9a726c4df35bb9578cc1649ee8c5f20159f8cda0f58c569fa5821c3736a3f65fc03cfff74da200b790d
> commons-jcs3-dist-3.1-src.zip
> 1990533137ca75dbbfa702bb8dedb680e2f6d96d301cf263794d96da845c2c72072c1e84b6e50b7dd0588f96fd9512be0d7a61cd08463f1e01044a55a75b0ed5
> 
> I have tested this with ***'mvn clean verify site site:stage'*** using: 
> 
> Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
> Java version: 1.8.0_311, vendor: Oracle Corporation, runtime: 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_311.jdk/Contents/Home/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
> 
> Details of changes since 3.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.1-rc2/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.1-rc2/site/changes-report.html
> 
> Site:
>https://dist.apache.org/repos/dist/dev/commons/jcs/3.1-rc2/site/index.html
>(note some *relative* links are broken and the 3.1 directories are not yet 
> created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 3.0):
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.1-rc2/site/commons-jcs3-core/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.1-rc2/site/commons-jcs3-core/rat-report.html
> 
> KEYS:
>  https://www.apache.org/dist/commons/KEYS
> 
> Please review the release candidate and vote.
> This vote will close no sooner that 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,
> 
> Thomas Vandahl (tv), 
> Release Manager (using key 88817402)
> 
> 
> -
> 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: [VOTE] Release Apache Commons JCS 3.1 based on rc2

[Thomas Vandahl]

Hi Gilles,

> Am 14.01.2022 um 15:37 schrieb Gilles Sadowski :
> 
>>> Maven artifacts are here:
>>>   
>>> https://repository.apache.org/content/repositories/orgapachecommons-1576/org/apache/commons/commons-jcs3/3.1/
> 
> I only see one ".pom" file and one ".xml" file (with their respective
> crypto sig).
> 
… and modules below 
https://repository.apache.org/content/repositories/orgapachecommons-1576/org/apache/commons/commons-jcs3

> We should note that this command requires the environment variable
>  JAVA_HOME
> to be set (otherwise the build will fail).
> 
Is this a special requirement of this build? If so, why?

> Shall we stop cluttering what should be a summary of important changes,
> easily readable by a human, with bot-generated messages and trivial
> one-liners like "isEmpty()"?
> 
I followed the directions for the release preparation at 
https://commons.apache.org/releases/prepare.html and generated the release 
notes with „mvn changes:announcement-generate -Prelease-notes“ and the vote 
e-mail with „mvn commons-release:vote-txt“ as recommended. What is wrong with 
this procedure?

> Is the Log4j2 version update related to the latest security issue?
> If so, that may have been important to note.
Actually, no. log4j is an optional dependency.

> Nit-pick: Rather than tagging them with "IMPORTANT CHANGE", it would
> be clearer that important changes are mentioned in the description, at the
> top of the release notes.
This *is* part of the description. You cannot tag changes in changes.xml. I 
remember discussions about making releasing easier. Every *manual* step such as 
writing release notes does not follow this direction, IMO.

> There are a few changes marked incompatible.  Is it expected in a minor 
> release?
The japicmp report recommends a 0.1.0 release which it is.

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

Would you please consider voting?

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

Re: [VOTE] Release Apache Commons JCS 3.1 based on rc2

[Thomas Vandahl]

Hi Gilles,

> Am 17.01.2022 um 14:11 schrieb Gilles Sadowski :
> 
> No; the remark is for making the reviewer's life easier, i.e just copy/paste
> the command and see the build succeed.  Without the environment variable,
> the "javadoc" step fails IIRC.

Ok, thanks for the hint. I didn’t know this.

> It's not the procedure.  I simply stress FTR that the release notes
> become less and less what they should be, that is a summary for
> human consumption that attracts the user's attention on functional
> changes. [The full set of changes is always accessible through the
> commits log.]
> To ensure clarity for users, changes that cannot affect them should
> not be listed in "changes.xml".
Yes. For the sake of clarity for the user, I find the manual maintenance of 
changes.xml much better than other measures like commit logs or JIRA-Ticket 
reports.
However, I’m a bit hesitant to change entries made by other committers. I guess 
that would require consent between all committers of a project on how to 
maintain the changes list.

>>> There are a few changes marked incompatible.  Is it expected in a minor 
>>> release?
>> The japicmp report recommends a 0.1.0 release which it is.
> 
> I don't understand why, but OK then…
Actually, it took several changes to be reverted just to get to this state. 

> [ ] +1 Release these artifacts
> [ ] +0 OK, but...
> [ ] -0 OK, but really should fix...
> [ ] -1 I oppose this release because…
>> 
>> Would you please consider voting?
> 
> +1
> 
> [There are no technical issues, only communication issues that are
> common problems with all the releases.]

Thanks, Gilles.

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

Re: [VOTE] Release Apache Commons JCS 3.1 based on rc2

[Thomas Vandahl]

Hi Gilles,

> Am 17.01.2022 um 14:11 schrieb Gilles Sadowski :
> 
> No; the remark is for making the reviewer's life easier, i.e just copy/paste
> the command and see the build succeed.  Without the environment variable,
> the "javadoc" step fails IIRC.

Ok, thanks for the hint. I didn’t know this.

> It's not the procedure.  I simply stress FTR that the release notes
> become less and less what they should be, that is a summary for
> human consumption that attracts the user's attention on functional
> changes. [The full set of changes is always accessible through the
> commits log.]
> To ensure clarity for users, changes that cannot affect them should
> not be listed in "changes.xml".
Yes. For the sake of clarity for the user, I find the manual maintenance of 
changes.xml much better than other measures like commit logs or JIRA-Ticket 
reports.
However, I’m a bit hesitant to change entries made by other committers. I guess 
that would require consent between all committers of a project on how to 
maintain the changes list.

>>> There are a few changes marked incompatible.  Is it expected in a minor 
>>> release?
>> The japicmp report recommends a 0.1.0 release which it is.
> 
> I don't understand why, but OK then…
Actually, it took several changes to be reverted just to get to this state. 

> [ ] +1 Release these artifacts
> [ ] +0 OK, but...
> [ ] -0 OK, but really should fix...
> [ ] -1 I oppose this release because…
>> 
>> Would you please consider voting?
> 
> +1
> 
> [There are no technical issues, only communication issues that are
> common problems with all the releases.]

Thanks, Gilles.

Bye, Thomas 

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

[RESULT][VOTE] Release Apache Commons JCS 3.1 based on rc2

[Thomas Vandahl]

Hi folks,

> Am 03.01.2022 um 18:24 schrieb Thomas Vandahl :
> 
> Please review the release candidate and vote.

This vote passes with the following votes:

Gilles Sadowski: +1
Bruno Kinoshita: +1
Thomas Vandahl: +1

I’ll go ahead with the release publication.
Thanks to the voters.

Bye, Thomas 



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

[ANNOUNCE] Apache Commons JCS 3.1

[Thomas Vandahl]

The Apache Commons project announces the release of Apache Commons JCS 3.1.

Apache Commons JCS is a distributed caching system written in Java. It is 
intended to speed up 
applications by providing a means to manage cached data of various dynamic 
natures.

JCS 3.0 and onwards require at least Java 8.

JCS 3.1 uses log4j as an optional component only. Nevertheless, the dependency 
has been updated to address the Log4Shell issues.

This is a feature and bug fix release.

For a list of changes in this release see:
https://commons.apache.org/proper/commons-jcs/changes-report.html#a3.1

For complete information on Apache Commons JCS, including instructions on
how to submit bug reports, patches, or suggestions for improvement, see the
Apache Apache Commons JCS website:
https://commons.apache.org/proper/commons-jcs/

Download page:
https://commons.apache.org/proper/commons-jcs/download_jcs.cgi

Have fun!


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

Re: [VOTE] Release Apache Commons Imaging 1.0-alpha3 based on RC1

[Thomas Vandahl]

Hi Bruno

> Am 13.05.2022 um 07:26 schrieb Bruno Kinoshita :
> 
> https://gitbox.apache.org/repos/asf?p=commons-imaging.git;a=commit;h=b1cfcaad38de7c30f7814a5b3d80e45fe2bd9af1
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-imaging.git
> --branch commons-imaging-1.0-alpha3-RC1 commons-imaging-1.0-alpha3-RC1
> 

I get a build failure running „mvn clean install site“ using the environment

Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
Java version: 11.0.13, vendor: GraalVM Community, runtime: 
/Library/Java/JavaVirtualMachines/graalvm-ce-java11-21.3.0/Contents/Home
Default locale: de_DE, platform encoding: UTF-8
OS name: "mac os x", version: "11.6.5", arch: "x86_64", family: "mac"

—8<—
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-antrun-plugin:3.0.0:run (prepare-checkout) on 
project commons-imaging: You are using 'tasks' which has been removed from the 
maven-antrun-plugin. Please use 'target' and refer to the >>Major Version 
Upgrade to version 3.0.0<< on the plugin site. -> [Help 1]
—8<— 

Do I miss something?

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

Re: [VOTE] Release Apache Commons Imaging 1.0-alpha3 based on RC2

[Thomas Vandahl]

Hi Bruno,

> Am 13.05.2022 um 14:02 schrieb Bruno Kinoshita :
> 
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons Imaging 1.0-alpha2 was released, so I would like to
> release Apache Commons Imaging 1.0-alpha3.
> 
> Apache Commons Imaging 1.0-alpha3 RC2 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha3-RC2
> (svn revision 54488)
> 
>  [X] +1 Release these artifacts
>  [ ] +0 OK, but...
>  [ ] -0 OK, but really should fix...
>  [ ] -1 I oppose this release because…

Signatures are ok. Please consider having your key signed by some fellow 
Apaches.

Build, test and site build works fine using

—8<—
Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
Java version: 11.0.13, vendor: GraalVM Community, runtime: 
/Library/Java/JavaVirtualMachines/graalvm-ce-java11-21.3.0/Contents/Home
Default locale: de_DE, platform encoding: UTF-8
OS name: "mac os x", version: "11.6.5", arch: "x86_64", family: "mac"
—8<—

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

Re: [ALL] Don't update ossf/scorecard-action

[Thomas Vandahl]

Hi Gary

> Am 28.09.2022 um 21:31 schrieb Gary Gregory :
> 
> A specific version of the ossf/scorecard-action is approved by Apache Infra.

Is there any discussion I might have missed why this is required now?

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

Re: [parent][release][rng] Issue with release plugin multi-module builds

[Thomas Vandahl]

> Am 28.09.2022 um 14:24 schrieb Alex Herbert :
> 
> So CP 53 behaviour was for this flag to be false. Now in CP 54 this flag is
> true. Thus all multi-module builds should set this flag to false in all
> non-distribution modules.
> 
> Q. Should these properties be present in CP? They have never been there
> before.
> 
> If we wish to keep these in CP then can I check that the flag should only
> be used in one module of a multi-module build. I have verified that if I
> set this flag to false in the RNG multi-module parent pom (it is set to
> true in the dist-archive module) then the release dry run works.
> 
> Alex

Same problem here with JCS. Is it possible to skip the commons-release-plugin 
steps altogether? I don't need them.

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

Re: [VOTE][LAZY] Release Apache Commons Parent 57 based on RC1

[Thomas Vandahl]

Hi Gary,

> Am 22.04.2023 um 16:24 schrieb Gary Gregory :
> 
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons Parent 56 was released, so I would like to
> release Apache Commons Parent 57.
> 

Can we please make the commons-release-plugin an optional component? It still 
does not handle multi-module builds properly.

Bye, Thomas 


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

Re: [VOTE][LAZY] Release Apache Commons Parent 57 based on RC1

[Thomas Vandahl]

Hi Gary,

> Am 22.04.2023 um 16:24 schrieb Gary Gregory  >:
> 
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons Parent 56 was released, so I would like to
> release Apache Commons Parent 57.
> 

Can we please make the commons-release-plugin an optional component? It still 
does not handle multi-module builds properly.

Bye, Thomas

[VOTE] Release Apache Commons JCS 3.2 based on rc1

[Thomas Vandahl]

We have fixed quite a few bugs and added some significant enhancements since 
Apache Commons JCS 3.1 was released, so I would like to release Apache Commons 
JCS 3.2.

Apache Commons JCS 3.2 rc1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1 (svn revision 
63581)

The Git tag commons-jcs-3.2-rc1 commit for this RC is 
eb9c5b36b48f2b6f45fba7986d46c7006cfb5c4c which you can browse here:

https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=eb9c5b36b48f2b6f45fba7986d46c7006cfb5c4c
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch 
commons-jcs3-3.2-rc1 commons-jcs3-3.2-rc1

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-orgapachecommons-1650/org/apache/commons/commons-jcs3/3.2/

These are the artifacts and their hashes:

6fb8c140c49229339ccea583c462e20b5f2abfd13b3615f466e5b7e44abfbfa7f662ce25b54edcf433c2b7010e4b32c2cde09f2da7754d7f697e871b76f61c91
  commons-jcs3-dist-3.2-bin.tar.gz
6d2c47f3e41a6fca3fa94dd423d8e9c4bc76929778d5d44ee094a2d8465f1449feffee24ee1248e80baaec8e2c08051ff3fdcae76610591b451e796904f5dd46
  commons-jcs3-dist-3.2-bin.zip
16c8bb7abe9268a39b80ce03a57adf1ac596191e4aee80756443d1861b850ffe5b67f6fbd9d46f1189d4247b7b928192cb7fb28f45e8bc768317972276acac9a
  commons-jcs3-dist-3.2-src.tar.gz
1f78fdc0be26f0b8b350ef2623191a28e13131b6a98abc51927aada192b7b381d1d7264a2083f23a72bf0906a0e4164e0c2a5aee11c3448408399cc87f0b912e
  commons-jcs3-dist-3.2-src.zip

I have tested this with ***'mvn clean install site site:stage'*** using:

Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
Java version: 1.8.0_311, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk1.8.0_311.jdk/Contents/Home/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"

Details of changes since 3.1 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/RELEASE-NOTES.txt

https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/site/changes-report.html

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

JApiCmp Report (compared to 3.1):

https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/site/commons-jcs3-core/japicmp.html

***
Note that the above report notes several errors.
These are considered OK for the reasons stated below.
These exceptions are also noted in the Changes and Release Notes.

Errors reported:
- methods added to interface: OK because that does not affect binary 
compatibility.
- annotation @Deprecated added to classes
***

RAT Report:

https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/site/rat-report.html

KEYS:
  https://www.apache.org/dist/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,

Thomas Vandahl (tv),
Release Manager (using key 88817402)

For following is intended as a helper and refresher for reviewers.

Validating a release candidate
==

These guidelines are NOT complete.

Requirements: Git, Java, Maven.

You can validate a release from a release candidate (RC) tag as follows.

1) Clone and checkout the RC tag

git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch 
commons-jcs3-3.2-rc1 commons-jcs3-3.2-rc1
cd commons-jcs3-3.2-rc1

2) Check Apache licenses

This step is not required if the site includes a RAT report page which you then 
must check.

mvn apache-rat:check

3) Check binary compatibility

Newer components use JApiCmp with the japicmp Maven Profile:

This step is not required if the site includes a JApiCmp report page which you 
then must check.

mvn install -DskipTests -P japicmp japicmp:cmp

4) Build the package

mvn -V clean package

You can record the Maven and Java version produced by -V in your VOTE reply.
To gather OS information from a command line:
Windows: ver
Linux: uname -a

5) Build the site for a single module project

Note: Some plugins require the components to be installed instead of packaged.

mvn site
Check the site reports in:
- Windows: target\site\index.html
- Linux: target/site/index.html

6) Build the site for a multi-module project

mvn site
mvn site:stage
Check the site reports in:
- Windows: target\site\index.html
- Linux: target/site/index.html

-the end-


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

Re: [VOTE] Release Apache Commons JCS 3.2 based on rc1

[Thomas Vandahl]

> Am 22.08.2023 um 15:14 schrieb Thomas Vandahl :
> 
> We have fixed quite a few bugs and added some significant enhancements since 
> Apache Commons JCS 3.1 was released, so I would like to release Apache 
> Commons JCS 3.2.
...
>  [X] +1 Release these artifacts
>  [ ] +0 OK, but...
>  [ ] -0 OK, but really should fix...
>  [ ] -1 I oppose this release because...

My vote.

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

Re: [VOTE] Release Apache Commons JCS 3.2 based on rc1

[Thomas Vandahl]

Hi Gary,

> Am 22.08.2023 um 15:58 schrieb Gary Gregory :
> 
> Something went wrong somewhere because the tag in this email points to a
> 3.3-SNAPSHOT version instead of 3.2:
> 
>> The Git tag commons-jcs-3.2-rc1 commit for this RC is
> eb9c5b36b48f2b6f45fba7986d46c7006cfb5c4c which you can browse here:
> 
> https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=eb9c5b36b48f2b6f45fba7986d46c7006cfb5c4c
> 
> Gary
> 

Yes, this should probably read:

The Git tag commons-jcs3-3.2-rc1 commit for this RC is 
6ff84134fa295b608531f9655f075ea58635cd57 which you can browse here:
   
https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=6ff84134fa295b608531f9655f075ea58635cd57

The tag naming confused first the commons-release-plugin and then me.

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

Re: [JCS] GitHub builds broken and Java 17

[Thomas Vandahl]

Hi Gary,

> Am 26.08.2023 um 19:58 schrieb Gary Gregory :
> 
> Does anyone know why it's broken?
If anyone broke it, that was me. I tried to fix the build configurations but I 
simply don't understand what there doing. I never put them up in the first 
place.

> And why is was switched to Java 17 only without warning?

Because it's about time? There's a major release necessary anyway because so 
much deprecated code needs to be removed, so when if not now?

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

Re: [JCS] GitHub builds broken and Java 17

[Thomas Vandahl]

Hi Gary,

> Am 26.08.2023 um 19:58 schrieb Gary Gregory :
> 
> Does anyone know why it's broken?
If anyone broke it, that was me. I tried to fix the build configurations but I 
simply don't understand what there doing. I never put them up in the first 
place.

> And why is was switched to Java 17 only without warning?

Because it's about time? There's a major release necessary anyway because so 
much deprecated code needs to be removed, so when if not now?

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

[CANCEL]: [VOTE] Release Apache Commons JCS 3.2 based on rc1

[Thomas Vandahl]

Will need to fix some links in the vote mail.

> Am 22.08.2023 um 15:14 schrieb Thomas Vandahl :
> 
> We have fixed quite a few bugs and added some significant enhancements since 
> Apache Commons JCS 3.1 was released, so I would like to release Apache 
> Commons JCS 3.2.
> 
> Apache Commons JCS 3.2 rc1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1 (svn revision 
> 63581)
> 
> The Git tag commons-jcs-3.2-rc1 commit for this RC is 
> eb9c5b36b48f2b6f45fba7986d46c7006cfb5c4c which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=eb9c5b36b48f2b6f45fba7986d46c7006cfb5c4c
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch 
> commons-jcs3-3.2-rc1 commons-jcs3-3.2-rc1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-orgapachecommons-1650/org/apache/commons/commons-jcs3/3.2/
> 
> These are the artifacts and their hashes:
> 
> 6fb8c140c49229339ccea583c462e20b5f2abfd13b3615f466e5b7e44abfbfa7f662ce25b54edcf433c2b7010e4b32c2cde09f2da7754d7f697e871b76f61c91
>   commons-jcs3-dist-3.2-bin.tar.gz
> 6d2c47f3e41a6fca3fa94dd423d8e9c4bc76929778d5d44ee094a2d8465f1449feffee24ee1248e80baaec8e2c08051ff3fdcae76610591b451e796904f5dd46
>   commons-jcs3-dist-3.2-bin.zip
> 16c8bb7abe9268a39b80ce03a57adf1ac596191e4aee80756443d1861b850ffe5b67f6fbd9d46f1189d4247b7b928192cb7fb28f45e8bc768317972276acac9a
>   commons-jcs3-dist-3.2-src.tar.gz
> 1f78fdc0be26f0b8b350ef2623191a28e13131b6a98abc51927aada192b7b381d1d7264a2083f23a72bf0906a0e4164e0c2a5aee11c3448408399cc87f0b912e
>   commons-jcs3-dist-3.2-src.zip
> 
> I have tested this with ***'mvn clean install site site:stage'*** using:
> 
> Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
> Java version: 1.8.0_311, vendor: Oracle Corporation, runtime: 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_311.jdk/Contents/Home/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
> 
> Details of changes since 3.1 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/site/changes-report.html
> 
> Site:
>https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/site/index.html
>(note some *relative* links are broken and the 3.2 directories are not yet 
> created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 3.1):
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/site/commons-jcs3-core/japicmp.html
> 
>***
>Note that the above report notes several errors.
>These are considered OK for the reasons stated below.
>These exceptions are also noted in the Changes and Release Notes.
> 
>Errors reported:
>- methods added to interface: OK because that does not affect binary 
> compatibility.
>- annotation @Deprecated added to classes
>***
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/site/rat-report.html
> 
> KEYS:
>  https://www.apache.org/dist/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,
> 
> Thomas Vandahl (tv),
> Release Manager (using key 88817402)
> 
> For following is intended as a helper and refresher for reviewers.
> 
> Validating a release candidate
> ==
> 
> These guidelines are NOT complete.
> 
> Requirements: Git, Java, Maven.
> 
> You can validate a release from a release candidate (RC) tag as follows.
> 
> 1) Clone and checkout the RC tag
> 
> git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch 
> commons-jcs3-3.2-rc1 commons-jcs3-3.2-rc1
> cd commons-jcs3-3.2-rc1
> 
> 2) Check Apache licenses
> 
> This step is not required if the site includes a RAT report page which you 
> then must check.
> 
> mvn apache-rat:check
> 
> 3) Check binary compatibility
> 
> Newer components use JApiCmp with the japicmp Maven Profile:
> 
> This step is not required if the site includes a JApiCmp report page which 
> you then must check.
> 
> mvn install -DskipTests -P japicmp japicmp:cmp
> 
> 4) Build the package
> 
> mvn -V clean package
> 
> You can record the Maven and Java version pr

[VOTE] Release Apache Commons JCS 3.2 based on rc1 (2nd round with fixed links)

[Thomas Vandahl]

We have fixed quite a few bugs and added some significant enhancements since 
Apache Commons JCS 3.1 was released, so I would like to release Apache Commons 
JCS 3.2.

Apache Commons JCS 3.2 rc1 is available for review here:
   https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1 (svn revision 
63581)

The Git tag commons-jcs3-3.2-rc1 commit for this RC is 
6ff84134fa295b608531f9655f075ea58635cd57 which you can browse here:
  
https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=6ff84134fa295b608531f9655f075ea58635cd57

You may checkout this tag using:
   git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch 
commons-jcs3-3.2-rc1 commons-jcs3-3.2-rc1

Maven artifacts are here:
   
https://repository.apache.org/content/repositories/orgapachecommons-1650/org/apache/commons/commons-jcs3/3.2/

These are the release artifacts and their hashes:

6fb8c140c49229339ccea583c462e20b5f2abfd13b3615f466e5b7e44abfbfa7f662ce25b54edcf433c2b7010e4b32c2cde09f2da7754d7f697e871b76f61c91
  commons-jcs3-dist-3.2-bin.tar.gz
6d2c47f3e41a6fca3fa94dd423d8e9c4bc76929778d5d44ee094a2d8465f1449feffee24ee1248e80baaec8e2c08051ff3fdcae76610591b451e796904f5dd46
  commons-jcs3-dist-3.2-bin.zip
16c8bb7abe9268a39b80ce03a57adf1ac596191e4aee80756443d1861b850ffe5b67f6fbd9d46f1189d4247b7b928192cb7fb28f45e8bc768317972276acac9a
  commons-jcs3-dist-3.2-src.tar.gz
1f78fdc0be26f0b8b350ef2623191a28e13131b6a98abc51927aada192b7b381d1d7264a2083f23a72bf0906a0e4164e0c2a5aee11c3448408399cc87f0b912e
  commons-jcs3-dist-3.2-src.zip

I have tested this with ***'mvn clean install site site:stage'*** using:

Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
Java version: 1.8.0_311, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk1.8.0_311.jdk/Contents/Home/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"

Details of changes since 3.1 are in the release notes:
   https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/RELEASE-NOTES.txt
   
https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/site/changes-report.html

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

JApiCmp Report (compared to 3.1):
   
https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/site/commons-jcs3-core/japicmp.html

   ***
   Note that the above report notes several errors.
   These are considered OK for the reasons stated below.
   These exceptions are also noted in the Changes and Release Notes.

   Errors reported:
   - methods added to interface: OK because that does not affect binary 
compatibility.
   - annotation @Deprecated added to classes
   ***

RAT Report:
   
https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/site/rat-report.html

KEYS:
 https://www.apache.org/dist/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,

Thomas Vandahl (tv),
Release Manager (using key 88817402)

For following is intended as a helper and refresher for reviewers.

Validating a release candidate
==

These guidelines are NOT complete.

Requirements: Git, Java, Maven.

You can validate a release from a release candidate (RC) tag as follows.

1) Clone and checkout the RC tag

git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch 
commons-jcs3-3.2-rc1 commons-jcs3-3.2-rc1
cd commons-jcs3-3.2-rc1

2) Check Apache licenses

This step is not required if the site includes a RAT report page which you then 
must check.

mvn apache-rat:check

3) Check binary compatibility

Newer components use JApiCmp with the japicmp Maven Profile:

This step is not required if the site includes a JApiCmp report page which you 
then must check.

mvn install -DskipTests -P japicmp japicmp:cmp

4) Build the package

mvn -V clean package

You can record the Maven and Java version produced by -V in your VOTE reply.
To gather OS information from a command line:
Windows: ver
Linux: uname -a

5) Build the site for a single module project

Note: Some plugins require the components to be installed instead of packaged.

mvn site
Check the site reports in:
- Windows: target\site\index.html
- Linux: target/site/index.html

6) Build the site for a multi-module project

mvn site
mvn site:stage
Check the site reports in:
- Windows: target\site\index.html
- Linux: target/site/index.html

-the end-


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


--

Re: [VOTE] Release Apache Commons JCS 3.2 based on rc1 (2nd round with fixed links)

[Thomas Vandahl]

> Please review the release candidate and vote.
> This vote will close no sooner than 72 hours from now.
> 
> [X] +1 Release these artifacts
> [ ] +0 OK, but...
> [ ] -0 OK, but really should fix...
> [ ] -1 I oppose this release because...

My vote

Bye, Thomas


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

Re: [VOTE] Release Apache Commons JCS 3.2 based on rc1 (2nd round with fixed links)

[Thomas Vandahl]

Could I have one more (positive :-) PMC vote please?

> Am 03.09.2023 um 17:51 schrieb Thomas Vandahl :
> 
> We have fixed quite a few bugs and added some significant enhancements since 
> Apache Commons JCS 3.1 was released, so I would like to release Apache 
> Commons JCS 3.2.
> 
> Apache Commons JCS 3.2 rc1 is available for review here:
>   https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1 (svn revision 
> 63581)
> 
> The Git tag commons-jcs3-3.2-rc1 commit for this RC is 
> 6ff84134fa295b608531f9655f075ea58635cd57 which you can browse here:
>  
> https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=6ff84134fa295b608531f9655f075ea58635cd57
> 
> You may checkout this tag using:
>   git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch 
> commons-jcs3-3.2-rc1 commons-jcs3-3.2-rc1
> 
> Maven artifacts are here:
>   
> https://repository.apache.org/content/repositories/orgapachecommons-1650/org/apache/commons/commons-jcs3/3.2/
> 
> These are the release artifacts and their hashes:
> 
> 6fb8c140c49229339ccea583c462e20b5f2abfd13b3615f466e5b7e44abfbfa7f662ce25b54edcf433c2b7010e4b32c2cde09f2da7754d7f697e871b76f61c91
>   commons-jcs3-dist-3.2-bin.tar.gz
> 6d2c47f3e41a6fca3fa94dd423d8e9c4bc76929778d5d44ee094a2d8465f1449feffee24ee1248e80baaec8e2c08051ff3fdcae76610591b451e796904f5dd46
>   commons-jcs3-dist-3.2-bin.zip
> 16c8bb7abe9268a39b80ce03a57adf1ac596191e4aee80756443d1861b850ffe5b67f6fbd9d46f1189d4247b7b928192cb7fb28f45e8bc768317972276acac9a
>   commons-jcs3-dist-3.2-src.tar.gz
> 1f78fdc0be26f0b8b350ef2623191a28e13131b6a98abc51927aada192b7b381d1d7264a2083f23a72bf0906a0e4164e0c2a5aee11c3448408399cc87f0b912e
>   commons-jcs3-dist-3.2-src.zip
> 
> I have tested this with ***'mvn clean install site site:stage'*** using:
> 
> Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
> Java version: 1.8.0_311, vendor: Oracle Corporation, runtime: 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_311.jdk/Contents/Home/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
> 
> Details of changes since 3.1 are in the release notes:
>   https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/RELEASE-NOTES.txt
>   
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/site/changes-report.html
> 
> Site:
>   https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/site/index.html
>   (note some *relative* links are broken and the 3.2 directories are not yet 
> created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 3.1):
>   
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/site/commons-jcs3-core/japicmp.html
> 
>   ***
>   Note that the above report notes several errors.
>   These are considered OK for the reasons stated below.
>   These exceptions are also noted in the Changes and Release Notes.
> 
>   Errors reported:
>   - methods added to interface: OK because that does not affect binary 
> compatibility.
>   - annotation @Deprecated added to classes
>   ***
> 
> RAT Report:
>   
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/site/rat-report.html
> 
> KEYS:
> https://www.apache.org/dist/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,
> 
> Thomas Vandahl (tv),
> Release Manager (using key 88817402)
> 
> For following is intended as a helper and refresher for reviewers.
> 
> Validating a release candidate
> ==
> 
> These guidelines are NOT complete.
> 
> Requirements: Git, Java, Maven.
> 
> You can validate a release from a release candidate (RC) tag as follows.
> 
> 1) Clone and checkout the RC tag
> 
> git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch 
> commons-jcs3-3.2-rc1 commons-jcs3-3.2-rc1
> cd commons-jcs3-3.2-rc1
> 
> 2) Check Apache licenses
> 
> This step is not required if the site includes a RAT report page which you 
> then must check.
> 
> mvn apache-rat:check
> 
> 3) Check binary compatibility
> 
> Newer components use JApiCmp with the japicmp Maven Profile:
> 
> This step is not required if the site includes a JApiCmp report page which 
> you then must check.
> 
> mvn install -DskipTests -P japicmp japicmp:cmp
> 
> 4) Build the package
> 
> mvn -V clean package
> 
> You can record the Maven and Java version produced by -V in your VOTE rep

JCS vote

[Thomas Vandahl]

Hi folks,

Could some kind soul please find some time to vote on the release 3.2 of JCS?
Perhaps this weekend? 

We would need one more PMC vote.

Thank you!
Bye, Thomas 

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

[RESULT][VOTE] Release Apache Commons JCS 3.2 based on rc1 (2nd round with fixed links)

[Thomas Vandahl]

This vote passes with the following binding +1 votes:
- Henri Biestro
- Rob Tompkins
- Gary Gregory
- Thomas Vandahl

Thanks to all the voters.
I will proceed with the publication.

Bye, Thomas 

> Am 16.09.2023 um 13:41 schrieb Rob Tompkins :
> 
> +1
> Signatures validate properly
> Build works appropriately on java 8, 11, and 17
> Reports all look appropriate, RAT (licenses), japicmp (backwards 
> compatibility), and soptbugs
> Nit (major, non-blocking). No site built for commons-jcs: Apache Commons 
> Distribution or for JCache, OpenJPA
> 
> Thanks for all the hard work!!!, pardon that I havent rolled a release 
> candidate for a while.
> -Rob
> 
>> On Sep 3, 2023, at 11:51 AM, Thomas Vandahl  wrote:
>> 
>> We have fixed quite a few bugs and added some significant enhancements since 
>> Apache Commons JCS 3.1 was released, so I would like to release Apache 
>> Commons JCS 3.2.
>> 
>> Apache Commons JCS 3.2 rc1 is available for review here:
>>  https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1 (svn revision 
>> 63581)
>> 
>> The Git tag commons-jcs3-3.2-rc1 commit for this RC is 
>> 6ff84134fa295b608531f9655f075ea58635cd57 which you can browse here:
>> https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=6ff84134fa295b608531f9655f075ea58635cd57
>> 
>> You may checkout this tag using:
>>  git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch 
>> commons-jcs3-3.2-rc1 commons-jcs3-3.2-rc1
>> 
>> Maven artifacts are here:
>>  
>> https://repository.apache.org/content/repositories/orgapachecommons-1650/org/apache/commons/commons-jcs3/3.2/
>> 
>> These are the release artifacts and their hashes:
>> 
>> 6fb8c140c49229339ccea583c462e20b5f2abfd13b3615f466e5b7e44abfbfa7f662ce25b54edcf433c2b7010e4b32c2cde09f2da7754d7f697e871b76f61c91
>>   commons-jcs3-dist-3.2-bin.tar.gz
>> 6d2c47f3e41a6fca3fa94dd423d8e9c4bc76929778d5d44ee094a2d8465f1449feffee24ee1248e80baaec8e2c08051ff3fdcae76610591b451e796904f5dd46
>>   commons-jcs3-dist-3.2-bin.zip
>> 16c8bb7abe9268a39b80ce03a57adf1ac596191e4aee80756443d1861b850ffe5b67f6fbd9d46f1189d4247b7b928192cb7fb28f45e8bc768317972276acac9a
>>   commons-jcs3-dist-3.2-src.tar.gz
>> 1f78fdc0be26f0b8b350ef2623191a28e13131b6a98abc51927aada192b7b381d1d7264a2083f23a72bf0906a0e4164e0c2a5aee11c3448408399cc87f0b912e
>>   commons-jcs3-dist-3.2-src.zip
>> 
>> I have tested this with ***'mvn clean install site site:stage'*** using:
>> 
>> Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
>> Java version: 1.8.0_311, vendor: Oracle Corporation, runtime: 
>> /Library/Java/JavaVirtualMachines/jdk1.8.0_311.jdk/Contents/Home/jre
>> Default locale: de_DE, platform encoding: UTF-8
>> OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
>> 
>> Details of changes since 3.1 are in the release notes:
>>  https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/RELEASE-NOTES.txt
>>  
>> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/site/changes-report.html
>> 
>> Site:
>>  https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/site/index.html
>>  (note some *relative* links are broken and the 3.2 directories are not yet 
>> created - these will be OK once the site is deployed.)
>> 
>> JApiCmp Report (compared to 3.1):
>>  
>> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/site/commons-jcs3-core/japicmp.html
>> 
>>  ***
>>  Note that the above report notes several errors.
>>  These are considered OK for the reasons stated below.
>>  These exceptions are also noted in the Changes and Release Notes.
>> 
>>  Errors reported:
>>  - methods added to interface: OK because that does not affect binary 
>> compatibility.
>>  - annotation @Deprecated added to classes
>>  ***
>> 
>> RAT Report:
>>  
>> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/site/rat-report.html
>> 
>> KEYS:
>> https://www.apache.org/dist/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,
>> 
>> Thomas Vandahl (tv),
>> Release Manager (using key 88817402)
>> 
>> For following is intended as a helper and refresher for reviewers.
>> 
>> Validating a release candidate
>> ==

[ANNOUNCEMENT] Apache Commons JCS 3.2 Released

[Thomas Vandahl]

The Apache Commons JCS team is pleased to announce the Apache Commons JCS 3.2 
release!

Apache Commons JCS is a distributed, versatile caching system.

Changes in this version include:

Fixed Bugs:
o Fix OSGi manifest  Issue: JCS-234. Thanks to Chris Lake. 
o Handle ServiceConfigurationError when using a different logging framework  
Issue: JCS-232. Thanks to Jeremy Long. 
o Fix Lateral TCP cache recovery loop for empty TCP servers  Issue: JCS-231. 
Thanks to Andrea Vettori. 
o UDPDiscoveryReceiver with EncryptingSerializer fails #88.  Issue: JCS-230. 
Thanks to Dorota Oeknigk-Urbanska. 
o LateralTCPListener class uses always StandardSerializer #89.  Issue: JCS-229. 
Thanks to Dorota Oeknigk-Urbanska. 

Changes:
o Bump actions/cache from 2.1.7 to 3.0.9 #86, #111. Thanks to Dependabot, Gary 
Gregory. 
o Bump actions/checkout from 2 to 3.0.2 #93. Thanks to Dependabot, Gary 
Gregory. 
o Bump actions/setup-java from 2 to 3.5.1. Thanks to Gary Gregory. 
o Bump commons-parent from 52 to 58 #90, #130, #154. Thanks to Dependabot. 
o Bump log4j-api from 2.17.1 to 2.20.0 #85, #100, #107, #145. Thanks to 
Dependabot. 
o Bump log4j-core from 2.17.1 to 2.20.0 #87, #99, #108, #144. Thanks to 
Dependabot. 
o Bump commons-text from 1.9 to 1.10.0 #110. Thanks to Dependabot. 
o Bump commons-io from 2.11.0 to 2.12.0. Thanks to Gary Gregory. 

For complete information on Apache Commons JCS, including instructions on how 
to submit bug reports, patches, or suggestions for improvement, see the Apache 
Commons JCS website:

https://commons.apache.org/proper/commons-jcs/

Download it from
https://commons.apache.org/proper/commons-jcs/download_jcs.cgi

Thomas Vandahl 
Apache Commons Team

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

[JCS] Could please anyone with access to bugs.openjdk.java.net help me documenting a bug fix?

[Thomas Vandahl]

Hi folks,

In JCS I just fixed a bug that was caused by a changed JDK behaviour when 
handling remote exported methods. 

The change reportedly was a fix for 
https://bugs.openjdk.java.net/browse/JDK-8230967 

This ticket, unfortunately, is not publicly available. I would like to document 
the JDK versions when this change was introduced. It looks like JDK 8u241 and 
JDK 11.0.6 are possible candidates but I don't know for sure. 

Could please someone with access to the ticket help me dig up the missing 
information?

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

[JCS] Advice sought on releasing just core

[Thomas Vandahl]

Hi folks,

would it be considered good practice to release just one sub-component 
(commons-jcs3-core) of the project to fix bugs? All other components are 
unaffected. What would be the release artefact to vote on? Please advise.

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

Re: [VOTE] Release Apache Commons Compress 1.25.0 based on RC1

[Thomas Vandahl]

>  [X] +1 Release these artifacts

Signatures ok, build and tests run fine, site and reports look good.

Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
Maven home: /Users/thomas/Dev/apache-maven-3.8.4
Java version: 17.0.8, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk-17.jdk/Contents/Home
Default locale: de_DE, platform encoding: UTF-8
OS name: "mac os x", version: "11.7.10", arch: "x86_64", family: "mac"

Bye, Thomas 


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

[VOTE] Release Apache Commons JCS 3.2.1 based on rc1

[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.

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 commons-jcs3-3.2.1-rc1 commit for this RC is 
0b20664b6c60b025cfe0e95c33e86f3239822a12 which you can browse here:

https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=0b20664b6c60b025cfe0e95c33e86f3239822a12
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch 
commons-jcs3-3.2.1-rc1 commons-jcs3-3.2.1-rc1

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1712/org/apache/commons/commons-jcs3/3.2.1/

These are the artifacts and their hashes:

5ea0cfd1ea5d17689ce35fd4a26ad104028b2b0d3209cf8c3d58d1a8e62c77442de95d51af278ad810a28117d0297725ded41b18553e05212dfc9e9db1dd185c
  commons-jcs3-dist-3.2.1-bin.tar.gz
ce7151767ebcf5ce08c9e91689ef1b240344b874963edc3042c0a6958e02deb95551aa9de1a8f63fd6e87198f179ad90501a0b76f96cf6c2c10cd546e867c8bf
  commons-jcs3-dist-3.2.1-bin.zip
8abc08f18edf6fcd86d9fcb8834ef4584d6932a6a7dca8936b199b6aec3622e634c20f639fdb5cd1077d2492e1a8fd3dafb0ceb9a259127c3dfc3ec54d6cea1b
  commons-jcs3-dist-3.2.1-src.tar.gz
e7a2796bc07b9da4d8e5db0423baa758e0e139e8cdc35aa6d50e32cdfa9163b874eeedfd52e90c599049faa1963546109389fb967e60df8a0198a025a3d75869
  commons-jcs3-dist-3.2.1-src.zip

I have tested this with ***'mvn clean install site'*** using:

Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
Java version: 1.8.0_311, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk1.8.0_311.jdk/Contents/Home/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"

Details of changes since 3.2 are in the release notes:

https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/RELEASE-NOTES.txt

https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/site/changes-report.html

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

JApiCmp Report (compared to 3.2):

https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/site/commons-jcs3-core/japicmp.html
RAT Report:

https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/site/commons-jcs3-core/rat-report.html

KEYS:
https://www.apache.org/dist/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,

Bye, Thomas 
Release Manager (using key 88817402)




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

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

[Thomas Vandahl]

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...
>  [ ] -1 I oppose this release because...

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

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

[Thomas Vandahl]

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 directory names are
> artifact IDs, for example, "commons-jcs3-core":
> https://github.com/apache/commons-jcs/tree/master/commons-jcs3-core
> 
> But at the release tag commons-jcs3-3.2.1-rc1, all of the folders are
> missing the "3" postfix:
> https://github.com/apache/commons-jcs/tree/commons-jcs3-3.2.1-rc1 ?
> 

Yes, this is intentional. The branch release-3.2.1 has been branched from 
release-3.2 because that was what I was trying to fix. The master branch is 
already at 4.0 and not ready for release. The directories were renamed in 
commit 49091a01a2ea6d658186872b7cb1ea6f45187320 which was after the 3.2 
release. 

HTH
Bye, Thomas 


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

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

[Thomas Vandahl]

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 much compared to 3.2.

Bye, Thomas 


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

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

[Thomas Vandahl]

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 the changes report 
was invented for?

Bye, Thomas 


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

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

[Thomas Vandahl]

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-report.html
 

 
Please note that the changes.xml is valid according to its xsd.
What VM file do you mean?

Bye, Thomas 

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

[Thomas Vandahl]

Hi Bruno,

> Am 04.04.2024 um 21:46 schrieb Bruno Kinoshita :
> 
> Failed to collect
> dependencies at org.apache.openjpa:openjpa:jar:2.4.3 ->
> org.apache.openjpa:openjpa-kernel:jar:2.4.3 ->
> com.ibm.websphere:websphere_uow_api:jar:0.0.1: Failed to read artifact
> descriptor for com.ibm.websphere:websphere_uow_api:jar:0.0.1: Could not
> transfer artifact com.ibm.websphere:websphere_uow_api:pom:0.0.1 from/to
> openjpa-internal (file://${basedir}/internal-repository): Repository path
> /internal-repository does not exist, and cannot be created.

This is probably caused by the settings in here: 
https://repo1.maven.org/maven2/org/apache/openjpa/openjpa-kernel/2.4.3/openjpa-kernel-2.4.3.pom

As this library has been a dependency of commons-jcs3-jcache-openjpa for quite 
a while, I don't know why the websphere artifact is missing all of a sudden. 
The comment in the pom mentions a private repository in SVN. The artifacts 
required can be found here, however: 
https://github.com/apache/openjpa/tree/2.4.x/openjpa-kernel/internal-repository/com/ibm/websphere/websphere_uow_api/0.0.1

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

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

[Thomas Vandahl]

Hi Gary,

> Am 04.04.2024 um 22:30 schrieb Gary D. Gregory :
> 
> 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, Time elapsed: 9.339 
> s <<< FAILURE! - in 
> org.apache.commons.jcs3.utils.discovery.UDPDiscoverySenderEncryptedUnitTest
> [ERROR] 
> org.apache.commons.jcs3.utils.discovery.UDPDiscoverySenderEncryptedUnitTest.testRequestBroadcast
>   Time elapsed: 3.23 s  <<< FAILURE!
> junit.framework.AssertionFailedError: message not received

This code has not been touched since 3.2. Could you please verify that this 
problem is also present in 3.2?

Bye, Thomas 


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

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

[Thomas Vandahl]

Hi folks,

> Am 05.04.2024 um 23:26 schrieb Gary Gregory :
> 
> Wow, that's the first macOS failure for this type of issue. Bruno and I
> both see this on Windows.

Ok, let's try to fix this. Could you please run the affected test only with 
debug log and provide the log files to me? 
I'll cancel the vote now.

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

[CANCEL][VOTE] Release Apache Commons JCS 3.2.1 based on rc1

[Thomas Vandahl]

I am cancelling the vote because of strange test failures in some environments.

Bye, Thomas 

> 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.
> 
> 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 commons-jcs3-3.2.1-rc1 commit for this RC is 
> 0b20664b6c60b025cfe0e95c33e86f3239822a12 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=0b20664b6c60b025cfe0e95c33e86f3239822a12
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch 
> commons-jcs3-3.2.1-rc1 commons-jcs3-3.2.1-rc1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1712/org/apache/commons/commons-jcs3/3.2.1/
> 
> These are the artifacts and their hashes:
> 
> 5ea0cfd1ea5d17689ce35fd4a26ad104028b2b0d3209cf8c3d58d1a8e62c77442de95d51af278ad810a28117d0297725ded41b18553e05212dfc9e9db1dd185c
>   commons-jcs3-dist-3.2.1-bin.tar.gz
> ce7151767ebcf5ce08c9e91689ef1b240344b874963edc3042c0a6958e02deb95551aa9de1a8f63fd6e87198f179ad90501a0b76f96cf6c2c10cd546e867c8bf
>   commons-jcs3-dist-3.2.1-bin.zip
> 8abc08f18edf6fcd86d9fcb8834ef4584d6932a6a7dca8936b199b6aec3622e634c20f639fdb5cd1077d2492e1a8fd3dafb0ceb9a259127c3dfc3ec54d6cea1b
>   commons-jcs3-dist-3.2.1-src.tar.gz
> e7a2796bc07b9da4d8e5db0423baa758e0e139e8cdc35aa6d50e32cdfa9163b874eeedfd52e90c599049faa1963546109389fb967e60df8a0198a025a3d75869
>   commons-jcs3-dist-3.2.1-src.zip
> 
> I have tested this with ***'mvn clean install site'*** using:
> 
> Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
> Java version: 1.8.0_311, vendor: Oracle Corporation, runtime: 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_311.jdk/Contents/Home/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
> 
> Details of changes since 3.2 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/site/index.html
>(note some *relative* links are broken and the 3.2.1 directories are not 
> yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 3.2):
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/site/commons-jcs3-core/japicmp.html
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/site/commons-jcs3-core/rat-report.html
> 
> KEYS:
>https://www.apache.org/dist/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,
> 
> Bye, Thomas 
> Release Manager (using key 88817402)
> 
> 
> 
> 
> -
> 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: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

[Thomas Vandahl]

Hi Gary,

> Am 05.04.2024 um 17:28 schrieb Gary D. Gregory :
> 
> [INFO] Running 
> org.apache.commons.jcs3.utils.discovery.UDPDiscoverySenderEncryptedUnitTest
> [ERROR] Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 9.526 
> s <<< FAILURE! - in 
> org.apache.commons.jcs3.utils.discovery.UDPDiscoverySenderEncryptedUnitTest
> [ERROR] 
> org.apache.commons.jcs3.utils.discovery.UDPDiscoverySenderEncryptedUnitTest.testRequestBroadcast
>   Time elapsed: 3.36 s  <<< FAILURE!

Could you please check that the test 
org.apache.commons.jcs3.utils.discovery.UDPDiscoverySenderUnitTest runs fine on 
Windows under all circumstances? If so, we would need to look at 
org.apache.commons.jcs3.utils.serialization.EncryptingSerializer because that 
is the only difference between the two tests.

Bye, Thomas 


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

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

[Thomas Vandahl]

Hi Gary,

> Am 06.04.2024 um 14:10 schrieb Gary D. Gregory :
> 
> Hi Thomas,
> 
> I ran:
> 
> mvn test -Dtest=UDPDiscoverySenderUnitTest -X >\test\out.txt
> 
> and killed it after 10 minutes since it never finished. I tried 3 times.

Thanks. Not good. 
Could you please repeat the test with the log levels in 
/commons-jcs3-core/src/test/test-conf/logging.properties set to FINER and send 
me the content of target/jcs-logging-0.log?

Does this test run successfully when you run mvn clean verify for 
commons-jcs3-core?

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

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

[Thomas Vandahl]

Hi Gary,

> Am 06.04.2024 um 15:07 schrieb Gary D. Gregory :
> 
> mvn test -Dtest=UDPDiscoverySenderEncryptedUnitTest
> 
> which failed with the log here: https://paste.apache.org/b4p09

Thanks for helping me to tackle this. I see that the network interface used for 
the test is a "Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter 
for Windows x64", IOW a VPN.

As far as Google can tell, this interface does not support multicast (see for 
example here: 
https://community.cisco.com/t5/vpn/anyconnect-multicast-support/td-p/4479734 
)

Could that be the problem?

Bye, Thomas 

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

[Thomas Vandahl]

Hi Gary,

> Am 06.04.2024 um 15:07 schrieb Gary D. Gregory :
> 
> mvn test -Dtest=UDPDiscoverySenderEncryptedUnitTest
> 
> which failed with the log here: https://paste.apache.org/b4p09

Please check out from branch release-3.2.1 and try again. 

Bye, Thomas 


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

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

[Thomas Vandahl]

Hi Gary,

> Am 06.04.2024 um 17:20 schrieb Gary D. Gregory :
> 
> Ah, I was on git master on Windows, which without the VPN, now hangs in:
> 
> [INFO] Running 
> org.apache.commons.jcs3.auxiliary.disk.indexed.IndexedDiskCacheConcurrentNoDeadLockUnitTest
> 

Thou shalt not run the whole test suite with debug log on. :-)

> Switching to origin/release-3.2.1 lets me run the default Maven goal (just 
> 'mvn') to successfully to completion!

Could you please send me the debug log of 

mvn test -Dtest=UDPDiscoverySenderEncryptedUnitTest

so that I can see what the HostNameUtil detects in your case?

Bye, Thomas 

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

[Thomas Vandahl]

Hi Gary,

> Am 06.04.2024 um 17:48 schrieb Gary D. Gregory :
> 
> And to confirm that VPN is the issue, I reconnected and got:
> 
> [ERROR] Failures:
> [ERROR]   UDPDiscoverySenderEncryptedUnitTest.testPassiveBroadcast:116 
> message not received
> [ERROR]   UDPDiscoverySenderEncryptedUnitTest.testRemoveBroadcast:138 message 
> not received
> [ERROR]   UDPDiscoverySenderEncryptedUnitTest.testRequestBroadcast:157 
> message not received
> 
> So that's one for the release notes!

Well, there are probably more cases where we cannot find a multicast capable 
interface. I'll rather try to dynamically skip the tests when no multicast is 
available.  

Bye, Thomas 


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

Re: (commons-jcs) 03/03: Skip multicast tests when no multicast interface is available

[Thomas Vandahl]

Hi Gary,

> Am 06.04.2024 um 19:35 schrieb Gary Gregory :
> 
> This is where you want to use JUnit assumptions so you get visibility for
> skipped tests.
> 

Yes, I know. However, that does not work with the old JUnit3-style tests. I 
will fix this in the master branch where all tests already have been migrated.

Bye, Thomas 


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

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

[Thomas Vandahl]

Hi Gary,

> Am 06.04.2024 um 17:20 schrieb Gary D. Gregory :
> 
> Switching to origin/release-3.2.1 lets me run the default Maven goal (just 
> 'mvn') to successfully to completion!
> 

May I kindly ask for the debug log again? I'd like to know whether JCS can find 
a valid multicast interface even if the VPN is on.

Bye, Thomas 


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

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

[Thomas Vandahl]

Hi Sebastian

> Am 06.04.2024 um 15:38 schrieb sebb :
> 
> Another minor issue:
> If you run 'mvn test' without first doing 'mvn clean', it fails with:
> 
> [ERROR]   JDBCDiskCacheUnitTest.testInitializePoolAccess_withPoolName:157
> » SQL Table already exists: JCSTESTTABLE_INITIALIZEPOOLACCESS in
> statement [CREATE CACHED TABLE JCSTESTTABLE_InitializePoolAccess]
> 
> Something is not cleaning up properly after a test.
> 
> Whilst this does not affect the main code, cleanup issues have been
> known to affect the source bundle.
> Should ideally be fixed if there is to be a new RC.

I propose to fix this in the master branch and leave the bugfix release as it 
is. Ok?

Bye, Thomas 


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

[jcs] multicast issues, was: Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

[Thomas Vandahl]

(trying to move this out of the vote thread)

Hi Gary,

> Am 07.04.2024 um 14:33 schrieb Gary D. Gregory :
> 
> Hi Thomas,
> 
> Ran:
> 
> mvn test -Dtest=UDPDiscoverySenderEncryptedUnitTest
> 
> Log: 
> 
> https://paste.apache.org/1hmkb

Thank you. Could you please make sure that you are at commit 
fe20ca994803b353c32fd0909621d822ee26263c ?
I don't see the debug messages from HostNameUtil where I added the check for 
multicast support. 

If the code is current, that would imply that the Cisco adapter lies about its 
multicast support and that we cannot rely on the JDK to configure the tests. 
That would be really bad news.

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

Re: [jcs] multicast issues, was: Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

[Thomas Vandahl]

Hi Gary

> Am 07.04.2024 um 20:54 schrieb Gary D. Gregory :
> 
> Hi Thomas,
> 
> OK, here we go:
> 
> VPN on (Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for 
> Windows x64)
> git checkout fe20ca994803b353c32fd0909621d822ee26263c
> mvn clean test -Dtest=UDPDiscoverySenderEncryptedUnitTest
> 
> Same 3 failures, log: https://paste.apache.org/grnpx

Thank you. Strange. I still miss the messages of the network detection.
Could you please run the following code for me https://paste.apache.org/fkww0 
 once with VPN on and once with VPN off and 
send me the output?
On my machine (Mac), all interfaces report multicast capability, even the VPN 
ones, which looks wrong to me. Let's see what Windows says.

TIA,
Bye, Thomas 

[VOTE] Release Apache Commons JCS 3.2.1 based on rc2

[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.

Apache Commons JCS 3.2.1 rc2 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc2 (svn revision 
68673)

The Git tag commons-jcs3-3.2.1-rc2 commit for this RC is 
a2263c39fb07410ec75cf961362f9d9371298844 which you can browse here:

https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=a2263c39fb07410ec75cf961362f9d9371298844
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch 
commons-jcs3-3.2.1-rc2 commons-jcs3-3.2.1-rc2

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1722/org/apache/commons/commons-jcs3/3.2.1/

These are the artifacts and their hashes:

20f898a3f7c41de29249d9e7e57cab754c5aa710da43c7018ce25413fa695d4edb363e036fd57884652e05ccf1e6b5946c7f4ff4b9a723affca42914e89935af
  commons-jcs3-dist-3.2.1-bin.tar.gz
fe454deabd3311c2c7b59db7ce25db49f6ba0bccfd97bb9262e38adaeb00cbb16d6ba8542b75d816a5ca05098782cf44374d3fe0573814370923fef940d00c56
  commons-jcs3-dist-3.2.1-bin.zip
7c9d912978f0f88a01e9e2a9475bd07a6c81379bb12f4a4cbdeec890899c7dbdcb6421c45c0655d28cf951f284ab32ca61d8a1aedbdad46d05bd127c060c5968
  commons-jcs3-dist-3.2.1-src.tar.gz
4c513b03909fdfe9dff1e6d6689e33b8badd92f5d6d470172ad1fdfe86f0869398cc77ff2cb114db8648a332d47375c6615ac26d574fa9882b7564481cc14f72
  commons-jcs3-dist-3.2.1-src.zip

I have tested this with ***'mvn clean install site site:stage'*** using:
--
Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
Java version: 17.0.8, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk-17.jdk/Contents/Home
Default locale: de_DE, platform encoding: UTF-8
OS name: "mac os x", version: "11.7.10", arch: "x86_64", family: "mac"
--

NOTE: Some JCS tests require a working multicast setup. If you get test 
failures from tests 
starting with UDPDiscovery*, make sure that your network supports multicast 
(most VPNs do not,
for example).


Details of changes since 3.2 are in the release notes:

https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc2/RELEASE-NOTES.txt

https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc2/site/changes-report.html

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

JApiCmp Report (compared to 3.2):

https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc2/site/commons-jcs3-core/japicmp.html

RAT Report:

https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc2/site/commons-jcs3-core/rat-report.html

KEYS:
  https://www.apache.org/dist/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,

tv,
Release Manager (using key 88817402)


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

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc2

[Thomas Vandahl]

My vote.

> Am 20.04.2024 um 12:25 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.
> 
> Apache Commons JCS 3.2.1 rc2 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc2 (svn revision 
> 68673)
> 
>  [X] +1 Release these artifacts
>  [ ] +0 OK, but...
>  [ ] -0 OK, but really should fix...
>  [ ] -1 I oppose this release because...
> 

Bye, Thomas 


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

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc2

[Thomas Vandahl]

Hi Gary,

> Am 20.04.2024 um 15:30 schrieb Gary D. Gregory :
> 
> Something is wrong with at least one ASC file: 
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc2/commons-jcs3-dist-3.2.1-src.zip.asc
> 
> $ gpg --verify commons-jcs3-dist-3.2.1-src.zip.asc
> gpg: assuming signed data in 'commons-jcs3-dist-3.2.1-src.zip'
> gpg: Signature made Sat, Apr 20, 2024 05:43:52 AM EDT
> gpg:using DSA key 839B8C32286C100BDB08F5522EB9468288817402

I have no idea why Maven suddenly prefers my DSA key over my RSA key. I added 
the former to the KEYS file. Please try again.

Bye, Thomas 


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

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc2

[Thomas Vandahl]

Hi folks,

> Am 20.04.2024 um 12:25 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.
> 
> Apache Commons JCS 3.2.1 rc2 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc2 (svn revision 
> 68673)
> 

Could I please ask for one more vote?

TIA
Bye, Thomas 


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

Re: [VOTE] Release Apache Commons CSV 1.11.0 based on RC1

[Thomas Vandahl]

Hi Gary,

> Am 29.04.2024 um 00:24 schrieb Gary Gregory :
> 
> We have fixed a few bugs and added enhancements (better Microsoft
> Excel compatibility) since Apache Commons CSV 1.10.0 was released, so
> I would like to release Apache Commons CSV 1.11.0.
> 
>  [X] +1 Release these artifacts
>  [ ] +0 OK, but...
>  [ ] -0 OK, but really should fix...
>  [ ] -1 I oppose this release because...
> 

Signatures and hashes are ok.

Build and tests run ok with "mvn clean verify site" using
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Java version: 17.0.8, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk-17.jdk/Contents/Home
Default locale: de_DE, platform encoding: UTF-8
OS name: "mac os x", version: "11.7.10", arch: "x86_64", family: "mac"

Bye, Thomas 

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc2

[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 

[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 
> <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

[CANCEL][VOTE] Release Apache Commons JCS 3.2.1 based on rc2

[Thomas Vandahl]

Next attempt.

> Am 20.04.2024 um 12:25 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.
> 
> Apache Commons JCS 3.2.1 rc2 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc2 (svn revision 
> 68673)
> 
> The Git tag commons-jcs3-3.2.1-rc2 commit for this RC is 
> a2263c39fb07410ec75cf961362f9d9371298844 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=a2263c39fb07410ec75cf961362f9d9371298844
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch 
> commons-jcs3-3.2.1-rc2 commons-jcs3-3.2.1-rc2
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1722/org/apache/commons/commons-jcs3/3.2.1/
> 
> These are the artifacts and their hashes:
> 
> 20f898a3f7c41de29249d9e7e57cab754c5aa710da43c7018ce25413fa695d4edb363e036fd57884652e05ccf1e6b5946c7f4ff4b9a723affca42914e89935af
>   commons-jcs3-dist-3.2.1-bin.tar.gz
> fe454deabd3311c2c7b59db7ce25db49f6ba0bccfd97bb9262e38adaeb00cbb16d6ba8542b75d816a5ca05098782cf44374d3fe0573814370923fef940d00c56
>   commons-jcs3-dist-3.2.1-bin.zip
> 7c9d912978f0f88a01e9e2a9475bd07a6c81379bb12f4a4cbdeec890899c7dbdcb6421c45c0655d28cf951f284ab32ca61d8a1aedbdad46d05bd127c060c5968
>   commons-jcs3-dist-3.2.1-src.tar.gz
> 4c513b03909fdfe9dff1e6d6689e33b8badd92f5d6d470172ad1fdfe86f0869398cc77ff2cb114db8648a332d47375c6615ac26d574fa9882b7564481cc14f72
>   commons-jcs3-dist-3.2.1-src.zip
> 
> I have tested this with ***'mvn clean install site site:stage'*** using:
> --
> Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
> Java version: 17.0.8, vendor: Oracle Corporation, runtime: 
> /Library/Java/JavaVirtualMachines/jdk-17.jdk/Contents/Home
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "11.7.10", arch: "x86_64", family: "mac"
> --
> 
> NOTE: Some JCS tests require a working multicast setup. If you get test 
> failures from tests 
> starting with UDPDiscovery*, make sure that your network supports multicast 
> (most VPNs do not,
> for example).
> 
> 
> Details of changes since 3.2 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc2/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc2/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc2/site/index.html
>(note some *relative* links are broken and the 3.2.1 directories are not 
> yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 3.2):
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc2/site/commons-jcs3-core/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc2/site/commons-jcs3-core/rat-report.html
> 
> KEYS:
>  https://www.apache.org/dist/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,
> 
> tv,
> Release Manager (using key 88817402)
> 
> 
> -
> 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

[VOTE] Release Apache Commons JCS 3.2.1 based on rc3

[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.

Apache Commons JCS 3.2.1 rc3 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc3 (svn revision 
69406)

The Git tag commons-jcs3-3.2.1-rc3 commit for this RC is 
2d54b71517cb2baf7d38107978b96a780a1c162c which you can browse here:

https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=2d54b71517cb2baf7d38107978b96a780a1c162c
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch 
commons-jcs3-3.2.1-rc3 commons-jcs3-3.2.1-rc3

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1735/org/apache/commons/commons-jcs3/3.2.1/

These are the artifacts and their hashes:

ef5d5144eade500659f3789ddcfc780ce61a65ea60b388f5b2c2d6605712707ccf324d4b7cb974a08c23ee46db11d9fcf26f1730b58bdf3ac44a99dfaab70577
  commons-jcs3-dist-3.2.1-bin.tar.gz
658d4639652e8b326015ca0673c7517226c7bf6a9d364de5d06852059ce6042b05c096bb5de3646236a0ad5e6dc0fdaa9268d678e3748a7cfae0c02655b7293c
  commons-jcs3-dist-3.2.1-bin.zip
7e70953e349ec90f764c009669b4c67c6cf520d28d71d2c649a31b0d6fec9fc3cb5933185b93a59d66e5bed7a4417586aba4624601b64903ca372dec0481db99
  commons-jcs3-dist-3.2.1-src.tar.gz
4674f3f0493d79977da6c12b8402336bb8539c5471cbeaa9b8563e02e6f8a0a3beacf6a8738c13ed3af75f20cf762ee9a176e0f63d0c1f7f116efc2346e77fd4
  commons-jcs3-dist-3.2.1-src.zip

I have tested this with ***'mvn clean install site site:stage'*** using:
--
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Java version: 17.0.8, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk-17.jdk/Contents/Home
Default locale: de_DE, platform encoding: UTF-8
OS name: "mac os x", version: "11.7.10", arch: "x86_64", family: "mac"
--

NOTE: Some JCS tests require a working multicast setup. They are disabled by 
default.
If you are sure that your network configuration supports multicast (most VPNs 
do not,
for example), you may enable the additional tests with "-P testWithMulticast".

Details of changes since 3.2 are in the release notes:
   
https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc3/RELEASE-NOTES.txt
   
https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc3/site/changes-report.html

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

JApiCmp Report (compared to 3.2):
   
https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc3/site/commons-jcs3-core/japicmp.html

RAT Report:
   
https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc3/site/commons-jcs3-core/rat-report.html

KEYS:
 https://www.apache.org/dist/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,

tv,
Release Manager (using key 88817402)


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

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc3

[Thomas Vandahl]

My vote

> Am 27.05.2024 um 20:24 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.
> 
> Apache Commons JCS 3.2.1 rc3 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc3 (svn revision 
> 69406)

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

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

[RESULT][VOTE] Release Apache Commons JCS 3.2.1 based on rc3

[Thomas Vandahl]

This vote thread passes with the following binding +1 votes:

- Gary Gregory (ggregory)
- Rob Tompkins (chtompki)
- Thomas Vandahl (tv)

I will proceed with the release process. Thanks to the voters.

Bye, Thomas 

> Am 27.05.2024 um 20:24 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.
> 
> Apache Commons JCS 3.2.1 rc3 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc3 (svn revision 
> 69406)
> 
> The Git tag commons-jcs3-3.2.1-rc3 commit for this RC is 
> 2d54b71517cb2baf7d38107978b96a780a1c162c which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=2d54b71517cb2baf7d38107978b96a780a1c162c
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch 
> commons-jcs3-3.2.1-rc3 commons-jcs3-3.2.1-rc3
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1735/org/apache/commons/commons-jcs3/3.2.1/
> 
> These are the artifacts and their hashes:
> 
> ef5d5144eade500659f3789ddcfc780ce61a65ea60b388f5b2c2d6605712707ccf324d4b7cb974a08c23ee46db11d9fcf26f1730b58bdf3ac44a99dfaab70577
>   commons-jcs3-dist-3.2.1-bin.tar.gz
> 658d4639652e8b326015ca0673c7517226c7bf6a9d364de5d06852059ce6042b05c096bb5de3646236a0ad5e6dc0fdaa9268d678e3748a7cfae0c02655b7293c
>   commons-jcs3-dist-3.2.1-bin.zip
> 7e70953e349ec90f764c009669b4c67c6cf520d28d71d2c649a31b0d6fec9fc3cb5933185b93a59d66e5bed7a4417586aba4624601b64903ca372dec0481db99
>   commons-jcs3-dist-3.2.1-src.tar.gz
> 4674f3f0493d79977da6c12b8402336bb8539c5471cbeaa9b8563e02e6f8a0a3beacf6a8738c13ed3af75f20cf762ee9a176e0f63d0c1f7f116efc2346e77fd4
>   commons-jcs3-dist-3.2.1-src.zip
> 
> I have tested this with ***'mvn clean install site site:stage'*** using:
> --
> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Java version: 17.0.8, vendor: Oracle Corporation, runtime: 
> /Library/Java/JavaVirtualMachines/jdk-17.jdk/Contents/Home
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "11.7.10", arch: "x86_64", family: "mac"
> --
> 
> NOTE: Some JCS tests require a working multicast setup. They are disabled by 
> default.
> If you are sure that your network configuration supports multicast (most VPNs 
> do not,
> for example), you may enable the additional tests with "-P testWithMulticast".
> 
> Details of changes since 3.2 are in the release notes:
>   
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc3/RELEASE-NOTES.txt
>   
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc3/site/changes-report.html
> 
> Site:
>   https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc3/site/index.html
>   (note some *relative* links are broken and the 3.2.1 directories are not 
> yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 3.2):
>   
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc3/site/commons-jcs3-core/japicmp.html
> 
> RAT Report:
>   
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc3/site/commons-jcs3-core/rat-report.html
> 
> KEYS:
> https://www.apache.org/dist/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,
> 
> tv,
> Release Manager (using key 88817402)
> 
> 
> -
> 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

[ANNOUNCE] Apache Commons JCS 3.2.1

[Thomas Vandahl]

The Apache Commons JCS team is pleased to announce the release of
Apache Commons JCS 3.2.1.

Apache Commons JCS is a distributed caching system written in Java. 
It is intended to speed up applications by providing means to 
manage cached data of various dynamic natures.

This is a maintenance and bug fix release (Java 8 or above).

For complete information on Apache Commons JCS, including instructions
on how to submit bug reports, patches, or suggestions for improvement,
see the Apache Commons JCS website:

https://commons.apache.org/proper/commons-jcs/

Download page: https://commons.apache.org/proper/commons-jcs/download_jcs.cgi

Historical list of changes:
https://commons.apache.org/proper/commons-jcs/changes-report.html

Enjoy!
Thomas Vandahl 
-Apache Commons JCS team


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

Re: [VOTE] Release Apache Commons Configuration 2.11.0 based on RC1

[Thomas Vandahl]

Hi Gary,

> Am 07.06.2024 um 15:53 schrieb Gary Gregory :
> 
> We have fixed a few bugs and added enhancements since Apache Commons
> Configuration 2.10.1 was released, so I would like to release Apache
> Commons Configuration 2.11.0.
> 
> Apache Commons Configuration 2.11.0 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/configuration/2.11.0-RC1
> (svn revision 69603)
...
>  [X] +1 Release these artifacts
>  [ ] +0 OK, but...
>  [ ] -0 OK, but really should fix...
>  [ ] -1 I oppose this release because...
> 

Checksums and signatures are ok. Build, tests and site generation run fine with
   mvn clean verify site
using
--8<--
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Java version: 17.0.8, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk-17.jdk/Contents/Home
Default locale: de_DE, platform encoding: UTF-8
OS name: "mac os x", version: "11.7.10", arch: "x86_64", family: "mac"
--8<--

Bye, Thomas 


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

Re: [VOTE][JCS] release [jcs] 2.0-beta-1 (take 3)

[Thomas Vandahl]

On 25.01.15 17:00, Romain Manni-Bucau wrote:
> It does AFAIK - was not here and just propagated existing legal text - and
> that is why it is referenced in core and not all artifacts.
>  Le 25 janv. 2015 16:55, "sebb"  a écrit :

The XEROX license relates to the file
/commons-jcs-core/src/aspect/org/apache/commons/Trace.aj

If the file continues to be part of the distribution, the license file
must be present, at least that is my understanding of the Apache
requirements.

This was discussed at length when JCS 1.3 was released.

Bye, Thomas.



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

Re: [VOTE][JCS] release [jcs] 2.0-beta-1 (take 3)

[Thomas Vandahl]

On 26.01.15 12:19, Romain Manni-Bucau wrote:
> if that's the case +1 but anyway it doesnt hurt
> 
> @Thomas: before dropping it can you confirm it a last time please?

I don't even know if it actually works with the current code. It was
like this when I got here (TM). I'd suggest to remove the aspect
directory altogether and we will be clean.

Bye, Thomas.

PS: Sorry, I cannot catch up with this mailbox right now.

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

Re: [VOTE][JCS] release [jcs] 2.0-beta-1 (take 3)

[Thomas Vandahl]

On 28.01.15 20:39, Benedikt Ritter wrote:
> Hello Romain,
> 
> I've looked at the RC.
> 
> - Signs and hashes are good
> - builds find with maven 3.2.5 and Java 6 and 7, although the build of the
> core takes forever... The build fails with Java 8 (I've run mvn clean
> verify). It looks like it's trying to create the JavaDocs but that fails
> because of doclint. Building with Java 8 should work IMHO.

The build should take somewhere between 2 and 4 minutes including all
tests. What environment do you have?

Bye, Thomas.



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

Re: [VOTE][JCS] release [jcs] 2.0-beta-1 (take 4)

[Thomas Vandahl]

On 19.02.15 14:28, Romain Manni-Bucau wrote:
> Hi
> 
> Another try, hopefully right this time (I speak about JCS in a JUG
> next thursday so would be awesome to have a release ;))
> 
> - here is the maven repo:
> https://repository.apache.org/content/repositories/orgapachecommons-1083/
> - assemblies can be found here
> https://repository.apache.org/content/repositories/orgapachecommons-1083/org/apache/commons/commons-jcs-dist/2.0-beta-1/
> - tag is here: 
> http://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.0-beta-1/
> - Site staging is:
> http://people.apache.org/~rmannibucau/commons-jcs-2.0-beta-1-site/
> - rat report is here (I deleted zipcodes.txt and CDI SPI
> (META-INF/services/...) from reports since it seems rat config with
> append parameter is not well respected but that's really what we
> want):
> http://people.apache.org/~rmannibucau/commons-jcs-2.0-beta-1-site/rat-report.html
> 
> Please review the release candidate and vote.
> This vote will close no sooner that 72 hours from now or until we get
> 3 PMC votes.
> 

Here is my vote:
> [X] +1 Release these artifacts
> [ ] +-0 OK, but...
> [ ] -1 I oppose this release because...

Everything builds fine on Mac OS/Java 7. All tests pass. Signatures are
fine. You may want to get your key signed by some others in the web of
trust some time.

Until 2.0 final, we should add/update some docs. The site looks a bit
outdated.

I agree with Oliver on the ReleaseNotes issue for 2.0 final. But this is
beta.

Romain, thanks for spending the effort.

Bye, Thomas.


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

Re: Fwd: Commons JCS - disk cache bugs

[Thomas Vandahl]

On 28.03.15 19:40, Wiktor Niesiobedzki wrote:
> Hi,
> 
> I'm trying to integrate Commons JCS into Java OpenStreetMap editor
> (http://josm.openstreetmap.de). During tests I see, that from time to
> time IndexedDiskCache is thrown away. I've made a simple unit test
> that detects this situation:
> https://issues.apache.org/jira/browse/JCS-146
> 
> Also, I took some time to find the bug, and I attached small patch
> that fixes this issue.
> 
> I tried also to use BlockDiskCache, that doesn't need optimization at
> all, but there is some locking problem:
> https://issues.apache.org/jira/browse/JCS-144
> 
> For which I've also attached the patch.
> 
> I see that JCS project doesn't enjoy much activity, but is there any
> chance, that someone could review and commit JCS-144 and JCS-146?
> 
> I'd really enjoy, if I could have a fix in mainstream repository
> instead of keeping local patches within JOSM tree.

I already had a look at the patches. I'll try to include them soon.

Bye, Thomas.



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

Re: [VOTE] Release Commons Collections 4.1 Based on RC2 (24h vote)

[Thomas Vandahl]

On 25.11.15 23:20, Thomas Neidhart wrote:
>   [X] +1 Release these artifacts

Bye, Thomas.


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

Re: [VOTE] Form a separate TLP based on [math]

[Thomas Vandahl]

On 16.01.16 16:18, Phil Steitz wrote:
> [ ] +1 I am in favor of this action
> [X] +0 I am OK with this
> [ ] -0 OK, but...
> [ ] -1 I oppose this action because...

Bye, Thomas



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

Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)

[Thomas Vandahl]

On 06.11.17 04:48, Gary Gregory wrote:
> The document http://commons.apache.org/releases/prepare.html clearly shows
> an example of an RC tag being labeled with the "RC1" postfix.

Not in the maven-release-plugin chapter. And with reason. The problem of
the later copy would be, that the tagged pom.xml contains the pathes to
the tag created originally (read: with the RC suffix) so that if you
checkout the copied tag (read: the release version), the settings in
pom.xml will still point to the RC tag.

Therefore, with a Maven build you should always create the release
version, tag it, vote on it and let it be. If the vote fails, the tag
can as well be removed. What's the point of keeping it around? The vote
failed, after all. The tag is invalid anyway.

BTW, using the SVN revisions given in the vote mail (this is why they
are important), you can always access the failed RC tag, ok?

Bye, Thomas


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

Re: Maven release plugin?

[Thomas Vandahl]

On 06.11.17 09:01, Romain Manni-Bucau wrote:
> 2017-11-06 8:59 GMT+01:00 Jochen Wiedmann :
>> On Mon, Nov 6, 2017 at 7:27 AM, Romain Manni-Bucau
>>  wrote:
>>
>>> due to the RCx procedure we cant use the maven release plugin, any
>>> plan to make it working with commons release procedure or do we just
>>> wait to move all to git?
>>
>> What problem is there when using the plugin?
> 
> the plugin doesn't support the RCx branch creation without corrupting
> the final release - due to nexus. It would be fancy to be able to
> *automatically* create the right tag if flagged as such in the pom.

There is nothing wrong with the plugin. If you read the commons release
docs, the chapter about the maven-release-plugin says nothing about RCs,
let alone tags. Moving to git would not help as long as the POM
scm-section still points to the original tag. (And I'm not suggesting to
change that!)

Bye, Thomas.


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

Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)

[Thomas Vandahl]

On 06.11.17 21:11, Romain Manni-Bucau wrote:
> created 
> http://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1-RC2/
> (rev 1814438)

Thanks, Romain. However, the POM file in this RC tag contains now

--8<--

  

scm:svn:http://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1
  
  

scm:svn:https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1
  
  
http://svn.apache.org/viewvc/commons/proper/jcs/tags/commons-jcs-2.2.1
  

--8<--

See my point? If you created the RC tag first and then copied, the
scm-entries would still point to the RC tag. In this case, it's the
other way round. It is difficult for me to see why this is believed to
make sense. I'd prefer to match tag name and file content.

Bye, Thomas

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

Re: prevent registering JCSAdminBean multiple times

[Thomas Vandahl]

On 16.11.17 21:54, Tim Cronin wrote:
> we have a few webapps running on the same server that use JCS.
> 
> when moving the 2.x we started getting the following error on tomcat startup
> 
> 
> 
> javax.management.InstanceAlreadyExistsException:

It looks like you load multiple instances of CompositeCacheManager from
different class loaders. Setting the jmxName to different values is not
possible at the moment. This should be configurable. Would you please
open an issue on this.

Bye, Thomas.


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