+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
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
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
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
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,
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
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
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
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
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
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
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
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
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
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
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 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,
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
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
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
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;
21 matches
Mail list logo
