Re: Defect in commons-compress 1.26.1 null handling of ZipArchiveOutputStream:setEncoding(String)

2024-04-28 Thread Gary Gregory
On Wed, Apr 24, 2024 at 12:34 PM Jeffrey Adamson
 wrote:
>
> I was able to create issue COMPRESS-677 with these details. I did not see
> any similar existing issues. Hopefully I followed the relevant
> processes correctly.

You did and thank you.

Gary

>
> On Wed, Apr 24, 2024 at 11:31 AM Jeffrey Adamson <
> jeffrey.adam...@hcl-software.com> wrote:
>
> > The following code prints out "Success" with commons-compress 1.26.0 and
> > earlier and a stack trace with 1.26.1.
> >
> > The javadocs specify that passing a null parameter value to.
> > ZipArchiveOutputStream.html#setEncoding(java.lang.String)
> > 
> > should use the platform's default encoding and not result in an
> > IllegalArgumentException
> >
> >
> >> import java.io.File;
> >> import org.apache.commons.compress.archivers.zip.ZipArchiveOutputStream;
> >>
> >> public class Main {
> >>
> >> public static void main(String[] args)
> >> throws Exception {
> >> ZipArchiveOutputStream zaos = new ZipArchiveOutputStream(new
> >> File("/dev/null"));
> >> zaos.setEncoding((String)null);
> >> System.out.println("Success");
> >> }
> >> }
> >>
> >
> > The 1.26.1 stack trace is:
> >
> > Exception in thread "main" java.lang.IllegalArgumentException: Null
> >> charset name
> >> at java.base/java.nio.charset.Charset.lookup(Charset.java:455)
> >> at java.base/java.nio.charset.Charset.forName(Charset.java:526)
> >> at
> >> org.apache.commons.compress.archivers.zip.ZipArchiveOutputStream.setEncoding(ZipArchiveOutputStream.java:1340)
> >> at Main.main(Test:11)
> >>
> >
> >
> > How can one go about filing a bug report for this to be fixed.
> >
> > --
> > Jeff A.
> >
>
>
> --
> Jeff A.

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



[ANNOUNCE] Apache Commons Codec 1.17.0

2024-04-27 Thread Gary Gregory
The Apache Commons Team is pleased to announce Apache Commons Codec 1.17.0.

The Apache Commons Codec component contains encoder and decoders for
various formats such as Base16, Base32, Base64, digest, and
Hexadecimal. In addition to these widely used encoders and decoders,
the codec package also maintains a collection of phonetic encoding
utilities.

Feature and fix release. Requires a minimum of Java 8.

For complete information on Apache Commons Codec, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons Codec website:

https://commons.apache.org/proper/commons-codec/

Download page: 
https://commons.apache.org/proper/commons-codec/download_codec.cgi

Gary Gregory
- Apache Commons Team

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



Re: [NET] 451-Error during read from data connection

2024-04-23 Thread Gary Gregory
Hello Marcin,

What version are you using? Make sure yoy test with the current version
3.10.0. Without a reproducible integration test, we don't have anything to
debug. If you can create a PR with a smallest reproducible test case,
that would be grea.  You can use Docker if it can't all be done in Java.

Gary

On Tue, Apr 23, 2024, 5:57 AM Marcin Kudla  wrote:

> Hi
>
> I used Apache Commons Net for long time without problems, but recently I
> get error from one of us server when we try to upload files over ftps.
>
> Error: 451-Error during read from data connection
> 451-Transfer aborted
> 451 0.233 seconds (measured here), 68.53 Kbytes per second
>
> This error occurs always on specific files, other files upload without
> problems.
>
> Here is some example of my code:
>
> FTPSClient client = new FTPSClient();
> client.setAuthValue("TLS");
> client.setControlEncoding("UTF-8");
> client.connect("host", "port");
> client.login("user", "passw");
> client.setKeepAlive(true);
> client.enterLocalPassiveMode();
> client.execPBSZ(0);
> client.execPROT("P");
> client.setFileType(FTP.BINARY_FILE_TYPE);
>
> client.storeFile(remotePath, inputStream)
>
> Server is Pure-FTPd, I tried set some buffers values for client but nothing
> help.
>
> Do you have any suggestions as to what could be the problem?
>
> Regards,
>
> Marcin Kudla
>


[ANNOUNCE] Apache Commons Imaging 1.0.0-alpha5

2024-04-18 Thread Gary Gregory
The Apache Commons Imaging team is pleased to announce the release of
Apache Commons Imaging 1.0.0-alpha5.

Apache Commons Imaging (previously Sanselan) is a pure-Java image library.

The 1.0.0-alpha5 release requires Java 8.

Historical list of changes:
https://commons.apache.org/proper/commons-imaging//changes-report.html

For complete information on Apache Commons Imaging, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons Imaging website:

https://commons.apache.org/proper/commons-imaging/

Download page: 
https://commons.apache.org/proper/commons-imaging//download_text.cgi

Gary Gregory
- Apache Commons Team

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



[ANNOUNCE] Apache Commons CLI Version 1.7.0

2024-04-17 Thread Gary Gregory
The Apache Commons team is pleased to announce Apache Commons CLI Version 1.7.0.

Commons CLI provides a simple API for working with the command line
arguments and options.

Historical list of changes:
https://commons.apache.org/proper/commons-cli/changes-report.html

For complete information on Apache Commons CLI, including instructions
on how to submit bug reports, patches, or suggestions for improvement,
see the Apache Commons CLI website:

https://commons.apache.org/proper/commons-cli/

Download page: https://commons.apache.org/proper/commons-cli/download_cli.cgi

Gary Gregory
- The Apache Commons Team

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



[ANNOUNCE] Apache Commons Text Version 1.12.0

2024-04-17 Thread Gary Gregory
The Apache Commons team is pleased to announce Apache Commons Text
Version 1.12.0.

Apache Commons Text is a set of utility functions and reusable
components for the purpose of processing and manipulating text that
should be of use in a Java environment.

Release 1.12.0. Requires Java 8 or above.

Historical list of changes:
https://commons.apache.org/proper/commons-text/changes-report.html

For complete information on Apache Commons Text, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons Text website:

https://commons.apache.org/proper/commons-text

Download page: https://commons.apache.org/proper/commons-text/download_text.cgi

Gary Gregory
- Apache Commons Team

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



Re: [CONFIGURATION] INIConfiguration with empty section key not supported

2024-04-15 Thread Gary Gregory
Hello Thomas,

You might want to look at the unit tests to see if there are any
expectations regarding empty section names. I don't know off the top of my
head.

Gary

On Mon, Apr 15, 2024, 11:41 AM Steiner Thomas
 wrote:

> Hi,
>
> should it possible to parse an ini-File with an empty section key with
> commons-configuration2 2.10.1?
>
> Or is there any intended purpose why the following example doesn't work:
> INIConfiguration iniConfiguration = new INIConfiguration();
> try (FileReader fileReader = new FileReader(file)) {
>   iniConfiguration.read(fileReader);
> } catch (ConfigurationException | IOException e) {
>   e.printStackTrace();
> }
> SubnodeConfiguration subSection = iniConfiguration.getSection("");
> String nextKey = subSection.getKeys().next();
> assertNotNull(nextKey);
> assertEquals("property", nextKey);
> Object nextValue = subSection.getProperty(nextKey);
> assertNotNull(nextValue); // FIXME: value is null
> assertEquals("property1", nextValue);
>
> emptySection.ini:
>   []
>   property = "property1"
>
> The value is null due to the keyBuffer's length in the
> DefaultConfigurationKey is 0 and the endIndex is also 0 so the
> KeyIterator's hasNext() is false.
>
> Sections with a space (' ') are parsed as expected:
> INIConfiguration iniConfiguration = new INIConfiguration();
> try (FileReader fileReader = new FileReader(file)) {
>   iniConfiguration.read(fileReader);
> } catch (ConfigurationException | IOException e) {
>   e.printStackTrace();
> }
> SubnodeConfiguration subSection = iniConfiguration.getSection(" ");
> String nextKey = subSection.getKeys().next();
> assertNotNull(nextKey);
> assertEquals("property", nextKey);
> Object nextValue = subSection.getProperty(nextKey);
> assertNotNull(nextValue);
> assertEquals("property1", nextValue);
>
> spaceSection.ini:
>   [ ]
>   property = "property1"
>
> Best regards,
> Thomas Steiner
>
>
> 
> Please note the information on data protection at
> https://www.engelglobal.com/dataprotection.
>
>
> 
>
> Important Notice:
> This electronic transmission (including any attachments) is intended
> solely for the use and information
> of the addressee(s). It may contain confidential or legally privileged
> information. Any unauthorized use
> or disclosure of this message is strictly prohibited.If you are not the
> intended recipient, please notify
> the sender immediately and delete the message and its attachments.
> The sender does not guarantee the integrity of this transmission and shall
> therefore never be liable if
> the message is altered or falsified nor for any virus, interception or
> damage to your system.
>


[ANNOUNCE] Apache Commons IO 2.16.1

2024-04-09 Thread Gary Gregory
The Apache Commons team is pleased to announce Apache Commons IO 2.16.1.

The Apache Commons IO library contains utility classes, stream
implementations, file filters,
file comparators, endian transformation classes, and much more.

Java 8 is required.

Fixed Bugs
--

o  Reimplement FileSystemUtils using NIO. Thanks to Gary Gregory.
o IO-851:  FileSystemUtils no longer throws IllegalStateException.
Thanks to Sebb, Gary Gregory.
o  Avoid possible NullPointerException in
FileUtils.listAccumulate(File, IOFileFilter, IOFileFilter,
FileVisitOption...). Thanks to Gary Gregory.
o IO-853:  BoundedInputStream.reset() not updating count. Thanks to
Mike Drob, Gary Gregory.
o  ThresholdingOutputStream: a negative threshold should
behave like a zero threshold and trigger the event on the first write
#609. Thanks to rproserpio, Gary Gregory.

Changes
---

o  Bump commons.bytebuddy.version from 1.14.12 to 1.14.13
#605. Thanks to Gary Gregory.
o  Bump org.apache.commons:commons-parent from 67 to 69 #608.
Thanks to Gary Gregory, Dependabot.


Commons IO 2.7 and up requires Java 8 or above.
Commons IO 2.6 requires Java 7 or above.
Commons IO 2.3 through 2.5 requires Java 6 or above.
Commons IO 2.2 requires Java 5 or above.
Commons IO 1.4 requires Java 1.3 or above.

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



Re: [commons-email] Upgrade to java 17 and jakarta mail

2024-04-04 Thread Gary Gregory
I ran into some issues with the multi module aspect of the build
unfortunately. It's on my list of components to work on.

Gary

On Thu, Apr 4, 2024, 5:08 AM Raffaele Gambelli
 wrote:

> Hi Gary, do you have any news about commons-email release?
>
> Thanks
>
> Cordiali saluti / Best regards,
>
> Raffaele Gambelli
> Senior Java Developer
> E  raffaele.gambe...@cegeka.com<mailto:raffaele.gambe...@cegeka.com>
>
> [CEGEKA]Via Ettore Cristoni, 84
> IT-40033 Bologna (IT), Italy
> T +39 02 2544271
> WWW.CEGEKA.COM<https://www.cegeka.com>
>
> [http://signature.cegeka.com/SignatureRO/bannerRO.jpg]
>
>
> 
> From: Gary Gregory 
> Sent: Monday, March 18, 2024 7:11 PM
> To: Commons Users List 
> Subject: Re: [commons-email] Upgrade to java 17 and jakarta mail
>
> I had some trouble with release candidate, I'll try to work out the kinks
> over the next week or so.
>
> Gary
>
> On Mon, Mar 18, 2024, 1:19 PM Raffaele Gambelli 
> wrote:
>
> > Hi,
> >
> > are there any news about the release of commons-email?
> >
> > -Messaggio originale-
> > Da: Raffaele Gambelli
> > Inviato: lunedì 29 gennaio 2024 17:12
> > A: Commons Users List 
> > Oggetto: R: [commons-email] Upgrade to java 17 and jakarta mail
> >
> > Hi Gary,
> >
> > my usage of commons-email is only about the sending of messages, simply
> > plain or html ones, with or without attachments.
> >
> > All my tests were ok.
> >
> > Here follows classes that I use in my project:
> >
> > import org.apache.commons.mail2.core.EmailConstants;
> > import org.apache.commons.mail2.core.EmailException;
> > import org.apache.commons.mail2.jakarta.DefaultAuthenticator;
> > import org.apache.commons.mail2.jakarta.Email;
> > import org.apache.commons.mail2.jakarta.EmailAttachment;
> > import org.apache.commons.mail2.jakarta.ImageHtmlEmail;
> > import org.apache.commons.mail2.jakarta.MultiPartEmail;
> > import org.apache.commons.mail2.jakarta.SimpleEmail;
> > import org.apache.commons.mail2.jakarta.resolver.DataSourceUrlResolver;
> >
> > Best regards
> >
> > -Messaggio originale-
> > Da: Raffaele Gambelli 
> > Inviato: lunedì 22 gennaio 2024 08:31
> > A: Commons Users List 
> > Oggetto: R: [commons-email] Upgrade to java 17 and jakarta mail
> >
> > Hi Gary,
> >
> > I've started adopting 2.0.0-M1, I'll test it within my application and
> > I'll let you know.
> >
> > Thanks
> >
> > -Messaggio originale-
> > Da: Gary Gregory 
> > Inviato: sabato 20 gennaio 2024 21:52
> > A: Commons Users List 
> > Oggetto: Re: [commons-email] Upgrade to java 17 and jakarta mail
> >
> > Raffael,
> >
> > I'm waiting to hear back ;-)
> >
> > Gary
> >
> > On Thu, Jan 18, 2024 at 8:24 AM Gary Gregory 
> > wrote:
> > >
> > > Raffael,
> > >
> > > I can cut 2.0.0-M1 anytime (mod our 72-hour review process). But I
> > > would prefer to have a use case like yours so we can avoid having to
> > > release a 2.0.0-M2 immediately to fix what you find in M1.
> > >
> > > Gary
> > >
> > > On Thu, Jan 18, 2024 at 8:19 AM Raffaele Gambelli
> > >  wrote:
> > > >
> > > > Really thanks Gary,
> > > >
> > > > I have to plan my work, so if you can, could you be more specific
> when
> > you say "soon"? Is it a question of weeks or months?
> > > >
> > > > I need an answer to choose if refactor the code using commons-email
> > without commons-email.
> > > >
> > > > Thank you again
> > > >
> > > > -Messaggio originale-
> > > > Da: Gary Gregory 
> > > > Inviato: giovedì 18 gennaio 2024 14:13
> > > > A: Commons Users List 
> > > > Oggetto: Re: [commons-email] Upgrade to java 17 and jakarta mail
> > > >
> > > > Hello Raffael,
> > > >
> > > > We have a release 2.0.0 in the works to support Jakarta for which a
> > release candidate for milestone release 1 should be available "soon".
> > > > In the meantime, the best I can offer is to point you to our snapshot
> > build for version 2.0.0-M1-SNAPSHOT in
> > https://repository.apache.org/content/repositories/snapshots/ using the
> > artifact IDs:
> > > >
> > > > commons-email2-bom
> > > > commons-email2-core
> > > > commons-email2-jakarta
> > 

[ANNOUNCE] Apache Commons Collections 4.5.0-M1

2024-04-02 Thread Gary Gregory
The Apache Commons team is pleased to announce Apache Commons
Collections 4.5.0-M1.

The Apache Commons Collections package contains types that extend and
augment the Java Collections Framework.

This milestone release requires Java 8 and adds the package
`org.apache.commons.collections4.bloomfilter` for review. This release
is the first milestone release toward 4.5.0. There may or may not be
additional milestone releases before 4.5.0, so chip in and review! :-)

For complete information on Apache Commons Collections, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons Collections website:

https://commons.apache.org/proper/commons-collections/

Download page: 
https://commons.apache.org/proper/commons-collections/download_collections.cgi

Gary Gregory
Apache Commons Team

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



[ANNOUNCE] Apache Commons Imaging 1.0.0-alpha4

2024-04-02 Thread Gary Gregory
The Apache Commons Imaging team is pleased to announce the release of
Apache Commons Imaging 1.0.0-alpha4.

Apache Commons Imaging (previously Sanselan) is a pure Java image library.

The 1.0.0-alpha4 release requires Java 8.

Historical list of changes:
https://commons.apache.org/proper/commons-imaging//changes-report.html

For complete information on Apache Commons Imaging, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons Imaging website:

https://commons.apache.org/proper/commons-imaging/

Download page: 
https://commons.apache.org/proper/commons-imaging//download_text.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



Re: Multiple errors while unpacking v1.26.1

2024-04-02 Thread Gary Gregory
I agree with Bindul's analysis.

Gary

On Tue, Apr 2, 2024, 4:01 AM Bindul Bhowmik  wrote:

