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
+1 for java17 :)
On Fri, 21 Jul 2023 at 21:52, Mark Thomas wrote:
>
> On 21/07/2023 16:18, Gary Gregory wrote:
> > Now that 2.0.0-M1 is out the door, let's talk about Java platform
> > requirements.
> >
> > I propose that for 2.0.0, FileUpload be bumped from Java 8 to 11, if not 17.
>
> +1 for J
+1
Tested:
- signatures
- build from sources (Ubuntu 22.04, mvn 3.9.1, openjdk 17.0.7)
- Apache Wicket build
please NOTE *.sha512 is not validatable with sha512sum tool:
```
sha512sum -c commons-fileupload2-2.0.0-M1-src.tar.gz.sha512
sha512sum: commons-fileupload2-2.0.0-M1-src.tar.gz.sha512: no p
http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
> Le mar. 11 juil.
Tomcat uses the code copy\pasted from commons-fileupload (due to there
was not release)
IMO it is better to use library instead of copy/pasting here and there .
On Tue, 11 Jul 2023 at 18:03, Romain Manni-Bucau wrote:
>
> This is a good point but guess it is not hard - and would be great - to
Hello,
On Wed, 14 Jun 2023 at 23:32, Efremov, Rodion
wrote:
>
> Hello,
>
> What Java version Collections 4.5 is being built for?
the answer is here:
https://github.com/apache/commons-collections/blob/master/pom.xml#L532
:)
ps I believe this question is for user@ list :)
>
> Best regards,
--
On Wed, 14 Jun 2023 at 23:32, Efremov, Rodion
wrote:
>
> Hello,
>
> What Java version Collections 4.5 is being built for?
>
> Best regards,
--
Best regards,
Maxim
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
F
eed to be refactored to use Factory ...
I'll try to take a look :) (most probably after vacation ... :))
>
> Gary
>
> On Wed, Jun 14, 2023, 09:06 Maxim Solodovnik wrote:
>
> > On Wed, 14 Jun 2023 at 19:46, Gary Gregory wrote:
> > >
> > > A FileItemHeade
>
> Gary
>
> On Wed, Jun 14, 2023, 06:50 Maxim Solodovnik wrote:
>
> > It seems I have API related question:
> >
> > FileItemHeadersImpl is not public anymore :((
> > How it can be created? :)))
> >
> > On Wed, 14 Jun 2023 at 17:28, Maxim Solo
It seems I have API related question:
FileItemHeadersImpl is not public anymore :((
How it can be created? :)))
On Wed, 14 Jun 2023 at 17:28, Maxim Solodovnik wrote:
>
> It seems new jar file missing `Automatic-Module-Name` would it be
> possible to add it? :)
>
> On Wed, 14 Ju
It seems new jar file missing `Automatic-Module-Name` would it be
possible to add it? :)
On Wed, 14 Jun 2023 at 17:10, Maxim Solodovnik wrote:
>
> On Wed, 14 Jun 2023 at 16:53, Gary Gregory wrote:
> >
> > Glad to hear that your testing went well.
> >
> > Some of
On Wed, 14 Jun 2023 at 16:53, Gary Gregory wrote:
>
> Glad to hear that your testing went well.
>
> Some of the documentation needs to be rewritten, so I'll look at that next
> unless someone else gets to it first.
>
> I plan on creating a release candidate for a 2.0.0-beta1 or 2.0.0-M1 within
> a
I guess, the title should be "[ANNOUNCE] Apache Commons IO 2.13.0" :)
from mobile (sorry for typos ;)
On Fri, Jun 9, 2023, 19:27 Gary Gregory wrote:
> The Apache Commons team announces Apache Commons IO version 2.13.0
>
> Commons IO is a package of Java utility classes like java.io. Classes
>
Hello Gary,
are there any news on release? :)
On Mon, 24 Apr 2023 at 19:18, Maxim Solodovnik wrote:
>
> Thanks for the update!
>
> from mobile (sorry for typos ;)
>
>
> On Mon, Apr 24, 2023, 17:33 Gary Gregory wrote:
>>
>> I am in the process of releasing comm
+1 :)
from mobile (sorry for typos ;)
On Sun, Apr 30, 2023, 21:22 Gary Gregory wrote:
> In the 2.0 snapshot code in git master, we support both javax and Jakarta
> servers, in different packages. I am thinking we should create maven
> modules for these and for portlets, such that all their de
Thanks for the update!
from mobile (sorry for typos ;)
On Mon, Apr 24, 2023, 17:33 Gary Gregory wrote:
> I am in the process of releasing commons-parent, then commons-io, then
> file-upload.
>
> Gary
>
> On Mon, Apr 24, 2023, 05:09 Maxim Solodovnik wrote:
>
> >
Hello Gary,
any new ETA for the release? :)
On Mon, 10 Apr 2023 at 19:45, Maxim Solodovnik wrote:
>
> Thais for the update! :)
>
> from mobile (sorry for typos ;)
>
>
> On Mon, Apr 10, 2023, 19:38 Gary Gregory wrote:
>>
>> Within a couple of weeks. There i
Thais for the update! :)
from mobile (sorry for typos ;)
On Mon, Apr 10, 2023, 19:38 Gary Gregory wrote:
> Within a couple of weeks. There is a little more work up to do and Commons
> IO is next on my list.
>
> Gary
>
> On Sun, Apr 9, 2023, 21:54 Maxim Solodovnik wrote
Hello Gary,
I saw new commits at the commons-fileupload repo, but no release :(
Can you please share new ETA for the 2.0 release? :)
On Thu, 30 Mar 2023 at 10:12, Maxim Solodovnik wrote:
>
> Thanks a million! :)
>
> On Thu, 30 Mar 2023 at 01:10, Gary Gregory wrote:
> >
>
Thanks a million! :)
On Thu, 30 Mar 2023 at 01:10, Gary Gregory wrote:
>
> Great, I'll take a closer look and see if it is in a state where I can cut
> a release candidate this weekend.
>
> Gary
>
> On Wed, Mar 29, 2023, 11:48 Maxim Solodovnik wrote:
>
> >
at 01:13, Gary Gregory wrote:
>
> You can use the git master branch in your projects and let us know if you
> find issues.
>
> Gary
>
>
> On Mon, Mar 27, 2023, 23:01 Maxim Solodovnik wrote:
>
> > Q1 is almost over :(
> > Are you still planning t
Q1 is almost over :(
Are you still planning to release 2.0?
Do you need any help? :))
On 2022/12/07 17:30:35 Gary Gregory wrote:
> The next release will be 2.0 which will hopefully happen Q1 2023.
>
> Gary
>
> On Wed, Dec 7, 2022, 11:28 Dennis Kieselhorst wrote:
>
> > Well this is the change I
Versions maven plugin missing the option to skip alpha/beta/rc :)
from mobile (sorry for typos ;)
On Wed, Dec 29, 2021, 05:28 Romain Manni-Bucau
wrote:
> Not sure, guess you have dependabot oovers and haters but let stay simple:
>
> 1. If maven version plugin does not do its job let's fix it,
This is caused by different versions of maven-project-info-reports-plugin
https://maven.apache.org/plugins/maven-project-info-reports-plugin/#Incompatibility_Notice
On Sat, 25 May 2019 at 17:24, sebb wrote:
> Why do some components use:
>
> http://commons.apache.org/proper/commons-lang/scm.ht
My bad, haven't checked rat.txt (was from mobile)
bla.tar.xz is not recognized
I guess you can report this to rat JIRA and add this file to exclude
list to unblock builds ...
On Tue, 26 Mar 2019 at 21:25, Maxim Solodovnik wrote:
>
> Maybe workspace wasn't cleaned and some gener
Maybe workspace wasn't cleaned and some generated file remain?
On Tue, Mar 26, 2019, 21:06 Gary Gregory wrote:
> Hi All:
>
> When I run a RAT check with 'mvn apache-rat:check', all is fine. When I run
> the same kind of build as Jenkins with 'mvn clean package', all is fine.
>
> Why does the Jen
SSRH to remove it?
> >>
> >> Best regards.
> >>
> >> On 05/02/2019 16:42, Gary Gregory wrote:
> >>> I do not understand why MC lists 4.3 as released back in December.
> >>>
> >>> https://search.maven.org/search?q=g:org.apache.common
The Apache Commons team is pleased to announce the release of Apache
Commons Collections 4.3. The release is available for download at
http://commons.apache.org/proper/commons-collections/download_collections.cgi
Apache Commons Collections is a project to develop and maintain
collection classes b
Wed, 6 Feb 2019 at 22:36, Maxim Solodovnik wrote:
> The site is not yet updated
> I'll modify release notes and will add note regarding clirr issue
>
> will try to do it tomorrow
> sorry for delay
>
> On Wed, 6 Feb 2019 at 22:30, Gilles Sadowski wrote:
>
>>
The site is not yet updated
I'll modify release notes and will add note regarding clirr issue
will try to do it tomorrow
sorry for delay
On Wed, 6 Feb 2019 at 22:30, Gilles Sadowski wrote:
> Le mer. 6 févr. 2019 à 02:59, Maxim Solodovnik a
> écrit :
> >
> > Can someon
Hello Rob,
I'm afraid you have to change 1.12 with 1.11: "since Apache Commons Codec
1.12 was released, so I would like to release Apache Commons Codec 1.12"
and in some other places: for ex. "CLIRR Report (compared to 1.12):"
On Wed, 6 Feb 2019 at 10:08, Rob Tompkins wrote:
> We have fixed qui
Can someone from PMCs add release data to https://reporter.apache.org ?
On Wed, 6 Feb 2019 at 08:16, Maxim Solodovnik wrote:
> Hello Gary,
>
> Actually all "old" releases should be downloaded from
> https://archive.apache.org/dist/commons/collections/
> dist.a.o is syn
e.commons%20AND%20a:commons-collections4&core=gav
>
> Do we need to republish to MC?
>
> Gary
>
> On Tue, Feb 5, 2019 at 11:41 AM Gary Gregory
> wrote:
>
> > On Tue, Feb 5, 2019 at 10:55 AM Maxim Solodovnik
> > wrote:
> >
> >> On Tue, 5 Feb 20
On Tue, 5 Feb 2019 at 22:29, Gary Gregory wrote:
> Hello,
>
> On Tue, Feb 5, 2019 at 8:44 AM Maxim Solodovnik
> wrote:
>
> > Hello All,
> >
> > I'm planning to finalize the release
> >
> > I have couple of questions:
> > Current dist/
Hello All,
I'm planning to finalize the release
I have couple of questions:
Current dist/release contains
1) binaries for 3.2.2 and 4.2
2) RELEASE-NOTES.txt for 3.2.2 + 4.1 + 4.2
I plan to move 4.3 binaries to dist/release, wait 24 hours then drop 4.2
Is it OK? shall I also drop 3.2.2 binaries?
Hello All,
I'm closing the VOTE, 72 hours are over
The VOTE was successful, it receives 3 binding +1 Rob Tompkins, Gary
Gregory, Gilles Sadowski
On Fri, 1 Feb 2019 at 20:49, Gilles Sadowski wrote:
>
> Hi.
>
> Le jeu. 31 janv. 2019 à 12:23, Maxim Solodovnik a
> écrit :
>
This is a [VOTE] for releasing
Apache Commons collections 4.3
Tag name:
collections-4.3-RC2 (signature can be checked from git using 'git tag
-v')
Previous RC2 VOTE was canceled due to long discussion regarding
Clirr report [1]. To resolve this Japicmp report has been created [2] as
well
simp
The VOTE in this thread has been canceled
On Thu, 31 Jan 2019 at 16:11, sebb wrote:
> +1, it has become very messy
>
> Cancel this vote thread and start another
>
> On Thu, 31 Jan 2019 at 08:42, Gilles Sadowski
> wrote:
> >
> > Hello Maxim.
> >
>
This release need your VOTES :)))
On Sun, 27 Jan 2019 at 19:47, Maxim Solodovnik wrote:
> Hello All,
>
> Thanks to the Rob, I was able to create "compatibility report" using
> japicmp
> It looks green :)
>
> Would it be OK if I will replace clirr report in gener
Latest version of test [2] shows all errors are false positive
On Wed, 30 Jan 2019 at 20:23, Gilles Sadowski wrote:
> Hi.
>
> Le mer. 30 janv. 2019 à 13:16, Rob Tompkins a écrit :
> >
> >
> >
> > > On Jan 30, 2019, at 1:12 AM, Maxim Solodo
Hello All,
It seems my previous post was missed somehow
so will re-post here:
I have added japicmp report here: [1] is has none issues
Additionally I have updated gist [2] it also show there are no issues
In case this is not enough I propose to cancel RC2 and to release 5.0
[1]
https://dist.ap
Hello All,
I have added japicmp report here:
https://dist.apache.org/repos/dist/dev/commons/collections/4.3-RC2/site/japicmp.html
I see no issues here :(
On Tue, 29 Jan 2019 at 03:03, Marcelo Vanzin
wrote:
> On Mon, Jan 28, 2019 at 11:36 AM sebb wrote:
> > > Haven't looked at the code, but if
might as well start with releasing fresh versions of our internal maven
> plugins, then commons-parent, then components... ;-) More work for the RM!
> :-)
>
> Gary
>
> On Sun, Jan 20, 2019 at 5:06 AM Gilles Sadowski
> wrote:
>
> > Le dim. 20 janv. 2019 à 04:56, Maxim Solo
ed it to a pdf for the sake of sending it to the ML.
>
> -Rob
>
> > On Jan 25, 2019, at 11:33 PM, Maxim Solodovnik
> wrote:
> >
> > Hello Rob,
> >
> > can you please share brief how-to, so I can regenerate the report? :)
> >
> > On Sat, 26 Jan 2019
20, 2019 at 5:06 AM Gilles Sadowski
> > wrote:
> >
> >> Le dim. 20 janv. 2019 à 04:56, Maxim Solodovnik
> a
> >> écrit :
> >>>
> >>> I can see there is activity with replacing clirr with japicmp, maybe it
> >>> worth to hold this
I can see there is activity with replacing clirr with japicmp, maybe it
worth to hold this release until commons-parent v48 will be released?
On Sun, 20 Jan 2019 at 05:52, Gilles Sadowski wrote:
> Hi.
>
> Le sam. 19 janv. 2019 à 11:36, Maxim Solodovnik a
> écrit :
> >
>
I'm afraid I need help with this
since I don't understand why clirr reports these errors
On Sat, 19 Jan 2019 at 17:32, sebb wrote:
> On Sat, 19 Jan 2019 at 03:40, Maxim Solodovnik
> wrote:
> >
> > Hello All,
> >
> > Am I right thinking it is OK to add s
Hello All,
Am I right thinking it is OK to add something like
"Clirr errors reported for this version can be ignored" to release NOTES
and proceed with VOTE?
If I'm not mistaken after almost a month of voting we have
Binding:
1: +1 (Bruno P. Kinoshita)
Non-binding:
1: +1 (Maxim So
be noted in the release notes.
>
> S.
>
>
>
> On Fri, 18 Jan 2019 at 15:20, Maxim Solodovnik
> wrote:
> >
> > OK
> >
> > I have checked
> > clirr is the same (comparing to 4.2)
> >
> > I would appreciate is someone can perform detail
;@Override" annotation was added
Why is this being reported as error?
[1]
https://dist.apache.org/repos/dist/dev/commons/collections/4.3-RC2/site/clirr-report.html
On Thu, 17 Jan 2019 at 23:50, Maxim Solodovnik wrote:
> I'll try to double-check if clirr version was changed
> So
I'll try to double-check if clirr version was changed
So far I believe the issue is caused by java8 update
Will report back here
On Thu, Jan 17, 2019, 23:39 Gilles Sadowski Hi.
>
> Le jeu. 17 janv. 2019 à 17:21, Maxim Solodovnik a
> écrit :
> >
> > It seems to be &qu
It seems to be "stalemate situation"
The test wasn't written for a long period of time
And there not enough votes to release :(
On Thu, Jan 17, 2019, 22:59 Gilles Sadowski Le jeu. 17 janv. 2019 à 16:17, Maxim Solodovnik a
> écrit :
> >
> > Actually I don't ge
lo.
>
> Le jeu. 17 janv. 2019 à 04:24, Maxim Solodovnik a
> écrit :
> >
> > Hello All,
> >
> > Shall I cancel this VOTE and change project coordinates to be
> > commons-collections5 ?
>
> I must have missed part of the thread... IMO, a major release is no
egesis.html
> > > [2]
> > >
> > >
> >
> https://github.com/apache/commons-collections/commit/482762a13f739631f94d03642b0a55a9b7214c44
> > >
> > > Regards,
> > > Amey
> > >
> > >
> > > On Thu, Jan 3, 2019 at
.html
Maybe its clirr issue?
Would appreciate any help with this investigation
On Mon, 31 Dec 2018 at 16:53, Gilles wrote:
>
> On Mon, 31 Dec 2018 07:41:40 +0700, Maxim Solodovnik wrote:
> > Hello Gilles,
> >
> > I already did analysis: [1], all errors are caused by pr
gt; -Rob
>
> > On Dec 30, 2018, at 12:25 AM, Maxim Solodovnik wrote:
> >
> > No votes after 3 days :(
> > Is there anything wrong with the RC?
> >
> >> On Thu, 27 Dec 2018 at 05:20, Bruno P. Kinoshita wrote:
> >>
> >> FWIW I had a simila
26 Dec 2018 21:21:34 +0100, Gilles wrote:
> > Hi.
> >
> > On Wed, 26 Dec 2018 20:41:59 +0700, Maxim Solodovnik wrote:
> >> This is a [VOTE] for releasing
> >> Apache Commons collections 4.3
> >>
> >> Tag name:
> >> collections-
This is a [VOTE] for releasing
Apache Commons collections 4.3
Tag name:
collections-4.3-RC2 (signature can be checked from git using 'git tag -v')
RC1 was cancelled due to some release steps were not done
Tag URL:
https://gitbox.apache.org/repos/asf?p=commons-collections.git;a=commit;h=7
> > On Dec 25, 2018, at 8:04 PM, Maxim Solodovnik
> wrote:
> >
> > In both git and svn you need a branch to create tag
> > But since git has local and remote repository, steps can be:
> >
> > 1) create local branch
> > 2) made "release" chang
l "release" changes
On Wed, 26 Dec 2018 at 05:40, Gilles wrote:
> Hi.
>
> On Tue, 25 Dec 2018 22:22:43 +0700, Maxim Solodovnik wrote:
> > Hello Gilles,
> >
> > Actually if release is made based on git it is not necessary to
> > perform commits
>
> ?
>
Hello All,
I will cancel the VOTE due to issues found in this RC
Will try to create RC2 ASAP
Thanks for your help!
On Wed, 26 Dec 2018 at 05:40, Gilles wrote:
> Hi.
>
> On Tue, 25 Dec 2018 22:22:43 +0700, Maxim Solodovnik wrote:
> > Hello Gilles,
> >
> > Actually
release
I totally miss these properties :(
Shall I cancel the VOTE and create RC2?
On Tue, 25 Dec 2018 at 07:48, Gilles wrote:
>
> On Tue, 25 Dec 2018 01:15:23 +0100, Gilles wrote:
> > On Mon, 24 Dec 2018 22:11:11 +0700, Maxim Solodovnik wrote:
> >> Hello All,
> >>
n Fri, 21 Dec 2018 at 01:17, Gary Gregory wrote:
>
> Hi all, I am unable to review for at least 3 or 4 days. I am on the road
> and my laptop just died...
>
> Gary
>
> On Wed, Dec 19, 2018, 08:41 Maxim Solodovnik
> > commons-collections4-4.3-src.zip.sha256This is a
see no issues need to be noted
[1]
https://github.com/apache/commons-collections/compare/commons-collections-4.2-RC1...collections-4.3-RC1
On Thu, 20 Dec 2018 at 00:29, sebb wrote:
>
> On Wed, 19 Dec 2018 at 16:09, Maxim Solodovnik wrote:
> >
> > Thanks for checking Gilles,
>
git;a=blob;f=doc/release/release.howto.txt
On Wed, 19 Dec 2018 at 21:19, Rob Tompkins wrote:
>
>
>
> > On Dec 19, 2018, at 8:29 AM, Maxim Solodovnik wrote:
> >
> > The build was successful
> > Staging repo is closed
> >
> > Thanks a lot for the help!
ollections" and in "RNG"!]
>
> On Wed, 19 Dec 2018 20:41:15 +0700, Maxim Solodovnik wrote:
> > This is a [VOTE] for releasing
> > Apache Commons collections 4.3
> >
> > Tag name:
> > collections-4.3-RC1 (signature can be checked from git
commons-collections4-4.3-src.zip.sha256This is a [VOTE] for releasing
Apache Commons collections 4.3
Tag name:
collections-4.3-RC1 (signature can be checked from git using 'git tag -v')
Tag URL:
https://gitbox.apache.org/repos/asf?p=commons-collections.git;a=commit;h=5f959fd8e77bf28f6286cfb4
The build was successful
Staging repo is closed
Thanks a lot for the help!
On Wed, 19 Dec 2018 at 08:54, Rob Tompkins wrote:
>
>
> > On Dec 18, 2018, at 7:51 PM, Maxim Solodovnik
> wrote:
> >
> > Is it possible staging-distribution fails because there is already
Is it possible staging-distribution fails because there is already 4.2-RC1/
at dist-dev?
On Wed, 19 Dec 2018 at 07:32, Maxim Solodovnik wrote:
> Now I'm getting:
>
> [ERROR] Failed to execute goal
> org.apache.commons:commons-release-plugin:1.3:stage-distributions
> (sta
cessfull
On Wed, 19 Dec 2018 at 07:16, Gilles wrote:
> On Wed, 19 Dec 2018 06:59:26 +0700, Maxim Solodovnik wrote:
> > I found it here:
> >
> >
> https://gitbox.apache.org/repos/asf?p=commons-rng.git;a=blob;f=doc/release/release.howto.txt#l300
> >
> > Shall I dro
I found it here:
https://gitbox.apache.org/repos/asf?p=commons-rng.git;a=blob;f=doc/release/release.howto.txt#l300
Shall I drop current staging repo and restart the build without this
profile?
On Wed, 19 Dec 2018 at 06:57, sebb wrote:
> On Tue, 18 Dec 2018 at 23:37, Maxim Solodovnik
>
the same applies to Nexus.
>
> I have added you as a Commons committer.
>
> On Tue, 18 Dec 2018 at 16:24, Maxim Solodovnik
> wrote:
> >
> > Thanks a lot for the help :)
> > Glad to check the release process ;)
> >
> > On Tue, 18 Dec 2018 at 23:19, Gilles
Thanks a lot for the help :)
Glad to check the release process ;)
On Tue, 18 Dec 2018 at 23:19, Gilles wrote:
> Hello.
>
> On Tue, 18 Dec 2018 23:05:12 +0700, Maxim Solodovnik wrote:
> > Thanks a lot
> >
> > Unfortunately the next error is: Failed to deploy artifacts:
ciate any help/hint :)
On Tue, 18 Dec 2018 at 22:54, Gilles wrote:
> On Tue, 18 Dec 2018 22:03:04 +0700, Maxim Solodovnik wrote:
> > It seems I'm unable to commit to SVN:
> >
> > URL: https://dist.apache.org/repos/dist/release/commons
> >
> > SendingKE
the
server
svn: E175013: Access to
'/repos/dist/!svn/txr/31592-qod/release/commons/KEYS' forbidden
Can someone help me with access rights?
On Tue, 18 Dec 2018 at 21:22, Maxim Solodovnik wrote:
> Moving conversation to dev@ list
>
> I was able to create branch using gitbox rem
Moving conversation to dev@ list
I was able to create branch using gitbox remote
Will proceed,
Thanks for the tip
On Tue, 18 Dec 2018 at 21:14, Gilles wrote:
> Hi.
>
> On Tue, 18 Dec 2018 20:54:22 +0700, Maxim Solodovnik wrote:
> > Hello Gilles,
> >
> > I read do
76 matches
Mail list logo
