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

2023-10-01 Thread sebb 
I've already updated site.xml.

I think all the needs to be done is to prepare the RC.

On Sun, 1 Oct 2023 at 14:50, Gary Gregory  wrote:
>
> Rob,
>
> To keep it simple, you can do whatever work you want when you can in
> git master. Then when you are done, I can cut a 64 RC1. Or I can
> cancel.
>
> Gary
>
> On Sun, Oct 1, 2023 at 9:38 AM Rob Tompkins  wrote:
> >
> > If gary cancel’s the vote I can do that work. Will try to sort it out this 
> > week.
> >
> > -Rob
> >
> > > On Oct 1, 2023, at 9:20 AM, sebb  wrote:
> > >
> > > Ideally we want to release a version with the updated site.xml...
> > >
> > > On Sat, 30 Sept 2023 at 18:44, Gary Gregory  
> > > wrote:
> > >>
> > >> We have added some enhancements since Apache Commons Parent 62 was
> > >> released, so I would like to release Apache Commons Parent 63.
> > >>
> > >> Apache Commons Parent 63 RC1 is available for review here:
> > >>https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1
> > >> (svn revision 64275)
> > >>
> > >> The Git tag commons-parent-63-RC1 commit for this RC is
> > >> 0fd27a2962b49dce17e6825d3d0a3f9d506164cd which you can browse here:
> > >>
> > >> https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=0fd27a2962b49dce17e6825d3d0a3f9d506164cd
> > >> You may checkout this tag using:
> > >>git clone https://gitbox.apache.org/repos/asf/commons-parent.git
> > >> --branch commons-parent-63-RC1 commons-parent-63-RC1
> > >>
> > >> Maven artifacts are here:
> > >>
> > >> https://repository.apache.org/content/repositories/orgapachecommons-1660/org/apache/commons/commons-parent/63/
> > >>
> > >> These are the artifacts and their hashes:
> > >>
> > >> #Release SHA-512s
> > >> #Sat Sep 30 13:31:17 EDT 2023
> > >> commons-parent-63-src.tar.gz=849823362a097cae5c3d6dd3be6a0369145da6a7a9a9ffaaac67bc0f4dd68c547a0b060055e5056e138d92aa029d84a0730c709797ac4392902fa5933059febb
> > >> org.apache.commons_commons-parent-63.spdx.json=7dd6414048549199d30dae095c65d1c42f783e622561451544453f8dae08a61121549edc4049019c475b2192e36b5377e81f89df9d9d6fc70bb43130c6c377d9
> > >> commons-parent-63-site.xml=c6aea4f2c03920366bee23b08b046dacc09710e92c78ccd83f47cd92f89bc53abc3b8bbc7f44017ee94a2cb022ce763fe3f7d8c9aa42d571350269ba6568ca07
> > >> commons-parent-63-src.zip=c074bfa5526f5d0eaa8f631fa8e04798d97dcb07336d3f094f70b87d4917181f540c47145f77acfe6e78d32317312b90358984226f7a21b4255846180acb9011
> > >> commons-parent-63-bom.json=d08fbea2168dcd027d6c2928c3604f22b081d4d88fd480f1f2b282c3ac32a15f312e47e72ad0d0f525680e931d311fe51472e9b6450e2bde5ee1a3f4632aaad2
> > >> commons-parent-63-bom.xml=36d3cb1aed436d44fbb97ef16e1e603196598dea68cc113ebfe630c7044a214132c6e7444f32f4e90ba8bf5d47f357d3426afa37b4ea6a8e735ddd666e8d0744
> > >>
> > >> I have tested this with
> > >>
> > >> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site 
> > >> deploy
> > >>
> > >> using:
> > >>
> > >> Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> > >> Maven home: /usr/local/Cellar/maven/3.9.4/libexec
> > >> Java version: 17.0.8.1, vendor: Homebrew, runtime:
> > >> /usr/local/Cellar/openjdk@17/17.0.8.1/libexec/openjdk.jdk/Contents/Home
> > >> Default locale: en_US, platform encoding: UTF-8
> > >> OS name: "mac os x", version: "14.0", arch: "x86_64", family: "mac"
> > >> Darwin gdg-mac-mini.local 23.0.0 Darwin Kernel Version 23.0.0: Fri Sep
> > >> 15 14:42:42 PDT 2023; root:xnu-10002.1.13~1/RELEASE_X86_64 x86_64
> > >>
> > >> Details of changes since 62 are in the release notes:
> > >>
> > >> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/RELEASE-NOTES.txt
> > >>
> > >> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/site/changes-report.html
> > >>
> > >> Site:
> > >>
> > >> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/site/index.html
> > >>(note some *relative* links are broken and the 63 directories are
> > >> not yet created - these will be OK once the site is deployed.)
> > >>
> > >> RAT Report:
> > >>
> > >> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/site/rat-report.html
> > >>
> > >> KEYS:
> > >>  https://downloads.apache.org/commons/KEYS
> > >>
> > >> Please review the release candidate and vote.
> > >> This vote will close no sooner than 72 hours from now.
> > >>
> > >>  [ ] +1 Release these artifacts
> > >>  [ ] +0 OK, but...
> > >>  [ ] -0 OK, but really should fix...
> > >>  [ ] -1 I oppose this release because...
> > >>
> > >> Thank you,
> > >>
> > >> garydgregory,
> > >> Release Manager (using key DEADBEEF)
> > >>
> > >> 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.
> > >>
> > >> 1a) Clone and checkout the RC tag
> > >>
> > >>

Re: [site] [all] broken links

2023-10-01 Thread sebb 
https://lists.apache.org/list.html?notificati...@commons.apache.org

On Sun, 1 Oct 2023 at 22:33, Phil Steitz  wrote:
>
> Thanks, Seb.  Where, btw, do the commit diffs for the site go?
>
> Phil
>
> On Sun, Oct 1, 2023 at 6:09 AM sebb  wrote:
> >
> > On Sun, 1 Oct 2023 at 13:32, Phil Steitz  wrote:
> > >
> > > Thanks, Sebb.  Strange that some of the links work but not others.
> >
> > The relative links were added to site.xml (in commons parent) earlier this 
> > year.
> > AFAICT only the sites built since then have the problem, because only
> > they have the extra links.
> >
> > Found a few more I had overlooked.
> >
> > Also did pool, because I realised that a rebuild of the site won't
> > solve the problem until commons parent is re-released.
> >
> > > Phil
> > >
> > > > On Oct 1, 2023, at 4:10 AM, sebb  wrote:
> > > >
> > > > I've already updated all the sites apart from pool.
> > > >
> > > >> On Sun, 1 Oct 2023 at 11:53, Rob Tompkins  wrote:
> > > >>
> > > >> Will look at this and write jira for it.
> > > >> -Rob
> > > >>
> > >  On Oct 1, 2023, at 4:52 AM, sebb  wrote:
> > > >>>
> > > >>> As to the other sites, there should be no need to regenerate them: 
> > > >>> one
> > > >>> can just update the production sites in SVN.
> > > >>> I should be able to do that a bit later.
> > > >>>
> > >  On Sun, 1 Oct 2023 at 09:41, sebb  wrote:
> > > 
> > >  Looks like the site-relative links in
> > >  https://github.com/apache/commons-parent/blob/master/src/site/site.xml
> > >  are not working.
> > > 
> > >  Try changing the links to absolute ones.
> > > 
> > > > On Sun, 1 Oct 2023 at 01:40, Phil Steitz  
> > > > wrote:
> > > >
> > > > I am not sure what is causing this, but somehow the links generated 
> > > > for
> > > > component sites with the current parent and plugins are messed up 
> > > > in the
> > > > General Information section (which appears on some sites and not 
> > > > others).
> > > > In verifying the updated [pool] site, I see that for some reason 
> > > > the links
> > > > for "site publication" and the "commons release plugin" are broken. 
> > > >  I
> > > > notice that io, dbcp and lang all have the same problem.  At first, 
> > > > I
> > > > thought it was due to the use of relative links in the main site nav
> > > > entries, but others in the same block work correctly.  Any ideas on 
> > > > how to
> > > > fix this?
> > > >
> > > > Phil
> > > >>>
> > > >>> -
> > > >>> 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
> > > >>
> > > >
> > > > -
> > > > 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
> > >
> >
> > -
> > 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
>

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

