Re: [ALL] pom.xml should not contain RM details
+1 but why then are those properties there? Phil > On Oct 2, 2023, at 3:58 PM, sebb wrote: > > As the subject says, please do not use the pom to store RM details such as > > commons.releaseManagerName > commons.releaseManagerKey > > These properties are personal to the user, and should be defined in > ~/.m2/settings.xml. > See https://commons.apache.org/proper/commons-release-plugin/index.html > > Or you can define them on the command line. > > If the RM details are stored in the pom, then it is all too easy for > the wrong values to be used. > > Thanks, > 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] pom.xml should not contain RM details
As the subject says, please do not use the pom to store RM details such as commons.releaseManagerName commons.releaseManagerKey These properties are personal to the user, and should be defined in ~/.m2/settings.xml. See https://commons.apache.org/proper/commons-release-plugin/index.html Or you can define them on the command line. If the RM details are stored in the pom, then it is all too easy for the wrong values to be used. Thanks, 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?
I think Dormant is fine for now. 2c, Gary On Mon, Oct 2, 2023, 5:26 PM sebb wrote: > Archiving is possible, but needs Infra intervention. > Likewise unarchiving. > > So if we did archive the code, it would be a bit more work to re-activate > it. > > I have added (Dormant) to the component name in .asf.yaml - this shows > up on the GH page and in the gitbox listings [1] > > If it turns out archiving is necessary, we can always do that later. > > Sebb > [1] https://gitbox.apache.org/repos/asf#commons > > On Sun, 1 Oct 2023 at 13:48, Bruno Kinoshita > wrote: > > > > 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 < > garydgreg...@gmail.com> > > > > > > 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 > > > > > > > > - > 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?
Archiving is possible, but needs Infra intervention. Likewise unarchiving. So if we did archive the code, it would be a bit more work to re-activate it. I have added (Dormant) to the component name in .asf.yaml - this shows up on the GH page and in the gitbox listings [1] If it turns out archiving is necessary, we can always do that later. Sebb [1] https://gitbox.apache.org/repos/asf#commons On Sun, 1 Oct 2023 at 13:48, Bruno Kinoshita wrote: > > 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 > > > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [BUILD-PLUGIN] Disable moditect profile to build
On Mon, 2 Oct 2023 at 15:30, sebb wrote: > > The moditect profile (which is activated for Java 9+) causes the build to > fail. > This prevents testing of snapshot builds, because it appears the > install stage is skipped even when using -fn > > Until the cause of the moditect failure is fixed, it is advisable to > use the CLI option: > -P!moditect > > e.g. mvn clean install -P!moditect > > I've updated the GH action, but I don't think it's possible to disable > the profile from within the build-plugin pom. However it is possible to skip execution of the plugin by setting the property moditect.skip = true > Sebb - 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 63 based on RC2
I get the following warnings on the parent pom with Java 11+: $ mvn clean install [WARNING] Unknown keyword additionalItems - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword [INFO]attaching as commons-parent-63-SNAPSHOT-cyclonedx.json [INFO] [INFO] --- spdx-maven-plugin:0.7.0:createSPDX (build-sbom-spdx) @ commons-parent --- [INFO] spdx file type = .json [INFO] Creating SPDX File /private/var/sebb/git/commons/parent/target/site/org.apache.commons_commons-parent-63-SNAPSHOT.spdx.json [WARNING] Unable to map maven licenses to a declared license. Using NOASSERTION [WARNING] Null package file On Mon, 2 Oct 2023 at 14:20, Gary Gregory wrote: > > I plan on eventually having all configs for checkstyle, spotbugs and so on > under the same dir in each component such that each component is not forced > to declare checkstyle, spotbugs and so on. > > Gary > > > On Mon, Oct 2, 2023, 9:05 AM Alex Herbert wrote: > > > Can you provide the usage for the new property? > > This is listed in the release notes as a new feature thanks to > > dependabot. But the commit was a single line added by Gary. I do not > > think it is attributed to dependabot. It is added under the release > > management section for properties for the Commons Release plugin but I > > cannot find 'commons.conf.dir' referenced in the current release > > plugin code. > > > > Alex > > > > On Mon, 2 Oct 2023 at 13:28, Gary Gregory wrote: > > > > > > We have fixed a few bugs and added some enhancements since Apache > > > Commons Parent 62 was released, so I would like to release Apache > > > Commons Parent 63. > > > > > > Apache Commons Parent 63 RC2 is available for review here: > > > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2 > > > (svn revision 64292) > > > > > > The Git tag commons-parent-63-RC2 commit for this RC is > > > cf512e1352e886a50c1f292420dbc052bdedbf39 which you can browse here: > > > > > https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=cf512e1352e886a50c1f292420dbc052bdedbf39 > > > You may checkout this tag using: > > > git clone https://gitbox.apache.org/repos/asf/commons-parent.git > > > --branch commons-parent-63-RC2 commons-parent-63-RC2 > > > > > > Maven artifacts are here: > > > > > https://repository.apache.org/content/repositories/orgapachecommons-1662/org/apache/commons/commons-parent/63/ > > > > > > These are the artifacts and their hashes: > > > > > > #Release SHA-512s > > > #Mon Oct 02 07:53:04 EDT 2023 > > > > > commons-parent-63-src.tar.gz=415919a83c9a84101c586e36da25aeacad9126119e5f3bee1de8db8e4dbda46c5b0a28a0c440ea64254533f31d31be5e2904838e1dd72d456e7befde7a6b2f77 > > > > > org.apache.commons_commons-parent-63.spdx.json=51ef87a005d61ad1aa1318770ad79f4decbe717d7a570266c3ad24223fe5f7e7fcaf0ef162a5e6dc232ba6f79799f484ce68345a8bf164bf52f6992bf6d5cc7c > > > > > commons-parent-63-site.xml=5f045989b2c281c567467548678fe8685efabf5c13104299eea87b6ab6b6a75c9e98b590d7b288b8ec3a06934061709d0851a6dd9d9b45100ee2950908ec2d6c > > > > > commons-parent-63-src.zip=3674e727c8a770117d40d21812d581774446d9144a9625d3b45535231ccc9ad7e923397d1e9df16133888fbcc8745c573639f89523ba3dd360d459d08069eea1 > > > > > 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 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-RC2/RELEASE-NOTES.txt > > > > > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2/site/changes-report.html > > > > > > Site: > > > > > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2/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-RC2/site/rat-report.html > > > > > > KEYS: > > > https://downloads.apache.org/commons/KEYS > > > > > > Please
[BUILD-PLUGIN] Disable moditect profile to build
The moditect profile (which is activated for Java 9+) causes the build to fail. This prevents testing of snapshot builds, because it appears the install stage is skipped even when using -fn Until the cause of the moditect failure is fixed, it is advisable to use the CLI option: -P!moditect e.g. mvn clean install -P!moditect I've updated the GH action, but I don't think it's possible to disable the profile from within the build-plugin pom. Sebb - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [BUILD-PLUGIN] Drop component list from README template?
On Mon, 2 Oct 2023 at 14:38, Gary Gregory wrote: > > I agree that we should only advertise active components. I wonder if we > could get the karma to create a GitHub "project" to group all Commons > repositories or if infra has to do that for us. That would alleviate the > need for the table in readme.md pages. This new GH project would still need to be maintained. But at least it would be a single point of failure. Feel free to investigate what would be required, and then we can decide if that is the way to go. It would be better if the same data could somehow be used for both the site generation and other uses such as this. > Gary > > On Mon, Oct 2, 2023, 9:10 AM sebb wrote: > > > On Mon, 2 Oct 2023 at 13:30, Gary Gregory wrote: > > > > > > On Mon, Oct 2, 2023 at 8:04 AM sebb wrote: > > > > > > > > On Mon, 2 Oct 2023 at 11:34, Gary Gregory > > wrote: > > > > > > > > > > My intent was to advertise the breadth of Commons without forcing > > users > > > > > away from GitHub but instead let them jump to another github repo > > directly. > > > > > > > > The problem is that the list gets out of date and needs a lot of > > > > ongoing manual maintenance. > > > > > > I'm not sure I buy that argument. The only change that's happened that > > > I can recall is our recent decision to make [functor] and [ognl] > > > dormant. > > > > I agree that's how I found the issue. > > > > However, the list did not contain OGNL, and it contained Signing, > > which was retired ages ago. > > > > So it was already out of date (and see below). > > > > > If that's how you want to advertise Commons to the wider > > > GitHub world, then go for it ;-) > > > > Do we really want to advertise dormant/retired/sandbox/internal > > projects in this way? > > > > For example, > > https://github.com/apache/commons-lang#apache-commons-components > > currently includes Signing, which has a link to a non-existent > > website. > > > > I've also just noticed that the template links to Graph which is in the > > Sandbox. > > > > There are also links to internal components such as the Build Plugin > > and Commons Parent. > > As well as Testing - status unknown (and no website AFAICT) > > > > > Gary > > > > > > > > > > > > Gary > > > > > > > > > > On Mon, Oct 2, 2023, 5:05 AM sebb wrote: > > > > > > > > > > > The Build Plugin currently includes a list of components in the > > README > > > > > > template. > > > > > > > > > > > > This duplicates information provided elsewhere, and gets out of > > date. > > > > > > > > > > > > Since this info is in every GH repo, any changes also need to be > > > > > > applied to every one of them, to ensure they are up to date. > > > > > > > > > > > > This is an unnecessary maintenance burden. > > > > > > > > > > > > I think this local list should be dropped, and replaced with a > > link to > > > > > > the main website. > > > > > > > > > > > > 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 > > > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [ANNOUNCEMENT] Apache Commons IO 2.14.0
YW! On Sat, Sep 30, 2023, 10:34 AM Rob Tompkins wrote: > Thank you for your work! > > -Rob > > > On Sep 30, 2023, at 10:31 AM, Gary Gregory wrote: > > > > The Apache Commons team is pleased to announce the release of Apache > > Commons IO 2.14.0. > > > > Commons IO is a package of Java utility classes like java.io. Classes > > in this package are considered to be so standard and of such high > > reuse as to justify existence in java.io. > > > > The Apache Commons IO library contains utility classes, stream > > implementations, file filters, file comparators, endian transformation > > classes, and much more. > > > > Java 8 is required. > > > > Historical list of changes: > > https://commons.apache.org/proper/commons-io/changes-report.html > > > > For complete information on Apache Commons IO, including instructions > > on how to submit bug reports, patches, or suggestions for improvement, > > see the Apache Commons IO website: > > > > https://commons.apache.org/proper/commons-io/ > > > > Download page: > https://commons.apache.org/proper/commons-io/download_io.cgi > > > > Have fun! > > Gary Gregory > > - Apache Commons Team > > > > - > > To unsubscribe, e-mail: user-unsubscr...@commons.apache.org > > For additional commands, e-mail: user-h...@commons.apache.org > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
Re: [BUILD-PLUGIN] Drop component list from README template?
I agree that we should only advertise active components. I wonder if we could get the karma to create a GitHub "project" to group all Commons repositories or if infra has to do that for us. That would alleviate the need for the table in readme.md pages. Gary On Mon, Oct 2, 2023, 9:10 AM sebb wrote: > On Mon, 2 Oct 2023 at 13:30, Gary Gregory wrote: > > > > On Mon, Oct 2, 2023 at 8:04 AM sebb wrote: > > > > > > On Mon, 2 Oct 2023 at 11:34, Gary Gregory > wrote: > > > > > > > > My intent was to advertise the breadth of Commons without forcing > users > > > > away from GitHub but instead let them jump to another github repo > directly. > > > > > > The problem is that the list gets out of date and needs a lot of > > > ongoing manual maintenance. > > > > I'm not sure I buy that argument. The only change that's happened that > > I can recall is our recent decision to make [functor] and [ognl] > > dormant. > > I agree that's how I found the issue. > > However, the list did not contain OGNL, and it contained Signing, > which was retired ages ago. > > So it was already out of date (and see below). > > > If that's how you want to advertise Commons to the wider > > GitHub world, then go for it ;-) > > Do we really want to advertise dormant/retired/sandbox/internal > projects in this way? > > For example, > https://github.com/apache/commons-lang#apache-commons-components > currently includes Signing, which has a link to a non-existent > website. > > I've also just noticed that the template links to Graph which is in the > Sandbox. > > There are also links to internal components such as the Build Plugin > and Commons Parent. > As well as Testing - status unknown (and no website AFAICT) > > > Gary > > > > > > > > > Gary > > > > > > > > On Mon, Oct 2, 2023, 5:05 AM sebb wrote: > > > > > > > > > The Build Plugin currently includes a list of components in the > README > > > > > template. > > > > > > > > > > This duplicates information provided elsewhere, and gets out of > date. > > > > > > > > > > Since this info is in every GH repo, any changes also need to be > > > > > applied to every one of them, to ensure they are up to date. > > > > > > > > > > This is an unnecessary maintenance burden. > > > > > > > > > > I think this local list should be dropped, and replaced with a > link to > > > > > the main website. > > > > > > > > > > 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: [VOTE][LAZY] Release Apache Commons Parent 63 based on RC2
I plan on eventually having all configs for checkstyle, spotbugs and so on under the same dir in each component such that each component is not forced to declare checkstyle, spotbugs and so on. Gary On Mon, Oct 2, 2023, 9:05 AM Alex Herbert wrote: > Can you provide the usage for the new property? > This is listed in the release notes as a new feature thanks to > dependabot. But the commit was a single line added by Gary. I do not > think it is attributed to dependabot. It is added under the release > management section for properties for the Commons Release plugin but I > cannot find 'commons.conf.dir' referenced in the current release > plugin code. > > Alex > > On Mon, 2 Oct 2023 at 13:28, Gary Gregory wrote: > > > > We have fixed a few bugs and added some enhancements since Apache > > Commons Parent 62 was released, so I would like to release Apache > > Commons Parent 63. > > > > Apache Commons Parent 63 RC2 is available for review here: > > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2 > > (svn revision 64292) > > > > The Git tag commons-parent-63-RC2 commit for this RC is > > cf512e1352e886a50c1f292420dbc052bdedbf39 which you can browse here: > > > https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=cf512e1352e886a50c1f292420dbc052bdedbf39 > > You may checkout this tag using: > > git clone https://gitbox.apache.org/repos/asf/commons-parent.git > > --branch commons-parent-63-RC2 commons-parent-63-RC2 > > > > Maven artifacts are here: > > > https://repository.apache.org/content/repositories/orgapachecommons-1662/org/apache/commons/commons-parent/63/ > > > > These are the artifacts and their hashes: > > > > #Release SHA-512s > > #Mon Oct 02 07:53:04 EDT 2023 > > > commons-parent-63-src.tar.gz=415919a83c9a84101c586e36da25aeacad9126119e5f3bee1de8db8e4dbda46c5b0a28a0c440ea64254533f31d31be5e2904838e1dd72d456e7befde7a6b2f77 > > > org.apache.commons_commons-parent-63.spdx.json=51ef87a005d61ad1aa1318770ad79f4decbe717d7a570266c3ad24223fe5f7e7fcaf0ef162a5e6dc232ba6f79799f484ce68345a8bf164bf52f6992bf6d5cc7c > > > commons-parent-63-site.xml=5f045989b2c281c567467548678fe8685efabf5c13104299eea87b6ab6b6a75c9e98b590d7b288b8ec3a06934061709d0851a6dd9d9b45100ee2950908ec2d6c > > > commons-parent-63-src.zip=3674e727c8a770117d40d21812d581774446d9144a9625d3b45535231ccc9ad7e923397d1e9df16133888fbcc8745c573639f89523ba3dd360d459d08069eea1 > > > 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 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-RC2/RELEASE-NOTES.txt > > > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2/site/changes-report.html > > > > Site: > > > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2/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-RC2/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-RC2 commons-parent-63-RC2 > > cd commons-parent-63-RC2 > > > > 1b) Download and unpack the source archive from: > > > > >
Re: [BUILD-PLUGIN] Drop component list from README template?
On Mon, 2 Oct 2023 at 13:30, Gary Gregory wrote: > > On Mon, Oct 2, 2023 at 8:04 AM sebb wrote: > > > > On Mon, 2 Oct 2023 at 11:34, Gary Gregory wrote: > > > > > > My intent was to advertise the breadth of Commons without forcing users > > > away from GitHub but instead let them jump to another github repo > > > directly. > > > > The problem is that the list gets out of date and needs a lot of > > ongoing manual maintenance. > > I'm not sure I buy that argument. The only change that's happened that > I can recall is our recent decision to make [functor] and [ognl] > dormant. I agree that's how I found the issue. However, the list did not contain OGNL, and it contained Signing, which was retired ages ago. So it was already out of date (and see below). > If that's how you want to advertise Commons to the wider > GitHub world, then go for it ;-) Do we really want to advertise dormant/retired/sandbox/internal projects in this way? For example, https://github.com/apache/commons-lang#apache-commons-components currently includes Signing, which has a link to a non-existent website. I've also just noticed that the template links to Graph which is in the Sandbox. There are also links to internal components such as the Build Plugin and Commons Parent. As well as Testing - status unknown (and no website AFAICT) > Gary > > > > > > Gary > > > > > > On Mon, Oct 2, 2023, 5:05 AM sebb wrote: > > > > > > > The Build Plugin currently includes a list of components in the README > > > > template. > > > > > > > > This duplicates information provided elsewhere, and gets out of date. > > > > > > > > Since this info is in every GH repo, any changes also need to be > > > > applied to every one of them, to ensure they are up to date. > > > > > > > > This is an unnecessary maintenance burden. > > > > > > > > I think this local list should be dropped, and replaced with a link to > > > > the main website. > > > > > > > > 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: [VOTE][LAZY] Release Apache Commons Parent 63 based on RC2
Can you provide the usage for the new property? This is listed in the release notes as a new feature thanks to dependabot. But the commit was a single line added by Gary. I do not think it is attributed to dependabot. It is added under the release management section for properties for the Commons Release plugin but I cannot find 'commons.conf.dir' referenced in the current release plugin code. Alex On Mon, 2 Oct 2023 at 13:28, Gary Gregory wrote: > > We have fixed a few bugs and added some enhancements since Apache > Commons Parent 62 was released, so I would like to release Apache > Commons Parent 63. > > Apache Commons Parent 63 RC2 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2 > (svn revision 64292) > > The Git tag commons-parent-63-RC2 commit for this RC is > cf512e1352e886a50c1f292420dbc052bdedbf39 which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=cf512e1352e886a50c1f292420dbc052bdedbf39 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-parent.git > --branch commons-parent-63-RC2 commons-parent-63-RC2 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1662/org/apache/commons/commons-parent/63/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Mon Oct 02 07:53:04 EDT 2023 > commons-parent-63-src.tar.gz=415919a83c9a84101c586e36da25aeacad9126119e5f3bee1de8db8e4dbda46c5b0a28a0c440ea64254533f31d31be5e2904838e1dd72d456e7befde7a6b2f77 > org.apache.commons_commons-parent-63.spdx.json=51ef87a005d61ad1aa1318770ad79f4decbe717d7a570266c3ad24223fe5f7e7fcaf0ef162a5e6dc232ba6f79799f484ce68345a8bf164bf52f6992bf6d5cc7c > commons-parent-63-site.xml=5f045989b2c281c567467548678fe8685efabf5c13104299eea87b6ab6b6a75c9e98b590d7b288b8ec3a06934061709d0851a6dd9d9b45100ee2950908ec2d6c > commons-parent-63-src.zip=3674e727c8a770117d40d21812d581774446d9144a9625d3b45535231ccc9ad7e923397d1e9df16133888fbcc8745c573639f89523ba3dd360d459d08069eea1 > 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 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-RC2/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2/site/changes-report.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2/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-RC2/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-RC2 commons-parent-63-RC2 > cd commons-parent-63-RC2 > > 1b) Download and unpack the source archive from: > > https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2/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: [BUILD-PLUGIN] Drop component list from README template?
On Mon, Oct 2, 2023 at 8:04 AM sebb wrote: > > On Mon, 2 Oct 2023 at 11:34, Gary Gregory wrote: > > > > My intent was to advertise the breadth of Commons without forcing users > > away from GitHub but instead let them jump to another github repo directly. > > The problem is that the list gets out of date and needs a lot of > ongoing manual maintenance. I'm not sure I buy that argument. The only change that's happened that I can recall is our recent decision to make [functor] and [ognl] dormant. If that's how you want to advertise Commons to the wider GitHub world, then go for it ;-) Gary > > > Gary > > > > On Mon, Oct 2, 2023, 5:05 AM sebb wrote: > > > > > The Build Plugin currently includes a list of components in the README > > > template. > > > > > > This duplicates information provided elsewhere, and gets out of date. > > > > > > Since this info is in every GH repo, any changes also need to be > > > applied to every one of them, to ensure they are up to date. > > > > > > This is an unnecessary maintenance burden. > > > > > > I think this local list should be dropped, and replaced with a link to > > > the main website. > > > > > > 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
[VOTE][LAZY] Release Apache Commons Parent 63 based on RC2
We have fixed a few bugs and added some enhancements since Apache Commons Parent 62 was released, so I would like to release Apache Commons Parent 63. Apache Commons Parent 63 RC2 is available for review here: https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2 (svn revision 64292) The Git tag commons-parent-63-RC2 commit for this RC is cf512e1352e886a50c1f292420dbc052bdedbf39 which you can browse here: https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=cf512e1352e886a50c1f292420dbc052bdedbf39 You may checkout this tag using: git clone https://gitbox.apache.org/repos/asf/commons-parent.git --branch commons-parent-63-RC2 commons-parent-63-RC2 Maven artifacts are here: https://repository.apache.org/content/repositories/orgapachecommons-1662/org/apache/commons/commons-parent/63/ These are the artifacts and their hashes: #Release SHA-512s #Mon Oct 02 07:53:04 EDT 2023 commons-parent-63-src.tar.gz=415919a83c9a84101c586e36da25aeacad9126119e5f3bee1de8db8e4dbda46c5b0a28a0c440ea64254533f31d31be5e2904838e1dd72d456e7befde7a6b2f77 org.apache.commons_commons-parent-63.spdx.json=51ef87a005d61ad1aa1318770ad79f4decbe717d7a570266c3ad24223fe5f7e7fcaf0ef162a5e6dc232ba6f79799f484ce68345a8bf164bf52f6992bf6d5cc7c commons-parent-63-site.xml=5f045989b2c281c567467548678fe8685efabf5c13104299eea87b6ab6b6a75c9e98b590d7b288b8ec3a06934061709d0851a6dd9d9b45100ee2950908ec2d6c commons-parent-63-src.zip=3674e727c8a770117d40d21812d581774446d9144a9625d3b45535231ccc9ad7e923397d1e9df16133888fbcc8745c573639f89523ba3dd360d459d08069eea1 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 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-RC2/RELEASE-NOTES.txt https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2/site/changes-report.html Site: https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2/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-RC2/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-RC2 commons-parent-63-RC2 cd commons-parent-63-RC2 1b) Download and unpack the source archive from: https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC2/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 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 -the end-
Re: [BUILD-PLUGIN] Drop component list from README template?
On Mon, 2 Oct 2023 at 11:34, Gary Gregory wrote: > > My intent was to advertise the breadth of Commons without forcing users > away from GitHub but instead let them jump to another github repo directly. The problem is that the list gets out of date and needs a lot of ongoing manual maintenance. > Gary > > On Mon, Oct 2, 2023, 5:05 AM sebb wrote: > > > The Build Plugin currently includes a list of components in the README > > template. > > > > This duplicates information provided elsewhere, and gets out of date. > > > > Since this info is in every GH repo, any changes also need to be > > applied to every one of them, to ensure they are up to date. > > > > This is an unnecessary maintenance burden. > > > > I think this local list should be dropped, and replaced with a link to > > the main website. > > > > 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
[VOTE][LAZY][CANCEL] Release Apache Commons Parent 63 based on RC1
I am canceling this RC to pickup the latest from master. Gary On Sun, Oct 1, 2023 at 5:42 PM sebb wrote: > > 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. > > >
Re: [BUILD-PLUGIN] Drop component list from README template?
My intent was to advertise the breadth of Commons without forcing users away from GitHub but instead let them jump to another github repo directly. Gary On Mon, Oct 2, 2023, 5:05 AM sebb wrote: > The Build Plugin currently includes a list of components in the README > template. > > This duplicates information provided elsewhere, and gets out of date. > > Since this info is in every GH repo, any changes also need to be > applied to every one of them, to ensure they are up to date. > > This is an unnecessary maintenance burden. > > I think this local list should be dropped, and replaced with a link to > the main website. > > Sebb > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
Re: [BUILD-PLUGIN] Drop component list from README template?
On Mon, 2 Oct 2023 at 10:05, sebb wrote: > > The Build Plugin currently includes a list of components in the README > template. > > This duplicates information provided elsewhere, and gets out of date. > > Since this info is in every GH repo, any changes also need to be > applied to every one of them, to ensure they are up to date. > > This is an unnecessary maintenance burden. > > I think this local list should be dropped, and replaced with a link to > the main website. +1 Alex - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[BUILD-PLUGIN] Drop component list from README template?
The Build Plugin currently includes a list of components in the README template. This duplicates information provided elsewhere, and gets out of date. Since this info is in every GH repo, any changes also need to be applied to every one of them, to ensure they are up to date. This is an unnecessary maintenance burden. I think this local list should be dropped, and replaced with a link to the main website. Sebb - 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
Builds ok, tests ok, site ok: [+1] Nitpick: no coverage report in site (using mvn site), Spotbugs report a tad verbose hbiestro@hbiestro-MBP16 commons-net-3.10.0-RC1 % uname -a Darwin hbiestro-MBP16 22.6.0 Darwin Kernel Version 22.6.0: Fri Sep 15 13:41:28 PDT 2023; root:xnu-8796.141.3.700.8~1/RELEASE_ARM64_T6000 arm64 hbiestro@hbiestro-MBP16 commons-net-3.10.0-RC1 % mvn -v Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) Maven home: /Users/hbiestro/Java/apache-maven-3.8.6 Java version: 1.8.0_352, vendor: Azul Systems, Inc., runtime: /Library/Java/JavaVirtualMachines/zulu-8.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "13.6", arch: "aarch64", family: "mac" - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
