ct dependencies within a project.
>> > >> Further, if publication/installation is needed, then one cannot rely
>> > >> 100% on the output: the poms might have changed since last push.
>> > >>
>> > >> > Gary
>> > >> >
>
> > >> >
> > >> > > Is this saying that not every commons artifact (1) is available
> in the
> > >> > > snapshot repo (2)?
> > >> > >
> > >> > > Why would some be in the snapshot repo and others not? Are e
ailable in the
> >> > > snapshot repo (2)?
> >> > >
> >> > > Why would some be in the snapshot repo and others not? Are each of
> >> the
> >> > > given just not setup to publish snapshots?
> >> > >
> >> >
hot repo (2)?
>> > >
>> > > Why would some be in the snapshot repo and others not? Are each of
>> the
>> > > given just not setup to publish snapshots?
>> > >
>> > >
>> > > 1. https://repo1.maven.org/mav
; given just not setup to publish snapshots?
> > >
> > >
> > > 1. https://repo1.maven.org/maven2/org/apache/commons/
> > > 2. https://repository.apache.org/content/groups/snapshots/
> > >
> > > Get Outlook for iOS<https://
On Wed, Feb 12, 2025 at 10:10 AM sebb wrote:
>
> On Wed, 12 Feb 2025 at 14:53, Volodymyr Siedlecki wrote:
> >
> > Hello,
> >
> > I don't see it explicitly on the commons website, but is 3.2.2 end of Life?
> > I'm assuming so (as there are no releases in 10 years), but I would like to
> > double c
On Wed, 12 Feb 2025 at 15:22, Volodymyr Siedlecki wrote:
>
> We are looking at collections4 as a possibility, but haven't determined if we
> can upgrade yet.
>
> The main issue is COLLECTIONS-701which is flagged by security scanners:
>
> ```
> The framework Apache Commons Collections before 4.3 i
Le mer. 12 févr. 2025 à 15:57, sebb a écrit :
>> [...]
> >
> > It's possible to setup GH to push snapshots but that requires setting up
> > secrets and makes the workflows more complex. I think infra might need to
> > get involved for the secrets part, not aure.
>
> My point is that it should not
We are looking at collections4 as a possibility, but haven't determined if we
can upgrade yet.
The main issue is COLLECTIONS-701which is flagged by security scanners:
```
The framework Apache Commons Collections before 4.3 is vulnerable to Stack
Overflow. The function add() in the file list/S
On Wed, 12 Feb 2025 at 14:53, Volodymyr Siedlecki wrote:
>
> Hello,
>
> I don't see it explicitly on the commons website, but is 3.2.2 end of Life?
> I'm assuming so (as there are no releases in 10 years), but I would like to
> double check?
Collections3 is no longer advertised on the download pa
Hi.
Le mer. 12 févr. 2025 à 15:10, Gary Gregory a écrit :
>
> Hi All,
>
> I always use dependency:tree, that always works for me.
>
> At some point someone set up Jenkins jobs for some of the Commons
> components to publish snapshots, but I never look at Jenkins, I find it
> unreliable with the r
/o0ukef>
> > ____
> > From: Elliotte Rusty Harold
> > Sent: Wednesday, February 12, 2025 7:23:16 AM
> > To: Commons Developers List
> > Subject: Re: [ALL] Maven module expert needed please
> >
> > On Wed, Feb 12, 2025 at
_
> From: Elliotte Rusty Harold
> Sent: Wednesday, February 12, 2025 7:23:16 AM
> To: Commons Developers List
> Subject: Re: [ALL] Maven module expert needed please
>
> On Wed, Feb 12, 2025 at 12:27 AM sebb wrote:
>
> > org.apache.commo
On Wed, 12 Feb 2025 at 13:26, Elliotte Rusty Harold wrote:
>
> On Wed, Feb 12, 2025 at 12:27 AM sebb wrote:
>
> > org.apache.commons:commons-weaver-processor:jar:2.1-SNAPSHOT
> >
> > Note that the component is currently at version 2.1-SNAPSHOT.
> >
> > Surely it should not be necessary to build a
g/content/groups/snapshots/
>
> Get Outlook for iOS<https://aka.ms/o0ukef>
>
> From: Elliotte Rusty Harold
> Sent: Wednesday, February 12, 2025 7:23:16 AM
> To: Commons Developers List
> Subject: Re: [ALL] Maven module expert
://repository.apache.org/content/groups/snapshots/
Get Outlook for iOS<https://aka.ms/o0ukef>
From: Elliotte Rusty Harold
Sent: Wednesday, February 12, 2025 7:23:16 AM
To: Commons Developers List
Subject: Re: [ALL] Maven module expert needed please
On Wed, Feb 12, 2025 at 12
On Wed, Feb 12, 2025 at 12:27 AM sebb wrote:
> org.apache.commons:commons-weaver-processor:jar:2.1-SNAPSHOT
>
> Note that the component is currently at version 2.1-SNAPSHOT.
>
> Surely it should not be necessary to build and install the component
> in order to list its dependencies?
> Or am I mis
On Tue, 11 Feb 2025 at 23:52, Melloware Inc wrote:
>
> Can’t you do “mvn -U clean package” the -U ignores the local cache timing.
It's not a question of cache timing: the missing jar does not yet
exist in any repo.
However, I did just try that, and it makes no difference; 'mvn
dependency:list' s
Can’t you do “mvn -U clean package” the -U ignores the local cache timing.
Melloware
@melloware on GitHub
> On Feb 11, 2025, at 6:47 PM, sebb wrote:
>
> Commons weaver seems to have an issue with its pom module settings.
>
> One symptom is that the following fails:
>
> $ mvn dependency:lis
Hi Arnout and all.
Le lun. 10 févr. 2025 à 12:11, Arnout Engelen a écrit :
>
> On Mon, Feb 10, 2025 at 11:45 AM Gilles Sadowski
> wrote:
>
> > Le lun. 10 févr. 2025 à 11:25, Arnout Engelen a
> > écrit :
> > > Do you mean we should leave out the whole line or just the "Thanks to
> > > Dependabot
If an API is deprecated, please make sure the @deprecated comment
states clearly with an @link what the replacement is.
This will allow people who use OpenRewrite to configure their wares
accordingly. IOW, don't give users a headache ;-)
Gary
On Tue, Feb 11, 2025 at 7:18 AM Gilles Sadowski wrot
Hi.
Le mar. 11 févr. 2025 à 12:56, Elliotte Rusty Harold
a écrit :
>
> I am not surprised you've found issues with FastDateFormat. I'd be
> more surprised if you didn't. Handling time zones is *hard* and almost
> everyone gets it wrong, at least at first. In 2025 I wouldn't use
> either SimpleDat
I am not surprised you've found issues with FastDateFormat. I'd be
more surprised if you didn't. Handling time zones is *hard* and almost
everyone gets it wrong, at least at first. In 2025 I wouldn't use
either SimpleDateFormat or FastDateFormat. Use java.time and
java.time.formatter instead. These
Hello Xeno,
Please start a new thread with your proposal.
Gary
On Mon, Feb 10, 2025, 08:10 Xeno Amess wrote:
> btw I just got an idea, is it meaningful to make a commons-bom or
> something?
> I really worried about if our repos can even runs in a same jvm(I mean
> normally, not osgi or shading
btw I just got an idea, is it meaningful to make a commons-bom or something?
I really worried about if our repos can even runs in a same jvm(I mean
normally, not osgi or shading)
Maybe a commons-bom repo and monthly release be useful? Gary what do you
think?
Xeno Amess 于2025年2月10日周一 21:08写道：
> >
> This is different Emanuel, Dependabot did in fact do all the work. I don't
think we would suggest not giving authorship if a person did the work. That
work is extremely valuable IMO, especially considering the OS x Java
version matrix.
Gary, root of the problem is as I described before, you and
This is different Emanuel, Dependabot did in fact do all the work. I don't
think we would suggest not giving authorship if a person did the work. That
work is extremely valuable IMO, especially considering the OS x Java
version matrix.
Gary
On Mon, Feb 10, 2025, 05:34 Emmanuel Bourg wrote:
> On
I think the idea of "celebration" is antiquated here, I see this as a label
that reflects the same idea that git has with the split of "author" and
"committer". In this case "dev" is the committer and "thanks" is the author.
Gary
On Mon, Feb 10, 2025, 05:25 Arnout Engelen wrote:
> On Mon, Feb 1
Knowing that Dependabot did the work should tell you that all builds were
green in the GH CI matrix (unless one commits a bump when a red build
exists in the matrix, it's happened before).
The alternative is that you have no idea what a dev did to validate an
upgrade (unless the commit comment say
> Gotcha, I didn't realize different commons- components had different ways
of working here, sorry about that.
yes. Gillis tends to remain on old versions of dependencies, and worries
about people using old versions dependency cannot upgrade to new versions
of commons-lib.
so Gillis and math libs
On Mon, Feb 10, 2025 at 11:45 AM Gilles Sadowski
wrote:
> Le lun. 10 févr. 2025 à 11:25, Arnout Engelen a
> écrit :
> > Do you mean we should leave out the whole line or just the "Thanks to
> > Dependabot" part?
>
> The whole line.
>
> > I tried to follow the convention from other Commons projec
ary 10, 2025 6:32:35 PM
To: dev@commons.apache.org
Subject: Re: [All] Useless update of "changes.xml"
On 10/02/2025 10:20, Gilles Sadowski wrote:
> Hi.
>
> The commit below will generate a line in the release notes that says
> "Thanks to Dependabot".
> I don
breaking dependency updates are another situation.
Xeno Amess
From: Gilles Sadowski
Sent: Monday, February 10, 2025 6:45:06 PM
To: Commons Developers List
Subject: Re: [All] Useless update of "changes.xml"
Hi.
Le lun. 10 févr. 2025 à 11:25, Arnout Engelen a écrit :
>
> On Mon,
Hi Arnout,
On 10.02.2025 11:24, Arnout Engelen wrote:
That doesn't seem easy to automate,
though, and I'd say we don't want to add additional steps to the release
process either.
It is possible to automate (see [1] for example), but it requires a
workflow to run as `pull-request-target`. Alte
Hi.
Le lun. 10 févr. 2025 à 11:25, Arnout Engelen a écrit :
>
> On Mon, Feb 10, 2025 at 10:21 AM Gilles Sadowski
> wrote:
>
> > The commit below will generate a line in the release notes that says
> > "Thanks to Dependabot".
> >
>
> It generates a line that says "Bump org.apache.commons:commons-
On 10/02/2025 10:20, Gilles Sadowski wrote:
Hi.
The commit below will generate a line in the release notes that says
"Thanks to Dependabot".
I don't that it is useful (IMHO, it is even harmful if it is littered
with hardly
informative automated messages that drown functional changes).
Fine if th
On Mon, Feb 10, 2025 at 10:21 AM Gilles Sadowski
wrote:
> The commit below will generate a line in the release notes that says
> "Thanks to Dependabot".
>
It generates a line that says "Bump org.apache.commons:commons-rng-bom from
1.5 to 1.6 #244 Thanks to Dependabot.".
> I don't that it is us
Le lun. 10 févr. 2025 à 10:31, Xeno Amess a écrit :
>
> thank is free imo...
It's not when it actually obscures the information.
> a free thank for a free bot, sounds fair to me...
It's not "fair" wrt all the other much more useful tools that we use to build
our software but is not celebrated e
btw I bet Gary would say yes to the thank, he really loves that bot lol
Xeno Amess 于2025年2月10日周一 17:31写道：
> thank is free imo...
> a free thank for a free bot, sounds fair to me...
>
> Xeno Amess
> --
> *From:* Gilles Sadowski
> *Sent:* Monday, February 10, 2025 5:20
thank is free imo...
a free thank for a free bot, sounds fair to me...
Xeno Amess
From: Gilles Sadowski
Sent: Monday, February 10, 2025 5:20:53 PM
To: Commons Developers List
Subject: [All] Useless update of "changes.xml"
Hi.
The commit below will generate a li
Hi Gary,
On 8.02.2025 00:35, Gary Gregory wrote:
Nice find! :-) I fixed the offending files (zip and tar). Committed SVN
revision 74783 (no longer revision 74565):
After this change everything checks out:
* hashes
* signatures
* build, test and reproducibility using:
$ mvn -version
Apache
On Fri, Feb 7, 2025 at 6:35 PM Gary Gregory wrote:
> On Fri, Feb 7, 2025 at 5:40 PM Piotr P. Karwasz
> wrote:
> >
> > Hi Gary,
> >
> > On 31.01.2025 16:38, Gary Gregory wrote:
> > > Please review the release candidate and vote.
> > > This vote will close no sooner than 72 hours from now.
> > >
>
On Fri, Feb 7, 2025 at 5:40 PM Piotr P. Karwasz
wrote:
>
> Hi Gary,
>
> On 31.01.2025 16:38, Gary Gregory wrote:
> > 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...
> >[
Hi Gary,
On 31.01.2025 16:38, Gary Gregory wrote:
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...
The b
On Thu, Feb 6, 2025 at 11:09 PM Arnout Engelen wrote:
> * I did not test the artifacts against any project
>
(I have also ran the jackrabbit-vfs-ext unit tests with the staged version
now, no surprises)
Arnout
> On Mon, Feb 3, 2025 at 12:27 AM Gary Gregory
> wrote:
>
>> We have fixed a few
I have:
* checked out git tag commons-vfs-2.10.0-RC1 (this needed a --force due to
leftover from previous vote)
* verified it (now) corresponds to 1b94883317d6687e2dd3a0294d9e6e2ab066cf56
* downloaded source zip and tgz
* verified the hashes match
37254a4e73862522017195b941b42c7befe6629a1cf9efc8902
Anthony,
Thank you for the note. Let's review these after the release. We've been
long overdue for this release as it is.
Ty!
Gary
On Tue, Feb 4, 2025, 09:45 Anthony Goubard
wrote:
> Hi,
>
> Here are a few PR/changes that I made to Commons-VFS in case someone
> thinks it should be added to th
Hi,
Here are a few PR/changes that I made to Commons-VFS in case someone
thinks it should be added to the master branch before (or after) the 2.10.0
final release.
First, I've updated my existing pull requests to resolve the conflicts
with the current master branch.
Improved performance of Uri
On Mon, Feb 3, 2025, 16:05 sebb wrote:
> On Sat, 1 Feb 2025 at 14:20, Gary Gregory wrote:
> >
> > +1 to remove.
> >
> > I'm on Slack FWIW.
>
> Is that open to the public?
>
I think it's only for committers, you login with your Apache ID IIRC.
Gary
If so, perhaps that could be added if someone
On Sat, 1 Feb 2025 at 14:20, Gary Gregory wrote:
>
> +1 to remove.
>
> I'm on Slack FWIW.
Is that open to the public?
If so, perhaps that could be added if someone knows how to link to it.
> Gary
>
> On Sat, Feb 1, 2025 at 8:46 AM sebb wrote:
> >
> > The main website says we have an IRC channe
My +1
Gary
On Sun, Feb 2, 2025, 18:26 Gary Gregory wrote:
> We have fixed a few bugs and added enhancements since Apache Commons
> VFS Project 2.9.0 was released over 3 years ago, so I would like to
> release Apache Commons VFS Project 2.10.0.
>
> [Note that try to verify reproducibility using
> (no coverage by default ?)
Hm, that's annoying I"ll see about fixing that post-release.
Gary
On Fri, Jan 31, 2025 at 11:15 AM Henri Biestro wrote:
>
> My [+1]
>
> Builds &tests ok, reproductible build check, reports ok (no coverage by
> default ?), changes ok.
>
> Checked on:
> Apache Maven
+1 to remove.
I'm on Slack FWIW.
Gary
On Sat, Feb 1, 2025 at 8:46 AM sebb wrote:
>
> The main website says we have an IRC channel #apache-commons (on Freenode)
>
> AFAIK that has not been using in ages, so I propose to remove the
> reference unless I hear otherwise.
>
> Sebb
>
> ---
My [+1]
Builds & tests ok, reproductible build check, reports ok, changes ok.
Checked on:
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) Maven home:
/Users/hbiestro/Java/apache-maven-3.8.6 Java version: 21.0.3, vendor: Azul
Systems, Inc., runtime:
/Library/Java/JavaVirtualMachin
My [+1]
Builds &tests ok, reproductible build check, reports ok (no coverage by default
?), changes ok.
Checked on:
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: /Users/hbiestro/Java/apache-maven-3.8.6
Java version: 21.0.3, vendor: Azul Systems, Inc., runtime:
/Libr
My +1
Gary
On Fri, Jan 31, 2025 at 10:38 AM Gary Gregory wrote:
>
> [The main change since RC1 is the fix for OSGi]
>
> We have fixed a few bugs and added enhancements since Apache Commons
> Logging 1.3.4 was released, so I would like to release Apache Commons
> Logging 1.3.5.
>
> Apache Commons
My non-binding +1
On Fri, Jan 31, 2025 at 10:36 AM Gary Gregory
wrote:
> My +1
>
> Gary
>
> On Fri, Jan 31, 2025 at 10:34 AM Gary Gregory
> wrote:
> >
> > We have fixed a few bugs and added enhancements since Apache Commons
> > BeanUtils 1.10.0 was released, so I would like to release Apache
>
My +1
Gary
On Fri, Jan 31, 2025 at 10:34 AM Gary Gregory wrote:
>
> We have fixed a few bugs and added enhancements since Apache Commons
> BeanUtils 1.10.0 was released, so I would like to release Apache
> Commons BeanUtils 1.10.1.
>
> Apache Commons BeanUtils 1.10.1 RC1 is available for review
My +1
Gary
On Wed, Jan 29, 2025 at 11:28 AM Gary Gregory wrote:
>
> [NOTE: This VOTE is only open for 24 hours as version 80 requires Java
> 8 to run SpotBugs]
>
> We have fixed a few bugs and added enhancements since Apache Commons
> Parent 80 was released, so I would like to release Apache Com
On Thu, 30 Jan 2025 at 01:36, Gilles Sadowski wrote:
>
> Hi.
>
> Le jeu. 30 janv. 2025 à 02:05, sebb a écrit :
> > > [...]
> > > >
> > > > I think this shows that a new CP release should be tried in a few
> > > > components first.
> > >
> > > +0.5
> > >
> > > Ideal would be to have some automatio
Hi.
Le jeu. 30 janv. 2025 à 02:05, sebb a écrit :
> > [...]
> > >
> > > I think this shows that a new CP release should be tried in a few
> > > components first.
> >
> > +0.5
> >
> > Ideal would be to have some automation that would, for every
> > component:
> > * create a branch (e.g. "master_a
On Thu, 30 Jan 2025 at 00:45, Gilles Sadowski wrote:
>
> Hi.
>
> Le jeu. 30 janv. 2025 à 01:32, sebb a écrit :
> >
> > On Thu, 30 Jan 2025 at 00:00, Gary Gregory wrote:
> > >
> > > On Wed, Jan 29, 2025 at 11:51 AM sebb wrote:
> > > >
> > > > On Wed, 29 Jan 2025 at 16:30, Gary Gregory
> > > >
Hi.
Le jeu. 30 janv. 2025 à 01:32, sebb a écrit :
>
> On Thu, 30 Jan 2025 at 00:00, Gary Gregory wrote:
> >
> > On Wed, Jan 29, 2025 at 11:51 AM sebb wrote:
> > >
> > > On Wed, 29 Jan 2025 at 16:30, Gary Gregory wrote:
> > > >
> > > > [NOTE: This VOTE is only open for 24 hours as version 80 re
On Thu, 30 Jan 2025 at 00:00, Gary Gregory wrote:
>
> On Wed, Jan 29, 2025 at 11:51 AM sebb wrote:
> >
> > On Wed, 29 Jan 2025 at 16:30, Gary Gregory wrote:
> > >
> > > [NOTE: This VOTE is only open for 24 hours as version 80 requires Java
> > > 8 to run SpotBugs]
> >
> > I don't see why this is
On Wed, Jan 29, 2025 at 11:51 AM sebb wrote:
>
> On Wed, 29 Jan 2025 at 16:30, Gary Gregory wrote:
> >
> > [NOTE: This VOTE is only open for 24 hours as version 80 requires Java
> > 8 to run SpotBugs]
>
> I don't see why this is urgent.
> Version 80 is optional; if it breaks something, just rever
On Wed, 29 Jan 2025 at 16:30, Gary Gregory wrote:
>
> [NOTE: This VOTE is only open for 24 hours as version 80 requires Java
> 8 to run SpotBugs]
I don't see why this is urgent.
Version 80 is optional; if it breaks something, just revert to 79.
> We have fixed a few bugs and added enhancements s
My +1
Gary
On Sat, Jan 25, 2025 at 4:51 PM Gary Gregory wrote:
>
> We have fixed a few bugs and added enhancements since Apache Commons
> Parent 79 was released, so I would like to release Apache Commons
> Parent 80.
>
> Apache Commons Parent 80 RC1 is available for review here:
> https://di
On Tue, 28 Jan 2025 at 07:10, Herve Boutemy wrote:
>
> thank you Aman,
>
> hi level view of results:
> https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/commons/commons-daemon/README.md
>
> reading release instructions
> https://github.com/apache/commons-dae
thank you Aman,
hi level view of results:
https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/commons/commons-daemon/README.md
reading release instructions
https://github.com/apache/commons-daemon/blob/master/HOWTO-RELEASE.txt
IIUC, a Windows machine is expe
it would be more a feature request = "build SPDX output in a reproducible way"
for now, I generally ignore SPDX output when checking rebuild output: I do not
have time to contribute more to spdx-maven-plugin
Regards,
Hervé
On 2025/01/24 13:19:53 Gary Gregory wrote:
> Piotr,
>
> Is there at le
It has been pointed out to me that this claim is too strong. I would want to
take it back and simply admit that I was not able to reproduce the artifacts
from source. I will appreciate any help to build those Windows binary and
package them in the jar on my Linux machine.
Regards,
Aman Sharma
I have:
* checked out git tag commons-codec-1.18.0-RC1
* verified it corresponds to a38de9528197b2d01e5b6c9b2e0af3a624cff017
* downloaded source zip and tgz
* verified the hashes match
079876efff8534650c6e9a5a207b7cc6b93d5c42f928f6c789279466eb1d82270ffa756300d0d0a91b24cf3cb0c029417e3fb043fd007d9462
Is this all part of making gitbox more reliable? It sure goes down a lot.
Gary
On Mon, Jan 27, 2025, 11:09 Arnout Engelen wrote:
> I saw them - I suspect they were related to the gitbox outage that was
> going on around the same time.
>
> (I did consider improving the error message/trace to mak
I saw them - I suspect they were related to the gitbox outage that was
going on around the same time.
(I did consider improving the error message/trace to make it more verbose,
but Infra is planning a migration to an overhauled asf.yaml system which
will replace the code that threw this error, so
I have:
* checked out git tag commons-pool-2.12.1-RC3
* verified it corresponds to 63610d0aa8f8409850c5a85bfadb002d7578f411
* downloaded source zip and tgz
* verified the hashes match
0fb56dbc9c74c67853c87da7ec499885086267a3f5a7dcf1aaf22254d2ec7408fce867b542340f2a75638bd709cb55a37650969b79aec2c5a06
Must be false postives because the GitHub builds are green. Kinda rude to
dump undecipherable messgaes...
Gary
On Mon, Jan 27, 2025, 10:35 Gilles Sadowski wrote:
> Hi.
>
> Did you see those error messages (sent by INFRA to commits@)?
>
> Gilles
>
> Le lun. 27 janv. 2025 à 15:20, Apache Infrastr
+1
> On Jan 24, 2025, at 9:47 AM, Gary Gregory wrote:
>
> We have added two methods to support Apache Jackrabbit's migration
> from Guava since Apache Commons Codec 1.17.1 was released, so I would
> like to release Apache Commons Codec 1.18.0.
>
> Apache Commons Codec 1.18.0 RC1 is available fo
Hi.
Did you see those error messages (sent by INFRA to commits@)?
Gilles
Le lun. 27 janv. 2025 à 15:20, Apache Infrastructure
a écrit :
>
>
> An error occurred while running notifications feature in .asf.yaml!:
> Expecting value: line 1 column 1 (char 0)
>
-
Le mer. 22 janv. 2025 à 23:55, sebb a écrit :
>
> On Wed, 22 Jan 2025 at 14:40, Gilles Sadowski wrote:
> >
> > Hi.
> >
> > Le mer. 22 janv. 2025 à 14:29, Gary Gregory a
> > écrit :
> > >
> > > On Wed, Jan 22, 2025 at 8:00 AM Gilles Sadowski
> > > wrote:
> > > >
> > > > Hi.
> > > >
> > > > Le
My +1
Gary
On Fri, Jan 24, 2025 at 9:47 AM Gary Gregory wrote:
>
> We have added two methods to support Apache Jackrabbit's migration
> from Guava since Apache Commons Codec 1.17.1 was released, so I would
> like to release Apache Commons Codec 1.18.0.
>
> Apache Commons Codec 1.18.0 RC1 is avai
+1
> On Jan 22, 2025, at 8:49 AM, Gary Gregory wrote:
>
> We have fixed a few bugs since Apache Commons Pool 2.12.0 was
> released, so I would like to release Apache Commons Pool 2.12.1.
>
> *The only difference between RC2 and RC3 is to fix the site's download
> link in the right-hand side men
Piotr,
Is there at least a bug to report to the SPDX project?
Gary
On Sun, Jan 12, 2025 at 11:03 AM Piotr P. Karwasz
wrote:
>
> Hi Gary,
>
> On 12.01.2025 13:40, Gary Gregory wrote:
> > [ERROR] sha512 mismatch commons-cli-1.10.0.spdx.json: investigate with
> > diffoscope target/reference/common
My +1
Gary
On Wed, Jan 22, 2025, 08:49 Gary Gregory wrote:
> We have fixed a few bugs since Apache Commons Pool 2.12.0 was
> released, so I would like to release Apache Commons Pool 2.12.1.
>
> *The only difference between RC2 and RC3 is to fix the site's download
> link in the right-hand side
On Wed, 22 Jan 2025 at 14:40, Gilles Sadowski wrote:
>
> Hi.
>
> Le mer. 22 janv. 2025 à 14:29, Gary Gregory a écrit :
> >
> > On Wed, Jan 22, 2025 at 8:00 AM Gilles Sadowski
> > wrote:
> > >
> > > Hi.
> > >
> > > Le mer. 22 janv. 2025 à 13:12, Gary Gregory a
> > > écrit :
> > > >
> > > > It'
On Wed, 22 Jan 2025 at 12:15, Gilles Sadowski wrote:
>
> Hi.
>
> Le mer. 22 janv. 2025 à 12:57, Maxim Solodovnik a
> écrit :
> >
> > Please NOTE 1.27 from here: https://summerofcode.withgoogle.com/rules :)
>
> Thanks for this reminder.
>
> In the other thread[1], Piotr mentioned
> > 1. Moving fr
Hi.
Le mer. 22 janv. 2025 à 14:29, Gary Gregory a écrit :
>
> On Wed, Jan 22, 2025 at 8:00 AM Gilles Sadowski wrote:
> >
> > Hi.
> >
> > Le mer. 22 janv. 2025 à 13:12, Gary Gregory a
> > écrit :
> > >
> > > It's unclear to me if we need the PMC's approval for this. We
> > > certainly did not v
On Wed, Jan 22, 2025 at 8:00 AM Gilles Sadowski wrote:
>
> Hi.
>
> Le mer. 22 janv. 2025 à 13:12, Gary Gregory a écrit :
> >
> > It's unclear to me if we need the PMC's approval for this. We
> > certainly did not vote on it.
Well, I certainly would like to know exactly what is proposed here.
Doe
Hi.
Le mer. 22 janv. 2025 à 13:12, Gary Gregory a écrit :
>
> It's unclear to me if we need the PMC's approval for this. We
> certainly did not vote on it.
Well, this thread is meant to gather opinions about this.
No need to vote if there is a clear argument, one way or
the other.
> It just loo
Hi.
Le mer. 22 janv. 2025 à 12:57, Maxim Solodovnik a écrit :
>
> Please NOTE 1.27 from here: https://summerofcode.withgoogle.com/rules :)
Thanks for this reminder.
In the other thread[1], Piotr mentioned
> 1. Moving from SVN to Git should be easy.
> 2. Converting from a variety of formats to A
It's unclear to me if we need the PMC's approval for this. We
certainly did not vote on it. It just looks like busy work to me for
little to no gain.
Gary
On Wed, Jan 22, 2025 at 6:45 AM Gilles Sadowski wrote:
>
> Hi.
>
> This is a formal follow-up of the proposal made there:
> https://lists.a
Please NOTE 1.27 from here: https://summerofcode.withgoogle.com/rules :)
from mobile (sorry for typos ;)
On Wed, Jan 22, 2025, 18:48 Piotr P. Karwasz
wrote:
> Hi Gilles,
>
> On 22.01.2025 12:51, Gilles Sadowski wrote:
> > * Who would be willing to co-mentor the project?
>
> I can co-mentor t
Hi Gilles,
On 22.01.2025 12:51, Gilles Sadowski wrote:
* Who would be willing to co-mentor the project?
I can co-mentor the project.
Piotr
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional comman
ease-plugin](https://commons.apache.org/proper/commons-release-plugin)
> > |
> > -| Apache Commons Rng |
> > [commons-rng](https://github.com/apache/commons-rng) |
> > [commons-rng](https://commons.apache.org/proper/commons-rng) |
> > -| Apache Commons Scxml |
&
-1, the source archive does not contain all the files needed to build a release.
Note that all the other components (apart from daemon, which is
special) use a single src.xml file that creates both tar.gz and zip
files.
They all include the entire src directory structure.
I'm not against keeping
thub.com/apache/commons-testing) |
> [commons-testing](https://commons.apache.org/proper/commons-testing) |
> -| Apache Commons Text |
> [commons-text](https://github.com/apache/commons-text) |
> [commons-text](https://commons.apache.org/proper/commons-text) |
> -| Apache Commons Validator
Hello Mehmet,
To narrow this down, I would try it from whatever command line tool Zstd
might have. If that doesn't work, then it's likely the file is corrupted.
If the Zstd CLI works, then I would try just using the Zstd library; if
that doesn't work for you, then that's where the problem should
Hi Dávid,
On 21.01.2025 18:44, Dávid Szigecsán wrote:
I'm not 100% sure this is a valid concern at the moment, but I think it
could be.
You can add exceptions to a `.gitattribute` file. For example the
`mvnw.cmd` file in Logging repos is configured to always have CRLF line
endings[1].
Piot
$ rm .git/index # Remove the index to force Git to
> > > $ git reset # re-scan the working directory
> > > $ git status# Show files that will be normalized
> > > $ git add -u
> > > $ git add .gitattributes
> > > $ git commit -m "Introdu
I have:
* checked out git tag commons-pool-2.12.1-RC1
* verified it corresponds to a65fc3457817abf993fdb29b69912346a2b4838b
* downloaded source zip and tgz
* verified the hashes match
c6c9731705c5d09f007a76350a35c3fb176184391923e8b1ab761b745f1256d79d0859b4f2802d065b6b9605174e771665debba26b4b1063d49
Also, if someone is thinking about doing this, they better be ready to
take on updating and testing our Maven Commons Release Plugin which
checks in the site and deliverables to Subversion.
Gary
On Sun, Jan 19, 2025 at 6:35 PM sebb wrote:
>
> On Sun, 19 Jan 2025 at 17:28, Piotr P. Karwasz
> wro
1 - 100 of 11061 matches
Mail list logo