Re: [site] [all] broken links

2023-10-01 Thread Phil Steitz 
Thanks, Seb.  Where, btw, do the commit diffs for the site go?

Phil

On Sun, Oct 1, 2023 at 6:09 AM sebb  wrote:
>
> On Sun, 1 Oct 2023 at 13:32, Phil Steitz  wrote:
> >
> > Thanks, Sebb.  Strange that some of the links work but not others.
>
> The relative links were added to site.xml (in commons parent) earlier this 
> year.
> AFAICT only the sites built since then have the problem, because only
> they have the extra links.
>
> Found a few more I had overlooked.
>
> Also did pool, because I realised that a rebuild of the site won't
> solve the problem until commons parent is re-released.
>
> > Phil
> >
> > > On Oct 1, 2023, at 4:10 AM, sebb  wrote:
> > >
> > > I've already updated all the sites apart from pool.
> > >
> > >> On Sun, 1 Oct 2023 at 11:53, Rob Tompkins  wrote:
> > >>
> > >> Will look at this and write jira for it.
> > >> -Rob
> > >>
> >  On Oct 1, 2023, at 4:52 AM, sebb  wrote:
> > >>>
> > >>> As to the other sites, there should be no need to regenerate them: one
> > >>> can just update the production sites in SVN.
> > >>> I should be able to do that a bit later.
> > >>>
> >  On Sun, 1 Oct 2023 at 09:41, sebb  wrote:
> > 
> >  Looks like the site-relative links in
> >  https://github.com/apache/commons-parent/blob/master/src/site/site.xml
> >  are not working.
> > 
> >  Try changing the links to absolute ones.
> > 
> > > On Sun, 1 Oct 2023 at 01:40, Phil Steitz  
> > > wrote:
> > >
> > > I am not sure what is causing this, but somehow the links generated 
> > > for
> > > component sites with the current parent and plugins are messed up in 
> > > the
> > > General Information section (which appears on some sites and not 
> > > others).
> > > In verifying the updated [pool] site, I see that for some reason the 
> > > links
> > > for "site publication" and the "commons release plugin" are broken.  I
> > > notice that io, dbcp and lang all have the same problem.  At first, I
> > > thought it was due to the use of relative links in the main site nav
> > > entries, but others in the same block work correctly.  Any ideas on 
> > > how to
> > > fix this?
> > >
> > > Phil
> > >>>
> > >>> -
> > >>> 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
> > >>
> > >
> > > -
> > > 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
> >
>
> -
> 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 Net 3.10.0 based on RC1

2023-10-01 Thread Phil Steitz 
Looks good to me.  I tested source tarball build with

Linux #93~20.04.1-Ubuntu SMP Wed Sep 6 16:15:40 UTC 2023 x86_64
openjdk version "1.8.0_382"
OpenJDK Runtime Environment (build 1.8.0_382-8u382-ga-1~20.04.1-b05)
OpenJDK 64-Bit Server VM (build 25.382-b05, mixed mode)
and
openjdk version "17.0.8.1" 2023-08-24
OpenJDK Runtime Environment (build 17.0.8.1+1-Ubuntu-0ubuntu120.04)
OpenJDK 64-Bit Server VM (build 17.0.8.1+1-Ubuntu-0ubuntu120.04, mixed
mode, sharing)

+1

Phil

On Sun, Oct 1, 2023 at 6:48 AM Gary Gregory  wrote:

> We have fixed a few bugs and added some enhancements since Apache
> Commons Net 3.9.0 was released, so I would like to release Apache
> Commons Net 3.10.0.
>
> Apache Commons Net 3.10.0 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1 (svn
> revision 64282)
>
> The Git tag commons-net-3.10.0-RC1 commit for this RC is
> c3f36eb9078971a159a93065389983fd60ee95f6 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-net.git;a=commit;h=c3f36eb9078971a159a93065389983fd60ee95f6
> You may checkout this tag using:
> git clone https://gitbox.apache.org/repos/asf/commons-net.git
> --branch 
> commons-net-3.10.0-RC1 commons-net-3.10.0-RC1
>
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1661/commons-net/commons-net/3.10.0/
>
> These are the artifacts and their hashes:
>
> #Release SHA-512s
> #Sun Oct 01 09:35:09 EDT 2023
>
> commons-net-examples-3.10.0.jar=f39be82d6f72f551a723467ca381de363290a4ebd2f885a939ee548b4c5469353bfc4dd6e8ba5c881ded85c5d5245cb70a1940729a61c3fbae9e0bb3d822333a
>
> commons-net-3.10.0-tests.jar=75428b4d6446f98a87ec5ffd76fecc96b292a585903e57b83626c488a8ef106ad682274db9b2964aded4a5a0321abaa48342d86076d5702714c8e80698bb017d
>
> commons-net_commons-net-3.10.0.spdx.json=bc092ab2f294d55df36ca306f072ddbe956e769c99c68867ad671eec6dde5d0de3888de02daf60b4440e87275f20a7271aebfbdc528dbd9f2a6f4f1b833c545b
>
> commons-net-3.10.0-test-sources.jar=7f5e769997dbb322c476ee16df08d32c85082f7a5cb2da0dbe971414df9bc18fff9454bf273913e4f6b2ebe3c680405108c877b2f3d2f66afb746f0b30956302
>
> commons-net-3.10.0-src.zip=a29748689c64660969fab26f4c33a86114fec6c680707ac78f51c84b3b0dd5465005e24b4e8ce2112e367d7a452b77147a00bb446573613759672265ec3c1891
>
> commons-net-3.10.0-sources.jar=acb8f07ac5a1f4e3369370f8549eb0951ae340933c851daa3271e072d42c2709789d2c5f62ca138c787787a9dcec5585666ad737f80f4e7c17f0cd6eff3ce26d
>
> commons-net-3.10.0-bin.zip=42d48be13ee3945d7e1ac1dc7cb467f698fed9b87e54f9fd02e8a37d95087823dc961c385f676e7b626f12552b2950f4c965f2f5ea309917a31b3faf2c2c08e6
>
> commons-net-3.10.0-bom.xml=b42bf3ab0403d66c6fffde48fe6cafcd0b332d2b8f960bd14e0725a3ec476f968907493182bb171dafe376060fa22fd119094d8f1ceece5d8476d4316d4938cb
>
> commons-net-3.10.0-bom.json=bc2c94f269b5cee82345b3e4d23ce3f2673a6cbc8ad1e1b212aa903a7a089017f5e8f30952495b24313d8d2bcb9209048a29a00fc208d7bab3ae6b59ecf7db59
>
> commons-net-3.10.0-javadoc.jar=ade9ed8ffc50a7d01867c2c60b6abb9da2657bb022cf9e3c1f85203887451b9cde1ee975e459fbcf222366f8d84ea3e883f69c90831b8ab63cd243a80f7716ee
>
> commons-net-ftp-3.10.0.jar=251ffd3ac6d516823aa5c0cba39793db01b65c17c974f1014f8315bf7775cc60f17f0411ec14ed8fd14d62e42963487ee0500ed42cd03a19f88a2fed2dee7874
>
> commons-net-3.10.0-src.tar.gz=d9d80255feddfb434d3baa629aa9e6d8feffd530c5e3172106fec55bbc986f6423a46dc9e737a1bb7020c62447229e6b83d0b7f9582d041e1def423536cc92dd
>
> commons-net-3.10.0-bin.tar.gz=8707be9410ee8d58889c142f1bf0628445278d38e941aaef2a1be1e16757fad5c50f0ebb3e4f6603bc18955822a8fd383476d4137085e769ddec5b68326015bf
>
> I have tested this with:
>
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site
> deploy
>
> using:
>
> Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> Maven home: /usr/local/Cellar/maven/3.9.4/libexec
> Java version: 17.0.8.1, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.8.1/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.0", arch: "x86_64", family: "mac"
> Darwin  23.0.0 Darwin Kernel Version 23.0.0: Fri Sep 15 14:42:42
> PDT 2023; root:xnu-10002.1.13~1/RELEASE_X86_64 x86_64
>
> Details of changes since 3.9.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1/site/changes-report.html
>
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1/site/index.html
> (note some *relative* links are broken and the 3.10.0 directories
> are not yet created - these will be OK once the site is deployed.)
>
> JApiCmp Report (compared to 3.9.0):
>
> https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1/site/japicmp.html
>
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1/site/rat-report.html
>
> KEYS:
>