> Sahil,
>
> It looks like whatever tool you are using is trying to recursively unpack
> all files within the archive. I don't think you mean to do that, do you?
> The commons compress test source tree contains bad archives for its own
> unit tests and any decompression tool should fail on those - like is
> happening in your case. In fact, if you are able to explode the archives in
> the test resources folder, your unit tests will fail if you try to build
> the code.
>
> Bindul
>
> On Tue, Apr 2, 2024 at 1:51 AM Sahil Sharma D
>  wrote:
>
> > Hi team,
> >
> > While unpacking the v1.26.1, we are getting below error:
> >
> > "unpackingFailures": {
> > "corruptedArchives": {
> >   "commons-compress-rel-commons-compress-1.26.1.tar.gz
> >
> >  commons-compress-rel-commons-compress-1.26.1.tar
> >
> >
> /commons-compress-rel-commons-compress-1.26.1/src/test/resources/bla-stored-dd.zip":
> > "ERROR:
> >
> commons-compress-rel-commons-compress-1.26.1/src/test/resources/bla-stored-dd.zip
> > Can not open the file as archive  ",
> >   "commons-compress-rel-commons-compress-1.26.1.tar.gz
> >
> >  commons-compress-rel-commons-compress-1.26.1.tar
> >
> >
> /commons-compress-rel-commons-compress-1.26.1/src/test/resources/bla-stored-dd-sizes-differ.zip":
> > " ERRORS: Unexpected end of archive  ",
> >   "commons-compress-rel-commons-compress-1.26.1.tar.gz
> >
> >  commons-compress-rel-commons-compress-1.26.1.tar
> >
> >
> /commons-compress-rel-commons-compress-1.26.1/src/test/resources/COMPRESS-228.zip":
> > " ERRORS: Headers Error  ",
> >   "commons-compress-rel-commons-compress-1.26.1.tar.gz
> >
> >  commons-compress-rel-commons-compress-1.26.1.tar
> >
> >
> /commons-compress-rel-commons-compress-1.26.1/src/test/resources/bla-stored-dd-nosig.zip":
> > " ERRORS: Unexpected end of archive  ",
> >   "commons-compress-rel-commons-compress-1.26.1.tar.gz
> >
> >  commons-compress-rel-commons-compress-1.26.1.tar
> >
> >
> /commons-compress-rel-commons-compress-1.26.1/src/test/resources/COMPRESS-544_truncated_in_padding-fail.tar":
> > "/opt/eppki/mss/bin/tar: Unexpected EOF in archive
> /opt/eppki/mss/bin/tar:
> > Unexpected EOF in archive /opt/eppki/mss/bin/tar: Error is not
> recoverable:
> > exiting now ",
> >   "commons-compress-rel-commons-compress-1.26.1.tar.gz
> >
> >  commons-compress-rel-commons-compress-1.26.1.tar
> >
> >
> /commons-compress-rel-commons-compress-1.26.1/src/test/resources/COMPRESS-546.zip":
> > "Unexpected end of archive  ERROR: Data Error",
> >   "commons-compress-rel-commons-compress-1.26.1.tar.gz
> >
> >  commons-compress-rel-commons-compress-1.26.1.tar
> >
> >
> /commons-compress-rel-commons-compress-1.26.1/src/test/resources/COMPRESS-548.zip":
> > "Unexpected end of archive  ERROR: Data Error",
> >   "commons-compress-rel-commons-compress-1.26.1.tar.gz
> >
> >  commons-compress-rel-commons-compress-1.26.1.tar
> >
> >
> /commons-compress-rel-commons-compress-1.26.1/src/test/resources/COMPRESS-544_truncated_in_content-fail.tar":
> > "/opt/eppki/mss/bin/tar: Unexpected EOF in archive
> /opt/eppki/mss/bin/tar:
> > Unexpected EOF in archive /opt/eppki/mss/bin/tar: Error is not
> recoverable:
> > exiting now ",
> >   "commons-compress-rel-commons-compress-1.26.1.tar.gz
> >
> >  commons-compress-rel-commons-compress-1.26.1.tar
> >
> >
> /commons-compress-rel-commons-compress-1.26.1/src/test/resources/moby.zip":
> > "Unsupported Method",
> >   "commons-compress-rel-commons-compress-1.26.1.tar.gz
> >
> >  commons-compress-rel-commons-compress-1.26.1.tar
> >
> >
> /commons-compress-rel-commons-compress-1.26.1/src/test/resources/bla-stored-dd-contradicts-actualsize.zip":
> > " ERRORS: Unexpected end of archive  ",
> >   "commons-compress-rel-commons-compress-1.26.1.tar.gz
> >
> >  commons-compress-rel-commons-compress-1.26.1.tar
> >
> >
> /commons-compress-rel-commons-compress-1.26.1/src/test/resources/COMPRESS-529-fail.tar":
> > "/opt/eppki/mss/bin/tar: Unexpected EOF in archive
> /opt/eppki/mss/bin/tar:
> > Unexpected EOF in archive /opt/eppki/mss/bin/tar: Error is not
> recoverable:
> > exiting now ",
> >   "commons-compress-rel-commons-compress-1.26.1.tar.gz
> >
> >  commons-compress-rel-commons-compress-1.26.1.tar
> >
> >
> /commons-compress-rel-commons-compress-1.26.1/src/test/resources/COMPRESS-356.tar":
> > "/opt/eppki/mss/bin/tar: This does not look like a tar archive
> > /opt/eppki/mss/bin/tar: Skipping to next header /opt/eppki/mss/bin/tar:
> > Exiting with failure status due to previous errors ",
> >   "commons-compress-rel-commons-compress-1.26.1.tar.gz
> >
> >  commons-compress-rel-commons-compress-1.26.1.tar
> >
> >
> /commons-compress-rel-commons-compress-1.26.1/src/test/resources/COMPRESS-530-fail.tar":
> > "/opt/eppki/mss/bin/tar: This does not look like a tar archive
> > /opt/eppki/mss/bin/tar: Skipping to next header /opt/eppki/mss/bin/tar:
> 

Re: [commons-cli] How to handle deprecating options?

2024-03-22 Thread Gary Gregory
That sounds like a great feature to add to Commons CLI.

Gary

On Fri, Mar 22, 2024, 10:25 AM Eric Pugh 
wrote:

> We use commons-cli in Apache Solr, and we’re currently trying to
> standardize our mash-mash of command line arguments.   How do people handle
> deprecating an option in the Builder and introducing new ones?  Is there
> any techniques/features of commons-cli that support this use case?
>
> If you are curious, here is the current state of the work:
> https://github.com/apache/solr/pull/1768
>
> Eric
>
> ___
> Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 |
> http://www.opensourceconnections.com <
> http://www.opensourceconnections.com/> | My Free/Busy <
> http://tinyurl.com/eric-cal>
> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
> https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw>
>
> This e-mail and all contents, including attachments, is considered to be
> Company Confidential unless explicitly stated otherwise, regardless of
> whether attachments are marked as such.
>
>


Re: RE: Re: release of commons-imaging

2024-03-22 Thread Gary Gregory
I'll see about creating a release candidate over the next few days.

Gary

On Fri, Mar 22, 2024, 6:07 AM William Borg Barthet <
william.borgbart...@bloomreach.com> wrote:

> Sorry to be a pain about this, is there any timeline for tagging/releasing
> a version of commons-imaging?
>
> Thanks again for your support.
>
> Regards,
>
> William
>
> On 2024/03/06 14:50:51 William Borg Barthet wrote:
> > Thanks for your replies.
> >
> > I am actually waiting on the WebP support. I found a PR and tested
> against
> > it and it seems to work for my purposes. I cannot really make use of a
> > SNAPSHOT, so any sort of tagged release, short of a 1.0 release would
> > suffice if it contained the WebP support.
> >
> > Thanks and regards
> >
> > William
> >
> > On 2024/02/28 15:43:06 Gary Gregory wrote:
> > > Yes: M is for milestone.
> > >
> > > Gary
> > >
> > > On Wed, Feb 28, 2024, 10:40 AM Bruno Kinoshita 
> > > wrote:
> > >
> > > > >
> > > > > Why not continue with experimental releases using the same scheme
> > > > > (i.e. "alpha", then "beta") with the agreed on semantics (that
> > > > > compatibility
> > > > > can be broken)?
> > > >
> > > >
> > > > Sounds good to me too, at least users wouldn't expect any difference
> > seeing
> > > > a new alphaN+1 announced. But not sure if there won't be any
> differences
> > > > with a milestone release (M is for milestone, right?)
> > > >
> > > > Cheers
> > > >
> > > > On Wed, 28 Feb 2024 at 16:11, Gilles Sadowski 
> > > > wrote:
> > > >
> > > > > Le mer. 28 févr. 2024 à 16:00, Bruno Kinoshita
> > > > >  a écrit :
> > > > > >
> > > > > > Hi Gary,
> > > > > >
> > > > > > What would be the main difference between the alpha and M1
> releases?
> > > > > >
> > > > > > I am not 100% confident that we have the public and protected API
> > > > right,
> > > > > > > specifically we might have too much public and protected. YMMV.
> > > > > >
> > > > > >
> > > > > > Agreed, and I think if we are to release anything, we would need
> > one or
> > > > > > more extra releases before we get everything right for the 1.0.
> But
> > if
> > > > we
> > > > > > can continue breaking backward compatibility (even though we will
> > try
> > > > > that
> > > > > > to only what's necessary to reduce impact to users) with
> M1/M2/M3,
> > the
> > > > > same
> > > > > > way we did with the alpha releases, then I'm +1 for that already.
> > > > >
> > > > > Why not continue with experimental releases using the same scheme
> > > > > (i.e. "alpha", then "beta") with the agreed on semantics (that
> > > > > compatibility
> > > > > can be broken)?
> > > > >
> > > > > > > > [...]
> > > > >
> > > > >
> -
> > > > > To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> > > > > For additional commands, e-mail: user-h...@commons.apache.org
> > > > >
> > > > >
> > > >
> > >
> >
>


[ANNOUNCE] Apache Commons Configuration 2.10.1

2024-03-20 Thread Gary Gregory
Introducing Apache Commons Configuration 2.10.1

The Apache Commons Configuration software library provides a generic
configuration interface that enables an application to read
configuration data from a variety of sources.

Tools to assist in the reading of configuration/preferences files in
various formats; this version requires Java 8.

Minor release with new features and updated dependencies; requires
Java 8 or above.

Changes in this version include:

Fixed Bugs

* CONFIGURATION-839: java.lang.module.FindException: Module
servlet.api not found. Thanks to Bob Marinier, Gary Gregory.

* CONFIGURATION-840: StackOverflowError adding property in
AbstractListDelimiterHandler.flattenIterator(). Thanks to Bob
Marinier, Gary Gregory.

* CONFIGURATION-841: StackOverflowError calling
ListDelimiterHandler.flatten(Object, int) with a cyclical object tree.
Thanks to Gary Gregory.

Changes

* Bump jackson-databind from 2.16.1 to 2.17.0
#378. Thanks to Dependabot.
* Bump log4j.version from 2.23.0 to 2.23.1 #379.
Thanks to Dependabot.
* Bump spring.version from 5.3.32 to 5.3.33 #380.
Thanks to Dependabot, Gary Gregory.

Historical list of changes:
https://commons.apache.org/proper/commons-configuration/changes-report.html

For complete information on Apache Commons Configuration, including
instructions on how to submit bug reports,
patches, or suggestions for improvement, see the Apache Apache Commons
Configuration website:

https://commons.apache.org/proper/commons-configuration/

Download it from
https://commons.apache.org/proper/commons-configuration//download_configuration.cgi

Gary Gregory
Apache Commons

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



Re: commons-compress-1.26.1 false positive on detecting archive

2024-03-19 Thread Gary Gregory
Hello Gren,

Feel free to provide a PR on GitHub (with a unit test) so we can see
clearly what you suggest.

TY!
Gary

On Tue, Mar 19, 2024, 7:46 AM Gren Elliot 
wrote:

> Hi,
>
>
>
> I’m finding that commons-compress-1.26.1 is recognising a utf-16 text file
> as a tar archive – unlike the previous version
>
>
>
> This is the code that changed in that release in ArchiveStreamFactory - 
> *public
> static String detect(final InputStream in) throws ArchiveException {*
>
> that differs in detection:
>
>
>
> if (signatureLength >= *TAR_HEADER_SIZE*) {
> try (TarArchiveInputStream inputStream = new TarArchiveInputStream(new
> ByteArrayInputStream(tarHeader))) {
>
>
> *// COMPRESS-191 - verify the header checksum // COMPRESS-644 - do
> not allow zero byte file entries *TarArchiveEntry entry =
> inputStream.getNextEntry();
>
> *// try to find the first non-directory entry within the first 10 entries.
> *int count = 0;
> while (entry != null && entry.isDirectory() && count++ <
> *TAR_TEST_ENTRY_COUNT*) {
> entry = inputStream.getNextEntry();
> }
> if (entry != null && entry.isCheckSumOK() && !entry.isDirectory()
> && entry.getSize() > 0 || count > 0) {
> return *TAR*;
> }
> } catch (final Exception e) {
>
> *// NOPMD NOSONAR // can generate IllegalArgumentException as well
> as IOException auto-detection, simply not a TAR ignored *}
> }
>
>
>
> I feel this is being too lenient.  For instance at the last “if”
> statement, for the test file, entry is null and count=1.  The code suggests
> it is looking for the first non-directory entry.  It hasn’t found a
> non-directory entry in our case.
>
>
>
> For instance, the earlier code at least checked that the checksum was OK
> for the one entry it checked (it isn’t for our test file…)
>
>
>
> Regards,
>
> Gren
>
>
>
>
> Gren Elliot m: +44 7590 571125 www.mimecast.com
> 
> Senior Software Engineer p: Address click here
> 
>
> [image: https://www.mimecast.com]
> 
>  *Work
> Protected.™*
>
>
> *Disclaimer*
> The information contained in this communication from *
> gell...@mimecast.com  * sent at 2024-03-19 11:45:54
> is confidential and may be legally privileged. It is intended solely for
> use by * user@commons.apache.org  * and others
> authorized to receive it. If you are not * user@commons.apache.org
>  * you are hereby notified that any disclosure,
> copying, distribution or taking action in reliance of the contents of this
> information is strictly prohibited and may be unlawful.
>
> Visit our preference center to change how often you hear from us: Preference
> Center
> .
>
>
>
>
>


Re: [commons-email] Upgrade to java 17 and jakarta mail

2024-03-18 Thread Gary Gregory
I had some trouble with release candidate, I'll try to work out the kinks
over the next week or so.

Gary

On Mon, Mar 18, 2024, 1:19 PM Raffaele Gambelli 
wrote:

> Hi,
>
> are there any news about the release of commons-email?
>
> -Messaggio originale-
> Da: Raffaele Gambelli
> Inviato: lunedì 29 gennaio 2024 17:12
> A: Commons Users List 
> Oggetto: R: [commons-email] Upgrade to java 17 and jakarta mail
>
> Hi Gary,
>
> my usage of commons-email is only about the sending of messages, simply
> plain or html ones, with or without attachments.
>
> All my tests were ok.
>
> Here follows classes that I use in my project:
>
> import org.apache.commons.mail2.core.EmailConstants;
> import org.apache.commons.mail2.core.EmailException;
> import org.apache.commons.mail2.jakarta.DefaultAuthenticator;
> import org.apache.commons.mail2.jakarta.Email;
> import org.apache.commons.mail2.jakarta.EmailAttachment;
> import org.apache.commons.mail2.jakarta.ImageHtmlEmail;
> import org.apache.commons.mail2.jakarta.MultiPartEmail;
> import org.apache.commons.mail2.jakarta.SimpleEmail;
> import org.apache.commons.mail2.jakarta.resolver.DataSourceUrlResolver;
>
> Best regards
>
> -Messaggio originale-
> Da: Raffaele Gambelli 
> Inviato: lunedì 22 gennaio 2024 08:31
> A: Commons Users List 
> Oggetto: R: [commons-email] Upgrade to java 17 and jakarta mail
>
> Hi Gary,
>
> I've started adopting 2.0.0-M1, I'll test it within my application and
> I'll let you know.
>
> Thanks
>
> -Messaggio originale-
> Da: Gary Gregory 
> Inviato: sabato 20 gennaio 2024 21:52
> A: Commons Users List 
> Oggetto: Re: [commons-email] Upgrade to java 17 and jakarta mail
>
> Raffael,
>
> I'm waiting to hear back ;-)
>
> Gary
>
> On Thu, Jan 18, 2024 at 8:24 AM Gary Gregory 
> wrote:
> >
> > Raffael,
> >
> > I can cut 2.0.0-M1 anytime (mod our 72-hour review process). But I
> > would prefer to have a use case like yours so we can avoid having to
> > release a 2.0.0-M2 immediately to fix what you find in M1.
> >
> > Gary
> >
> > On Thu, Jan 18, 2024 at 8:19 AM Raffaele Gambelli
> >  wrote:
> > >
> > > Really thanks Gary,
> > >
> > > I have to plan my work, so if you can, could you be more specific when
> you say "soon"? Is it a question of weeks or months?
> > >
> > > I need an answer to choose if refactor the code using commons-email
> without commons-email.
> > >
> > > Thank you again
> > >
> > > -Messaggio originale-
> > > Da: Gary Gregory 
> > > Inviato: giovedì 18 gennaio 2024 14:13
> > > A: Commons Users List 
> > > Oggetto: Re: [commons-email] Upgrade to java 17 and jakarta mail
> > >
> > > Hello Raffael,
> > >
> > > We have a release 2.0.0 in the works to support Jakarta for which a
> release candidate for milestone release 1 should be available "soon".
> > > In the meantime, the best I can offer is to point you to our snapshot
> build for version 2.0.0-M1-SNAPSHOT in
> https://repository.apache.org/content/repositories/snapshots/ using the
> artifact IDs:
> > >
> > > commons-email2-bom
> > > commons-email2-core
> > > commons-email2-jakarta
> > > commons-email2-javax
> > >
> > > Gary
> > >
> > > On Thu, Jan 18, 2024 at 4:37 AM Raffaele Gambelli <
> r.gambe...@westpole.it> wrote:
> > > >
> > > > Hi all,
> > > >
> > > > I'm going to upgrade one springboot application to springboot 3.x,
> until recently it was using commons-email 1.5 but I upgraded to the latest
> 1.6 which I thinked was compatible with jakarta mail but it is not.
> > > >
> > > > I would like to know if you have some information about one next
> release of commons-email which will be fully compatible with jakarta mail
> and if you know when its release date is expected.
> > > >
> > > > Thank you very much
> > > >
> > > > Raffaele
> > > > [https://westpole.it/firma/westpole_cegeka_logo.jpg]
> > > >
> > > > Raffaele Gambelli
> > > > Research & Development
> > > >
> > > > P +390518550576
> > > > M 3371641888
> > > > E r.gambe...@westpole.it
> > > > W https://westpole.webex.com/meet/R.Gambelli
> > > > A Via Ettore Cristoni, 84 - 40033 Casalecchio di Reno
> > > >
> > > > [https://westpole.it/firma/website.png]<https://westpole.it>  [
> https

Re: [math] Add module-info.java

2024-03-14 Thread Gary Gregory
The commons-parent POM automatically creates module-info.java files. A
Commons component should not have to do anything beyond using a recent
version.

Gary

On Thu, Mar 14, 2024, 8:03 PM Gili Tzabari  wrote:

> Hi,
>
> I'd like Commons Math to add module-info.java to all the components. I
> noticed that you are adding a "Automatic-Module" entry in META-INF but
> this isn't enough for jlink (and related tools) to work properly. We
> absolutely need to add module-info.java.
>
> You just need to add a few lines to pom.xml to turn your releases into
> multirelease JAR files and you're done. Here is the code I lifted from
>
> https://medium.com/@ankitagrahari.rkgit/multi-release-functionality-8fc423b6c94e
> :
>
> | java11 compile
>  11
> ${project.basedir}/src/main/java11
>
> true 
>  |
>
> ||
>
> |Gili|
>


[ANNOUNCE] Apache Commons Configuration 2.10.0

2024-03-13 Thread Gary Gregory
The Apache Commons is pleased to announce Apache Commons Configuration 2.10.0.

The Commons Configuration software library provides a generic
configuration interface that enables an application to read
configuration data from a variety of sources and tools to assist in
the reading of configuration/preferences files in various formats

This is a minor release with new features and updated dependencies
that require Java 8.

Historical list of changes:
https://commons.apache.org/proper/commons-configuration/changes
report.html

For complete information on Apache Commons Configuration, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Apache Commons Configuration website:

https://commons.apache.org/proper/commons-configuration/

Download it from
https://commons.apache.org/proper/commons-configuration//download_configuration.cgi

Gary Gregory
Apache Commons Team

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



Re: Processing password protected zipfiles

2024-03-12 Thread Gary Gregory
Hello Sana,

Please see https://commons.apache.org/proper/commons-compress/examples.html

Gary


On Tue, Mar 12, 2024, 5:59 AM Sana Kausar
 wrote:

> Hi Team,
>
> I have a requirement of extracting a zip file and a .7z file which are
> password protected. Does your latest release support extraction from
> password protected zip files. If yes, could you please provide any
> reference on how to achieve it. or else kindly acknowledge.
>
> Thank you
> Sana Kausar
>


Re: [External] - Re: MultivariateNormalMixtureExpectationMaximization only 1 dimension

2024-03-11 Thread Gary Gregory
I'll let someone familiar with that code base opine 

Gary

On Mon, Mar 11, 2024, 2:48 PM Craig Brautigam 
wrote:

> Gary,
> Gary is this something you would agree is an issue?  I don't want to go
> through the effort of putting an official issue out there if it's something
> I'm misunderstanding.  Also I definitely do not have enough math chops to
> change this type of code, I'm simply trying to do a port from matlab to
> java.
>
> -Craig
>
>
> ____
> From: Gary Gregory 
> Sent: Monday, March 11, 2024 12:27 PM
> To: Commons Users List 
> Subject: Re: [External] - Re:
> MultivariateNormalMixtureExpectationMaximization only 1 dimension
>
> [You don't often get email from garydgreg...@gmail.com. Learn why this is
> important at https://aka.ms/LearnAboutSenderIdentification ]
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
> Hi Craig,
>
> In general, the fastest way to address an issue you care about is to
> provide a PR in GitHub, with a unit test 
>
> Gary
>
>
> On Mon, Mar 11, 2024, 2:06 PM Craig Brautigam 
> wrote:
>
> > Just bumping this up...Would it be possible to get a fix for this?
> >
> >
> > Thx!
> >
> >
> > 
> > From: Craig Brautigam 
> > Sent: Thursday, March 7, 2024 2:47 PM
> > To: Commons Users List 
> > Subject: Re: [External] - Re:
> > MultivariateNormalMixtureExpectationMaximization only 1 dimension
> >
> > Alex,
> >
> > Your fix seems to be working however, there is a similar problem in
> > MultivariateNormalMixtureExpectationMaximization.estimate().  The number
> of
> > components must be at least 2.  I think that you should be able to try to
> > estimate with 1 component if you want to.  The matlab function fitgmdist
> > does allow for  1 component, and much of our data does in fact best fit
> to
> > only 1 component.
> >
> > Thoughts on fixing that restriction as well?
> >
> >
> > Thx!
> > Craig
> >
> >
> > 
> > From: Alex Herbert 
> > Sent: Tuesday, March 5, 2024 11:35 AM
> > To: Commons Users List 
> > Subject: [External] - Re:
> MultivariateNormalMixtureExpectationMaximization
> > only 1 dimension
> >
> > [You don't often get email from alex.d.herb...@gmail.com. Learn why this
> > is important at https://aka.ms/LearnAboutSenderIdentification ]
> >
> > CAUTION: This email originated from outside of the organization. Do not
> > click links or open attachments unless you recognize the sender and know
> > the content is safe.
> >
> >
> > I have updated the master branch with a change to allow fitting a mixture
> > with 1-column data.
> >
> > You should be able to pick up the 4.0-SNAPSHOT from the ASF snapshots
> repo
> > if you configure your build to add the snapshot repository (see [1]).
> >
> > Let us know if this works for you. Note that if you only require fitting
> 1
> > column data then you would be able to optimise the implementation as it
> > will no longer require matrix inversion to compute the mixture
> probability
> > distribution. The CM implementation can act as a reference point for your
> > own implementation if desired.
> >
> > Regards,
> >
> > Alex
> >
> > [1]
> >
> >
> https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Fcommons%2Fcommons-math4-legacy%2F4.0-SNAPSHOT%2F=05%7C02%7Ccbrautigam%40icr-team.com%7Ce02533ac3d844a550c6408dc41f8fbd5%7C3d860a84424d44f9ab2bc61a036b4904%7C0%7C0%7C638457784848076395%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=l%2FPU0SIG1EftKyBiM4uV13PExBK%2FfPPThFePB5YGT1s%3D=0
> <
> https://repository.apache.org/content/repositories/snapshots/org/apache/commons/commons-math4-legacy/4.0-SNAPSHOT/
> >
> > <
> >
> https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Fcommons%2Fcommons-math4-legacy%2F4.0-SNAPSHOT%2F=05%7C02%7Ccbrautigam%40icr-team.com%7Ce02533ac3d844a550c6408dc41f8fbd5%7C3d860a84424d44f9ab2bc61a036b4904%7C0%7C0%7C638457784848076395%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=l%2FPU0SIG1EftKyBiM4uV13PExBK%2FfPPThFePB5YGT1s%3D=0
> <
> https://repository.apache.org/conten

Re: [External] - Re: MultivariateNormalMixtureExpectationMaximization only 1 dimension

2024-03-11 Thread Gary Gregory
Hi Craig,

In general, the fastest way to address an issue you care about is to
provide a PR in GitHub, with a unit test 

Gary


On Mon, Mar 11, 2024, 2:06 PM Craig Brautigam 
wrote:

> Just bumping this up...Would it be possible to get a fix for this?
>
>
> Thx!
>
>
> 
> From: Craig Brautigam 
> Sent: Thursday, March 7, 2024 2:47 PM
> To: Commons Users List 
> Subject: Re: [External] - Re:
> MultivariateNormalMixtureExpectationMaximization only 1 dimension
>
> Alex,
>
> Your fix seems to be working however, there is a similar problem in
> MultivariateNormalMixtureExpectationMaximization.estimate().  The number of
> components must be at least 2.  I think that you should be able to try to
> estimate with 1 component if you want to.  The matlab function fitgmdist
> does allow for  1 component, and much of our data does in fact best fit to
> only 1 component.
>
> Thoughts on fixing that restriction as well?
>
>
> Thx!
> Craig
>
>
> 
> From: Alex Herbert 
> Sent: Tuesday, March 5, 2024 11:35 AM
> To: Commons Users List 
> Subject: [External] - Re: MultivariateNormalMixtureExpectationMaximization
> only 1 dimension
>
> [You don't often get email from alex.d.herb...@gmail.com. Learn why this
> is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
> I have updated the master branch with a change to allow fitting a mixture
> with 1-column data.
>
> You should be able to pick up the 4.0-SNAPSHOT from the ASF snapshots repo
> if you configure your build to add the snapshot repository (see [1]).
>
> Let us know if this works for you. Note that if you only require fitting 1
> column data then you would be able to optimise the implementation as it
> will no longer require matrix inversion to compute the mixture probability
> distribution. The CM implementation can act as a reference point for your
> own implementation if desired.
>
> Regards,
>
> Alex
>
> [1]
>
> https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Fcommons%2Fcommons-math4-legacy%2F4.0-SNAPSHOT%2F=05%7C02%7Ccbrautigam%40icr-team.com%7Cbb1041fe6b994488070808dc3d431216%7C3d860a84424d44f9ab2bc61a036b4904%7C0%7C0%7C638452605500058423%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=pV5bELVx3%2FwNJ0LADZVQHv4Mf0UZEWq5GdwTFJTTyP0%3D=0
> <
> https://repository.apache.org/content/repositories/snapshots/org/apache/commons/commons-math4-legacy/4.0-SNAPSHOT/
> >
>
> On Tue, 5 Mar 2024 at 00:06, Alex Herbert 
> wrote:
>
> > Hi,
> >
> > I think this is a bug in the
> > MultivariateNormalMixtureExpectationMaximization class. When I update the
> > code to allow 1 column in the rows it outputs a similar fit to matlab.
> > Here's an example of Matlab:
> >
> > X = [normrnd(0, 1, 100, 1); normrnd(2, 2, 100, 1)]
> > GMModel = fitgmdist(X,2);
> >
> > >> GMModel.mu
> > ans =
> > 0.0737
> > 3.0914
> > >> GMModel.ComponentProportion
> > ans =
> > 0.67500.3250
> > >> GMModel.Sigma
> > ans(:,:,1) =
> > 1.0505
> > ans(:,:,2) =
> > 1.6593
> >
> > I pasted the same X data into a test for
> > MultivariateNormalMixtureExpectationMaximization that had been updated to
> > allow data with a single column and get the following fit:
> >
> > MultivariateNormalMixtureExpectationMaximization fitter
> > = new MultivariateNormalMixtureExpectationMaximization(data);
> >
> > MixtureMultivariateNormalDistribution initialMix
> > = MultivariateNormalMixtureExpectationMaximization.estimate(data, 2);
> > fitter.fit(initialMix);
> > MixtureMultivariateNormalDistribution fittedMix =
> fitter.getFittedModel();
> > List> components =
> > fittedMix.getComponents();
> >
> > for (Pair component :
> components) {
> > final double weight = component.getFirst();
> > final MultivariateNormalDistribution mvn = component.getSecond();
> > final double[] mean = mvn.getMeans();
> > final RealMatrix covMat = mvn.getCovariances();
> > System.out.printf("%s : %s : %s%n", weight, Arrays.toString(mean),
> > covMat.toString());
> > }
> >
> > 0.6420433138817465 : [0.016942587744259194] :
> > Array2DRowRealMatrix{{0.9929681356}}
> > 0.3579566861182536 : [2.9152176347671754] :
> > Array2DRowRealMatrix{{1.8940290549}}
> >
> > The numbers are close enough to indicate that the fit is valid.
> >
> > I think the error has been in assuming that because you require 2
> > components to have a mixture model then you must have 2 columns in the
> > input data. However this is not true. You can fit single dimension data
> > with a mixture of single Gaussians.
> >
> > Is this the functionality that you are expecting?
> >
> > Regards,
> >
> > Alex
> >
> >
> > On Mon, 4 Mar 2024 at 20:48, Craig 

[ANNOUNCE] Apache Commons Compress Version 1.26.1

2024-03-09 Thread Gary Gregory
The Apache Commons team is pleased to announce Apache Commons Compress
Version 1.26.1.

Apache Commons Compress defines an API for working with compression and
archive formats.  These include bzip2, gzip, pack200, LZMA, XZ,
Snappy, traditional Unix Compress, DEFLATE, DEFLATE64, LZ4, Brotli,
Zstandard and ar, cpio, jar, tar, zip, dump, 7z, arj.

Historical list of changes:
https://commons.apache.org/proper/commons-compress/changes-report.html

For complete information on Apache Commons Compress, including
instructions on how to submit bug reports,
patches, or suggestions for improvement, see the Apache Commons
Compress website:

https://commons.apache.org/proper/commons-compress/

Download page: 
https://commons.apache.org/proper/commons-compress/download_io.cgi

Gary Gregory
- Apache Commons Team

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



Re: common-compress 1.26.1 not available on Maven

2024-03-08 Thread Gary Gregory
The vote is in progress and closes tonight. If all goes well, the files
should hit Maven Central later tonight.

Gary


On Fri, Mar 8, 2024, 10:09 AM Sahib Yar 
wrote:

> Hello Commons Team,
>
> I can see on github
> <
> https://github.com/apache/commons-compress/commit/01858bbe4ca4fef85bc0fb85cec83915fd963af2
> >,
> COMPRESS-661  was
> fixed in 1.26.1 but it not yet published on Maven
> 
> yet,
> By when will this be published on Maven ?
>
> Sahib Yar
>
> Tech Lead at securiti
>
> +92 336 6037321 <+92+336+6037321>
>
> sahib@securiti.ai
>
> See Your DataCommand.Center
> <
> https://datacommand.center/?utm_source=email_signature_medium=banner_campaign=datacommandcenter
> >
> <
> https://datacommand.center/?utm_source=email_signature_medium=banner_campaign=datacommandcenter
> >
>
> *Confidentiality Notice:* The content of this message, including any
> attachments, is confidential. The information contained herein is for
> informational purposes only and should not be construed as legal or tax
> advice. It is intended to be read only by the individual or entity to whom
> it is addressed. If you are not the intended recipient, please notify the
> sender by replying to this message and delete the material immediately from
> your system. Any further use, dissemination, distribution or reproduction
> of this message is strictly prohibited.
>
> --
>
>
> See Your DataCommand.Center
> <
> https://datacommand.center/?utm_source=email_signature_medium=banner_campaign=datacommandcenter
> >
>
> <
> https://datacommand.center/?utm_source=email_signature_medium=banner_campaign=datacommandcenter
> >
>
> --
> Confidentiality Notice: The content of this message, including any
> attachments, is confidential. The information contained herein is for
> informational purposes only and should not be construed as legal or tax
> advice. It is intended to be read only by the individual or entity to whom
> it is addressed. If you are not the intended recipient, please notify the
> sender by replying to this message and delete the material immediately
> from
> your system. Any further use, dissemination, distribution or reproduction
> of this message is strictly prohibited.
>


[ANNOUNCE] Apache Commons DBCP 2.12.0

2024-03-04 Thread Gary Gregory
The Apache Commons DBCP team is pleased to announce the release of
Apache Commons DBCP 2.12.0.

Apache Commons DBCP software implements Database Connection Pooling.

This is a minor release, including bug fixes and enhancements. Commons
DBCP requires Java 8 or above.

The list of changes is here:
https://commons.apache.org/proper/commons-dbcp/changes-report.html#a2.12.0

For complete information on Apache Commons DBCP, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons DBCP website:

https://commons.apache.org/proper/commons-dbcp/

Download page: https://commons.apache.org/proper/commons-dbcp/download_dbcp.cgi

Gary Gregory
Apache Commons Team

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



Re: release of commons-imaging

2024-02-28 Thread Gary Gregory
Yes: M is for milestone.

Gary

On Wed, Feb 28, 2024, 10:40 AM Bruno Kinoshita 
wrote:

> >
> > Why not continue with experimental releases using the same scheme
> > (i.e. "alpha", then "beta") with the agreed on semantics (that
> > compatibility
> > can be broken)?
>
>
> Sounds good to me too, at least users wouldn't expect any difference seeing
> a new alphaN+1 announced. But not sure if there won't be any differences
> with a milestone release (M is for milestone, right?)
>
> Cheers
>
> On Wed, 28 Feb 2024 at 16:11, Gilles Sadowski 
> wrote:
>
> > Le mer. 28 févr. 2024 à 16:00, Bruno Kinoshita
> >  a écrit :
> > >
> > > Hi Gary,
> > >
> > > What would be the main difference between the alpha and M1 releases?
> > >
> > > I am not 100% confident that we have the public and protected API
> right,
> > > > specifically we might have too much public and protected. YMMV.
> > >
> > >
> > > Agreed, and I think if we are to release anything, we would need one or
> > > more extra releases before we get everything right for the 1.0. But if
> we
> > > can continue breaking backward compatibility (even though we will try
> > that
> > > to only what's necessary to reduce impact to users) with M1/M2/M3, the
> > same
> > > way we did with the alpha releases, then I'm +1 for that already.
> >
> > Why not continue with experimental releases using the same scheme
> > (i.e. "alpha", then "beta") with the agreed on semantics (that
> > compatibility
> > can be broken)?
> >
> > > > > [...]
> >
> > -
> > To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> > For additional commands, e-mail: user-h...@commons.apache.org
> >
> >
>


Re: release of commons-imaging

2024-02-28 Thread Gary Gregory
It's just a label that says not 1.0 but really it seems like a label I see
more often than alpha and beta these days. The main idea for me is that we
should have a couple of releases IMO before we stamp a 1.0 and set a binary
compatibility base line.

I am happy to call releases alpha, beta, or milestones until then.

Gary


On Wed, Feb 28, 2024, 10:01 AM Bruno Kinoshita 
wrote:

> Hi Gary,
>
> What would be the main difference between the alpha and M1 releases?
>
> I am not 100% confident that we have the public and protected API right,
> > specifically we might have too much public and protected. YMMV.
>
>
> Agreed, and I think if we are to release anything, we would need one or
> more extra releases before we get everything right for the 1.0. But if we
> can continue breaking backward compatibility (even though we will try that
> to only what's necessary to reduce impact to users) with M1/M2/M3, the same
> way we did with the alpha releases, then I'm +1 for that already.
>
> Thanks!
>
> On Wed, 28 Feb 2024 at 13:50, Gary Gregory  wrote:
>
> > I would like to have an M1 release to push out the current code base.
> >
> > I am not 100% confident that we have the public and protected API right,
> > specifically we might have too much public and protected. YMMV.
> >
> > Gary
> >
> > On Wed, Feb 28, 2024, 6:36 AM Bruno Kinoshita 
> > wrote:
> >
> > > BTW, let us know if there is any issue not resolved that you need/would
> > > like to see in the next release, or if you can help testing/triaging
> the
> > > issues.
> > >
> > > On JIRA you can filter by the milestone/release. Check what's in 1.0
> and
> > > 1.0-alphaN (where N may vary) and is open. Any help there would be
> > > appreciated.
> > >
> > > Cheers
> > >
> > > On Wed, 28 Feb 2024 at 12:30, Bruno Kinoshita  >
> > > wrote:
> > >
> > > > Hi William,
> > > >
> > > > Not sure. I will start looking at the issues to see what is missing
> for
> > > > 1.0, but I suspect we are not ready for a final release yet.
> > > >
> > > > I think there was some discussion about an M1 or RC1 release of
> sorts,
> > > but
> > > > I am out of the loop. The most important thing to know is that there
> > is a
> > > > version to be released soon (as soon as a volunteer has time to go
> > > through
> > > > issues and prepare it), but not the final 1.0 yet.
> > > >
> > > > Cheers,
> > > >
> > > > Bruno
> > > >
> > > > On Wed, 28 Feb 2024 at 12:00, William Borg Barthet <
> > > > william.borgbart...@bloomreach.com> wrote:
> > > >
> > > >> Hi there,
> > > >>
> > > >> Apologies if this is already covered in another thread, but I can't
> > seem
> > > >> to
> > > >> find it. Is a new release of Apache Commons Imaging imminent?
> > > >>
> > > >> Thanks for your help
> > > >>
> > > >> William
> > > >>
> > > >
> > >
> >
>


Re: release of commons-imaging

2024-02-28 Thread Gary Gregory
I would like to have an M1 release to push out the current code base.

I am not 100% confident that we have the public and protected API right,
specifically we might have too much public and protected. YMMV.

Gary

On Wed, Feb 28, 2024, 6:36 AM Bruno Kinoshita 
wrote:

> BTW, let us know if there is any issue not resolved that you need/would
> like to see in the next release, or if you can help testing/triaging the
> issues.
>
> On JIRA you can filter by the milestone/release. Check what's in 1.0 and
> 1.0-alphaN (where N may vary) and is open. Any help there would be
> appreciated.
>
> Cheers
>
> On Wed, 28 Feb 2024 at 12:30, Bruno Kinoshita 
> wrote:
>
> > Hi William,
> >
> > Not sure. I will start looking at the issues to see what is missing for
> > 1.0, but I suspect we are not ready for a final release yet.
> >
> > I think there was some discussion about an M1 or RC1 release of sorts,
> but
> > I am out of the loop. The most important thing to know is that there is a
> > version to be released soon (as soon as a volunteer has time to go
> through
> > issues and prepare it), but not the final 1.0 yet.
> >
> > Cheers,
> >
> > Bruno
> >
> > On Wed, 28 Feb 2024 at 12:00, William Borg Barthet <
> > william.borgbart...@bloomreach.com> wrote:
> >
> >> Hi there,
> >>
> >> Apologies if this is already covered in another thread, but I can't seem
> >> to
> >> find it. Is a new release of Apache Commons Imaging imminent?
> >>
> >> Thanks for your help
> >>
> >> William
> >>
> >
>


[ANNOUNCE] Apache Commons BCEL 3.8.2

2024-02-26 Thread Gary Gregory
The Apache Commons BCEL team is pleased to announce the release of
Apache Commons BCEL 6.8.2.

The Byte Code Engineering Library (BCEL) is intended to give users a
convenient way to analyze, create, and manipulate compiled .class
files. Classes are represented by objects containing all the symbolic
information of the given class: methods, fields, and byte code
instructions.

This is a maintenance and bug fix release.

Historical list of changes:
https://commons.apache.org/proper/commons-bcelchanges report.html

For complete information on Apache Commons BCEL, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons BCEL website:

https://commons.apache.org/proper/commons-bcel

Download it from
https://commons.apache.org/proper/commons-bcel/download_bcel.cgi

Have fun!
Gary Gregory
-Apache Commons BCEL team

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



Re: CVE-2024-25710: Apache Commons Compress: Denial of service caused by an infinite loop for a corrupted DUMP file

2024-02-19 Thread Gary Gregory
Ses also https://github.com/google/oss-fuzz/pull/11616/files

Gary

On Mon, Feb 19, 2024 at 3:57 PM Gary Gregory  wrote:
>
> Hi Magnus and all,
>
> This was discovered through fuzz testing, basically if some bits in
> some parts of a file follow some pattern, then the infinite loop kicks
> in. It only happens if your Commons Compress client code decides to
> parse a DUMP file.
>
> The ticket https://issues.apache.org/jira/browse/COMPRESS-632 is an
> umbrella ticket that gathers fuzz testing issues, and it was recently
> amended with further tests for this specific issue.
>
> The PR you show for a different issue.
>
> Security issues are NOT reported or discussed in public until a fix is
> made available in a release.
>
> Please see:
> - https://commons.apache.org/proper/commons-compress/security.html
> - https://commons.apache.org/security.html
>
> Gary
>
> On Mon, Feb 19, 2024 at 3:33 PM Reftel, Magnus
>  wrote:
> >
> > Hi,
> >
> > Are there any more details on this issue? For instance, under what 
> > circumstances would an application that uses the commons-compress library 
> > be vulnerable? The subject line hints that the flaw is specific to the Dump 
> > format. Is that correct? Are there any options that need to be 
> > enabled/disabled for the application to vulnerable?
> > Also, is it correct that this is related to what was reported in 
> > https://issues.apache.org/jira/browse/COMPRESS-632 and was fixed in 
> > https://github.com/apache/commons-compress/pull/442 ?
> >
> > Best Regards
> > Magnus Reftel
> >
> > On 2024/02/19 01:25:47 "Gary D. Gregory" wrote:
> > > Severity: important
> > >
> > > Affected versions:
> > >
> > > - Apache Commons Compress 1.3 through 1.25.0
> > >
> > > Description:
> > >
> > > Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in 
> > > Apache Commons Compress.This issue affects Apache Commons Compress: from 
> > > 1.3 through 1.25.0.
> > >
> > > Users are recommended to upgrade to version 1.26.0 which fixes the issue.
> > >
> > > Credit:
> > >
> > > Yakov Shafranovich, Amazon Web Services (reporter)
> > >
> > > References:
> > >
> > > https://commons.apache.org/
> > > https://www.cve.org/CVERecord?id=CVE-2024-25710
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: 
> > > user-unsubscr...@commons.apache.org<mailto:user-unsubscr...@commons.apache.org>
> > > For additional commands, e-mail: 
> > > user-h...@commons.apache.org<mailto:user-h...@commons.apache.org>
> > >
> > >
> >
> > 
> > Denne e-posten og eventuelle vedlegg er beregnet utelukkende for den 
> > institusjon eller person den er rettet til og kan vaere belagt med 
> > lovbestemt taushetsplikt. Dersom e-posten er feilsendt, vennligst slett den 
> > og kontakt Skatteetaten.
> > The contents of this email message and any attachments are intended solely 
> > for the addressee(s) and may contain confidential information and may be 
> > legally protected from disclosure. If you are not the intended recipient of 
> > this message, please immediately delete the message and alert the Norwegian 
> > Tax Administration.

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



Re: CVE-2024-25710: Apache Commons Compress: Denial of service caused by an infinite loop for a corrupted DUMP file

2024-02-19 Thread Gary Gregory
Hi Magnus and all,

This was discovered through fuzz testing, basically if some bits in
some parts of a file follow some pattern, then the infinite loop kicks
in. It only happens if your Commons Compress client code decides to
parse a DUMP file.

The ticket https://issues.apache.org/jira/browse/COMPRESS-632 is an
umbrella ticket that gathers fuzz testing issues, and it was recently
amended with further tests for this specific issue.

The PR you show for a different issue.

Security issues are NOT reported or discussed in public until a fix is
made available in a release.

Please see:
- https://commons.apache.org/proper/commons-compress/security.html
- https://commons.apache.org/security.html

Gary

On Mon, Feb 19, 2024 at 3:33 PM Reftel, Magnus
 wrote:
>
> Hi,
>
> Are there any more details on this issue? For instance, under what 
> circumstances would an application that uses the commons-compress library be 
> vulnerable? The subject line hints that the flaw is specific to the Dump 
> format. Is that correct? Are there any options that need to be 
> enabled/disabled for the application to vulnerable?
> Also, is it correct that this is related to what was reported in 
> https://issues.apache.org/jira/browse/COMPRESS-632 and was fixed in 
> https://github.com/apache/commons-compress/pull/442 ?
>
> Best Regards
> Magnus Reftel
>
> On 2024/02/19 01:25:47 "Gary D. Gregory" wrote:
> > Severity: important
> >
> > Affected versions:
> >
> > - Apache Commons Compress 1.3 through 1.25.0
> >
> > Description:
> >
> > Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in 
> > Apache Commons Compress.This issue affects Apache Commons Compress: from 
> > 1.3 through 1.25.0.
> >
> > Users are recommended to upgrade to version 1.26.0 which fixes the issue.
> >
> > Credit:
> >
> > Yakov Shafranovich, Amazon Web Services (reporter)
> >
> > References:
> >
> > https://commons.apache.org/
> > https://www.cve.org/CVERecord?id=CVE-2024-25710
> >
> >
> > -
> > To unsubscribe, e-mail: 
> > user-unsubscr...@commons.apache.org
> > For additional commands, e-mail: 
> > user-h...@commons.apache.org
> >
> >
>
> 
> Denne e-posten og eventuelle vedlegg er beregnet utelukkende for den 
> institusjon eller person den er rettet til og kan vaere belagt med lovbestemt 
> taushetsplikt. Dersom e-posten er feilsendt, vennligst slett den og kontakt 
> Skatteetaten.
> The contents of this email message and any attachments are intended solely 
> for the addressee(s) and may contain confidential information and may be 
> legally protected from disclosure. If you are not the intended recipient of 
> this message, please immediately delete the message and alert the Norwegian 
> Tax Administration.

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



Re: [ANNOUNCE] Apache Commons Compress 1.26.0

2024-02-19 Thread Gary Gregory
Hi Oliver,

What you point out is documented in the release notes [1] and the
site's changes section [2].

Don't confuse binary compatibility (formally defined by the JLS and we
follow) with "drop-in replacement" which can mean different things to
different people.

If you update the version of the dependency on your POM (or whatever
dependency management tool you use), transitive dependencies should be
automatically picked up.

Gary
[1] https://dlcdn.apache.org//commons/compress/RELEASE-NOTES.txt
[2] 
https://commons.apache.org/proper/commons-compress/changes-report.html#a1.26.0

On Mon, Feb 19, 2024 at 9:27 AM Olivier Jaquemet
 wrote:
>
> Hello Gary,
>
> Thank you for this release.
>
> I'd like to point out to users of Commons Compress that this version
> 1.26.0 introduce a *new* dependency to commons-codec (for which it uses
> the latest 1.16.1).
>
> https://central.sonatype.com/artifact/org.apache.commons/commons-compress/dependencies
>
> So in case some of you were expecting to perform drop in replacement of
> the commons-compress jar to benefit from vulnerbabilities fixes, beware
> that you must also introduce new dependencies. (Using dependency
> management tool would have included thoses dependency, so this is more
> of a warning for people still doing old and ugly "jar pickup and drop" ;) )
>
> And for more details, below are the dependencies that were introduced
> (in case you want to update anyway, you probably could without addding
> commons codec, if you are not using those features...) :
>
> org.apache.commons.compress.archivers.tar
>  --> org.apache.commons.codec.Charsets.toCharset(java.lang.String) *
> org.apache.commons.compress.compressors.lz4
>  --> org.apache.commons.codec.digest.XXHash32 *
>  --> org.apache.commons.codec.digest.XXHash32.XXHash32() *
>  --> org.apache.commons.codec.digest.XXHash32.XXHash32(int) *
>  --> org.apache.commons.codec.digest.XXHash32.getValue() *
>  --> org.apache.commons.codec.digest.XXHash32.reset() *
>  --> org.apache.commons.codec.digest.XXHash32.update(byte[], int, int) *
>  --> org.apache.commons.codec.digest.XXHash32.update(int) *
> org.apache.commons.compress.compressors.snappy
>  --> org.apache.commons.codec.digest.PureJavaCrc32C *
>  --> org.apache.commons.codec.digest.PureJavaCrc32C.PureJavaCrc32C() *
>  --> org.apache.commons.codec.digest.PureJavaCrc32C.getValue() *
>  --> org.apache.commons.codec.digest.PureJavaCrc32C.reset() *
>  --> org.apache.commons.codec.digest.PureJavaCrc32C.update(byte[],
> int, int) *
>
> Regards
>
> On 19/02/2024 02:28, Gary Gregory wrote:
> > The Apache Commons team is pleased to announce Apache Compress 1.26.0.
> >
> > Apache Commons Compress defines an API for working with compression
> > and archive formats.  These include bzip2, gzip, pack200, LZMA, XZ,
> > Snappy, traditional Unix Compress, DEFLATE, DEFLATE64, LZ4, Brotli,
> > Zstandard and ar, cpio, jar, tar, zip, dump, 7z, arj.
> >
> > This minor feature and maintenance release.
> >
> > Historical list of changes:
> > https://commons.apache.org/proper/commons-compress/changes-report.html
> >
> > For complete information on Apache Commons Compress, including
> > instructions on how to submit bug reports, patches, or suggestions for
> > improvement, see the Apache Commons Compress website:
> >
> > https://commons.apache.org/proper/commons-compress/
> >
> > Download page: 
> > https://commons.apache.org/proper/commons-compress/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
> > EXTERNAL SENDER: Do not click any links or open any attachments unless you 
> > trust the sender and know the content is safe.
> > EXPÉDITEUR EXTERNE: Ne cliquez sur aucun lien et n’ouvrez aucune pièce 
> > jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous 
> > ayez l'assurance que le contenu provient d'une source sûre.
>
> -
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
>

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



[ANNOUNCE] Apache Commons Compress 1.26.0

2024-02-18 Thread Gary Gregory
The Apache Commons team is pleased to announce Apache Compress 1.26.0.

Apache Commons Compress defines an API for working with compression
and archive formats.  These include bzip2, gzip, pack200, LZMA, XZ,
Snappy, traditional Unix Compress, DEFLATE, DEFLATE64, LZ4, Brotli,
Zstandard and ar, cpio, jar, tar, zip, dump, 7z, arj.

This minor feature and maintenance release.

Historical list of changes:
https://commons.apache.org/proper/commons-compress/changes-report.html

For complete information on Apache Commons Compress, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons Compress website:

https://commons.apache.org/proper/commons-compress/

Download page: 
https://commons.apache.org/proper/commons-compress/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



[ANNOUNCE] Apache Commons Codec 1.16.1

2024-02-09 Thread Gary Gregory
The Apache Commons team is pleased to announce Apache Commons Codec 1.16.1.

Commons Codec contains encoder and decoders for various formats such
as Base16, Base32, Base64, digest, and Hexadecimal. In addition to
these widely used encoders and decoders, the codec package also
maintains a collection of phonetic encoding utilities.

This is a maintenance release and requires a minimum of Java 8.

What's new: 
https://commons.apache.org/proper/commons-codec/changes-report.html#a1.16.1

For complete information on Apache Commons Codec, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons Codec website:

https://commons.apache.org/proper/commons-codec/

Download page: 
https://commons.apache.org/proper/commons-codec/download_codec.cgi

Gary Gregory
Apache Commons Team

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



Re: Missing commons-fileupload2-jakarta-2.0.0-M2.jar in fileupload2 binaries

2024-02-02 Thread Gary Gregory
The next release will address any issues. In the meantime, you can get the
jars from a Maven repository.

Gary


On Fri, Feb 2, 2024, 1:10 AM Subbu V  wrote:

> I see that commons-fileupload2-jakarta-2.0.0-M2.jar is missing in the
> zip/tar binary files for fileupload2 M2 release; in M1 I can see this jar.
> Any thoughts?
>


Re: Evaluating FileAlterationMonitor

2024-01-30 Thread Gary Gregory
BTW, what are your findings that make WatchSerice not work well?

Gary


On Tue, Jan 30, 2024, 11:57 AM Gary D. Gregory  wrote:

> Patrick,
>
> ATM, I think you could create a subclass of the FileAlterationObserver and
> re-implement FileAlterationObserver.checkAndNotify(). You'll have to decide
> what to do in the case of file trees. Do you want to sort by timestamp for
> all files in the tree or just sort files in the current folder being
> processed. At least, that's the consideration needed for a general
> solution. You'll notice that any solution will likely need a second file
> comparator that sorts files for presentation to listeners in the customized
> order. The current comparator is needed as is since it is used for event
> and event type detection.
>
> Let me know what you think and you are considering providing a PR on
> GitHub.
>
> TY!
>
> Gary
>
> On 2024/01/29 23:15:17 Gary Gregory wrote:
> > YW. I think you could sort files if I refactor the monitor a bit such
> that
> > you can plug in a custom comparator (it's already there internally)...
> >
> > Gary
> >
> > On Mon, Jan 29, 2024, 5:19 PM Thomas, Patrick R
> >  wrote:
> >
> > > Thanks for the quick response. I will need to test its behavior for
> lost
> > > connections.
> > >
> > > Based on what I have discovered so far, I will have to create my own
> > > monitor. I need to create a list of new files from all of the monitored
> > > folders during each pass and then sort them by date/time to make sure
> they
> > > are processed in the correct order.
> > >
> > > It doesn't seem to notify about files that already exist. I will have
> to
> > > add this as well, although it is optional because it doesn't work
> correctly
> > > in my current system.
> > >
> > > Thank you,
> > >
> > > Patrick R. Thomas
> > >
> > > -Original Message-
> > > From: Gary Gregory 
> > > Sent: Monday, January 29, 2024 2:05 PM
> > > To: Commons Users List 
> > > Subject: Re: Evaluating FileAlterationMonitor
> > >
> > > CAUTION! This email originated outside of Quest Diagnostics. DO NOT
> click
> > > links or open attachments unless you recognize the sender and know the
> > > content is safe. Please report suspicious emails to:
> > > ph...@questdiagnostics.com
> > >
> > >
> > > The documentation we have is on the site and the Java document. If you
> > > have improvements on the code or documentation, we welcome them as PRs
> on
> > > GitHub.
> > >
> > > The monitor thread wakes up, looks around, and fires events. If a file
> is
> > > not there because a network connection is broken, this will show up as
> a
> > > deleted file.
> > >
> > > YYMV since we do not test this use case in unit tests.
> > >
> > > Gary
> > >
> > >
> > > On Mon, Jan 29, 2024, 1:45 PM Thomas, Patrick R
> > >  wrote:
> > >
> > > > Hello,
> > > >
> > > > Our application monitors multiple folders for new files to import.
> > > > Once a new file is detected, it is moved to a working folder where it
> > > > is processed and then moved to an archive folder. Files are never
> > > > updated, and ones that are deleted before processing are skipped. The
> > > > current implementation has the folders on the same server as the
> > > > application. We are using Java's WatchService to do the monitoring.
> > > > For security reasons, we have to move to a new design where the
> > > > folders will be on a different server. My understanding is that
> > > > WatchService will not work well for this. I am evaluating
> > > > FileAlterationMonitor as an alternative. I have several questions. Is
> > > > there additional documentation I can reference? If the folder being
> > > > monitored is on a mapped network drive and the connection is lost,
> > > > what happens? Can the monitor detect files that already exist when it
> > > > starts? It is also important that the files remain in the order they
> > > were created to be imported.
> > > >
> > > > Any help would be greatly appreciated.
> > > >
> > > > Thank you,
> > > >
> > > > Patrick R. Thomas
> > > > Software Engineer
> > > >
> > > >
> > > >
> __
&

Re: Evaluating FileAlterationMonitor

2024-01-29 Thread Gary Gregory
YW. I think you could sort files if I refactor the monitor a bit such that
you can plug in a custom comparator (it's already there internally)...

Gary

On Mon, Jan 29, 2024, 5:19 PM Thomas, Patrick R
 wrote:

> Thanks for the quick response. I will need to test its behavior for lost
> connections.
>
> Based on what I have discovered so far, I will have to create my own
> monitor. I need to create a list of new files from all of the monitored
> folders during each pass and then sort them by date/time to make sure they
> are processed in the correct order.
>
> It doesn't seem to notify about files that already exist. I will have to
> add this as well, although it is optional because it doesn't work correctly
> in my current system.
>
> Thank you,
>
> Patrick R. Thomas
>
> -Original Message-
> From: Gary Gregory 
> Sent: Monday, January 29, 2024 2:05 PM
> To: Commons Users List 
> Subject: Re: Evaluating FileAlterationMonitor
>
> CAUTION! This email originated outside of Quest Diagnostics. DO NOT click
> links or open attachments unless you recognize the sender and know the
> content is safe. Please report suspicious emails to:
> ph...@questdiagnostics.com
>
>
> The documentation we have is on the site and the Java document. If you
> have improvements on the code or documentation, we welcome them as PRs on
> GitHub.
>
> The monitor thread wakes up, looks around, and fires events. If a file is
> not there because a network connection is broken, this will show up as a
> deleted file.
>
> YYMV since we do not test this use case in unit tests.
>
> Gary
>
>
> On Mon, Jan 29, 2024, 1:45 PM Thomas, Patrick R
>  wrote:
>
> > Hello,
> >
> > Our application monitors multiple folders for new files to import.
> > Once a new file is detected, it is moved to a working folder where it
> > is processed and then moved to an archive folder. Files are never
> > updated, and ones that are deleted before processing are skipped. The
> > current implementation has the folders on the same server as the
> > application. We are using Java's WatchService to do the monitoring.
> > For security reasons, we have to move to a new design where the
> > folders will be on a different server. My understanding is that
> > WatchService will not work well for this. I am evaluating
> > FileAlterationMonitor as an alternative. I have several questions. Is
> > there additional documentation I can reference? If the folder being
> > monitored is on a mapped network drive and the connection is lost,
> > what happens? Can the monitor detect files that already exist when it
> > starts? It is also important that the files remain in the order they
> were created to be imported.
> >
> > Any help would be greatly appreciated.
> >
> > Thank you,
> >
> > Patrick R. Thomas
> > Software Engineer
> >
> >
> > __
> > The contents of this message, together with any attachments, are
> > intended only for the use of the person(s) to which they are addressed
> > and may contain confidential and/or privileged information. Further,
> > any medical information herein is confidential and protected by law.
> > It is unlawful for unauthorized persons to use, review, copy,
> > disclose, or disseminate confidential medical information. If you are
> > not the intended recipient, immediately advise the sender and delete
> this message and any attachments.
> > Any distribution, or copying of this message, or any attachment, is
> > prohibited.
>
> __
> The contents of this message, together with any attachments, are intended
> only for the use of the person(s) to which they are addressed and may
> contain confidential and/or privileged information. Further, any medical
> information herein is confidential and protected by law. It is unlawful for
> unauthorized persons to use, review, copy, disclose, or disseminate
> confidential medical information. If you are not the intended recipient,
> immediately advise the sender and delete this message and any attachments.
> Any distribution, or copying of this message, or any attachment, is
> prohibited.
>


Re: Evaluating FileAlterationMonitor

2024-01-29 Thread Gary Gregory
Sigh, Java document -> Javadoc.

Gary

On Mon, Jan 29, 2024, 2:04 PM Gary Gregory  wrote:

> The documentation we have is on the site and the Java document. If you
> have improvements on the code or documentation, we welcome them as PRs on
> GitHub.
>
> The monitor thread wakes up, looks around, and fires events. If a file is
> not there because a network connection is broken, this will show up as a
> deleted file.
>
> YYMV since we do not test this use case in unit tests.
>
> Gary
>
>
> On Mon, Jan 29, 2024, 1:45 PM Thomas, Patrick R
>  wrote:
>
>> Hello,
>>
>> Our application monitors multiple folders for new files to import. Once a
>> new file is detected, it is moved to a working folder where it is processed
>> and then moved to an archive folder. Files are never updated, and ones that
>> are deleted before processing are skipped. The current implementation has
>> the folders on the same server as the application. We are using Java's
>> WatchService to do the monitoring. For security reasons, we have to move to
>> a new design where the folders will be on a different server. My
>> understanding is that WatchService will not work well for this. I am
>> evaluating FileAlterationMonitor as an alternative. I have several
>> questions. Is there additional documentation I can reference? If the folder
>> being monitored is on a mapped network drive and the connection is lost,
>> what happens? Can the monitor detect files that already exist when it
>> starts? It is also important that the files remain in the order they were
>> created to be imported.
>>
>> Any help would be greatly appreciated.
>>
>> Thank you,
>>
>> Patrick R. Thomas
>> Software Engineer
>>
>>
>> __
>> The contents of this message, together with any attachments, are intended
>> only for the use of the person(s) to which they are addressed and may
>> contain confidential and/or privileged information. Further, any medical
>> information herein is confidential and protected by law. It is unlawful for
>> unauthorized persons to use, review, copy, disclose, or disseminate
>> confidential medical information. If you are not the intended recipient,
>> immediately advise the sender and delete this message and any attachments.
>> Any distribution, or copying of this message, or any attachment, is
>> prohibited.
>
>


Re: Evaluating FileAlterationMonitor

2024-01-29 Thread Gary Gregory
The documentation we have is on the site and the Java document. If you have
improvements on the code or documentation, we welcome them as PRs on GitHub.

The monitor thread wakes up, looks around, and fires events. If a file is
not there because a network connection is broken, this will show up as a
deleted file.

YYMV since we do not test this use case in unit tests.

Gary


On Mon, Jan 29, 2024, 1:45 PM Thomas, Patrick R
 wrote:

> Hello,
>
> Our application monitors multiple folders for new files to import. Once a
> new file is detected, it is moved to a working folder where it is processed
> and then moved to an archive folder. Files are never updated, and ones that
> are deleted before processing are skipped. The current implementation has
> the folders on the same server as the application. We are using Java's
> WatchService to do the monitoring. For security reasons, we have to move to
> a new design where the folders will be on a different server. My
> understanding is that WatchService will not work well for this. I am
> evaluating FileAlterationMonitor as an alternative. I have several
> questions. Is there additional documentation I can reference? If the folder
> being monitored is on a mapped network drive and the connection is lost,
> what happens? Can the monitor detect files that already exist when it
> starts? It is also important that the files remain in the order they were
> created to be imported.
>
> Any help would be greatly appreciated.
>
> Thank you,
>
> Patrick R. Thomas
> Software Engineer
>
>
> __
> The contents of this message, together with any attachments, are intended
> only for the use of the person(s) to which they are addressed and may
> contain confidential and/or privileged information. Further, any medical
> information herein is confidential and protected by law. It is unlawful for
> unauthorized persons to use, review, copy, disclose, or disseminate
> confidential medical information. If you are not the intended recipient,
> immediately advise the sender and delete this message and any attachments.
> Any distribution, or copying of this message, or any attachment, is
> prohibited.


[IO] Evaluating FileAlterationMonitor

2024-01-29 Thread Gary Gregory
Resetting the subject to include the component.

Gafy

On Mon, Jan 29, 2024, 1:45 PM Thomas, Patrick R
 wrote:

> Hello,
>
> Our application monitors multiple folders for new files to import. Once a
> new file is detected, it is moved to a working folder where it is processed
> and then moved to an archive folder. Files are never updated, and ones that
> are deleted before processing are skipped. The current implementation has
> the folders on the same server as the application. We are using Java's
> WatchService to do the monitoring. For security reasons, we have to move to
> a new design where the folders will be on a different server. My
> understanding is that WatchService will not work well for this. I am
> evaluating FileAlterationMonitor as an alternative. I have several
> questions. Is there additional documentation I can reference? If the folder
> being monitored is on a mapped network drive and the connection is lost,
> what happens? Can the monitor detect files that already exist when it
> starts? It is also important that the files remain in the order they were
> created to be imported.
>
> Any help would be greatly appreciated.
>
> Thank you,
>
> Patrick R. Thomas
> Software Engineer
>
>
> __
> The contents of this message, together with any attachments, are intended
> only for the use of the person(s) to which they are addressed and may
> contain confidential and/or privileged information. Further, any medical
> information herein is confidential and protected by law. It is unlawful for
> unauthorized persons to use, review, copy, disclose, or disseminate
> confidential medical information. If you are not the intended recipient,
> immediately advise the sender and delete this message and any attachments.
> Any distribution, or copying of this message, or any attachment, is
> prohibited.


Re: [commons-email] Upgrade to java 17 and jakarta mail

2024-01-20 Thread Gary Gregory
Raffael,

I'm waiting to hear back ;-)

Gary

On Thu, Jan 18, 2024 at 8:24 AM Gary Gregory  wrote:
>
> Raffael,
>
> I can cut 2.0.0-M1 anytime (mod our 72-hour review process). But I
> would prefer to have a use case like yours so we can avoid having to
> release a 2.0.0-M2 immediately to fix what you find in M1.
>
> Gary
>
> On Thu, Jan 18, 2024 at 8:19 AM Raffaele Gambelli
>  wrote:
> >
> > Really thanks Gary,
> >
> > I have to plan my work, so if you can, could you be more specific when you 
> > say "soon"? Is it a question of weeks or months?
> >
> > I need an answer to choose if refactor the code using commons-email without 
> > commons-email.
> >
> > Thank you again
> >
> > -Messaggio originale-
> > Da: Gary Gregory 
> > Inviato: giovedì 18 gennaio 2024 14:13
> > A: Commons Users List 
> > Oggetto: Re: [commons-email] Upgrade to java 17 and jakarta mail
> >
> > Hello Raffael,
> >
> > We have a release 2.0.0 in the works to support Jakarta for which a release 
> > candidate for milestone release 1 should be available "soon".
> > In the meantime, the best I can offer is to point you to our snapshot build 
> > for version 2.0.0-M1-SNAPSHOT in 
> > https://repository.apache.org/content/repositories/snapshots/ using the 
> > artifact IDs:
> >
> > commons-email2-bom
> > commons-email2-core
> > commons-email2-jakarta
> > commons-email2-javax
> >
> > Gary
> >
> > On Thu, Jan 18, 2024 at 4:37 AM Raffaele Gambelli  
> > wrote:
> > >
> > > Hi all,
> > >
> > > I'm going to upgrade one springboot application to springboot 3.x, until 
> > > recently it was using commons-email 1.5 but I upgraded to the latest 1.6 
> > > which I thinked was compatible with jakarta mail but it is not.
> > >
> > > I would like to know if you have some information about one next release 
> > > of commons-email which will be fully compatible with jakarta mail and if 
> > > you know when its release date is expected.
> > >
> > > Thank you very much
> > >
> > > Raffaele
> > > [https://westpole.it/firma/westpole_cegeka_logo.jpg]
> > >
> > > Raffaele Gambelli
> > > Research & Development
> > >
> > > P +390518550576
> > > M 3371641888
> > > E r.gambe...@westpole.it
> > > W https://westpole.webex.com/meet/R.Gambelli
> > > A Via Ettore Cristoni, 84 - 40033 Casalecchio di Reno
> > >
> > > [https://westpole.it/firma/website.png]<https://westpole.it>  
> > > [https://westpole.it/firma/twitter.png] 
> > > <https://twitter.com/WESTPOLE_SPA>   
> > > [https://westpole.it/firma/linkedin.png] 
> > > <https://www.linkedin.com/company/westpole-italia/>   
> > > [https://westpole.it/firma/mortarboard.png] <https://careers.westpole.eu/>
> > >
> > > This email for the D.lgs.196/2003 (Privacy Code) and European Regulation 
> > > 679/2016/UE (GDPR) may contain confidential and/or privileged information 
> > > for the exclusive use of the intended recipient. Any review or 
> > > distribution by others is strictly prohibited. If you are not the 
> > > intended recipient, you must not use, copy, disclose or take any action 
> > > based on this message or any information here. If you have received this 
> > > email in error, please contact us (email:priv...@westpole.it) by reply 
> > > email and delete all copies. Legal privilege is not waived because you 
> > > have read this email. Thank you for your cooperation.
> > >
> > > [https://westpole.it/firma/ambiente.png] Please consider the
> > > environment before printing this email
> >
> > -
> > To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> > For additional commands, e-mail: user-h...@commons.apache.org
> >
> >
> > -
> > To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> > For additional commands, e-mail: user-h...@commons.apache.org

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



Re: [commons-email] Upgrade to java 17 and jakarta mail

2024-01-18 Thread Gary Gregory
Raffael,

I can cut 2.0.0-M1 anytime (mod our 72-hour review process). But I
would prefer to have a use case like yours so we can avoid having to
release a 2.0.0-M2 immediately to fix what you find in M1.

Gary

On Thu, Jan 18, 2024 at 8:19 AM Raffaele Gambelli
 wrote:
>
> Really thanks Gary,
>
> I have to plan my work, so if you can, could you be more specific when you 
> say "soon"? Is it a question of weeks or months?
>
> I need an answer to choose if refactor the code using commons-email without 
> commons-email.
>
> Thank you again
>
> -----Messaggio originale-
> Da: Gary Gregory 
> Inviato: giovedì 18 gennaio 2024 14:13
> A: Commons Users List 
> Oggetto: Re: [commons-email] Upgrade to java 17 and jakarta mail
>
> Hello Raffael,
>
> We have a release 2.0.0 in the works to support Jakarta for which a release 
> candidate for milestone release 1 should be available "soon".
> In the meantime, the best I can offer is to point you to our snapshot build 
> for version 2.0.0-M1-SNAPSHOT in 
> https://repository.apache.org/content/repositories/snapshots/ using the 
> artifact IDs:
>
> commons-email2-bom
> commons-email2-core
> commons-email2-jakarta
> commons-email2-javax
>
> Gary
>
> On Thu, Jan 18, 2024 at 4:37 AM Raffaele Gambelli  
> wrote:
> >
> > Hi all,
> >
> > I'm going to upgrade one springboot application to springboot 3.x, until 
> > recently it was using commons-email 1.5 but I upgraded to the latest 1.6 
> > which I thinked was compatible with jakarta mail but it is not.
> >
> > I would like to know if you have some information about one next release of 
> > commons-email which will be fully compatible with jakarta mail and if you 
> > know when its release date is expected.
> >
> > Thank you very much
> >
> > Raffaele
> > [https://westpole.it/firma/westpole_cegeka_logo.jpg]
> >
> > Raffaele Gambelli
> > Research & Development
> >
> > P +390518550576
> > M 3371641888
> > E r.gambe...@westpole.it
> > W https://westpole.webex.com/meet/R.Gambelli
> > A Via Ettore Cristoni, 84 - 40033 Casalecchio di Reno
> >
> > [https://westpole.it/firma/website.png]<https://westpole.it>  
> > [https://westpole.it/firma/twitter.png] <https://twitter.com/WESTPOLE_SPA>  
> >  [https://westpole.it/firma/linkedin.png] 
> > <https://www.linkedin.com/company/westpole-italia/>   
> > [https://westpole.it/firma/mortarboard.png] <https://careers.westpole.eu/>
> >
> > This email for the D.lgs.196/2003 (Privacy Code) and European Regulation 
> > 679/2016/UE (GDPR) may contain confidential and/or privileged information 
> > for the exclusive use of the intended recipient. Any review or distribution 
> > by others is strictly prohibited. If you are not the intended recipient, 
> > you must not use, copy, disclose or take any action based on this message 
> > or any information here. If you have received this email in error, please 
> > contact us (email:priv...@westpole.it) by reply email and delete all 
> > copies. Legal privilege is not waived because you have read this email. 
> > Thank you for your cooperation.
> >
> > [https://westpole.it/firma/ambiente.png] Please consider the
> > environment before printing this email
>
> -
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
>
>
> -
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org

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



Re: [commons-email] Upgrade to java 17 and jakarta mail

2024-01-18 Thread Gary Gregory
Hello Raffael,

We have a release 2.0.0 in the works to support Jakarta for which a
release candidate for milestone release 1 should be available "soon".
In the meantime, the best I can offer is to point you to our snapshot
build for version 2.0.0-M1-SNAPSHOT in
https://repository.apache.org/content/repositories/snapshots/ using
the artifact IDs:

commons-email2-bom
commons-email2-core
commons-email2-jakarta
commons-email2-javax

Gary

On Thu, Jan 18, 2024 at 4:37 AM Raffaele Gambelli
 wrote:
>
> Hi all,
>
> I'm going to upgrade one springboot application to springboot 3.x, until 
> recently it was using commons-email 1.5 but I upgraded to the latest 1.6 
> which I thinked was compatible with jakarta mail but it is not.
>
> I would like to know if you have some information about one next release of 
> commons-email which will be fully compatible with jakarta mail and if you 
> know when its release date is expected.
>
> Thank you very much
>
> Raffaele
> [https://westpole.it/firma/westpole_cegeka_logo.jpg]
>
> Raffaele Gambelli
> Research & Development
>
> P +390518550576
> M 3371641888
> E r.gambe...@westpole.it
> W https://westpole.webex.com/meet/R.Gambelli
> A Via Ettore Cristoni, 84 - 40033 Casalecchio di Reno
>
> [https://westpole.it/firma/website.png]  
> [https://westpole.it/firma/twitter.png]    
> [https://westpole.it/firma/linkedin.png] 
>    
> [https://westpole.it/firma/mortarboard.png] 
>
> This email for the D.lgs.196/2003 (Privacy Code) and European Regulation 
> 679/2016/UE (GDPR) may contain confidential and/or privileged information for 
> the exclusive use of the intended recipient. Any review or distribution by 
> others is strictly prohibited. If you are not the intended recipient, you 
> must not use, copy, disclose or take any action based on this message or any 
> information here. If you have received this email in error, please contact us 
> (email:priv...@westpole.it) by reply email and delete all copies. Legal 
> privilege is not waived because you have read this email. Thank you for your 
> cooperation.
>
> [https://westpole.it/firma/ambiente.png] Please consider the environment 
> before printing this email

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



[ANNOUNCE] Apache Commons BCEL 6.8.1

2024-01-12 Thread Gary Gregory
The Apache Commons BCEL team is pleased to announce the release of
Apache Commons BCEL 6.8.1.

The Byte Code Engineering Library (BCEL) is intended to give users a
convenient way to analyze, create, and manipulate compiled .class
files. Classes are represented by objects containing all the symbolic
information of the given class: methods, fields, and byte code
instructions.

This is a maintenance and bug fix release; requires Java 8.

Historical list of changes:
https://commons.apache.org/proper/commons-bcelchanges-report.html

For complete information on Apache Commons BCEL, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons BCEL website:

https://commons.apache.org/proper/commons-bcel

Download it from
https://commons.apache.org/proper/commons-bcel/download_bcel.cgi

Have fun!
Gary Gregory
-Apache Commons BCEL team

Feedback


Open source works best when you give feedback:

https://commons.apache.org/bcel

Please direct all bug reports to JIRA:

https://issues.apache.org/jira/browse/BCEL

Or subscribe to the commons-user mailing list

The Apache Commons Team

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



[ANNOUNCE] Apache Commons BCEL 6.8.1

2024-01-12 Thread Gary Gregory
The Apache Commons BCEL team is pleased to announce the release of
Apache Commons BCEL 6.8.1.

The Byte Code Engineering Library (BCEL) is intended to give users a
convenient way to analyze, create, and manipulate compiled .class
files. Classes are represented by objects containing all the symbolic
information of the given class: methods, fields, and byte code
instructions.

This is a maintenance and bug fix release; requires Java 8.

Historical list of changes:
https://commons.apache.org/proper/commons-bcelchanges-report.html

For complete information on Apache Commons BCEL, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons BCEL website:

https://commons.apache.org/proper/commons-bcel

Download it from
https://commons.apache.org/proper/commons-bcel/download_bcel.cgi

Have fun!
Gary Gregory
-Apache Commons BCEL team

Feedback


Open source works best when you give feedback:

https://commons.apache.org/bcel

Please direct all bug reports to JIRA:

https://issues.apache.org/jira/browse/BCEL

Or subscribe to the commons-user mailing list

The Apache Commons Team

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



Re: JDK 17 compatibility with commons-cli

2024-01-12 Thread Gary Gregory
I think the next commons-parent will fix that by updating the Maven
SpotBugs plugin.

Gary

On Fri, Jan 12, 2024, 7:06 AM Tamás Cservenák  wrote:

> Howdy,
>
> Gary, is that "Maven issue" reported? If so, which one is it?
>
> Thanks
> T
>
> On Fri, Jan 12, 2024 at 1:03 PM Gary Gregory 
> wrote:
>
> > The GitHub build tests
> > https://github.com/apache/commons-cli/actions/runs/7501684649 with Java
> > LTS
> > versiosn 8, 11, 17, 21. Also 22-ea as an experiment which currently fails
> > due to a Maven issue.
> >
> > Gary
> >
> > On Fri, Jan 12, 2024, 4:20 AM Hrach Papikyan 
> > wrote:
> >
> > > Hey,
> > >
> > > I would like to clarify whether commons-cli is compatible with jdk17 or
> > > not, if yes please clarify as well version.
> > >
> > > Best Regards,
> > > Hrach
> > >
> >
>


Re: JDK 17 compatibility with commons-cli

2024-01-12 Thread Gary Gregory
The GitHub build tests
https://github.com/apache/commons-cli/actions/runs/7501684649 with Java LTS
versiosn 8, 11, 17, 21. Also 22-ea as an experiment which currently fails
due to a Maven issue.

Gary

On Fri, Jan 12, 2024, 4:20 AM Hrach Papikyan 
wrote:

> Hey,
>
> I would like to clarify whether commons-cli is compatible with jdk17 or
> not, if yes please clarify as well version.
>
> Best Regards,
> Hrach
>


[ANNOUNCE] Apache Commons Exec Version 1.4.0

2024-01-06 Thread Gary Gregory
Apache Commons Exec is a library to reliably execute external
processes from within the JVM.

Maintenance and feature Release (Java 8 or above)

Historical list of changes:
https://commons.apache.org/proper/commons-exec//changes-report.html

For complete information on Apache Commons Exec, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons Exec website:

https://commons.apache.org/proper/commons-exec/

Download page: https://commons.apache.org/proper/commons-exec//download_text.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



Re: XmlStreamReader encoding regexp does not work anymore without version

2024-01-02 Thread Gary Gregory
I fixed this in git master and 2.16.0-SNAPSHOT builds.

Please test and report back! 

Gary


On Tue, Jan 2, 2024, 11:03 AM Gary Gregory  wrote:

> Ah, intersection, I'll look into it.
>
> Gary
>
>
> On Tue, Jan 2, 2024, 9:50 AM Andreas Hubold
>  wrote:
>
>> Hi Gary,
>>
>> right, but it is optional for external entities, see
>> https://www.w3.org/TR/xml/#TextEntities
>>
>> And the examples in https://www.w3.org/TR/xml/#NT-EncodingDecl also
>> don't have version attributes, so this might still be a valid use case?
>>
>> > 
>> > 
>>
>> Cheers
>> Andreas
>>
>>
>> Gary Gregory schrieb am 02.01.24 um 15:42:
>> > [Sie erhalten nicht häufig E-Mails vongarydgreg...@gmail.com. Weitere
>> Informationen, warum dies wichtig ist, finden Sie unterhttps://
>> aka.ms/LearnAboutSenderIdentification  ]
>> >
>> > Hi Andreas,
>> >
>> > In an "xml" PI, the "version" is NOT optional, see
>> > https://www.w3.org/TR/REC-xml/#sec-pi
>> >
>> > If we tried to handle all cases of invalid documents, then there would
>> > be no end to it.
>> >
>> > Gary
>> >
>> > On Tue, Jan 2, 2024 at 9:36 AM Gary Gregory
>> wrote:
>> >> Ah, you are talking about something different, I am sorry about that.
>> Looking...
>> >>
>> >> Gary
>> >>
>> >> On Tue, Jan 2, 2024 at 9:35 AM Gary Gregory
>> wrote:
>> >>> Hello Andrea,
>> >>>
>> >>> Please try git master or a 2.16.0-SNAPSHOT build
>> >>> (
>> https://repository.apache.org/content/repositories/snapshots/commons-io/commons-io/2.16.0-SNAPSHOT
>> )
>> >>> I fixed this today as reported inhttps://
>> github.com/apache/commons-io/pull/550
>> >>>
>> >>> TY!
>> >>> Gary
>> >>>
>> >>> On Tue, Jan 2, 2024 at 9:33 AM Andreas Hubold
>> >>>   wrote:
>> >>>> Hi,
>> >>>>
>> >>>> the regular expression for the encoding was changed in
>> XmlStreamReader
>> >>>> between 2.13.0 and 2.15.1.
>> >>>>
>> >>>> It now requires a version attribute in the XML declaration and does
>> not
>> >>>> work anymore with some real world files.
>> >>>>
>> >>>> For example, the encoding from the following example declaration is
>> >>>> respected by 2.13.0, but not by 2.15.1
>> >>>>
>> >>>> 
>> >>>>
>> >>>> It works if the version is specified: > >>>> encoding='Cp1047'?>
>> >>>>
>> >>>> However note, thathttps://www.w3.org/TR/xml/#NT-EncodingDecl  also
>> >>>> mentions examples without version attribute, at least for entities.
>> It
>> >>>> would be good to restore the previous behavior, IMHO.
>> >>>>
>> >>>> Cheers,
>> >>>> Andreas
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> -
>> >>>> To unsubscribe, e-mail:user-unsubscr...@commons.apache.org
>> >>>> For additional commands, e-mail:user-h...@commons.apache.org
>> >>>>
>> > -
>> > To unsubscribe, e-mail:user-unsubscr...@commons.apache.org
>> > For additional commands, e-mail:user-h...@commons.apache.org
>> >
>>
>


Re: XmlStreamReader encoding regexp does not work anymore without version

2024-01-02 Thread Gary Gregory
Ah, intersection, I'll look into it.

Gary


On Tue, Jan 2, 2024, 9:50 AM Andreas Hubold
 wrote:

> Hi Gary,
>
> right, but it is optional for external entities, see
> https://www.w3.org/TR/xml/#TextEntities
>
> And the examples in https://www.w3.org/TR/xml/#NT-EncodingDecl also
> don't have version attributes, so this might still be a valid use case?
>
> > 
> > 
>
> Cheers
> Andreas
>
>
> Gary Gregory schrieb am 02.01.24 um 15:42:
> > [Sie erhalten nicht häufig E-Mails vongarydgreg...@gmail.com. Weitere
> Informationen, warum dies wichtig ist, finden Sie unterhttps://
> aka.ms/LearnAboutSenderIdentification  ]
> >
> > Hi Andreas,
> >
> > In an "xml" PI, the "version" is NOT optional, see
> > https://www.w3.org/TR/REC-xml/#sec-pi
> >
> > If we tried to handle all cases of invalid documents, then there would
> > be no end to it.
> >
> > Gary
> >
> > On Tue, Jan 2, 2024 at 9:36 AM Gary Gregory
> wrote:
> >> Ah, you are talking about something different, I am sorry about that.
> Looking...
> >>
> >> Gary
> >>
> >> On Tue, Jan 2, 2024 at 9:35 AM Gary Gregory
> wrote:
> >>> Hello Andrea,
> >>>
> >>> Please try git master or a 2.16.0-SNAPSHOT build
> >>> (
> https://repository.apache.org/content/repositories/snapshots/commons-io/commons-io/2.16.0-SNAPSHOT
> )
> >>> I fixed this today as reported inhttps://
> github.com/apache/commons-io/pull/550
> >>>
> >>> TY!
> >>> Gary
> >>>
> >>> On Tue, Jan 2, 2024 at 9:33 AM Andreas Hubold
> >>>   wrote:
> >>>> Hi,
> >>>>
> >>>> the regular expression for the encoding was changed in XmlStreamReader
> >>>> between 2.13.0 and 2.15.1.
> >>>>
> >>>> It now requires a version attribute in the XML declaration and does
> not
> >>>> work anymore with some real world files.
> >>>>
> >>>> For example, the encoding from the following example declaration is
> >>>> respected by 2.13.0, but not by 2.15.1
> >>>>
> >>>> 
> >>>>
> >>>> It works if the version is specified:  >>>> encoding='Cp1047'?>
> >>>>
> >>>> However note, thathttps://www.w3.org/TR/xml/#NT-EncodingDecl  also
> >>>> mentions examples without version attribute, at least for entities. It
> >>>> would be good to restore the previous behavior, IMHO.
> >>>>
> >>>> Cheers,
> >>>> Andreas
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> -
> >>>> To unsubscribe, e-mail:user-unsubscr...@commons.apache.org
> >>>> For additional commands, e-mail:user-h...@commons.apache.org
> >>>>
> > -
> > To unsubscribe, e-mail:user-unsubscr...@commons.apache.org
> > For additional commands, e-mail:user-h...@commons.apache.org
> >
>


Re: XmlStreamReader encoding regexp does not work anymore without version

2024-01-02 Thread Gary Gregory
Andreas,

I just remembered that we have a lenient setting that could be used to
access a different regular expression that does not care about correctness.

If we do support this, then the regular expression must be lenient enough
but not so much that it can be used as an attack vector for resource
consumption, which was a problem in the past IIRC.

Whether or not it's a good idea to have a new lenient setting, overload the
current one, or have one at all, is a different topic.

Gary

On Tue, Jan 2, 2024, 9:42 AM Gary Gregory  wrote:

> Hi Andreas,
>
> In an "xml" PI, the "version" is NOT optional, see
> https://www.w3.org/TR/REC-xml/#sec-pi
>
> If we tried to handle all cases of invalid documents, then there would
> be no end to it.
>
> Gary
>
> On Tue, Jan 2, 2024 at 9:36 AM Gary Gregory 
> wrote:
> >
> > Ah, you are talking about something different, I am sorry about that.
> Looking...
> >
> > Gary
> >
> > On Tue, Jan 2, 2024 at 9:35 AM Gary Gregory 
> wrote:
> > >
> > > Hello Andrea,
> > >
> > > Please try git master or a 2.16.0-SNAPSHOT build
> > > (
> https://repository.apache.org/content/repositories/snapshots/commons-io/commons-io/2.16.0-SNAPSHOT
> )
> > > I fixed this today as reported in
> https://github.com/apache/commons-io/pull/550
> > >
> > > TY!
> > > Gary
> > >
> > > On Tue, Jan 2, 2024 at 9:33 AM Andreas Hubold
> > >  wrote:
> > > >
> > > > Hi,
> > > >
> > > > the regular expression for the encoding was changed in
> XmlStreamReader
> > > > between 2.13.0 and 2.15.1.
> > > >
> > > > It now requires a version attribute in the XML declaration and does
> not
> > > > work anymore with some real world files.
> > > >
> > > > For example, the encoding from the following example declaration is
> > > > respected by 2.13.0, but not by 2.15.1
> > > >
> > > > 
> > > >
> > > > It works if the version is specified:  > > > encoding='Cp1047'?>
> > > >
> > > > However note, that https://www.w3.org/TR/xml/#NT-EncodingDecl also
> > > > mentions examples without version attribute, at least for entities.
> It
> > > > would be good to restore the previous behavior, IMHO.
> > > >
> > > > Cheers,
> > > > Andreas
> > > >
> > > >
> > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> > > > For additional commands, e-mail: user-h...@commons.apache.org
> > > >
>


Re: XmlStreamReader encoding regexp does not work anymore without version

2024-01-02 Thread Gary Gregory
Hi Andreas,

In an "xml" PI, the "version" is NOT optional, see
https://www.w3.org/TR/REC-xml/#sec-pi

If we tried to handle all cases of invalid documents, then there would
be no end to it.

Gary

On Tue, Jan 2, 2024 at 9:36 AM Gary Gregory  wrote:
>
> Ah, you are talking about something different, I am sorry about that. 
> Looking...
>
> Gary
>
> On Tue, Jan 2, 2024 at 9:35 AM Gary Gregory  wrote:
> >
> > Hello Andrea,
> >
> > Please try git master or a 2.16.0-SNAPSHOT build
> > (https://repository.apache.org/content/repositories/snapshots/commons-io/commons-io/2.16.0-SNAPSHOT)
> > I fixed this today as reported in 
> > https://github.com/apache/commons-io/pull/550
> >
> > TY!
> > Gary
> >
> > On Tue, Jan 2, 2024 at 9:33 AM Andreas Hubold
> >  wrote:
> > >
> > > Hi,
> > >
> > > the regular expression for the encoding was changed in XmlStreamReader
> > > between 2.13.0 and 2.15.1.
> > >
> > > It now requires a version attribute in the XML declaration and does not
> > > work anymore with some real world files.
> > >
> > > For example, the encoding from the following example declaration is
> > > respected by 2.13.0, but not by 2.15.1
> > >
> > > 
> > >
> > > It works if the version is specified:  > > encoding='Cp1047'?>
> > >
> > > However note, that https://www.w3.org/TR/xml/#NT-EncodingDecl also
> > > mentions examples without version attribute, at least for entities. It
> > > would be good to restore the previous behavior, IMHO.
> > >
> > > Cheers,
> > > Andreas
> > >
> > >
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> > > For additional commands, e-mail: user-h...@commons.apache.org
> > >

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



Re: XmlStreamReader encoding regexp does not work anymore without version

2024-01-02 Thread Gary Gregory
Ah, you are talking about something different, I am sorry about that. Looking...

Gary

On Tue, Jan 2, 2024 at 9:35 AM Gary Gregory  wrote:
>
> Hello Andrea,
>
> Please try git master or a 2.16.0-SNAPSHOT build
> (https://repository.apache.org/content/repositories/snapshots/commons-io/commons-io/2.16.0-SNAPSHOT)
> I fixed this today as reported in 
> https://github.com/apache/commons-io/pull/550
>
> TY!
> Gary
>
> On Tue, Jan 2, 2024 at 9:33 AM Andreas Hubold
>  wrote:
> >
> > Hi,
> >
> > the regular expression for the encoding was changed in XmlStreamReader
> > between 2.13.0 and 2.15.1.
> >
> > It now requires a version attribute in the XML declaration and does not
> > work anymore with some real world files.
> >
> > For example, the encoding from the following example declaration is
> > respected by 2.13.0, but not by 2.15.1
> >
> > 
> >
> > It works if the version is specified:  > encoding='Cp1047'?>
> >
> > However note, that https://www.w3.org/TR/xml/#NT-EncodingDecl also
> > mentions examples without version attribute, at least for entities. It
> > would be good to restore the previous behavior, IMHO.
> >
> > Cheers,
> > Andreas
> >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> > For additional commands, e-mail: user-h...@commons.apache.org
> >

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



Re: XmlStreamReader encoding regexp does not work anymore without version

2024-01-02 Thread Gary Gregory
Hello Andrea,

Please try git master or a 2.16.0-SNAPSHOT build
(https://repository.apache.org/content/repositories/snapshots/commons-io/commons-io/2.16.0-SNAPSHOT)
I fixed this today as reported in https://github.com/apache/commons-io/pull/550

TY!
Gary

On Tue, Jan 2, 2024 at 9:33 AM Andreas Hubold
 wrote:
>
> Hi,
>
> the regular expression for the encoding was changed in XmlStreamReader
> between 2.13.0 and 2.15.1.
>
> It now requires a version attribute in the XML declaration and does not
> work anymore with some real world files.
>
> For example, the encoding from the following example declaration is
> respected by 2.13.0, but not by 2.15.1
>
> 
>
> It works if the version is specified:  encoding='Cp1047'?>
>
> However note, that https://www.w3.org/TR/xml/#NT-EncodingDecl also
> mentions examples without version attribute, at least for entities. It
> would be good to restore the previous behavior, IMHO.
>
> Cheers,
> Andreas
>
>
>
>
> -
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
>

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



[ANNOUNCE] Apache Commons FileUpload 2.0.0-M2

2023-12-28 Thread Gary Gregory
The Apache Commons FileUpload team is pleased to announce the release
of Apache Commons FileUpload 2.0.0-M2.

The Apache Commons FileUpload component provides a simple yet flexible means of
adding support for multipart file upload functionality to Servlets and web
applications. This version requires Java 11 or above.

To read what's new, go to
https://commons.apache.org/proper/commons-fileupload/changes-report.html#a2.0.0-M2

For complete information on Apache Commons FileUpload, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons FileUpload website:

https://commons.apache.org/proper/commons-fileupload/

Download it from
https://commons.apache.org/proper/commons-fileupload/download_fileupload.cgi

Gary Gregory
Apache Commons Team

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



Re: Release date for commons-fileupload2-jakarta?

2023-12-24 Thread Gary Gregory
Just FYI, I pushed out a release candidate for a 2.0.0-M2 release.

Gary

On Thu, Dec 21, 2023 at 2:39 AM Paolo Bazzi
 wrote:
>
> Hi Gary
>
> Thanks for your reply. Since there is no planned date for a stable release 
> and we need a production-ready library in January 2024, we decided to switch 
> to another solution.
>
> Thanks,
> Paolo
>
>
> -Ursprüngliche Nachricht-
> Von: Gary Gregory 
> Gesendet: Montag, 11. Dezember 2023 21:33
> An: Commons Users List 
> Betreff: Re: Release date for commons-fileupload2-jakarta?
>
> [Sie erhalten nicht häufig E-Mails von garydgreg...@gmail.com. Weitere 
> Informationen, warum dies wichtig ist, finden Sie unter 
> https://aka.ms/LearnAboutSenderIdentification ]
>
> First, this needs fixing:
>
> https://github.com/apache/commons-fileupload/pull/248
>
> Feel free to provide a fix.
>
> There is no schedule ATM. We would like more testing, hence the M1 milestone 
> release to make the jar easily accessible. Do test this version.
>
> We can cut a M2 version once the above PR 248 issue is addressed and code has 
> been reviewed again.
>
> TY,
> Gary
>
>
> On Mon, Dec 11, 2023, 9:50 AM Paolo Bazzi 
> wrote:
>
> > Hi All,
> >
> >
> >
> > The commons fileupload page [1] lists the 2.0.0-M1 as latest release
> > which is Jakarta-ready. This build was published in July 2023 and is
> > marked as Milestone build.
> >
> >
> >
> > Is there a planned release date for an official, production-ready build?
> >
> >
> >
> > Artefact:
> >
> >
> >
> > 
> >
> >   org.apache.commons
> >
> >   commons-fileupload2
> >
> >   2.0.0-M1
> >
> > 
> >
> >
> >
> > [1]
> > https://gith/
> > ub.com%2Fapache%2Fcommons-fileupload%23where-can-i-get-the-latest-rele
> > ase=05%7C02%7Cpaolo.bazzi%40bsi-software.com%7C7f71f3a29c924a3eae
> > be08dbfa887a01%7C26f00d3eed2549d1917420bfdd2a2564%7C1%7C0%7C6383792364
> > 49362455%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiL
> > CJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C=pIJYuWT3AqvLYC%2BL
> > RhSja%2F3NyVEQdBtgB8vcLG4ygF0%3D=0
> >
> >
> >
> > Regards,
> >
> > Paolo
> >
> >
> >

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



Re: Release date for commons-fileupload2-jakarta?

2023-12-11 Thread Gary Gregory
First, this needs fixing:

https://github.com/apache/commons-fileupload/pull/248

Feel free to provide a fix.

There is no schedule ATM. We would like more testing, hence the M1
milestone release to make the jar easily accessible. Do test this version.

We can cut a M2 version once the above PR 248 issue is addressed and code
has been reviewed again.

TY,
Gary


On Mon, Dec 11, 2023, 9:50 AM Paolo Bazzi 
wrote:

> Hi All,
>
>
>
> The commons fileupload page [1] lists the 2.0.0-M1 as latest release which
> is Jakarta-ready. This build was published in July 2023 and is marked as
> Milestone build.
>
>
>
> Is there a planned release date for an official, production-ready build?
>
>
>
> Artefact:
>
>
>
> 
>
>   org.apache.commons
>
>   commons-fileupload2
>
>   2.0.0-M1
>
> 
>
>
>
> [1]
> https://github.com/apache/commons-fileupload#where-can-i-get-the-latest-release
>
>
>
> Regards,
>
> Paolo
>
>
>


[ANNOUNCE] Apache Commons BCEL Version 6.8.0

2023-12-09 Thread Gary Gregory
The Apache Commons BCEL team is pleased to announce the release of
Apache Commons BCEL 6.8.0!

The Byte Code Engineering Library (BCEL) is intended to give users a
convenient way to analyze, create, and manipulate compiled .class
files. Classes are represented by objects containing all the symbolic
information of the given class: methods, fields, and byte code
instructions.

This maintenance and bug fix release requires Java 8, and was tested
on Java 8, 11, 17, and 21.

Historical list of changes:
https://commons.apache.org/proper/commons-bcelchanges-report.html

For complete information on Apache Commons BCEL, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons BCEL website:

https://commons.apache.org/proper/commons-bcel

Download it from
https://commons.apache.org/proper/commons-bcel/download_bcel.cgi

Have fun!
Gary Gregory
-Apache Commons BCEL team

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



[ANNOUNCE] Apache Commons Logging 1.3.0

2023-12-02 Thread Gary Gregory
The Apache Commons Logging team is pleased to announce the release of
Apache Commons Logging 1.3.0.

Apache Commons Logging is a thin adapter allowing configurable
bridging to other,
well-known logging systems.

This is a feature and maintenance release. Java 8 or later is required.

Historical list of changes:
https://commons.apache.org/proper/commons-logging/changes-report.html

Download it from
https://commons.apache.org/proper/commons-logging/download_logging.cgi

For complete information on Apache Commons Logging, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons Logging website:

https://commons.apache.org/proper/commons-logging/

Gary Gregory
Apache Commons Team

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



Re: Regression/Error on commons-io FileUtils.copyFile ?

2023-11-30 Thread Gary Gregory
Hello Luis,

Thank you for your detailed report.

An interesting question is to check to see if the file attributes are
correctly updated using 2.11 or if the file timestamp is not changed and
that fact is not reported as an exception.

For a new feature, free to create a PR on GitHub so we can see what this
would really look like.

TY,
Gary

On Tue, Nov 28, 2023, 2:29 PM Luis Panadero Guardeño <
luis.panad...@digibis.com> wrote:

> Good afternoon,
>
> I recently noticed a issue when we update our projects from Commons-io
> 2.11.0 to 2.13.0 with FileUtils.copyFile
>
> In our code base, we was using FileUtils.copyFile(src, dst) , that as is
> said on the JavaDoc, must preserve the file's last modified date/times.
> Sometimes, we do this over a SMB/CIFs share folder, and we never had
> problems or errors with this.
>
> But, since we update to 2.13.0 , we got IOExceptions because copyFile
> fails to preserve the file's last modified date/times. I see that the
> implementation changed a bit. on 2.11.0 copyFile uses directly
> File.setLastModified(long) and now tries with
> BasicFileAttributeView.setTimes(FileTime, FileTime, FileTime) and if fails,
> tries with File.setLastModified(long) . So, it should keep working exactly
> like before. But, obviously, for our use case, isn't. We workaround ,
> calling copyFile with preserveFileDate set to false.
>
> Also, I noticed an problem with the actual API of FileUtils.copyFile
> methods. I think that an improvement should be that when copyFile fails to
> set file's last modified date/times, should throw a different exception
> from IOException (extend an exception from it). Actually it's imposible to
> differentiated from another bigger IO problems. In out case, we would like
> to try to preserve the file's last modified date/times, but ignore the
> error if it fails to do that. And I can't see any way of doing it.
> Specially with the current implementation of FileUtils.copyFile .
> --
>
> *Luis Panadero Guardeño*
> Departamento de Informática
> luis.panad...@digibis.com
> [image: DIGIBÍS S.L.]
> DIGIBÍS S.L.U.
>
>
> C/ Alenza, 4, 5ª planta.
> 28003 Madrid
> Tf. 91 432 08 88 . Fax 91 432 11 13
>
> http://www.digibis.com
>
> Certificado ISO 9001.
> No imprimir si no es necesario. Protejamos el Medio Ambiente
>
> En cumplimiento de la LOPD y la LSSI, le informamos de que sus datos
> personales son incorporados a un fichero, titularidad de DIGIBÍS, S.L.U.,
> con el fin de ofrecerle información sobre servicios que pueden ser de su
> interés. Podrá ejercitar sus derechos ARCO (de acceso, rectificación,
> cancelación y oposición) mediante un escrito dirigido a
> digi...@digibis.com , con copia del DNI o documento identificativo
> sustitutorio.
> En caso de querer darse de baja pinche aquí
> .
>
>

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

[ANNOUNCE] Apache Commons Lang Version 3.14.0

2023-11-27 Thread Gary Gregory
The Apache Commons team is pleased to announce Apache Commons Lang
Version 3.14.0.

Commons Lang is a set of utility functions and reusable components
that should be of use in any Java environment.

Starting with Commons Lang 3.9, we target Java 8, making use of those features.

For advice on upgrading from 2.x to 3.x, see:

https://commons.apache.org/lang/article3_0.html

Apache Commons Lang, a package of Java utility classes for the classes
that are in java.lang's hierarchy, or are considered to be so standard
as to justify existence in java.lang.

New features and bug fixes (Java 8 or above).

Historical list of changes:
https://commons.apache.org/proper/commons-lang/changes-report.html

For complete information on Apache Commons Lang, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons Lang website:

https://commons.apache.org/proper/commons-lang/

Download page: https://commons.apache.org/proper/commons-lang/download_lang.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



Re: Issue in the Compress library extracting sparse tarballs

2023-11-24 Thread Gary Gregory
Hello Xudong Yang,

I do not see a pending JIRA request in my inbox for the name "Xudong
Yang", maybe someone else approved it already, otherwise, try again,
please.

In the meantime, the best way to move forward would be to create a PR
on GitHub with a failing unit test annotated with @Disabled but I am
not sure who will try to fix the issue or when.

TY,
Gary


On Tue, Nov 21, 2023 at 3:45 PM Xudong Yang  wrote:
>
> Hi there,
>
> We maintain the Bazel (https://bazel.build/) build system, which uses
> Apache Commons Compress to handle archive extraction. A user reported that
> a certain sparse tarball always triggers an error (
> https://github.com/bazelbuild/bazel/issues/20269#issuecomment-1821250607),
> and the steps to reproduce the error are very simple:
>
> #!/usr/bin/env bash
>
> set -o errexit -o nounset
>
> echo "Downloading commons-compress"
> wget 
> https://repo1.maven.org/maven2/org/apache/commons/commons-compress/1.25.0/commons-compress-1.25.0.jar
> echo "Downloading sample sparse archive"
> wget 
> https://github.com/astral-sh/ruff/releases/download/v0.1.6/ruff-aarch64-apple-darwin.tar.gz
> gunzip ruff-aarch64-apple-darwin.tar.gz
>
> echo "Testing with system tar"
> tar -tf ruff-aarch64-apple-darwin.tar
> echo "Testing with commons-compress"
> java -jar commons-compress-1.25.0.jar ruff-aarch64-apple-darwin.tar
>
> ->
>
> Testing with system tar
> ruff
> Testing with commons-compress
> Analysing ruff-aarch64-apple-darwin.tar
> Created 
> org.apache.commons.compress.archivers.tar.TarArchiveInputStream@17f052a3
> ruff
> Exception in thread "main" java.io.IOException: Truncated TAR archive
> at 
> org.apache.commons.compress.archivers.tar.TarArchiveInputStream.read(TarArchiveInputStream.java:694)
> at 
> org.apache.commons.compress.utils.IOUtils.readFully(IOUtils.java:244)
> at org.apache.commons.compress.utils.IOUtils.skip(IOUtils.java:355)
> at 
> org.apache.commons.compress.archivers.tar.TarArchiveInputStream.getNextTarEntry(TarArchiveInputStream.java:451)
> at 
> org.apache.commons.compress.archivers.tar.TarArchiveInputStream.getNextEntry(TarArchiveInputStream.java:426)
> at 
> org.apache.commons.compress.archivers.tar.TarArchiveInputStream.getNextEntry(TarArchiveInputStream.java:50)
> at 
> org.apache.commons.compress.archivers.Lister.listStream(Lister.java:79)
> at org.apache.commons.compress.archivers.Lister.main(Lister.java:133)
>
>
> I tried to file an issue on JIRA but my account signup is pending approval.
> The signup page asked me to try the mailing list, so here goes.
>
> -X

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



[ANNOUNCE] Apache Commons Compress 1.25.0

2023-11-17 Thread Gary Gregory
The Apache Commons team announces Commons Compress version 1.25.0

Apache Commons Compress defines an API for working with compression
and archive formats. These include bzip2, gzip, pack200, LZMA, XZ,
Snappy, traditional Unix Compress, DEFLATE,  EFLATE64, LZ4, Brotli,
Zstandard and ar, cpio, jar, tar, zip, dump, 7z, arj.

Apache Commons Compress defines an API for working with compression
and archive formats.  These include: bzip2, gzip, pack200, LZMA, XZ,
Snappy, traditional Unix Compress, DEFLATE, DEFLATE64, LZ4, Brotli,
Zstandard and ar, cpio, jar, tar, zip, dump, 7z, arj.

This is a minor feature and maintenance release.

Historical list of changes:
https://commons.apache.org/proper/commons-compress/changes-report.html

For complete information on Apache Commons Compress, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons Compress website:

https://commons.apache.org/proper/commons-compress/

Download page: 
https://commons.apache.org/proper/commons-compress/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



Re: Dependency problem in commons-text 1.11.0?

2023-10-30 Thread Gary Gregory
The site is up to date and is published after released binaries are
propagated to mirrors and maven central.

You are likely bringing in Lang transitive from elsewhere. You can either
list Text first in your dependencies or add a direct dependency on Lang
first.

Gary


On Mon, Oct 30, 2023, 10:39 AM Hans.Sebastian IT-DL-DK-SC <
hans.sebast...@swm.de> wrote:

> Hello!
>
>
>
> yesterday, Renovate Bot generated a pull request to update commons-text
> from 1.10.0 to 1.11.0 in my application. This version is not listed in the 
> release
> history
> , so
> I guess it is not released officially, but it *is* published. Anyway,
> tests failed with the following exception.
>
>
>
> java.lang.NoSuchMethodError: 'org.apache.commons.lang3.Range
> org.apache.commons.lang3.Range.of(java.lang.Comparable,
> java.lang.Comparable)'
>
> at
> org.apache.commons.text.translate.NumericEntityEscaper.(NumericEntityEscaper.java:97)
>
> at
> org.apache.commons.text.translate.NumericEntityEscaper.between(NumericEntityEscaper.java:59)
>
> at
> org.apache.commons.text.StringEscapeUtils.(StringEscapeUtils.java:271)
>
>
>
> Apparently, commons-text 1.11.0 uses Range.of(java.lang.Comparable,
> java.lang.Comparable), which appears to have been added to commons-lang3 in
> version 3.13.0. My application does not use commons-lang3 directly, so it
> is transitively pulled in by commons-text, but with version 3.12.0, which
> does not have Range.of(java.lang.Comparable, java.lang.Comparable).
> Manually adding commons-lang 3.13.0 to my POM fixes the problem.
>
>
>
> Is there an error in the commons-text POM?
>
>
>
> Kind regards,
>
> Sebastian Hans
>


[ANNOUNCE] Apache Commons Text 1.11.0

2023-10-30 Thread Gary Gregory
The Apache Commons Team announces Apache Commons Text version 1.11.0

Apache Commons Text is a set of utility functions and reusable
components for the purpose of processing and manipulating text that
should be of use in a Java environment.

Release 1.11.0. Requires Java 8.

Historical list of changes:
https://commons.apache.org/proper/commons-text/changes-report.html

For complete information on Apache Commons Text, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons Text website:

https://commons.apache.org/proper/commons-text

Download page: https://commons.apache.org/proper/commons-text/download_text.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



Re: commons-text upgrade 1.10.0 -> 1.11.0 java.lang.NoSuchMethodError

2023-10-30 Thread Gary Gregory
Right, you can let Text transitively bring in Lang.

Gary

On Mon, Oct 30, 2023 at 7:56 AM Alex Herbert  wrote:
>
> On Mon, 30 Oct 2023 at 09:40, Greg Huber  wrote:
> >
> > Hello,
> >
> > Upgrading  commons-text  to 1.11.0,  I get now this error
> >
> > SEVERE: Servlet.service() for servlet [PageServlet] threw exception
> >
> > java.lang.NoSuchMethodError: 'org.apache.commons.lang3.Range
> > org.apache.commons.lang3.Range.of(java.lang.Comparable,
> > java.lang.Comparable)'
> >
> >  at
> > org.apache.commons.text.translate.NumericEntityEscaper.(NumericEntityEscaper.java:97)
> >
> >  at
> > org.apache.commons.text.translate.NumericEntityEscaper.between(NumericEntityEscaper.java:59)
> >
> >  at
> > org.apache.commons.text.StringEscapeUtils.(StringEscapeUtils.java:271)
> >
> > calling org.apache.commons.text.StringEscapeUtils.escapeHtml4(str);
> >
> > the jar I have is:
> >
> > commons-lang3-3.12.0.jar
> >
> > Is there anything I need to do here?
>
> Commons Text 1.11.0 depends on Commons Lang 3.13.0 [1].
>
> Try upgrading Commons Lang and see if this resolves your issue.
>
> [1] https://commons.apache.org/proper/commons-text/dependencies.html
>
> -
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
>

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



[ANNOUNCE] Apache Commons CLI 1.6.0

2023-10-27 Thread Gary Gregory
The Apache Commons team announces Apache Commons CLI 1.6.0.

Apache Commons CLI provides a simple API for working with the command
line arguments and options.

This release contains small new features and bug fixes

Historical list of changes:
https://commons.apache.org/proper/commons-cli/changes-report.html

For complete information on Apache Commons CLI, including instructions
on how to submit bug reports, patches, or suggestions for improvement,
see the Apache Commons CLI website:

https://commons.apache.org/proper/commons-cli/

Download page: https://commons.apache.org/proper/commons-cli/download_cli.cgi

Have fun!
Gary Gregory
- The Apache Commons Team

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



[ANNOUNCE] Apache Commons IO 2.15.0

2023-10-26 Thread Gary Gregory
The Apache Commons team announces Apache Commons IO Version 2.15.0

Commons IO is a package of Java utility classes like java.io. Classes
in this package are considered so standard and of such high reuse as
to justify their 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



Re: [commons-fileupload2-jakarta] JakartaServletFileUpload.getItemIterator() not working in 2.0.0-M1

2023-10-08 Thread Gary Gregory
Please provide a PR so tye build checks can run.

TY,
Gary

On Sun, Oct 8, 2023, 11:52 AM Maxim Solodovnik  wrote:

> Here is the patch inlined (not sure if it worth PR ... )
>
> 
> diff --git
> a/commons-fileupload2-jakarta-servlet5/src/test/java/org/apache/commons/fileupload2/jakarta/servlet5/JakartaServletFileUploadTest.java
>
> b/commons-fileupload2-jakarta-servlet5/src/test/java/org/apache/commons/fileupload2/jakarta/servlet5/JakartaServletFileUploadTest.java
> index 06b8de62..b3f1c772 100644
> ---
> a/commons-fileupload2-jakarta-servlet5/src/test/java/org/apache/commons/fileupload2/jakarta/servlet5/JakartaServletFileUploadTest.java
> +++
> b/commons-fileupload2-jakarta-servlet5/src/test/java/org/apache/commons/fileupload2/jakarta/servlet5/JakartaServletFileUploadTest.java
> @@ -19,8 +19,10 @@ package org.apache.commons.fileupload2.jakarta.servlet5;
>  import static org.junit.jupiter.api.Assertions.assertEquals;
>  import static org.junit.jupiter.api.Assertions.assertTrue;
>
> +import java.io.InputStream;
>  import java.nio.charset.StandardCharsets;
>  import java.util.List;
> +import java.util.concurrent.atomic.AtomicInteger;
>
>  import org.apache.commons.fileupload2.core.AbstractFileUploadTest;
>  import org.apache.commons.fileupload2.core.Constants;
> @@ -107,6 +109,22 @@ public class JakartaServletFileUploadTest
>
>  assertTrue(mappedParameters.containsKey("multi"));
>  assertEquals(2, mappedParameters.get("multi").size());
> +
> +final var itemCount = new AtomicInteger(0);
> +upload.getItemIterator(request).forEachRemaining(item -> {
> +itemCount.incrementAndGet();
> +String name = item.getFieldName();
> +InputStream stream = item.getInputStream();
> +if (item.isFormField()) {
> +System.out.println("Form field " + name + " with value "
> ++ " detected.");
> +} else {
> +System.out.println("File field " + name + " with file
> name "
> ++ item.getName() + " detected.");
> +// Process the input stream
> +}
> +});
> +assertEquals(4, itemCount.get());
>  }
>
>  @Override
>
> On Fri, 29 Sept 2023 at 19:00, Gary Gregory 
> wrote:
> >
> > Please provide a patch attached to a Jira ticket or a PR for a failing
> unit
> > test to make it simple for a maintainer to help you out.
> >
> > Gary
> >
> > On Thu, Sep 28, 2023, 12:39 AM Maxim Solodovnik 
> > wrote:
> >
> > > Hello,
> > >
> > > I've tried to check this one :)
> > >
> > > Modified this test:
> > >
> > >
> commons-fileupload2-jakarta-servlet5/src/test/java/org/apache/commons/fileupload2/jakarta/servlet5/JakartaServletFileUploadTest.java
> > >
> > > Add this block at the bottom:
> > >
> > > ```
> > > final var itemCount = new AtomicInteger(0);
> > > upload.getItemIterator(new JakartaMockServletHttpRequest(bytes,
> > > Constants.CONTENT_TYPE)).forEachRemaining(item -> {
> > > String name = item.getFieldName();
> > > InputStream stream = item.getInputStream();
> > > if (item.isFormField()) {
> > > System.out.println("Form field " + name + " with value " + "
> > > detected.");
> > > } else {
> > > System.out.println("File field " + name + " with file name " +
> > > item.getName() + " detected.");
> > > // Process the input stream
> > > }
> > > });
> > > assertEquals(4, itemCount.get());
> > > ```
> > >
> > > The test is GREEN
> > >
> > > BUT
> > >
> > > if i try to reuse previously created request like this:
> > >
> > > ```
> > > upload.getItemIterator(request).forEachRemaining(item -> {
> > > ```
> > >
> > > The test will fail
> > >
> > >
> > > Is it be possible request was already iterated before
> > > `forEachRemaining` was called?
> > >
> > > On Thu, 28 Sept 2023 at 08:31, Gary Gregory 
> > > wrote:
> > > >
> > > > Hi,
> > > >
> > > > The best way to help would be to provide a PR on GitHub with a
> failing
> > > > test, and if you find it, a fix.
> > > >
> > > >

[ANNOUNCEMENT] Apache Commons Net 3.10.0

2023-10-06 Thread Gary Gregory
The Apache Commons Net team is pleased to announce the release of
Apache Commons Net 3.10.0.

Apache Commons Net library contains a collection of network utilities
and protocol implementations. Supported protocols include Echo,
Finger, FTP, NNTP, NTP, POP3(S), SMTP(S), Telnet, and Whois.

Maintenance and bug fix release (Java 8).

For complete information on Apache Commons Net, including instructions
on how to submit bug reports, patches, or suggestions for improvement,
see the Apache Commons Net website:

https://commons.apache.org/proper/commons-net/

Download page: https://commons.apache.org/proper/commons-net/download_net.cgi

Historical list of changes:
https://commons.apache.org/proper/commons-net/changes-report.html

Enjoy!
Gary Gregory
-Apache Commons Net team

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



Re: [io] Encoding bug in XmlStreamReader in Commons IO 2.14.0?

2023-10-03 Thread Gary Gregory
Feel free to provide a PR on GitHub where the unit test must fail if main
changes are not applied. You can also provide a PR that only contains a
unit test.

Gary


On Tue, Oct 3, 2023, 4:13 AM Laurence Gonsalves  wrote:

> Hello,
>
> It looks like XmlStreamReader is not correctly handling several encodings
> in Commons IO 2.14.0 that previously worked in version 2.13.0.
>
> Here's a self-contained snippet (Kotlin) that demonstrates the problem:
>
> val xml = "Ç"
>
> val stream = xml.byteInputStream(Charset.forName("437"))
>
> val reader = XmlStreamReader.builder()
> .setInputStream(stream)
> .setLenient(false)
> .get()
>
> reader.readText() shouldBe xml
>
> With 2.13.0 this code works fine, but in 2.14.0 the "Ç" (C-cedilla) becomes
> a "�" (Unicode replacement character).
>
> We're seeing similar issues with all of the other code page encodings we've
> tried (850, 852, 855, 857, 860, 861, 862, 863, 865, and 866).
>


[ANNOUNCEMENT] Apache Commons IO 2.14.0

2023-09-30 Thread Gary Gregory
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



Re: [commons-fileupload2-jakarta] JakartaServletFileUpload.getItemIterator() not working in 2.0.0-M1

2023-09-29 Thread Gary Gregory
Please provide a patch attached to a Jira ticket or a PR for a failing unit
test to make it simple for a maintainer to help you out.

Gary

On Thu, Sep 28, 2023, 12:39 AM Maxim Solodovnik 
wrote:

> Hello,
>
> I've tried to check this one :)
>
> Modified this test:
>
> commons-fileupload2-jakarta-servlet5/src/test/java/org/apache/commons/fileupload2/jakarta/servlet5/JakartaServletFileUploadTest.java
>
> Add this block at the bottom:
>
> ```
> final var itemCount = new AtomicInteger(0);
> upload.getItemIterator(new JakartaMockServletHttpRequest(bytes,
> Constants.CONTENT_TYPE)).forEachRemaining(item -> {
> String name = item.getFieldName();
> InputStream stream = item.getInputStream();
> if (item.isFormField()) {
> System.out.println("Form field " + name + " with value " + "
> detected.");
> } else {
> System.out.println("File field " + name + " with file name " +
> item.getName() + " detected.");
> // Process the input stream
> }
> });
> assertEquals(4, itemCount.get());
> ```
>
> The test is GREEN
>
> BUT
>
> if i try to reuse previously created request like this:
>
> ```
> upload.getItemIterator(request).forEachRemaining(item -> {
> ```
>
> The test will fail
>
>
> Is it be possible request was already iterated before
> `forEachRemaining` was called?
>
> On Thu, 28 Sept 2023 at 08:31, Gary Gregory 
> wrote:
> >
> > Hi,
> >
> > The best way to help would be to provide a PR on GitHub with a failing
> > test, and if you find it, a fix.
> >
> > Gary
> >
> >
> > On Wed, Sep 27, 2023, 7:33 PM Ian Evans 
> > wrote:
> >
> > > Using the following library:
> > >
> > > 
> > > org.apache.commons
> > > commons-fileupload2-jakarta
> > > 2.0.0-M1
> > > 
> > >
> > > The Streaming API (documented here FileUpload – The Streaming API (
> > > apache.org)<
> > > https://commons.apache.org/proper/commons-fileupload/streaming.html>)
> > > does not return any items. I've tested the following code using
> postman and
> > > curl to send a multipart/form-data request, in both cases
> getItemIterator
> > > fails to return any items (internally it seems an exceptio is thrown):
> > >
> > >
> > >  public ResponseEntity upload(HttpServletRequest request) throws
> > > IOException {
> > > if (!JakartaServletFileUpload.isMultipartContent(request)) {
> > > throw new IllegalArgumentException("not multipart");
> > > }
> > >
> > > JakartaServletFileUpload upload = new
> JakartaServletFileUpload();
> > >
> > > upload.getItemIterator(request).forEachRemaining(item -> {
> > > String name = item.getFieldName();
> > > InputStream stream = item.getInputStream();
> > > if (item.isFormField()) {
> > > System.out.println("Form field " + name + " with value
> "
> > > + convertInputStreamToString(stream) + "
> > > detected.");
> > > } else {
> > > System.out.println("File field " + name + " with file
> name
> > > "
> > > + item.getName() + " detected.");
> > > // Process the input stream
> > > }
> > > });
> > > ...
> > > }
> > >
> > > If I can help diagnose the issue in any way I'm more than happy.
> > >
> > >
> > >
> > >
>
>
>
> --
> Best regards,
> Maxim
>
> -
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
>
>


Re: [commons-fileupload2-jakarta] JakartaServletFileUpload.getItemIterator() not working in 2.0.0-M1

2023-09-27 Thread Gary Gregory
Hi,

The best way to help would be to provide a PR on GitHub with a failing
test, and if you find it, a fix.

Gary


On Wed, Sep 27, 2023, 7:33 PM Ian Evans 
wrote:

> Using the following library:
>
> 
> org.apache.commons
> commons-fileupload2-jakarta
> 2.0.0-M1
> 
>
> The Streaming API (documented here FileUpload – The Streaming API (
> apache.org)<
> https://commons.apache.org/proper/commons-fileupload/streaming.html>)
> does not return any items. I've tested the following code using postman and
> curl to send a multipart/form-data request, in both cases getItemIterator
> fails to return any items (internally it seems an exceptio is thrown):
>
>
>  public ResponseEntity upload(HttpServletRequest request) throws
> IOException {
> if (!JakartaServletFileUpload.isMultipartContent(request)) {
> throw new IllegalArgumentException("not multipart");
> }
>
> JakartaServletFileUpload upload = new JakartaServletFileUpload();
>
> upload.getItemIterator(request).forEachRemaining(item -> {
> String name = item.getFieldName();
> InputStream stream = item.getInputStream();
> if (item.isFormField()) {
> System.out.println("Form field " + name + " with value "
> + convertInputStreamToString(stream) + "
> detected.");
> } else {
> System.out.println("File field " + name + " with file name
> "
> + item.getName() + " detected.");
> // Process the input stream
> }
> });
> ...
> }
>
> If I can help diagnose the issue in any way I'm more than happy.
>
>
>
>


Re: Updating Apache Commons DBCP 2.10.0

2023-09-26 Thread Gary Gregory
The build works on Java 8 because the moditect plug-in is only invoked on
Java 11 and up.

Gary


On Tue, Sep 26, 2023, 4:00 PM Phil Steitz  wrote:

> On Tue, Sep 26, 2023 at 4:50 AM Gary Gregory 
> wrote:
>
> > (Let's stop high jacking the announcement thread.)
> >
>
> Agreed.  Sorry about that.
>
> >
> > In the future, FYI, I plan on supporting both Java and Jakarta by
> splitting
> > DBCP into a multi-module Maven project. I'm not sure exactly when but
> it's
> > on my to do list.
> >
>
> That sounds good.  But we may need to do something before that to restore
> backward compatibility (if there is in fact a problem).  The build error
> that Greg reports below is somehow related to the Commons Parent 62
> version.  If I back rev Commons Parent to version 60 and revert the JTA
> spec jar change (per below), the build works.  (Greg - can you try that -
> just change Commons Parent version to 60 along with the change below).
>
> Alternatively, maybe there is some other workaround to avoid the conflict
> that Greg is reporting.  I am not sure if there is in fact a backward
> compat issue here.  Any better ideas?
>
> One more thing is the EPL/GPL license on the Jakarta jars.   Have these
> been cleared for use (as dependencies) in ASF projects? Do we need some
> kind of notice for this?
>
> Phil
>
> >
> > Gary
> >
> >
> >
> > On Tue, Sep 26, 2023, 5:00 AM Greg Huber  wrote:
> >
> > > If I am understanding this correctly, I replace
> > >
> > > 
> > > 
> > >   jakarta.transaction
> > >   jakarta.transaction-api
> > >   1.3.1
> > > 
> > >
> > > with
> > >
> > > 
> > > org.apache.geronimo.specs
> > > geronimo-jta_1.1_spec
> > > 1.1.1
> > > true
> > > 
> > >
> > > in the source of 2.10.0 pom.xml and then mvn clean package.
> > >
> > > I get this error
> > >
> > > [ERROR] Failed to execute goal
> > > org.moditect:moditect-maven-plugin:1.0.0.Final:add-module-info
> > > (add-module-infos) on project commons-dbcp2: Execution add-module-infos
> > > of goal org.moditect:moditect-maven-plugin:1.0.0.Final:add-module-info
> > > failed: No assignedModuleName provided for jar with invalid module
> name:
> > >
> >
> ~/.m2/repository/org/apache/geronimo/specs/geronimo-jta_1.1_spec/1.1.1/geronimo-jta_1.1_spec-1.1.1.jar
> > >
> > > -> [Help 1]
> > >
> > > #
> > >
> > >
> > > I did a diff of my apps /lib folder between the 2.10.0 and 2.9.0
> > >
> > > Only in ~/downloads/commons-dbcp2-2.10.0-src/target/lib.9:
> > > commons-dbcp2-2.9.0.jar
> > > Only in ~/downloads/commons-dbcp2-2.10.0-src/target/lib.10:
> > > commons-dbcp2-2.10.0.jar
> > >
> > > Only in ~/downloads/commons-dbcp2-2.10.0-src/target/lib.9:
> > > commons-pool2-2.10.0.jar
> > > Only in ~/downloads/commons-dbcp2-2.10.0-src/target/lib.10:
> > > commons-pool2-2.11.1.jar
> > >
> > > Only in ~/downloads/commons-dbcp2-2.10.0-src/target/lib.9:
> > > jakarta.transaction-api-2.0.1.jar
> > > Only in ~/downloads/commons-dbcp2-2.10.0-src/target/lib.10:
> > > jakarta.transaction-api-1.3.1.jar
> > >
> > >
> > > If I copy lib.9: jakarta.transaction-api-2.0.1.jar to replace the
> > > lib.10: jakarta.transaction-api-1.3.1.jar class
> > > ThreadLocalSessionContextNoAutoClose compiles and works.
> > >
> > > Cheers Greg
> > >
> > > On 25/09/2023 18:49, Phil Steitz wrote:
> > > > Thanks, Greg.  I assume that dependency was there and working with
> DBCP
> > > > 2.9, correct?
> > > >
> > > > Can you try reverting the pom change above, replacing the
> > > > Jakarta transactions reference with
> > > >
> > > > 
> > > >org.apache.geronimo.specs
> > > >geronimo-jta_1.1_spec
> > > >1.1.1
> > > >true
> > > > 
> > > >
> > > > Then recompile DBCP from 2.10 sources and test (just use mvn clean
> > > package
> > > > from the root of an extract of the source distribution).
> > > >
> > > > Phil
> > > >
> > > > On Mon, Sep 25, 2023 at 12:44 AM Greg Huber 
> > wrote:
> > > >
> > > >>>> does your code maybe bring in the 2.

Updating Apache Commons DBCP 2.10.0

2023-09-26 Thread Gary Gregory
   */
> >>   protected boolean isAutoFlushEnabled() {
> >>   return false;
> >>   }
> >>
> >>   /**
> >>* Uses super.buildOrObtainSession(), then sets the
> >> resulting
> >>* Session's flush mode to
> FlushMode.NEVER
> >> to
> >>* prevent auto-flushing.
> >>*
> >>* @return A session configured with FlushMode.NEVER.
> >>*/
> >>   protected Session buildOrObtainSession() {
> >>   Session s = super.buildOrObtainSession();
> >>   s.setHibernateFlushMode(FlushMode.MANUAL);
> >>   return s;
> >>   }
> >>
> >>   /**
> >>* Returns an instance of CleanupSynch which prevents
> >> auto
> >>* closing and unbinding.
> >>*
> >>* @return A CleanupSynch which prevents auto
> closing and
> >>* unbinding.
> >>*/
> >>   protected CleanupSync buildCleanupSynch() {
> >>   return new NoCleanupSynch(factory());
> >>   }
> >>
> >>   /**
> >>* A simple extension of CleanupSynch that prevents
> >> any cleanup
> >>* from happening. No session closing or unbinding.
> >>*/
> >>   private static class NoCleanupSynch
> >>   extends ThreadLocalSessionContext.CleanupSync {
> >>
> >>   private static final long serialVersionUID =
> >> -6191453375299821467L;
> >>
> >>   /**
> >>* Creates a new instance based on the given factory.
> >>*
> >>* @param factory The required SessionFactory
> that is
> >>*passed to the super constructor.
> >>*/
> >>   public NoCleanupSynch(SessionFactory factory) {
> >>   super(factory);
> >>   }
> >>
> >>   /**
> >>* Does nothing, thus helping to prevent session closing
> and/or
> >>* unbinding.
> >>*/
> >>   public void beforeCompletion() {
> >>   // do nothing
> >>   }
> >>
> >>   /**
> >>* Does nothing, thus helping to prevent session closing
> and/or
> >>* unbinding.
> >>*
> >>* @param i
> >>*/
> >>   public void afterCompletion(int i) {
> >>   // do nothing
> >>   }
> >>   }
> >>
> >> }
> >>
> >> Thanks.
> >>
> >> On 24/09/2023 20:34, Phil Steitz wrote:
> >>> On Sun, Sep 24, 2023 at 10:28 AM Greg Huber
> wrote:
> >>>
> >>>> Forgot to add, I use hibernate 6.
> >>>>
> >>> I suspect this is a side effect of the change to use the jakarta spec
> jar
> >>>
> >>> In 2.10, we have
> >>>
> >>> 
> >>>   jakarta.transaction
> >>>   jakarta.transaction-api
> >>>   1.3.1
> >>> 
> >>>
> >>> vs
> >>>
> >>> 
> >>> org.apache.geronimo.specs
> >>> geronimo-jta_1.1_spec
> >>> 1.1.1
> >>> true
> >>> 
> >>>
> >>> in 2.9.  What I don't get is where Greg's code is picking
> >>> up jakarta.transaction.Synchronization because the jakarta version we
> >>> "upgraded" to still exports the javax classes and these are what dbcp
> >>> uses.  Greg - does your code maybe bring in the 2.0 jakarta spec jar?
> >>>
> >>> Phil
> >>>
> >>>
> >>>> Cheers.
> >>>>
> >>>> On Sun, 24 Sept 2023 at 12:49, Gary Gregory
> >>>> wrote:
> >>>>
> >>>>> What else has changed in your app?
> >>>>>
> >>>>> Gary
> >>>>>
> >>>>> On Sun, Sep 24, 2023 at 5:13 AM Greg Huber
> >> wrote:
> >>>>>> Hello,
> >>>>>>
> >>>>>> On upgrading from 2.9.0 I get this message and my class won't
> compile.
> >>>>>>
> >>>>>> I get this error
> >>>>>>
> >>>>>> The 

Re: [ANNOUNCEMENT] Apache Commons DBCP 2.10.0

2023-09-24 Thread Gary Gregory
What else has changed in your app?

Gary

On Sun, Sep 24, 2023 at 5:13 AM Greg Huber  wrote:
>
> Hello,
>
> On upgrading from 2.9.0 I get this message and my class won't compile.
>
> I get this error
>
> The type jakarta.transaction.Synchronization cannot be resolved. It is
> indirectly referenced from required type
> org.hibernate.context.internal.ThreadLocalSessionContext.CleanupSync
>
> I am on :
>
> openjdk version "11.0.19" 2023-04-18 LTS
> OpenJDK Runtime Environment Zulu11.64+19-CA (build 11.0.19+7-LTS)
> OpenJDK 64-Bit Server VM Zulu11.64+19-CA (build 11.0.19+7-LTS, mixed mode)
>
> Not too sure what I need to do to fix this.
>
> Cheers
>
> On 03/09/2023 22:51, Gary Gregory wrote:
> > The Apache Commons DBCP team is pleased to announce the release of
> > Apache Commons DBCP 2.10.0.
> >
> > Apache Commons DBCP software implements Database Connection Pooling.
> >
> > This is a minor release, including bug fixes and enhancements:
> > https://commons.apache.org/proper/commons-dbcp/changes-report.html#a2.10.0
> >
> > For complete information on Apache Commons DBCP, including
> > instructions on how to submit bug reports, patches, or suggestions for
> > improvement, see the Apache Commons DBCP website:
> >
> > https://commons.apache.org/dbcp/
> >
> > Download page: https://commons.apache.org/dbcp/download_dbcp.cgi
> >
> > Gary Gregory
> > Apache Commons
> >
> > -
> > To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> > For additional commands, e-mail: user-h...@commons.apache.org
> >
>
> -
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
>

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



Re: [EMAIL] Jakarta version of commons-email ?

2023-09-22 Thread Gary Gregory
There is no time-line ATM. It's on my too list. With weeks to a few months.

Gary

On Fri, Sep 22, 2023, 9:19 AM John Muczynski
 wrote:

> Re: commons-email
>
> My project uses commons-email and I’m upgrading to Sprint Boot 3. This
> means the transition from javax.mail -> jakarta.mail
>
> What’s the timeline look like for releasing a commons-email that fully
> supports jakarta.mail ?
>
> Thanks,
> John
>
>


Re: Is commons-jxpath still maintained?

2023-09-22 Thread Gary Gregory
It's still alive but there is not much activity. I might push out a release
candidate in the future to support JPMS.

Gary

On Fri, Sep 22, 2023, 7:10 AM Debraj Manna  wrote:

> Hi
>
> We are using commons-jxpath 1.3 but the last release was done about 7 years
> ago. There are some open vulnerabilities also in 1.3 version. Can someone
> let me know if this project is still maintained or if I should be using
> some other dependency instead of the one below?
>
> 
> commons-jxpath
> commons-jxpath
> 1.3
> 
>
> If this is not the right mailing list for asking this query can you please
> point me to the correct mailing list?
>


[ANNOUNCEMENT] Apache Commons DbUtils 1.8.1

2023-09-15 Thread Gary Gregory
The Apache Commons DbUtils team is pleased to announce the release of
Apache Commons DbUtils 1.8.1

The Apache Commons DbUtils package is a set of Java utility classes
for easing JDBC development.

Changes in this version include:

Fixed Bugs:
o DBUTILS-151:  Module org.apache.commons.dbutils does not declare
`uses`. Thanks to mark, Gary Gregory.

Changes:
o Bump commons-parent from 61 to 62. Thanks to Gary Gregory.

For complete information on Apache Commons DbUtils, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons DbUtils website:

https://commons.apache.org/proper/commons-dbutils/

Download it from
https://commons.apache.org/proper/commons-dbutils/download_dbcp.cgi

Gary Gregory
Apache Commons Team

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



[ANNOUNCEMENT] Apache Commons Compress 1.24.0

2023-09-09 Thread Gary Gregory
The Apache Commons Team announces Apache Commons Compress 1.24.0.

Apache Commons Compress defines an API for working with compression
and archive formats. These include: bzip2, gzip, pack200, lzma, xz,
Snappy, traditional Unix Compress, DEFLATE, DEFLATE64, LZ4, Brotli,
Zstandard and ar, cpio, jar, tar, zip, dump, 7z, arj.

New features, fixed bugs, and changes:
https://commons.apache.org/proper/commons-compress/changes-report.html#a1.24.0

For complete information on Apache Commons Compress, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons Compress website:

https://commons.apache.org/compress/

Download it from https://commons.apache.org/compress/download_compress.cgi

Gary Gregory,
Apache Commons

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



Re: [Exec] connect to already running process

2023-09-04 Thread Gary Gregory
I can't say there is enough in the text below to advise you. If you think
there is a bug, you could create a failing uni test that anyone watching
this list could try to debug or review no guarantees though. If there
is a bug in the library, then that's a different iissue ;-)

Gary

On Sun, Aug 13, 2023, 8:34 AM Mohd. Rizwan Ansari 
wrote:

> Hi guys,
> I was using apache commons exec to run a child process(worker) from a
> parent process(agent). agent takes care of monitoring(start,stop,restore)
> worker..and it works great.
> Now my use case is to connect to already running worker...and not start a
> new one, when the agent is restarted.
> Im creating a class ExistingProcess.java which extends Process, and in
> waitFor() it's waiting until it keeps finding a cmd process running with by
> its ID, which normally works but for connecting to an already running
> worker...it's throwing Exception.
> Ideas on what I may be missing? or alternative ways to achieve the same.
> Thanks,
>


[ANNOUNCEMENT] Apache Commons DBCP 2.10.0

2023-09-03 Thread Gary Gregory
The Apache Commons DBCP team is pleased to announce the release of
Apache Commons DBCP 2.10.0.

Apache Commons DBCP software implements Database Connection Pooling.

This is a minor release, including bug fixes and enhancements:
https://commons.apache.org/proper/commons-dbcp/changes-report.html#a2.10.0

For complete information on Apache Commons DBCP, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons DBCP website:

https://commons.apache.org/dbcp/

Download page: https://commons.apache.org/dbcp/download_dbcp.cgi

Gary Gregory
Apache Commons

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



Re: [COMPRESS] Gracefully handling multiple compressor streams with garbage at end

2023-08-15 Thread Gary Gregory
Hm, I see where it is throwing the exception. Would you create a Jira
ticket for this feature request and attach at least one example gz file and
a failing JUnit test?

TY,
Gary

On Tue, Aug 15, 2023, 12:31 PM Tim Allison  wrote:

> Gary,
>
> I'm sorry for my delay.  I'm just back to the keyboard from some time away.
>
> This is an example from the gz stream.  We had similar messages from some
> bzip2 and xz.
>
> Caused by: java.io.IOException: Garbage after a valid .gz stream
> at
> org.apache.commons.compress.compressors.gzip.GzipCompressorInputStream.init(GzipCompressorInputStream.java:240)
> at
> org.apache.commons.compress.compressors.gzip.GzipCompressorInputStream.read(GzipCompressorInputStream.java:391)
> at
> org.apache.commons.io.input.ProxyInputStream.read(ProxyInputStream.java:205)
> at java.base/java.io
> .BufferedInputStream.fill(BufferedInputStream.java:252)
> at java.base/java.io
> .BufferedInputStream.read1(BufferedInputStream.java:292)
> at java.base/java.io
> .BufferedInputStream.read(BufferedInputStream.java:351)
> at
> org.apache.commons.io.input.ProxyInputStream.read(ProxyInputStream.java:205)
>
> Thank you!
>
> On 2023/07/29 14:49:23 Gary Gregory wrote:
> > Hi Tim,
> >
> > Do you have a stack trace? Maybe this is an option we can add...
> >
> > Gary
> >
> > On Wed, Jul 26, 2023, 3:22 PM Tim Allison  wrote:
> >
> > > We recently had a request to change our default behavior to turn on
> > > processing multiple/concatenated compressor streams for gzip, bzip2,
> etc.
> > > When we made this change and compared the updated results with our
> previous
> > > results, we lost quite a few attachments because of the "garbage after
> a
> > > valid x" exception and because of how we're buffering/digesting the
> stream.
> > >
> > > Is there any way to turn on extraction of concatenated compressor
> streams,
> > > but have it silently stop reading instead of throwing a garbage
> exception?
> > >
> > > Thank you!
> > >
> > > Best,
> > >
> > > Tim
> > >
> > >
> > > [0] https://issues.apache.org/jira/browse/TIKA-4048
> > >
> >
>
> -
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
>
>


[ANNOUNCEMENT] Apache Commons DbUtils 1.8.0

2023-08-09 Thread Gary Gregory
The Apache Commons DbUtils team is pleased to announce the release of
Apache Commons DbUtils 1.8.0.

The Apache Commons DbUtils package is a set of Java utility classes
for easing JDBC development.

This is a feature and bug fix release, read the change log here:
https://commons.apache.org/proper/commons-dbutils/changes-report.html#a1.8.0

For complete information on Apache Commons DbUtils, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons DbUtils website:

https://commons.apache.org/proper/commons-dbutils/

Download it from
https://commons.apache.org/proper/commons-dbutils/download_dbcp.cgi

Enjoy,
Gary Gregory
Apache Commons Team

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



Re: [commons-collections4] Next release

2023-08-01 Thread Gary Gregory
K, give me a heads up when you think it is time...

Gary

On Tue, Aug 1, 2023, 7:19 PM Alex Herbert  wrote:

> On Tue, 1 Aug 2023 at 14:31, Gary Gregory  wrote:
> >
> > That all sounds good.
> >
> > Do you all feel the API will be stable and final enough for a 4.5.0
> release
> > or that we should release a milestone 4.5.0-M1 first?
>
> Given the frequency of changes that are still taking place I don't
> think it wise to set the bloomfilter package API as stable. An M1
> would be useful to get community feedback here.
>
> Alex
>
> -
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
>
>


Re: [commons-collections4] Next release

2023-08-01 Thread Gary Gregory
That all sounds good.

Do you all feel the API will be stable and final enough for a 4.5.0 release
or that we should release a milestone 4.5.0-M1 first?

Gary

On Tue, Aug 1, 2023, 9:26 AM Claude Warren  wrote:

> There are currently 3 planned Bloom filter changes.  The first is [1], the
> second [2] is waiting for 1 to land before being completed, and the final
> one is a Stable bloom filter implementation [3] is waiting for the second
> to land to reduce the size of the change.
>
> [1] https://github.com/apache/commons-collections/pull/406
> [2] https://github.com/apache/commons-collections/pull/402
> [3] https://github.com/Claudenw/BloomFilters/tree/stable
>
> On Sat, Jul 29, 2023 at 2:15 PM Gary Gregory 
> wrote:
>
> > I think we are waiting for the new bloom filter package to settle on a
> > final public (and protected) API.
> >
> > Gary
> >
> > On Sat, Jul 29, 2023 at 6:44 AM Vadim Meshcheryakov 
> > wrote:
> > >
> > > Hello everyone.
> > >
> > > The latest version of commons-collections4 is 4.4, which was issued
> four
> > > years ago. When is the next release scheduled? I guess it is time for
> > 4.5.
> > >
> > > Thank you
> > > Vadim
> >
> > -
> > To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> > For additional commands, e-mail: user-h...@commons.apache.org
> >
> >
>
> --
> LinkedIn: http://www.linkedin.com/in/claudewarren
>


Re: commons-cli: Trouble understanding the purpose of optionalArg method

2023-08-01 Thread Gary Gregory
The tests have to cover both deprecated and current APIs.

Gary

On Mon, Jul 31, 2023, 12:18 PM Sruteesh Kumar
 wrote:

> But all the test cases are following deprecated OptionBuilder class right?
> optionalArg is handled differently in OptionBuilder and Option.builder()
> and that's where I got confused
>
>  Original Message 
> On 31 Jul 2023, 8:27 pm, Gary Gregory wrote:
>
> > Please have a look at the unit tests and the web site, the combination
> of those two is a good way to see the API in action. Gary On Mon, Jul 31,
> 2023, 9:58 AM Sruteesh Kumar  wrote: > What does it mean when
> optionalArg(true) is called for building an option? > > As per my
> understanding, it may or may not take an argument. But in this > case,
> getOptionValue is giving null even when a value is given after the > option
> > > For example, if args = {"-foo","value"} and option = >
> Option.builder().option("f").longOpt("foo").optionalArg(true).build(). In >
> this case, getOptionValue is returning null. But, as per my understanding,
> > it should return value > > Thank you, > Sruteesh Kumar Paramata


Re: commons-cli: Trouble understanding the purpose of optionalArg method

2023-07-31 Thread Gary Gregory
Please have a look at the unit tests and the web site, the combination of
those two is a good way to see the API in action.

Gary


On Mon, Jul 31, 2023, 9:58 AM Sruteesh Kumar
 wrote:

> What does it mean when optionalArg(true) is called for building an option?
>
> As per my understanding, it may or may not take an argument. But in this
> case, getOptionValue is giving null even when a value is given after the
> option
>
> For example, if args = {"-foo","value"} and option =
> Option.builder().option("f").longOpt("foo").optionalArg(true).build(). In
> this case, getOptionValue is returning null. But, as per my understanding,
> it should return value
>
> Thank you,
> Sruteesh Kumar Paramata


Re: commons daemon - Error (Cannot find any VM in Java Home)

2023-07-31 Thread Gary Gregory
Hello,

Can you confirm that the _only_ thing that changes from one test to the
other is the JAVA_HOME value? What about the PATH?

Gary

On Mon, Jul 24, 2023, 5:59 PM Harsha Thota 
wrote:

> Hello,
>
> I am an active user of the apache commons daemon.
> I am trying to get the JSVC run with Java 11 and getting this error-
> "Cannot find any VM in Java Home".
> I am running the JSVC on linux. The commons-daemon version we're using is
> 1.3.4. Java version is 11 (we use adoptopenjfk
>  >
> ).
> I verified that "java_home" is set correctly. The same application runs
> without any issues with Java 8.
> Please let me know if there is any way to fix this issue. I tried
> everything I could and was not able to fix the issue. Please advise.
>
> Thanks,
> Harsha Thota
>


Re: EOS/EOL Date

2023-07-31 Thread Gary Gregory
Right, this is not an Apache project!

Gary

On Mon, Jul 31, 2023, 5:41 AM Ruby Paasche  wrote:

> Hallo Pranav,
>
> as far as I can, see it's not from apache,
>
> And looking at the Github page [1] you will see, that is a dead project.
>
> The README stated:
> *IMPORTANT NOTE: cglib is unmaintained and does not work well (or possibly
> at all?) in newer JDKs, particularly JDK17+. If you need to support newer
> JDKs, we will accept well-tested well-thought-out patches... but you'll
> probably have better luck migrating to something like ByteBuddy
> .*
>
> Best regards,
> Ruby
>
> [1] https://github.com/cglib/cglib
>
>
>
>
>
> ‑‑​
> Ruby Paasche
> Senior Entwicklerin
> Tel:
> +49 (0)89 45 22 808 ‑ 30
> Email:
> r.paas...@pripares.com
> Web:
> https://pripares.com
> [image: LinkedIn] 
> PRIPARES Software Solutions GmbH
> Ridlerstraße 57
> 80339 München
> Handelsregister: Registergericht München HRB 138701
> Sitz der Gesellschaft: München
> Geschäftsführer: Aßmann Christoph, Ertl Andreas
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
> löschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
> Weitergabe dieser Mail und der darin enthaltenen Informationen sind nicht
> gestattet.
>
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and delete this e-mail. Any
> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden.
> Am Mo., 31. Juli 2023 um 11:35 Uhr schrieb Pranav Kumar (EXT)
> :
>
>> Hi,
>>
>> Could you please share End of life/End of support detail or any EoS
>> criteria that is followed:
>>
>>
>>   *   CGLIB Version 3.3.0
>>
>>
>> Regards,
>> Pranav
>>
>>


Re: VFS: Multiple providers registered for URL scheme "file"

2023-07-31 Thread Gary Gregory
Hello Jenny,

You should not need to call init(). That's likely the cause of the problem.

Gary



On Mon, Jul 31, 2023, 12:30 AM Jenny Kwan  wrote:

> Hi,
>
> I'm getting started with VFS, using version 2.9.0. I'm calling
> `VFS.getManager().init()`, and getting the exception:
>
> org.apache.commons.vfs2.FileSystemException: Multiple providers registered
> for URL scheme "file".
>
> This is the cause of:
>
> org.apache.commons.vfs2.FileSystemException: Could not load VFS
> configuration from
>
> "jar:file:/home//.m2/repository/org/apache/commons/commons-vfs2/2.9.0/commons-vfs2-2.9.0.jar!/org/apache/commons/vfs2/impl/providers.xml".
>
> I checked out the jar and it looks fine; the providers.xml file has the
> single provider for the file scheme, right after the default
> UrlFileProvider.
>
> I happen to be using Clojure with Leiningen. I checked out `lein classpath`
> and there's no duplicate entry for this jar.
>
> What should I be looking for?
>
> Thanks,
> Jenny
>


Re: Issue: Can not find Apache Commons DbUtils version 1.8

2023-07-30 Thread Gary Gregory
There is no version 1.8, what you see on the github site is a reflection of
whatever is in the master branch.

I'll take a look over the weekend at what tye state of the code is...

Gary

On Sun, Jul 30, 2023, 5:05 AM sharedata  wrote:

> Apache Commons DbUtils1.7 version have thread bugs in BeanProcessor
> class via SPI ServiceLoader.
>
> Apache Commons DbUtilsgithub website have declared version 1.8, but
> the apache officialwebsite and maven repository all still stay in 1.7
> old version.
>
>
>
>
> See:
>
> https://github.com/apache/commons-dbutils
>
> https://commons.apache.org/proper/commons-dbutils/download_dbutils.cgi
>
> https://mvnrepository.com/artifact/commons-dbutils/commons-dbutils


Re: [COMPRESS] Gracefully handling multiple compressor streams with garbage at end

2023-07-29 Thread Gary Gregory
Hi Tim,

Do you have a stack trace? Maybe this is an option we can add...

Gary

On Wed, Jul 26, 2023, 3:22 PM Tim Allison  wrote:

> We recently had a request to change our default behavior to turn on
> processing multiple/concatenated compressor streams for gzip, bzip2, etc.
> When we made this change and compared the updated results with our previous
> results, we lost quite a few attachments because of the "garbage after a
> valid x" exception and because of how we're buffering/digesting the stream.
>
> Is there any way to turn on extraction of concatenated compressor streams,
> but have it silently stop reading instead of throwing a garbage exception?
>
> Thank you!
>
> Best,
>
> Tim
>
>
> [0] https://issues.apache.org/jira/browse/TIKA-4048
>


Re: [commons-collections4] Next release

2023-07-29 Thread Gary Gregory
I think we are waiting for the new bloom filter package to settle on a
final public (and protected) API.

Gary

On Sat, Jul 29, 2023 at 6:44 AM Vadim Meshcheryakov  wrote:
>
> Hello everyone.
>
> The latest version of commons-collections4 is 4.4, which was issued four
> years ago. When is the next release scheduled? I guess it is time for 4.5.
>
> Thank you
> Vadim

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



[ANNOUNCEMENT] Apache Commons Lang 3.13.0

2023-07-28 Thread Gary Gregory
The Apache Commons Team is pleased to announce Apache Commons Lang 3.13.0.

Apache Commons Lang is a package of Java utility classes for the
classes that are in java.lang's hierarchy, or are considered to be so
standard as to justify existence in java.lang.

Historical list of changes:
https://commons.apache.org/proper/commons-lang/changes-report.html

For complete information on Apache Commons Lang, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons Lang website:

https://commons.apache.org/proper/commons-lang/

Download page: https://commons.apache.org/proper/commons-lang/download_lang.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



Re: SCXML maven artifact

2023-07-27 Thread Gary Gregory
And yes, we use Jira for issue tracking.

Gary

On Thu, Jul 27, 2023, 9:16 AM proton_mail_bridge
 wrote:

> Hello, I am trying to use the latest maven artifact of commons-scxml2. The
> projects readme on GitHub suggests to use version 2.0-alpha-1, but [2.0-M1](
> https://mvnrepository.com/artifact/org.apache.commons/commons-scxml2/2.0-M1)
> (2014) is the latest version that’s indexed. Is there a way to use the more
> recent alpha build via maven without downloading the binaries?
>
> And is the projects JIRA the best way to see open issues? If there is any
> work blocking a more current release, I would be happy to contribute.
>
> - Jason


Re: SCXML maven artifact

2023-07-27 Thread Gary Gregory
Hi Jason,

The current version is in git master and the Maven snapshot repository (
https://repository.apache.org/snapshots/) as version 2.0-SNAPSHOT.

Gary

On Thu, Jul 27, 2023, 9:16 AM proton_mail_bridge
 wrote:

> Hello, I am trying to use the latest maven artifact of commons-scxml2. The
> projects readme on GitHub suggests to use version 2.0-alpha-1, but [2.0-M1](
> https://mvnrepository.com/artifact/org.apache.commons/commons-scxml2/2.0-M1)
> (2014) is the latest version that’s indexed. Is there a way to use the more
> recent alpha build via maven without downloading the binaries?
>
> And is the projects JIRA the best way to see open issues? If there is any
> work blocking a more current release, I would be happy to contribute.
>
> - Jason


[ANNOUNCE] Apache Commons FileUpload 2.0.0-M1

2023-07-20 Thread Gary Gregory
The Apache Commons FileUpload Parent team is pleased to announce the
release of Apache Commons FileUpload Parent 2.0.0-M1.

The Apache Commons FileUpload component provides a simple yet flexible
means of adding support for multipart file upload functionality to
servlets and web applications. This version requires Java 8 or later
and supports both the jakarta and javax namespaces.

For complete information on Apache Commons FileUpload, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons FileUpload Parent website:

https://commons.apache.org/proper/commons-fileupload/

Download it from:

https://commons.apache.org/proper/commons-fileupload/download_fileupload.cgi

Enjoy,
Gary Gregory
Apache Commons, PMC

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



Re: [Lang] Advice on "Diff" usage

2023-07-11 Thread Gary Gregory
I updated the Javadoc for both classes.

Gary


On Mon, Jul 10, 2023, 13:40 Gilles Sadowski  wrote:

> Le dim. 9 juil. 2023 à 19:32, Gary Gregory  a
> écrit :
> >
> > How about the reflection variant? You won't need to edit any of the
> target
> > code.
>
> Thanks, I missed it.  [Maybe worth adding a "@see ReflectionDiffBuilder"
> tag in "DiffBuilder" (and vice-versa) ?]
>
> However, the output is much too verbose when the "Container" is a
> large object.  For example, in my case, the number of reported
> differences is
>   11
> but the "toString()" outputs a line that is
>   371397
> characters long...
> Is there a way to only print the (primitive) fields for which the values
> differ?  [It seems (?) that if, deep down the composite "Container",
> something is different then all the enclosing instances are considered
> different (it's true) and printed in full.]
>
> Also, the "MULTI_LINE_STYLE" is somewhat inconsistent: It does
> indeed print each field of the top-level object on a new line, but it
> does not apply this layout to the "composing" objects: Referring to
> the example quoted below, the array "contentArr" would be printed on
> a single line (in my use case, that line is 183312 characters long).]
>
> For large objects, this makes it quite difficult  to spot what differences
> were actually detected...
>
> Regards,
> Gilles
>
> >
> > Gary
> >
> >
> > On Sun, Jul 9, 2023, 09:51 Gilles Sadowski  wrote:
> >
> > > Hi.
> > >
> > > In the Javadoc of the "DiffBuilder" class[1]:
> > > ---CUT---
> > > [...]
> > > To use this class, write code as follows:
> > >
> > >  public class Person implements Diffable {
> > >String name;
> > >int age;
> > >boolean smoker;
> > > [...]
> > > ---CUT---
> > >
> > > However, a common use-case would be that we can't directly
> > > modify the class whose instances we want to compare.
> > > Assuming that interfaces are given and non-modifiable (i.e.
> > > they cannot implement "Diffable"):
> > > ---CUT---
> > > public interface Content {
> > >  double getValue();
> > > }
> > >
> > > public interface Container {
> > > Content[] getContentArray();
> > > }
> > > ---CUT---
> > > and the modifiable user code is similar to
> > > ---CUT---
> > > public class MyContent implements Content {
> > > private final double c;
> > >
> > > public MyContent(double input) {
> > > c = input:
> > > }
> > >
> > > @Override
> > > public double getValue() {
> > > return c;
> > > }
> > > }
> > >
> > > public class MyContainer implements Container {
> > > private final Content[] contentArr;
> > >
> > > MyContainer(double ... inputs) {
> > > final int len = inputs.length;
> > > contentArr = new Content[len];
> > > for (int i = 0; i < len; i++) {
> > > contentArr[i] = new MyContent(inputs[i]);
> > > }
> > > }
> > >
> > > @Override
> > > public Content[] getContentArray() {
> > > return contentArr;
> > > }
> > > }
> > > ---CUT---
> > > how should I go about in order to get the "diff" between instances
> > > of "MyContainer"?
> > >
> > > Thanks,
> > > Gilles
> > >
> > > [1]
> > >
> https://commons.apache.org/proper/commons-lang/javadocs/api-release/org/apache/commons/lang3/builder/DiffBuilder.html
>
> -
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
>
>


  1   2   3   4   5   6   >