[ANNOUNCEMENT] Apache Commons Pool 2.12.0

2023-10-01 Thread Phil Steitz 
The Apache Commons team is pleased to announce the release of
Apache Commons Pool 2.12.0.

Commons Pool provides an object-pooling API and a number of object pool
implementations.

Java 8 or above is required.

Version 2.12.0 is a maintenance release, including bug fixes and
enhancements.  This release is source and binary compatible with the prior
version, 2.11.1.  All users are encouraged to upgrade.

A complete historical list of changes to Commons Pool is available here:
https://commons.apache.org/proper/commons-pool/changes-report.html

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

Source and binary distributions are available from the Commons Pool
download page:
https://commons.apache.org/proper/commons-pool/download_pool.cgi

Please verify the hashes and signatures on downloaded artifacts.

The 2.x versions of Commons Pool are distributed under the commons-pool2
maven artifactId. To pull Commons Pool 2.12.0 into an Apache Maven build as
a dependency, use


org.apache.commons
commons-pool2
2.12.0


Thanks in advance for bug reports, suggestions for improvement, patches or
other contributions to the Apache Commons community.

Phil Steitz
-Apache Commons Team

Re: [VOTE] Release Apache Commons Net 3.10.0 based on RC1

2023-10-01 Thread Bruno Kinoshita 
   [x] +1 Release these artifacts

Building OK, tests passing, site generated OK, reports look good.

Bruno

On Sun, 1 Oct 2023 at 15:48, Gary Gregory  wrote:

> We have fixed a few bugs and added some enhancements since Apache
> Commons Net 3.9.0 was released, so I would like to release Apache
> Commons Net 3.10.0.
>
> Apache Commons Net 3.10.0 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1 (svn
> revision 64282)
>
> The Git tag commons-net-3.10.0-RC1 commit for this RC is
> c3f36eb9078971a159a93065389983fd60ee95f6 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-net.git;a=commit;h=c3f36eb9078971a159a93065389983fd60ee95f6
> You may checkout this tag using:
> git clone https://gitbox.apache.org/repos/asf/commons-net.git
> --branch 
> commons-net-3.10.0-RC1 commons-net-3.10.0-RC1
>
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1661/commons-net/commons-net/3.10.0/
>
> These are the artifacts and their hashes:
>
> #Release SHA-512s
> #Sun Oct 01 09:35:09 EDT 2023
>
> commons-net-examples-3.10.0.jar=f39be82d6f72f551a723467ca381de363290a4ebd2f885a939ee548b4c5469353bfc4dd6e8ba5c881ded85c5d5245cb70a1940729a61c3fbae9e0bb3d822333a
>
> commons-net-3.10.0-tests.jar=75428b4d6446f98a87ec5ffd76fecc96b292a585903e57b83626c488a8ef106ad682274db9b2964aded4a5a0321abaa48342d86076d5702714c8e80698bb017d
>
> commons-net_commons-net-3.10.0.spdx.json=bc092ab2f294d55df36ca306f072ddbe956e769c99c68867ad671eec6dde5d0de3888de02daf60b4440e87275f20a7271aebfbdc528dbd9f2a6f4f1b833c545b
>
> commons-net-3.10.0-test-sources.jar=7f5e769997dbb322c476ee16df08d32c85082f7a5cb2da0dbe971414df9bc18fff9454bf273913e4f6b2ebe3c680405108c877b2f3d2f66afb746f0b30956302
>
> commons-net-3.10.0-src.zip=a29748689c64660969fab26f4c33a86114fec6c680707ac78f51c84b3b0dd5465005e24b4e8ce2112e367d7a452b77147a00bb446573613759672265ec3c1891
>
> commons-net-3.10.0-sources.jar=acb8f07ac5a1f4e3369370f8549eb0951ae340933c851daa3271e072d42c2709789d2c5f62ca138c787787a9dcec5585666ad737f80f4e7c17f0cd6eff3ce26d
>
> commons-net-3.10.0-bin.zip=42d48be13ee3945d7e1ac1dc7cb467f698fed9b87e54f9fd02e8a37d95087823dc961c385f676e7b626f12552b2950f4c965f2f5ea309917a31b3faf2c2c08e6
>
> commons-net-3.10.0-bom.xml=b42bf3ab0403d66c6fffde48fe6cafcd0b332d2b8f960bd14e0725a3ec476f968907493182bb171dafe376060fa22fd119094d8f1ceece5d8476d4316d4938cb
>
> commons-net-3.10.0-bom.json=bc2c94f269b5cee82345b3e4d23ce3f2673a6cbc8ad1e1b212aa903a7a089017f5e8f30952495b24313d8d2bcb9209048a29a00fc208d7bab3ae6b59ecf7db59
>
> commons-net-3.10.0-javadoc.jar=ade9ed8ffc50a7d01867c2c60b6abb9da2657bb022cf9e3c1f85203887451b9cde1ee975e459fbcf222366f8d84ea3e883f69c90831b8ab63cd243a80f7716ee
>
> commons-net-ftp-3.10.0.jar=251ffd3ac6d516823aa5c0cba39793db01b65c17c974f1014f8315bf7775cc60f17f0411ec14ed8fd14d62e42963487ee0500ed42cd03a19f88a2fed2dee7874
>
> commons-net-3.10.0-src.tar.gz=d9d80255feddfb434d3baa629aa9e6d8feffd530c5e3172106fec55bbc986f6423a46dc9e737a1bb7020c62447229e6b83d0b7f9582d041e1def423536cc92dd
>
> commons-net-3.10.0-bin.tar.gz=8707be9410ee8d58889c142f1bf0628445278d38e941aaef2a1be1e16757fad5c50f0ebb3e4f6603bc18955822a8fd383476d4137085e769ddec5b68326015bf
>
> I have tested this with:
>
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site
> deploy
>
> using:
>
> Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> Maven home: /usr/local/Cellar/maven/3.9.4/libexec
> Java version: 17.0.8.1, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.8.1/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.0", arch: "x86_64", family: "mac"
> Darwin  23.0.0 Darwin Kernel Version 23.0.0: Fri Sep 15 14:42:42
> PDT 2023; root:xnu-10002.1.13~1/RELEASE_X86_64 x86_64
>
> Details of changes since 3.9.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1/site/changes-report.html
>
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1/site/index.html
> (note some *relative* links are broken and the 3.10.0 directories
> are not yet created - these will be OK once the site is deployed.)
>
> JApiCmp Report (compared to 3.9.0):
>
> https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1/site/japicmp.html
>
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1/site/rat-report.html
>
> KEYS:
>   https://downloads.apache.org/commons/KEYS
>
> Please review the release candidate and vote.
> This vote will close no sooner than 72 hours from now.
>
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
>
> Thank you,
>
> Gary Gregory,
> Release Manager (using key

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

2023-10-01 Thread Gary Gregory 
Rob,

To keep it simple, you can do whatever work you want when you can in
git master. Then when you are done, I can cut a 64 RC1. Or I can
cancel.

Gary

On Sun, Oct 1, 2023 at 9:38 AM Rob Tompkins  wrote:
>
> If gary cancel’s the vote I can do that work. Will try to sort it out this 
> week.
>
> -Rob
>
> > On Oct 1, 2023, at 9:20 AM, sebb  wrote:
> >
> > Ideally we want to release a version with the updated site.xml...
> >
> > On Sat, 30 Sept 2023 at 18:44, Gary Gregory  wrote:
> >>
> >> We have added some enhancements since Apache Commons Parent 62 was
> >> released, so I would like to release Apache Commons Parent 63.
> >>
> >> Apache Commons Parent 63 RC1 is available for review here:
> >>https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1
> >> (svn revision 64275)
> >>
> >> The Git tag commons-parent-63-RC1 commit for this RC is
> >> 0fd27a2962b49dce17e6825d3d0a3f9d506164cd which you can browse here:
> >>
> >> https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=0fd27a2962b49dce17e6825d3d0a3f9d506164cd
> >> You may checkout this tag using:
> >>git clone https://gitbox.apache.org/repos/asf/commons-parent.git
> >> --branch commons-parent-63-RC1 commons-parent-63-RC1
> >>
> >> Maven artifacts are here:
> >>
> >> https://repository.apache.org/content/repositories/orgapachecommons-1660/org/apache/commons/commons-parent/63/
> >>
> >> These are the artifacts and their hashes:
> >>
> >> #Release SHA-512s
> >> #Sat Sep 30 13:31:17 EDT 2023
> >> commons-parent-63-src.tar.gz=849823362a097cae5c3d6dd3be6a0369145da6a7a9a9ffaaac67bc0f4dd68c547a0b060055e5056e138d92aa029d84a0730c709797ac4392902fa5933059febb
> >> org.apache.commons_commons-parent-63.spdx.json=7dd6414048549199d30dae095c65d1c42f783e622561451544453f8dae08a61121549edc4049019c475b2192e36b5377e81f89df9d9d6fc70bb43130c6c377d9
> >> commons-parent-63-site.xml=c6aea4f2c03920366bee23b08b046dacc09710e92c78ccd83f47cd92f89bc53abc3b8bbc7f44017ee94a2cb022ce763fe3f7d8c9aa42d571350269ba6568ca07
> >> commons-parent-63-src.zip=c074bfa5526f5d0eaa8f631fa8e04798d97dcb07336d3f094f70b87d4917181f540c47145f77acfe6e78d32317312b90358984226f7a21b4255846180acb9011
> >> commons-parent-63-bom.json=d08fbea2168dcd027d6c2928c3604f22b081d4d88fd480f1f2b282c3ac32a15f312e47e72ad0d0f525680e931d311fe51472e9b6450e2bde5ee1a3f4632aaad2
> >> commons-parent-63-bom.xml=36d3cb1aed436d44fbb97ef16e1e603196598dea68cc113ebfe630c7044a214132c6e7444f32f4e90ba8bf5d47f357d3426afa37b4ea6a8e735ddd666e8d0744
> >>
> >> I have tested this with
> >>
> >> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site 
> >> deploy
> >>
> >> using:
> >>
> >> Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> >> Maven home: /usr/local/Cellar/maven/3.9.4/libexec
> >> Java version: 17.0.8.1, vendor: Homebrew, runtime:
> >> /usr/local/Cellar/openjdk@17/17.0.8.1/libexec/openjdk.jdk/Contents/Home
> >> Default locale: en_US, platform encoding: UTF-8
> >> OS name: "mac os x", version: "14.0", arch: "x86_64", family: "mac"
> >> Darwin gdg-mac-mini.local 23.0.0 Darwin Kernel Version 23.0.0: Fri Sep
> >> 15 14:42:42 PDT 2023; root:xnu-10002.1.13~1/RELEASE_X86_64 x86_64
> >>
> >> Details of changes since 62 are in the release notes:
> >>
> >> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/RELEASE-NOTES.txt
> >>
> >> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/site/changes-report.html
> >>
> >> Site:
> >>
> >> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/site/index.html
> >>(note some *relative* links are broken and the 63 directories are
> >> not yet created - these will be OK once the site is deployed.)
> >>
> >> RAT Report:
> >>
> >> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/site/rat-report.html
> >>
> >> KEYS:
> >>  https://downloads.apache.org/commons/KEYS
> >>
> >> Please review the release candidate and vote.
> >> This vote will close no sooner than 72 hours from now.
> >>
> >>  [ ] +1 Release these artifacts
> >>  [ ] +0 OK, but...
> >>  [ ] -0 OK, but really should fix...
> >>  [ ] -1 I oppose this release because...
> >>
> >> Thank you,
> >>
> >> garydgregory,
> >> Release Manager (using key DEADBEEF)
> >>
> >> 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.
> >>
> >> 1a) Clone and checkout the RC tag
> >>
> >> git clone https://gitbox.apache.org/repos/asf/commons-parent.git
> >> --branch commons-parent-63-RC1 commons-parent-63-RC1
> >> cd commons-parent-63-RC1
> >>
> >> 1b) Download and unpack the source archive from:
> >>
> >> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/source
> >>
> >> 2) Check Apache licenses
> >>
> >> This step is not required

[VOTE] Release Apache Commons Net 3.10.0 based on RC1

2023-10-01 Thread Gary Gregory 
We have fixed a few bugs and added some enhancements since Apache
Commons Net 3.9.0 was released, so I would like to release Apache
Commons Net 3.10.0.

Apache Commons Net 3.10.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1 (svn
revision 64282)

The Git tag commons-net-3.10.0-RC1 commit for this RC is
c3f36eb9078971a159a93065389983fd60ee95f6 which you can browse here:

https://gitbox.apache.org/repos/asf?p=commons-net.git;a=commit;h=c3f36eb9078971a159a93065389983fd60ee95f6
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-net.git
--branch commons-net-3.10.0-RC1 commons-net-3.10.0-RC1

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1661/commons-net/commons-net/3.10.0/

These are the artifacts and their hashes:

#Release SHA-512s
#Sun Oct 01 09:35:09 EDT 2023
commons-net-examples-3.10.0.jar=f39be82d6f72f551a723467ca381de363290a4ebd2f885a939ee548b4c5469353bfc4dd6e8ba5c881ded85c5d5245cb70a1940729a61c3fbae9e0bb3d822333a
commons-net-3.10.0-tests.jar=75428b4d6446f98a87ec5ffd76fecc96b292a585903e57b83626c488a8ef106ad682274db9b2964aded4a5a0321abaa48342d86076d5702714c8e80698bb017d
commons-net_commons-net-3.10.0.spdx.json=bc092ab2f294d55df36ca306f072ddbe956e769c99c68867ad671eec6dde5d0de3888de02daf60b4440e87275f20a7271aebfbdc528dbd9f2a6f4f1b833c545b
commons-net-3.10.0-test-sources.jar=7f5e769997dbb322c476ee16df08d32c85082f7a5cb2da0dbe971414df9bc18fff9454bf273913e4f6b2ebe3c680405108c877b2f3d2f66afb746f0b30956302
commons-net-3.10.0-src.zip=a29748689c64660969fab26f4c33a86114fec6c680707ac78f51c84b3b0dd5465005e24b4e8ce2112e367d7a452b77147a00bb446573613759672265ec3c1891
commons-net-3.10.0-sources.jar=acb8f07ac5a1f4e3369370f8549eb0951ae340933c851daa3271e072d42c2709789d2c5f62ca138c787787a9dcec5585666ad737f80f4e7c17f0cd6eff3ce26d
commons-net-3.10.0-bin.zip=42d48be13ee3945d7e1ac1dc7cb467f698fed9b87e54f9fd02e8a37d95087823dc961c385f676e7b626f12552b2950f4c965f2f5ea309917a31b3faf2c2c08e6
commons-net-3.10.0-bom.xml=b42bf3ab0403d66c6fffde48fe6cafcd0b332d2b8f960bd14e0725a3ec476f968907493182bb171dafe376060fa22fd119094d8f1ceece5d8476d4316d4938cb
commons-net-3.10.0-bom.json=bc2c94f269b5cee82345b3e4d23ce3f2673a6cbc8ad1e1b212aa903a7a089017f5e8f30952495b24313d8d2bcb9209048a29a00fc208d7bab3ae6b59ecf7db59
commons-net-3.10.0-javadoc.jar=ade9ed8ffc50a7d01867c2c60b6abb9da2657bb022cf9e3c1f85203887451b9cde1ee975e459fbcf222366f8d84ea3e883f69c90831b8ab63cd243a80f7716ee
commons-net-ftp-3.10.0.jar=251ffd3ac6d516823aa5c0cba39793db01b65c17c974f1014f8315bf7775cc60f17f0411ec14ed8fd14d62e42963487ee0500ed42cd03a19f88a2fed2dee7874
commons-net-3.10.0-src.tar.gz=d9d80255feddfb434d3baa629aa9e6d8feffd530c5e3172106fec55bbc986f6423a46dc9e737a1bb7020c62447229e6b83d0b7f9582d041e1def423536cc92dd
commons-net-3.10.0-bin.tar.gz=8707be9410ee8d58889c142f1bf0628445278d38e941aaef2a1be1e16757fad5c50f0ebb3e4f6603bc18955822a8fd383476d4137085e769ddec5b68326015bf

I have tested this with:

mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy

using:

Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
Maven home: /usr/local/Cellar/maven/3.9.4/libexec
Java version: 17.0.8.1, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@17/17.0.8.1/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "14.0", arch: "x86_64", family: "mac"
Darwin  23.0.0 Darwin Kernel Version 23.0.0: Fri Sep 15 14:42:42
PDT 2023; root:xnu-10002.1.13~1/RELEASE_X86_64 x86_64

Details of changes since 3.9.0 are in the release notes:

https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1/RELEASE-NOTES.txt

https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1/site/changes-report.html

Site:

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

JApiCmp Report (compared to 3.9.0):

https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1/site/japicmp.html

RAT Report:

https://dist.apache.org/repos/dist/dev/commons/net/3.10.0-RC1/site/rat-report.html

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

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

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

Thank you,

Gary Gregory,
Release Manager (using key 86fdc7e2a11262cb)

For following is intended as a helper and refresher for 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.

1a) Clone and checkout the RC tag

git clone https://gitbox.apache.org/repos/asf/commons-net.git

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

2023-10-01 Thread Rob Tompkins 
If gary cancel’s the vote I can do that work. Will try to sort it out this week.

-Rob

> On Oct 1, 2023, at 9:20 AM, sebb  wrote:
> 
> Ideally we want to release a version with the updated site.xml...
> 
> On Sat, 30 Sept 2023 at 18:44, Gary Gregory  wrote:
>> 
>> We have added some enhancements since Apache Commons Parent 62 was
>> released, so I would like to release Apache Commons Parent 63.
>> 
>> Apache Commons Parent 63 RC1 is available for review here:
>>https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1
>> (svn revision 64275)
>> 
>> The Git tag commons-parent-63-RC1 commit for this RC is
>> 0fd27a2962b49dce17e6825d3d0a3f9d506164cd which you can browse here:
>>
>> https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=0fd27a2962b49dce17e6825d3d0a3f9d506164cd
>> You may checkout this tag using:
>>git clone https://gitbox.apache.org/repos/asf/commons-parent.git
>> --branch commons-parent-63-RC1 commons-parent-63-RC1
>> 
>> Maven artifacts are here:
>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1660/org/apache/commons/commons-parent/63/
>> 
>> These are the artifacts and their hashes:
>> 
>> #Release SHA-512s
>> #Sat Sep 30 13:31:17 EDT 2023
>> commons-parent-63-src.tar.gz=849823362a097cae5c3d6dd3be6a0369145da6a7a9a9ffaaac67bc0f4dd68c547a0b060055e5056e138d92aa029d84a0730c709797ac4392902fa5933059febb
>> org.apache.commons_commons-parent-63.spdx.json=7dd6414048549199d30dae095c65d1c42f783e622561451544453f8dae08a61121549edc4049019c475b2192e36b5377e81f89df9d9d6fc70bb43130c6c377d9
>> commons-parent-63-site.xml=c6aea4f2c03920366bee23b08b046dacc09710e92c78ccd83f47cd92f89bc53abc3b8bbc7f44017ee94a2cb022ce763fe3f7d8c9aa42d571350269ba6568ca07
>> commons-parent-63-src.zip=c074bfa5526f5d0eaa8f631fa8e04798d97dcb07336d3f094f70b87d4917181f540c47145f77acfe6e78d32317312b90358984226f7a21b4255846180acb9011
>> commons-parent-63-bom.json=d08fbea2168dcd027d6c2928c3604f22b081d4d88fd480f1f2b282c3ac32a15f312e47e72ad0d0f525680e931d311fe51472e9b6450e2bde5ee1a3f4632aaad2
>> commons-parent-63-bom.xml=36d3cb1aed436d44fbb97ef16e1e603196598dea68cc113ebfe630c7044a214132c6e7444f32f4e90ba8bf5d47f357d3426afa37b4ea6a8e735ddd666e8d0744
>> 
>> I have tested this with
>> 
>> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
>> 
>> using:
>> 
>> Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
>> Maven home: /usr/local/Cellar/maven/3.9.4/libexec
>> Java version: 17.0.8.1, vendor: Homebrew, runtime:
>> /usr/local/Cellar/openjdk@17/17.0.8.1/libexec/openjdk.jdk/Contents/Home
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "mac os x", version: "14.0", arch: "x86_64", family: "mac"
>> Darwin gdg-mac-mini.local 23.0.0 Darwin Kernel Version 23.0.0: Fri Sep
>> 15 14:42:42 PDT 2023; root:xnu-10002.1.13~1/RELEASE_X86_64 x86_64
>> 
>> Details of changes since 62 are in the release notes:
>>
>> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/RELEASE-NOTES.txt
>>
>> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/site/changes-report.html
>> 
>> Site:
>>
>> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/site/index.html
>>(note some *relative* links are broken and the 63 directories are
>> not yet created - these will be OK once the site is deployed.)
>> 
>> RAT Report:
>>
>> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/site/rat-report.html
>> 
>> KEYS:
>>  https://downloads.apache.org/commons/KEYS
>> 
>> Please review the release candidate and vote.
>> This vote will close no sooner than 72 hours from now.
>> 
>>  [ ] +1 Release these artifacts
>>  [ ] +0 OK, but...
>>  [ ] -0 OK, but really should fix...
>>  [ ] -1 I oppose this release because...
>> 
>> Thank you,
>> 
>> garydgregory,
>> Release Manager (using key DEADBEEF)
>> 
>> 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.
>> 
>> 1a) Clone and checkout the RC tag
>> 
>> git clone https://gitbox.apache.org/repos/asf/commons-parent.git
>> --branch commons-parent-63-RC1 commons-parent-63-RC1
>> cd commons-parent-63-RC1
>> 
>> 1b) Download and unpack the source archive from:
>> 
>> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/source
>> 
>> 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
>> 
>> Older components still use Apache Clirr:
>> 
>> This step is not required if the site includes a Clirr report page
>> which you then must check.
>> 
>> mvn clirr:check
>> 
>> Newer components use JApiCmp with the japicmp Maven Profile:
>> 
>> This step is not

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

2023-10-01 Thread Gary Gregory 
I'm not sure what that means. But sure, go for it.

Gary

On Sun, Oct 1, 2023 at 9:20 AM sebb  wrote:
>
> Ideally we want to release a version with the updated site.xml...
>
> On Sat, 30 Sept 2023 at 18:44, Gary Gregory  wrote:
> >
> > We have added some enhancements since Apache Commons Parent 62 was
> > released, so I would like to release Apache Commons Parent 63.
> >
> > Apache Commons Parent 63 RC1 is available for review here:
> > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1
> > (svn revision 64275)
> >
> > The Git tag commons-parent-63-RC1 commit for this RC is
> > 0fd27a2962b49dce17e6825d3d0a3f9d506164cd which you can browse here:
> > 
> > https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=0fd27a2962b49dce17e6825d3d0a3f9d506164cd
> > You may checkout this tag using:
> > git clone https://gitbox.apache.org/repos/asf/commons-parent.git
> > --branch commons-parent-63-RC1 commons-parent-63-RC1
> >
> > Maven artifacts are here:
> > 
> > https://repository.apache.org/content/repositories/orgapachecommons-1660/org/apache/commons/commons-parent/63/
> >
> > These are the artifacts and their hashes:
> >
> > #Release SHA-512s
> > #Sat Sep 30 13:31:17 EDT 2023
> > commons-parent-63-src.tar.gz=849823362a097cae5c3d6dd3be6a0369145da6a7a9a9ffaaac67bc0f4dd68c547a0b060055e5056e138d92aa029d84a0730c709797ac4392902fa5933059febb
> > org.apache.commons_commons-parent-63.spdx.json=7dd6414048549199d30dae095c65d1c42f783e622561451544453f8dae08a61121549edc4049019c475b2192e36b5377e81f89df9d9d6fc70bb43130c6c377d9
> > commons-parent-63-site.xml=c6aea4f2c03920366bee23b08b046dacc09710e92c78ccd83f47cd92f89bc53abc3b8bbc7f44017ee94a2cb022ce763fe3f7d8c9aa42d571350269ba6568ca07
> > commons-parent-63-src.zip=c074bfa5526f5d0eaa8f631fa8e04798d97dcb07336d3f094f70b87d4917181f540c47145f77acfe6e78d32317312b90358984226f7a21b4255846180acb9011
> > commons-parent-63-bom.json=d08fbea2168dcd027d6c2928c3604f22b081d4d88fd480f1f2b282c3ac32a15f312e47e72ad0d0f525680e931d311fe51472e9b6450e2bde5ee1a3f4632aaad2
> > commons-parent-63-bom.xml=36d3cb1aed436d44fbb97ef16e1e603196598dea68cc113ebfe630c7044a214132c6e7444f32f4e90ba8bf5d47f357d3426afa37b4ea6a8e735ddd666e8d0744
> >
> > I have tested this with
> >
> > mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site 
> > deploy
> >
> > using:
> >
> > Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> > Maven home: /usr/local/Cellar/maven/3.9.4/libexec
> > Java version: 17.0.8.1, vendor: Homebrew, runtime:
> > /usr/local/Cellar/openjdk@17/17.0.8.1/libexec/openjdk.jdk/Contents/Home
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "mac os x", version: "14.0", arch: "x86_64", family: "mac"
> > Darwin gdg-mac-mini.local 23.0.0 Darwin Kernel Version 23.0.0: Fri Sep
> > 15 14:42:42 PDT 2023; root:xnu-10002.1.13~1/RELEASE_X86_64 x86_64
> >
> > Details of changes since 62 are in the release notes:
> > 
> > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/RELEASE-NOTES.txt
> > 
> > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/site/changes-report.html
> >
> > Site:
> > 
> > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/site/index.html
> > (note some *relative* links are broken and the 63 directories are
> > not yet created - these will be OK once the site is deployed.)
> >
> > RAT Report:
> > 
> > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/site/rat-report.html
> >
> > KEYS:
> >   https://downloads.apache.org/commons/KEYS
> >
> > Please review the release candidate and vote.
> > This vote will close no sooner than 72 hours from now.
> >
> >   [ ] +1 Release these artifacts
> >   [ ] +0 OK, but...
> >   [ ] -0 OK, but really should fix...
> >   [ ] -1 I oppose this release because...
> >
> > Thank you,
> >
> > garydgregory,
> > Release Manager (using key DEADBEEF)
> >
> > 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.
> >
> > 1a) Clone and checkout the RC tag
> >
> > git clone https://gitbox.apache.org/repos/asf/commons-parent.git
> > --branch commons-parent-63-RC1 commons-parent-63-RC1
> > cd commons-parent-63-RC1
> >
> > 1b) Download and unpack the source archive from:
> >
> > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/source
> >
> > 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
> >
> > Older components still use Apache Clirr:
> >
> > This step is not required if the site includes a Clirr report page
> > which you then must check.
> >
> > mvn clirr:check
> >
> > Newer components use

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

2023-10-01 Thread sebb 
Ideally we want to release a version with the updated site.xml...

On Sat, 30 Sept 2023 at 18:44, Gary Gregory  wrote:
>
> We have added some enhancements since Apache Commons Parent 62 was
> released, so I would like to release Apache Commons Parent 63.
>
> Apache Commons Parent 63 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1
> (svn revision 64275)
>
> The Git tag commons-parent-63-RC1 commit for this RC is
> 0fd27a2962b49dce17e6825d3d0a3f9d506164cd which you can browse here:
> 
> https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=0fd27a2962b49dce17e6825d3d0a3f9d506164cd
> You may checkout this tag using:
> git clone https://gitbox.apache.org/repos/asf/commons-parent.git
> --branch commons-parent-63-RC1 commons-parent-63-RC1
>
> Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1660/org/apache/commons/commons-parent/63/
>
> These are the artifacts and their hashes:
>
> #Release SHA-512s
> #Sat Sep 30 13:31:17 EDT 2023
> commons-parent-63-src.tar.gz=849823362a097cae5c3d6dd3be6a0369145da6a7a9a9ffaaac67bc0f4dd68c547a0b060055e5056e138d92aa029d84a0730c709797ac4392902fa5933059febb
> org.apache.commons_commons-parent-63.spdx.json=7dd6414048549199d30dae095c65d1c42f783e622561451544453f8dae08a61121549edc4049019c475b2192e36b5377e81f89df9d9d6fc70bb43130c6c377d9
> commons-parent-63-site.xml=c6aea4f2c03920366bee23b08b046dacc09710e92c78ccd83f47cd92f89bc53abc3b8bbc7f44017ee94a2cb022ce763fe3f7d8c9aa42d571350269ba6568ca07
> commons-parent-63-src.zip=c074bfa5526f5d0eaa8f631fa8e04798d97dcb07336d3f094f70b87d4917181f540c47145f77acfe6e78d32317312b90358984226f7a21b4255846180acb9011
> commons-parent-63-bom.json=d08fbea2168dcd027d6c2928c3604f22b081d4d88fd480f1f2b282c3ac32a15f312e47e72ad0d0f525680e931d311fe51472e9b6450e2bde5ee1a3f4632aaad2
> commons-parent-63-bom.xml=36d3cb1aed436d44fbb97ef16e1e603196598dea68cc113ebfe630c7044a214132c6e7444f32f4e90ba8bf5d47f357d3426afa37b4ea6a8e735ddd666e8d0744
>
> I have tested this with
>
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
>
> using:
>
> Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> Maven home: /usr/local/Cellar/maven/3.9.4/libexec
> Java version: 17.0.8.1, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.8.1/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.0", arch: "x86_64", family: "mac"
> Darwin gdg-mac-mini.local 23.0.0 Darwin Kernel Version 23.0.0: Fri Sep
> 15 14:42:42 PDT 2023; root:xnu-10002.1.13~1/RELEASE_X86_64 x86_64
>
> Details of changes since 62 are in the release notes:
> 
> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/RELEASE-NOTES.txt
> 
> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/site/changes-report.html
>
> Site:
> 
> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/site/index.html
> (note some *relative* links are broken and the 63 directories are
> not yet created - these will be OK once the site is deployed.)
>
> RAT Report:
> 
> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/site/rat-report.html
>
> KEYS:
>   https://downloads.apache.org/commons/KEYS
>
> Please review the release candidate and vote.
> This vote will close no sooner than 72 hours from now.
>
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
>
> Thank you,
>
> garydgregory,
> Release Manager (using key DEADBEEF)
>
> 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.
>
> 1a) Clone and checkout the RC tag
>
> git clone https://gitbox.apache.org/repos/asf/commons-parent.git
> --branch commons-parent-63-RC1 commons-parent-63-RC1
> cd commons-parent-63-RC1
>
> 1b) Download and unpack the source archive from:
>
> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/source
>
> 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
>
> Older components still use Apache Clirr:
>
> This step is not required if the site includes a Clirr report page
> which you then must check.
>
> mvn clirr:check
>
> 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

Re: [site] [all] broken links

2023-10-01 Thread sebb 
On Sun, 1 Oct 2023 at 13:32, Phil Steitz  wrote:
>
> Thanks, Sebb.  Strange that some of the links work but not others.

The relative links were added to site.xml (in commons parent) earlier this year.
AFAICT only the sites built since then have the problem, because only
they have the extra links.

Found a few more I had overlooked.

Also did pool, because I realised that a rebuild of the site won't
solve the problem until commons parent is re-released.

> Phil
>
> > On Oct 1, 2023, at 4:10 AM, sebb  wrote:
> >
> > I've already updated all the sites apart from pool.
> >
> >> On Sun, 1 Oct 2023 at 11:53, Rob Tompkins  wrote:
> >>
> >> Will look at this and write jira for it.
> >> -Rob
> >>
>  On Oct 1, 2023, at 4:52 AM, sebb  wrote:
> >>>
> >>> As to the other sites, there should be no need to regenerate them: one
> >>> can just update the production sites in SVN.
> >>> I should be able to do that a bit later.
> >>>
>  On Sun, 1 Oct 2023 at 09:41, sebb  wrote:
> 
>  Looks like the site-relative links in
>  https://github.com/apache/commons-parent/blob/master/src/site/site.xml
>  are not working.
> 
>  Try changing the links to absolute ones.
> 
> > On Sun, 1 Oct 2023 at 01:40, Phil Steitz  wrote:
> >
> > I am not sure what is causing this, but somehow the links generated for
> > component sites with the current parent and plugins are messed up in the
> > General Information section (which appears on some sites and not 
> > others).
> > In verifying the updated [pool] site, I see that for some reason the 
> > links
> > for "site publication" and the "commons release plugin" are broken.  I
> > notice that io, dbcp and lang all have the same problem.  At first, I
> > thought it was due to the use of relative links in the main site nav
> > entries, but others in the same block work correctly.  Any ideas on how 
> > to
> > fix this?
> >
> > Phil
> >>>
> >>> -
> >>> 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
> >>
> >
> > -
> > 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
>

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

Re: No sign of releases for Functor or OGNL - move to dormant?

2023-10-01 Thread Bruno Kinoshita 
Are we (or infra) able to archive a repository? That would be a good
indicator for the user that the repository is not actively maintained. Then
they could find out more in the README file. Example archive repository:
https://github.com/cylc/cylc-conda

On Sun, 1 Oct 2023 at 14:04, Gary Gregory  wrote:

> Maybe just put text at the TOP of the README.md, and keep the rest
> below (for posterity and in case of unlikely resurrection).
>
> Warning: The Apache Commons Function component is now DORMANT, meaning
> this component is not open for development. Post to the user's mailing
> list at <> for questions.
>
> Gary
>
> On Sun, Oct 1, 2023 at 7:53 AM sebb  wrote:
> >
> > OK, mostly done.
> >
> > I'm just wondering how we document dormancy in the GH repos?
> >
> > Perhaps just override the generated README.md ?
> >
> > Sebb
> >
> > On Thu, 21 Sept 2023 at 02:29, Gary Gregory 
> wrote:
> > >
> > > Ah, right! Dormant it is for Functor then.
> > >
> > > Gary
> > >
> > > On Wed, Sep 20, 2023, 7:03 PM sebb  wrote:
> > >
> > > > FTR: Attic is only for PMCs, not individual projects/components
> > > >
> > > > On Wed, 20 Sept 2023 at 17:32, Gary Gregory 
> > > > wrote:
> > > > >
> > > > > Functor should be attic'd IMO.
> > > > >
> > > > > Gary
> > > > >
> > > > >
> > > > > On Wed, Sep 20, 2023, 10:29 AM Gilles Sadowski <
> gillese...@gmail.com>
> > > > wrote:
> > > > >
> > > > > > Le mer. 20 sept. 2023 à 15:36, sebb  a écrit :
> > > > > > >
> > > > > > > I cannot find any releases for Functor
> > > > > >
> > > > > > Briefly looking at the description and examples pages (not the
> code),
> > > > > > it seems that much functionality has been superseded by the
> standard
> > > > > > "java.util.function" package and lambdas.
> > > > > > What looks interesting is the mention of "design patterns";
> maybe this
> > > > > > part could be moved to somewhere else (if sufficiently useful)...
> > > > > >
> > > > > > > or OGNL,
> > > > > >
> > > > > > No site update since 2013 (according to the date on the web
> page).
> > > > > > Code never moved to "git" (according to the "source repository"
> page).
> > > > > > Just inferring potential usage from the description, it seems
> that
> > > > > > "Groovy" would be a more appropriate (and supported) tool (?).
> > > > > >
> > > > > > Regards,
> > > > > > Gilles
> > > > > >
> > > > > > > yet they are listed on
> > > > > > > the commons home page, and the releases page.
> > > > > > >
> > > > > > > Seems to me they should be moved to dormant?
> > > > > > >
> > > > > > > Sebb
> > > > > >
> > > > > >
> -
> > > > > > 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
> > > >
> > > >
> >
> > -
> > 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: [site] [all] broken links

2023-10-01 Thread Phil Steitz 
Thanks, Sebb.  Strange that some of the links work but not others.

Phil

> On Oct 1, 2023, at 4:10 AM, sebb  wrote:
> 
> I've already updated all the sites apart from pool.
> 
>> On Sun, 1 Oct 2023 at 11:53, Rob Tompkins  wrote:
>> 
>> Will look at this and write jira for it.
>> -Rob
>> 
 On Oct 1, 2023, at 4:52 AM, sebb  wrote:
>>> 
>>> As to the other sites, there should be no need to regenerate them: one
>>> can just update the production sites in SVN.
>>> I should be able to do that a bit later.
>>> 
 On Sun, 1 Oct 2023 at 09:41, sebb  wrote:
 
 Looks like the site-relative links in
 https://github.com/apache/commons-parent/blob/master/src/site/site.xml
 are not working.
 
 Try changing the links to absolute ones.
 
> On Sun, 1 Oct 2023 at 01:40, Phil Steitz  wrote:
> 
> I am not sure what is causing this, but somehow the links generated for
> component sites with the current parent and plugins are messed up in the
> General Information section (which appears on some sites and not others).
> In verifying the updated [pool] site, I see that for some reason the links
> for "site publication" and the "commons release plugin" are broken.  I
> notice that io, dbcp and lang all have the same problem.  At first, I
> thought it was due to the use of relative links in the main site nav
> entries, but others in the same block work correctly.  Any ideas on how to
> fix this?
> 
> Phil
>>> 
>>> -
>>> 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
>> 
> 
> -
> 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: [all] stopping dependabot and security analyses on dormant components

2023-10-01 Thread sebb 
That has already been done for functor (some time ago), but the checks
are still shown as enabled:

https://github.com/apache/commons-functor/security

On Sun, 1 Oct 2023 at 13:12, Gary Gregory  wrote:
>
> Edit the files in the .github folder (or remove them).
>
> Gary
>
> On Sun, Oct 1, 2023 at 8:09 AM sebb  wrote:
> >
> > As the subject says: how does one stop dependabot and other analyses
> > from running on dormant components?
> >
> > Sebb
> >
> > -
> > 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
>

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

Re: [all] stopping dependabot and security analyses on dormant components

2023-10-01 Thread Gary Gregory 
Edit the files in the .github folder (or remove them).

Gary

On Sun, Oct 1, 2023 at 8:09 AM sebb  wrote:
>
> As the subject says: how does one stop dependabot and other analyses
> from running on dormant components?
>
> Sebb
>
> -
> 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

[all] stopping dependabot and security analyses on dormant components

2023-10-01 Thread sebb 
As the subject says: how does one stop dependabot and other analyses
from running on dormant components?

Sebb

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

Re: No sign of releases for Functor or OGNL - move to dormant?

2023-10-01 Thread Gary Gregory 
Maybe just put text at the TOP of the README.md, and keep the rest
below (for posterity and in case of unlikely resurrection).

Warning: The Apache Commons Function component is now DORMANT, meaning
this component is not open for development. Post to the user's mailing
list at <> for questions.

Gary

On Sun, Oct 1, 2023 at 7:53 AM sebb  wrote:
>
> OK, mostly done.
>
> I'm just wondering how we document dormancy in the GH repos?
>
> Perhaps just override the generated README.md ?
>
> Sebb
>
> On Thu, 21 Sept 2023 at 02:29, Gary Gregory  wrote:
> >
> > Ah, right! Dormant it is for Functor then.
> >
> > Gary
> >
> > On Wed, Sep 20, 2023, 7:03 PM sebb  wrote:
> >
> > > FTR: Attic is only for PMCs, not individual projects/components
> > >
> > > On Wed, 20 Sept 2023 at 17:32, Gary Gregory 
> > > wrote:
> > > >
> > > > Functor should be attic'd IMO.
> > > >
> > > > Gary
> > > >
> > > >
> > > > On Wed, Sep 20, 2023, 10:29 AM Gilles Sadowski 
> > > wrote:
> > > >
> > > > > Le mer. 20 sept. 2023 à 15:36, sebb  a écrit :
> > > > > >
> > > > > > I cannot find any releases for Functor
> > > > >
> > > > > Briefly looking at the description and examples pages (not the code),
> > > > > it seems that much functionality has been superseded by the standard
> > > > > "java.util.function" package and lambdas.
> > > > > What looks interesting is the mention of "design patterns"; maybe this
> > > > > part could be moved to somewhere else (if sufficiently useful)...
> > > > >
> > > > > > or OGNL,
> > > > >
> > > > > No site update since 2013 (according to the date on the web page).
> > > > > Code never moved to "git" (according to the "source repository" page).
> > > > > Just inferring potential usage from the description, it seems that
> > > > > "Groovy" would be a more appropriate (and supported) tool (?).
> > > > >
> > > > > Regards,
> > > > > Gilles
> > > > >
> > > > > > yet they are listed on
> > > > > > the commons home page, and the releases page.
> > > > > >
> > > > > > Seems to me they should be moved to dormant?
> > > > > >
> > > > > > Sebb
> > > > >
> > > > > -
> > > > > 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
> > >
> > >
>
> -
> 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: No sign of releases for Functor or OGNL - move to dormant?

2023-10-01 Thread sebb 
OK, mostly done.

I'm just wondering how we document dormancy in the GH repos?

Perhaps just override the generated README.md ?

Sebb

On Thu, 21 Sept 2023 at 02:29, Gary Gregory  wrote:
>
> Ah, right! Dormant it is for Functor then.
>
> Gary
>
> On Wed, Sep 20, 2023, 7:03 PM sebb  wrote:
>
> > FTR: Attic is only for PMCs, not individual projects/components
> >
> > On Wed, 20 Sept 2023 at 17:32, Gary Gregory 
> > wrote:
> > >
> > > Functor should be attic'd IMO.
> > >
> > > Gary
> > >
> > >
> > > On Wed, Sep 20, 2023, 10:29 AM Gilles Sadowski 
> > wrote:
> > >
> > > > Le mer. 20 sept. 2023 à 15:36, sebb  a écrit :
> > > > >
> > > > > I cannot find any releases for Functor
> > > >
> > > > Briefly looking at the description and examples pages (not the code),
> > > > it seems that much functionality has been superseded by the standard
> > > > "java.util.function" package and lambdas.
> > > > What looks interesting is the mention of "design patterns"; maybe this
> > > > part could be moved to somewhere else (if sufficiently useful)...
> > > >
> > > > > or OGNL,
> > > >
> > > > No site update since 2013 (according to the date on the web page).
> > > > Code never moved to "git" (according to the "source repository" page).
> > > > Just inferring potential usage from the description, it seems that
> > > > "Groovy" would be a more appropriate (and supported) tool (?).
> > > >
> > > > Regards,
> > > > Gilles
> > > >
> > > > > yet they are listed on
> > > > > the commons home page, and the releases page.
> > > > >
> > > > > Seems to me they should be moved to dormant?
> > > > >
> > > > > Sebb
> > > >
> > > > -
> > > > 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
> >
> >

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

Re: [site] [all] broken links

2023-10-01 Thread sebb 
I've already updated all the sites apart from pool.

On Sun, 1 Oct 2023 at 11:53, Rob Tompkins  wrote:
>
> Will look at this and write jira for it.
> -Rob
>
> > On Oct 1, 2023, at 4:52 AM, sebb  wrote:
> >
> > As to the other sites, there should be no need to regenerate them: one
> > can just update the production sites in SVN.
> > I should be able to do that a bit later.
> >
> >> On Sun, 1 Oct 2023 at 09:41, sebb  wrote:
> >>
> >> Looks like the site-relative links in
> >> https://github.com/apache/commons-parent/blob/master/src/site/site.xml
> >> are not working.
> >>
> >> Try changing the links to absolute ones.
> >>
> >>> On Sun, 1 Oct 2023 at 01:40, Phil Steitz  wrote:
> >>>
> >>> I am not sure what is causing this, but somehow the links generated for
> >>> component sites with the current parent and plugins are messed up in the
> >>> General Information section (which appears on some sites and not others).
> >>> In verifying the updated [pool] site, I see that for some reason the links
> >>> for "site publication" and the "commons release plugin" are broken.  I
> >>> notice that io, dbcp and lang all have the same problem.  At first, I
> >>> thought it was due to the use of relative links in the main site nav
> >>> entries, but others in the same block work correctly.  Any ideas on how to
> >>> fix this?
> >>>
> >>> Phil
> >
> > -
> > 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
>

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

Re: [site] [all] broken links

2023-10-01 Thread Rob Tompkins 
Will look at this and write jira for it.
-Rob

> On Oct 1, 2023, at 4:52 AM, sebb  wrote:
> 
> As to the other sites, there should be no need to regenerate them: one
> can just update the production sites in SVN.
> I should be able to do that a bit later.
> 
>> On Sun, 1 Oct 2023 at 09:41, sebb  wrote:
>> 
>> Looks like the site-relative links in
>> https://github.com/apache/commons-parent/blob/master/src/site/site.xml
>> are not working.
>> 
>> Try changing the links to absolute ones.
>> 
>>> On Sun, 1 Oct 2023 at 01:40, Phil Steitz  wrote:
>>> 
>>> I am not sure what is causing this, but somehow the links generated for
>>> component sites with the current parent and plugins are messed up in the
>>> General Information section (which appears on some sites and not others).
>>> In verifying the updated [pool] site, I see that for some reason the links
>>> for "site publication" and the "commons release plugin" are broken.  I
>>> notice that io, dbcp and lang all have the same problem.  At first, I
>>> thought it was due to the use of relative links in the main site nav
>>> entries, but others in the same block work correctly.  Any ideas on how to
>>> fix this?
>>> 
>>> Phil
> 
> -
> 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: [site] [all] broken links

2023-10-01 Thread sebb 
As to the other sites, there should be no need to regenerate them: one
can just update the production sites in SVN.
I should be able to do that a bit later.

On Sun, 1 Oct 2023 at 09:41, sebb  wrote:
>
> Looks like the site-relative links in
> https://github.com/apache/commons-parent/blob/master/src/site/site.xml
> are not working.
>
> Try changing the links to absolute ones.
>
> On Sun, 1 Oct 2023 at 01:40, Phil Steitz  wrote:
> >
> > I am not sure what is causing this, but somehow the links generated for
> > component sites with the current parent and plugins are messed up in the
> > General Information section (which appears on some sites and not others).
> > In verifying the updated [pool] site, I see that for some reason the links
> > for "site publication" and the "commons release plugin" are broken.  I
> > notice that io, dbcp and lang all have the same problem.  At first, I
> > thought it was due to the use of relative links in the main site nav
> > entries, but others in the same block work correctly.  Any ideas on how to
> > fix this?
> >
> > Phil

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

Re: [site] [all] broken links

2023-10-01 Thread sebb 
Looks like the site-relative links in
https://github.com/apache/commons-parent/blob/master/src/site/site.xml
are not working.

Try changing the links to absolute ones.

On Sun, 1 Oct 2023 at 01:40, Phil Steitz  wrote:
>
> I am not sure what is causing this, but somehow the links generated for
> component sites with the current parent and plugins are messed up in the
> General Information section (which appears on some sites and not others).
> In verifying the updated [pool] site, I see that for some reason the links
> for "site publication" and the "commons release plugin" are broken.  I
> notice that io, dbcp and lang all have the same problem.  At first, I
> thought it was due to the use of relative links in the main site nav
> entries, but others in the same block work correctly.  Any ideas on how to
> fix this?
>
> Phil

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