Re: Initializing asMapView in AbstractMultiValuedMap

2024-09-13 Thread Gary Gregory
I agree, field-to-field is a recipient for headaches. I think the
comparison should be done using the public API. An interesting tangent is
what Commons Lang's EqualsBuilder reflectionEquals API shows, likely
similar issues which is understandable.

Gary

On Fri, Sep 13, 2024, 11:11 AM Willi Schönborn 
wrote:

> I'm assuming that's a private field in which case it shouldn't be
> documented because it shouldn't be relied on in any way.
>
> My 2c
>
> On Fri, Sep 13, 2024, 16:09 Kaan Berk Yaman 
> wrote:
>
> > Hello,
> >
> > I was doing some testing with a record that has an
> > ArrayListValuedHashMap as one of its components. I use AssertJ to do a
> > deep, recursive, field-to-field comparison of the record. All of the
> > members of the list-valued map have respective `equals` and `hashCode`
> > implementations. I have, however, noticed that, when I have two equal
> > LV-maps, if I call `asMap` on one, AssertJ reports that the two
> > LV-valued maps are not equal, due to the `asMapView` field, which is
> > `null` for the other LV-map; this field seems to be initialized upon the
> > first call of `asMap`. The assertion runs through if I call `asMap` on
> > the other map, too.
> > It seems like `asMapView` is kept updated as long as `asMap` is called
> > at least once. Is this expected behaviour? If yes, I feel like this
> > should be documented somewhere; the Javadoc comment of `asMap` has no
> > mention of `asMapView` and how this field is used for caching.
> >
> > Thanks in advance.
> >
> > Kind regards
> > Kaan
> >
> >
> > -
> > To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> > For additional commands, e-mail: user-h...@commons.apache.org
> >
> >
>


Re: beanutils2 | Planned Release Date

2024-09-12 Thread Gary Gregory
We should have a release candidate within a month or so.

Gary

On Thu, Sep 12, 2024, 11:55 AM Modi, Vinay (Berkeley Heights)
 wrote:

> Apache Team
>
>
>
> Can someone please acknowledge or direct me to the right group
>
>
>
> Regards
>
> Vinay
>
>
>
> *From:* Modi, Vinay (Berkeley Heights)
> *Sent:* Tuesday, September 3, 2024 2:12 PM
> *To:* user@commons.apache.org; brit...@apache.org;
> simonetrip...@apache.org; mcucchi...@apache.org; grobme...@apache.org
> *Cc:* Commons Security 
> *Subject:* RE: beanutils2 | Planned Release Date
>
>
>
> Team
>
>
>
> Can someone please help me with an answer. Is there any plan to release a
> stable version of *BeanUtils2.*
>
>
>
> My understanding is that this is the way to step away from Apache Commons
> 3.2.2
>
>
>
> Sonatype rules indicate Apache Commons 3.2.2 as vulnerable.
>
>
>
> Regards
>
> Vinay
>
> *From:* Modi, Vinay (Berkeley Heights) 
> *Sent:* Thursday, August 29, 2024 9:13 AM
> *To:* user@commons.apache.org
> *Subject:* beanutils2 | Planned Release Date
>
>
>
>
>
> Good Afternoon. We at Fiserv use Apache commons libraries in our web
> applications.  I am just curious to know when is Apache planning to release
> a stable version of *BeanUtils2. *This is because we are still using
> BeanUtils which in turn has a dependency on Apache Commons 3.2.2
>
>
>
> A recent vulnerability discovered in Apache Commons 3.2.2 requires us to
> upgrade this version, which means a new version of BeanUtils that uses
> Apache Commons 4
>
>
>
> Appreciate your feedback/response.
>
>
>
>- There is a *resolution
>* to the 
> *vulnerability
>* available in
>commons-collections (*4.3
>
> *
>).
>
>
>
>
>
>  Regards
>
> Vinay
>


Re: beanutils2 | Planned Release Date

2024-09-03 Thread Gary Gregory
We are working towards a release but there is no schedule. I expect to
create a release candidate within the next few weeks.

Gary

On Tue, Sep 3, 2024, 2:20 PM Modi, Vinay (Berkeley Heights)
 wrote:

> Team
>
>
>
> Can someone please help me with an answer. Is there any plan to release a
> stable version of *BeanUtils2.*
>
>
>
> My understanding is that this is the way to step away from Apache Commons
> 3.2.2
>
>
>
> Sonatype rules indicate Apache Commons 3.2.2 as vulnerable.
>
>
>
> Regards
>
> Vinay
>
> *From:* Modi, Vinay (Berkeley Heights) 
> *Sent:* Thursday, August 29, 2024 9:13 AM
> *To:* user@commons.apache.org
> *Subject:* beanutils2 | Planned Release Date
>
>
>
>
>
> Good Afternoon. We at Fiserv use Apache commons libraries in our web
> applications.  I am just curious to know when is Apache planning to release
> a stable version of *BeanUtils2. *This is because we are still using
> BeanUtils which in turn has a dependency on Apache Commons 3.2.2
>
>
>
> A recent vulnerability discovered in Apache Commons 3.2.2 requires us to
> upgrade this version, which means a new version of BeanUtils that uses
> Apache Commons 4
>
>
>
> Appreciate your feedback/response.
>
>
>
>- There is a *resolution
>* to the 
> *vulnerability
>* available in
>commons-collections (*4.3
>
> *
>).
>
>
>
>
>
>  Regards
>
> Vinay
>


[ANNOUNCE] Apache Commons Lang 3.17.0

2024-08-29 Thread Gary Gregory
The Apache Commons team is pleased to announce Apache Commons Lang
Version 3.17.0.

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

Starting with Commons Lang 3.9, we target Java 8, using 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.

The code is tested using the latest revision of the JDK for supported
LTS releases: 8, 11, 17 and 21 currently. See
https://github.com/apache/commons-lang/blob/master/.github/workflows/maven.yml

Please ensure your build environment is up-to-date and kindly report
any build issues.

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

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

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: beanutils2 | Planned Release Date

2024-08-29 Thread Gary Gregory
We are planning to do so "soon", there are a small number of technical
issues that need to be addressed first. I'd say within 4 to 6 weeks.

Gary

On Thu, Aug 29, 2024 at 11:57 AM Modi, Vinay (Berkeley Heights)
 wrote:
>
>
> Good Afternoon. We at Fiserv use Apache commons libraries in our web 
> applications.  I am just curious to know when is Apache planning to release a 
> stable version of BeanUtils2. This is because we are still using BeanUtils 
> which in turn has a dependency on Apache Commons 3.2.2
>
> A recent vulnerability discovered in Apache Commons 3.2.2 requires us to 
> upgrade this version, which means a new version of BeanUtils that uses Apache 
> Commons 4
>
> Appreciate your feedback/response.
>
>
>   *   There is a 
> resolution to the 
> vulnerability 
> available in  commons-collections 
> (4.3).
>
>
>
>  Regards
> Vinay

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



Re: Issue with Commons Compress and setting last access time

2024-08-23 Thread Gary Gregory
Hello Nick,

If you can write this up in the form of a failing unit test, then we'll
have something to debug.

You can create a Jira ticket and attach it there or create a PR on GitHub.

TY!
Gary

On Fri, Aug 23, 2024, 6:40 PM Nicholas Woodward <
woodward.nicholas@gmail.com> wrote:

> Hello,
> I'm using Apache Commons Compress version 1.27.0 to create a zip archive
> and running into a problem when I set the creation, last modified and last
> access times of the ZipArchiveEntry objects. As I iterate over the files to
> add to the ZipArchiveOutputStream I set all three times to the same value
> like this:
>
> ...
> final FileTime time = FileTime.fromMillis(timeInMilliseconds);
> final ZipArchiveOutputStream zip = new ZipArchiveOutputStream(os));
> final ZipArchiveEntry entry = zip.createArchiveEntry(file, name);
> entry.setCreationTime(time);
> entry.setLastModifiedTime(time);
> entry.setLastAccessTime(time);
> zip.putArchiveEntry(entry);
> ...
>
> But when I open the zip archive after it has been created, not every file
> has the same times for those metadata fields. For example, all of the XML
> files in the zip archive have correctly set creation, last modified and
> last access times. The same is true with directories. But all other files
> in the archive, whether they are plain text or images or any other mime
> type, only have the correct creation and last modified times. None of them
> have the correct last access time.
>
> I cannot figure out why the setLastAccessTime() method works for one
> particular type of file but not any others. Has anyone else experienced
> this issue? Is there a solution that I'm missing? Thank you in advance for
> any information you can provide.
>
>
> Thanks,
> Nick W.
>
>
> ---
> Senior Software Engineer
> Texas Digital Library
>


[ANNOUNCE] Apache Commons Compress version 1.27.1

2024-08-20 Thread Gary Gregory
The Apache Commons Team is pleased to announce Commons Compress version 1.27.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.

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

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 Logging 1.3.4

2024-08-19 Thread Gary Gregory
The Apache Commons Logging team is pleased to announce the release of
Apache Commons Logging 1.3.4.

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

This is a 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


Re: [EMAIL] commons-emmail2 encountered error in java17

2024-08-17 Thread Gary Gregory
It looks like you are missing a Jar from your classpath. You could use
Maven to build your project which will automatically resolve your
dependencies, then look at its debug output to see what class path it built.

Gary

On Sat, Aug 17, 2024, 4:48 AM 송희경  wrote:

>  Hi.
> The Java version of the site I manage has changed, causing a problem with
> the HtmlEmail service using commons-email.
>
> - Environment Before Change
> - jdk1.7
> - spring 4.0.9
> - commons-email 1.3.2
>
> - Environment After Change
> - java17
> - spring 4.3.20
>
> I used java17 so I downloaded commons-email2.
> When I created and ran a simple application Java file on my local PC, I got
> an error.
>
> How do I solve this problem?
> Is there any more libraries I need?
> Is there a dependency issue between libraries?
> I want to know how to reliably send out HtmlEmail from Java17.
>
>
> Below is the classpath, source code, and error message.
>
> - local test smtp server : MailHog_windows_386.exe
>
> - SET CLASSPATH =
>
> %CLASSPATH%;C:\lib\commons-email2-core-2.0.0-M1.jar;C:\lib\commons-email2-jakarta-2.0.0-M1.jar;C:\lib\commons-email2-javax-2.0.0-M1.jar;C:\lib\jakarta.mail-api-2.0.1.jar;C:\lib\jakarta.mail-activation-api-2.0.1.jar;.;
>
>
> [HtmlEmail.java]  =
>
> import org.apache.commons.mail2.core.*;
> import org.apache.commons.mail2.jakarta.*;
> import jakarta.mail.*;
> import java.io.*;
>
> public class HtmlEmailTest {
>
> public static void main(String args[]) {
>sendMail();
> }
>
> public static void sendMail() {
>
> try {
> HtmlEmail email = new HtmlEmail();
> email.setHostName("localhost");
> email.setSmtpPort(1025);
> email.addTo("tot...@test.co.kr","toName");
> email.setFrom("fro...@test.go.kr",fromName");
> email.setSubject("mail send test");
> email.setHtmlMsg("test to send
> EmailContentscontent");
> email.setTextMsg("support HTML messages");
> email.send();
>
> } catch (Exception e) {
>  StringWriter sw = new StringWriter();
>  PrintWriter pw = new PrintWriter(sw);
>  e.printStackTrace(pw);
>  System.out.println(sw.toString());
> }
> }
> }
>
> [error msg]  =
>
> Exception in thread "main" java.lang.NoClassDefFoundError :
> com.sun.mail.util.PropUtil
> at jakarta.mail.internet.InternetAddress.(InternetAddress.java:62)
> at
>
> org.apache.commons.mail2.jakarta.Email.createInternetAddress(Email.java:633)
> at org.apache.commons.mail2.jakarta.Email.addTo(Email.java:491)
> at org.apache.commons.mail2.jakarta.Email.addTo(Email.java:477)
> at HtmlEmailTest.sendMail(HtmlEmailTest.java:35)
>


[ANNOUNCE] Apache Commons CLI Version 1.9.0

2024-08-14 Thread Gary Gregory
The Apache Commons team is please to announce Commons CLI Version 1.9.0.

Apache Commons CLI provides a simple API for presenting, processing,
and validating a Command Line Interface.

This release contains new features and bug fixes and requires Java 8 or above.

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 Compress 1.27.0

2024-08-08 Thread Gary Gregory
The Apache Commons team is pleased to announce Apache Commons Compress 1.27.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 is a feature and maintenance release. Java 8 or later is required.

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 Lang Version 3.16.0

2024-08-07 Thread Gary Gregory
The Apache Commons team is pleased to announce Apache Commons Lang
Version 3.16.0.

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

Starting with Commons Lang 3.9, we target Java 8, using 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.

The code is tested using the latest revision of the JDK for supported
LTS releases: 8, 11, 17 and 21 currently. See
https://github.com/apache/commons-lang/blob/master/.github/workflows/maven.yml

Please ensure your build environment is up-to-date and kindly report
any build issues.

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

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: Inquiry about Alternatives to commons-el Supporting Java 17

2024-08-05 Thread Gary Gregory
Anitha.

As you found, the closest match in the Commons project is JEXL:
https://commons.apache.org/proper/commons-jexl/

Related: BSF https://commons.apache.org/proper/commons-bsf/

Gary

On Mon, Aug 5, 2024 at 7:06 AM Anitha Ramatenki
 wrote:
>
> Dear Apache Commons Team,
>
> I hope this message finds you well.
>
> I am currently working on updating a Java project from Java 8 to Java 17. The 
> project makes extensive use of the commons-el library. However, I have 
> noticed that commons-el is no longer actively maintained, with the last 
> update being published in February 2013. It depends on javax.servlet package 
> which won't support JakartaEE 10.
>
> While researching alternatives, I came across Apache Commons JEXL. However, I 
> noted from the documentation that JEXL is not a compatible implementation of 
> the EL as defined in JSTL 1.1 (JSR-052) or JSP 2.0 (JSR-152) specifications. 
> Since my project requires compatibility with these specifications, I am 
> seeking guidance on the following:
>
>
>   *   Is there a recommended alternative within the Apache Commons family or 
> any other library that offers similar functionality to commons-el and 
> supports Java 17?
>   *   Are there any migration guides or best practices for transitioning from 
> commons-el to a more modern and supported library?
>
> Thank you for your time and assistance. I appreciate any guidance you can 
> provide.
>
> Thanks,
> Anitha
>

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



[ANNOUNCE] Apache Commons BCEL Version 6.10.0

2024-07-24 Thread Gary Gregory
The Apache Commons BCEL team is pleased to announce the release of
Apache Commons BCEL 6.10.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.

Maintenance and bug fix release. Requires a minimum of Java 8.

Historical list of changes:
https://commons.apache.org/proper/commons-bcel/changes-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: Compatibility Inquiry for Commons Validator with Java 17

2024-07-22 Thread Gary Gregory
The build passes on GitHub and I usually build release candidates with Java
17 these days, so you should OK to use Java 17. The only way to know for
certain is if your specific software stack passes it's tests on your
specific Java environment on your specific operating system.

Gary

On Mon, Jul 22, 2024, 2:40 AM Anitha Ramatenki 
wrote:

> Dear Apache Commons Team,
>
>
>
> Thank you, Gray,  for the response.
>
>
>
> I am currently working on Infor project that involves upgrading from java
> 8 to Java 17, and I am using the commons-validator library. According to
> the maven.yml (
> https://github.com/apache/commons-validator/commit/c87eba774db50ae15ed67c8e9617bea8c6feb2a5),
> it is stated that commons-validator has been tested with Java 17. However,
> I have a concern regarding its dependency on commons-logging, which in turn
> depends on javax.servlet-api (which is not compatible with java 17).
>
>
>
> Could you please confirm if commons-validator and its dependencies,
> particularly commons-logging are fully compatible with Java 17?
>
>
>
> Any insights or guidance you can provide would be greatly appreciated.
>
>
>
> Thank you for your time and assistance.
>
>
>
> Thanks,
>
> Anitha
>
> *From:* Gary Gregory 
> *Sent:* Wednesday, July 3, 2024 1:02 PM
> *To:* Commons Users List 
> *Cc:* Anitha Ramatenki ; Krishna Prasad
> Daggubati 
> *Subject:* Re: REG: Information on the commons Beanutils
>
>
>
> Sent by an external sender.  Please be cautious about clicking on links
> and opening attachments.
>
> 
>
>
> Hello Sasirekha,
>
>
>
> There is not but you can use the current release with Java 17. There are a
> handful of tasks that remain better 2.0. If you look at the GitHub CI,
> you'll see that we test with LTS versions.
>
>
>
> Gary
>
> On Wed, Jul 3, 2024, 2:45 AM Sasirekha Kumaran <
> sasirekha.kuma...@infor.com.invalid> wrote:
>
> Hello Team,
>
>
>
> This is Sasirekha from the Expense management team part of Infor. I am
> currently working on upgrading our project from JDK-8 to JDK-17, and we are
> using common Beanutils as a dependency. We are using commons
> beanutils-1.6.1 and when researching about the version compatible with the
> JDK-17. In the GitHub (
> https://github.com/apache/commons-beanutils?tab=readme-ov-file) it is
> mentioned for release 2.0.0 (commons-beanutils2). But it’s not released
> yet, is there a timeline for when it will be released?
>
>
>
> Thanks
>
> Sasirekha
>
>


[ANNOUNCE] Apache Commons Lang Version 3.15.0

2024-07-18 Thread Gary Gregory
The Apache Commons team is pleased to announce Apache Commons Lang
Version 3.15.0.

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

Starting with Commons Lang 3.9, we target Java 8, using 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.

The code is tested using the latest revision of the JDK for supported
LTS releases: 8, 11, 17 and 21 currently.

See 
https://github.com/apache/commons-lang/blob/master/.github/workflows/maven.yml

Please ensure your build environment is up-to-date and kindly report
any build issues.

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



[ANNOUNCE] Apache Commons Codec 1.17.1

2024-07-15 Thread Gary Gregory
The Apache Apache Commons team is pleased to announce Commons Codec 1.17.1.

The Apache Commons Codec component contains encoders and decoders for
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



[ANNOUNCE] Apache Commons Logging 1.3.3

2024-07-04 Thread Gary Gregory
The Apache Commons Logging team is pleased to announce the release of
Apache Commons Logging 1.3.3.

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: REG: Information on the commons beanutils release

2024-07-04 Thread Gary Gregory
There is not. There are a few tasks that remain like merging the one class
with a "2" postfix with its super. In the meantime, you can use 1.9.4.

Gary

On Thu, Jul 4, 2024, 4:10 AM Sasirekha Kumaran
 wrote:

> Hello Team,
>
> This is Sasirekha from Expense management team part of Infor. I am
> currently working on upgrading our project from JDK-8 to JDK-17, and we are
> using commons Beanutils as a dependency. We are using commons
> beanutils-1.6.1 and when researching about the version compatible with the
> JDK-17. In the GitHub (
> https://github.com/apache/commons-beanutils?tab=readme-ov-file) it
> mentioned for release 2.0.0 (commons-beanutils2). But it's not released
> yet, is there a timeline when it will be released.
>
> Thanks
> Sasirekha
>


Re: REG: Information on the commons Beanutils

2024-07-03 Thread Gary Gregory
Hello Sasirekha,

There is not but you can use the current release with Java 17. There are a
handful of tasks that remain better 2.0. If you look at the GitHub CI,
you'll see that we test with LTS versions.

Gary

On Wed, Jul 3, 2024, 2:45 AM Sasirekha Kumaran
 wrote:

> Hello Team,
>
>
>
> This is Sasirekha from the Expense management team part of Infor. I am
> currently working on upgrading our project from JDK-8 to JDK-17, and we are
> using common Beanutils as a dependency. We are using commons
> beanutils-1.6.1 and when researching about the version compatible with the
> JDK-17. In the GitHub (
> https://github.com/apache/commons-beanutils?tab=readme-ov-file) it is
> mentioned for release 2.0.0 (commons-beanutils2). But it’s not released
> yet, is there a timeline for when it will be released?
>
>
>
> Thanks
>
> Sasirekha
>


Re: EOL/EOS for Apache Commons Codec

2024-07-01 Thread Gary Gregory
Apache Commons Codec is alive and well.

In general, each component's website or the README file in its
repository should state if they are EOL.

Gary

On Mon, Jul 1, 2024 at 4:34 AM You Li Sia  wrote:
>
> Hi,
>
> I would like to find out where can we find out about the information of 
> EOL/EOS for Apache Commons Codec and other libraries?
>
> Thanks & Regards,
> Mr. Kaysier

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



Re: Malware scan failing

2024-07-01 Thread Gary Gregory
The tests intentionally include broken test fixtures, which is probably
what your scanner reports. These tests and their fixtures will remain.

Gary

On Mon, Jul 1, 2024, 3:03 AM Sahil Sharma D
 wrote:

> Hi Team,
>
> In commons compress  version 1.26.2, Can we remove these two jar files
> from the delivery of the commons compress  before installation? Are these
> jar files necessary for the installation? Are they are related to testing
> only? commons-compress-1.26.2-test-sources.jar and
> commons-compress-1.26.2-tests.jar
>
> The reason is that due to some tar files inside above two jar files, can
> not be open ,malware scan is failing
>
> Regards,
> Sahil
>
>


[ANNOUNCE] Apache Commons Email Parent POM 2.0.0-M1

2024-06-30 Thread Gary Gregory
The Apache Commons Email Parent POM team is pleased to announce the
release of Apache Commons Email Parent POM 2.0.0-M1.

Apache Commons Email provides an API for sending email, simplifying
the JavaMail API.

Feature release (Java 8 or above).

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

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

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

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

Enjoy!
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 Collections 4.5.0-M2

2024-06-18 Thread Gary Gregory
The Apache Commons team is pleased to announce Commons Collections
4.5.0-M2, the second milestone release toward 4.5.0. Commons
Collections contains types that extend and augment the Java
Collections Framework.

This milestone release requires Java 8 and makes small changes to the
package `org.apache.commons.collections4.bloomfilter`.

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 Configuration 2.11.0

2024-06-10 Thread Gary Gregory
The Apache Commons Team is pleased to announce Commons Configuration 2.11.0.

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

Commons Configuration includes tools to assist in reading
configuration/preference files in various formats; requires Java 8.

This is a minor release with new features and updated dependencies;
requires Java 8 or above.

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



[ANNOUNCE] Apache Commons Net 3.11.1

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

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.

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

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: Compatible version with openjdk21

2024-06-10 Thread Gary Gregory
Hello Sahil,

Each component is different. In general, most but not all components are
tested on GitHub CI with Java LTS versions (8, 11, 17, 21) plus the
current version (22) and sometimes the EA version (23). Have a look at the
GitHub repository for the components that matter to you.

HTH,
Gary


On Mon, Jun 10, 2024, 3:46 AM Sahil Sharma D
 wrote:

> Hello team,
>
> Which version of Apache commons is compatible with openjdk21?
>
> Regards,
> Sahil
>
>


Re: [ANNOUNCE] Apache Commons Net 3.11.0

2024-06-06 Thread Gary Gregory
I'll create a release candidate later today.

Thank you for testing!

Gary


On Thu, Jun 6, 2024, 12:33 PM Stuart Maclean 
wrote:

> Hi Gary, all,
>
> yes I did miss the fact that you had fixed the error.  I just consulted
> the sources and saw your fix, thanks for that.
>
> And I tested my exact same small test case w 3.11.1-SNAPSHOT (after
> adding that repo you mentioned to my pom) and it now WORKS where it
> FAILED w 3.11.0.
>
> Stuart
>
> On 6/6/24 02:56, Gary Gregory wrote:
> > Hi Stuart,
> >
> > You might have missed a reply in this thread, there were a few. I fixed
> the
> > issue in git master and 3.11.1-SNAPSHOT builds. Let us know.
> >
> > Thank you,
> > Gary
> >
> > On Thu, Jun 6, 2024, 1:42 AM Stuart Maclean 
> > wrote:
> >
> >> Hi Gary, all,
> >>
> >> following up to my post last week...
> >>
> >> I managed to discount the OAuth2 part being the culprit.
> >>
> >> The simplest code I can write that FAILS under commons net 3.11.0 but
> >> WORKS with 3.10.0, 3.9.0 and 3.8.0 is this
> >>
> >> AuthenticatingIMAPClient aic = new AuthenticatingIMAPClient(true);
> >> String server = "imap-mail.outlook.com";
> >> try {
> >>aic.connect( server );
> >> } catch( Exception e ) {
> >>e.printStackTrace();
> >> }
> >>
> >> When binding to the 3.11.0 commons net jar, the code above produces this
> >> on my (Linux) terminal:
> >>
> >> org.apache.commons.net.MalformedServerReplyException: Received
> >> unexpected IMAP protocol response from server: '* OK The Microsoft
> >> Exchange IMAP4 service is ready.
> >>
> >>
> [TQBXADQAUABSADAAMwBDAEEAMAAyADkAMwAuAG4AYQBtAHAAcgBkADAAMwAuAHAAcgBvAGQALgBvAHUAdABsAG8AbwBrAC4AYwBvAG0A]'.
> >>   at
> >> org.apache.commons.net.imap.IMAPReply.getReplyCode(IMAPReply.java:119)
> >>   at
> >>
> >>
> org.apache.commons.net.imap.IMAPReply.getUntaggedReplyCode(IMAPReply.java:130)
> >>   at org.apache.commons.net.imap.IMAP.getReply(IMAP.java:288)
> >>   at org.apache.commons.net.imap.IMAP._connectAction_(IMAP.java:152)
> >>   at
> >>
> >>
> org.apache.commons.net.imap.IMAPSClient._connectAction_(IMAPSClient.java:176)
> >>   at org.apache.commons.net
> >> .SocketClient._connect(SocketClient.java:142)
> >>   at org.apache.commons.net
> .SocketClient.connect(SocketClient.java:308)
> >>   at org.apache.commons.net
> .SocketClient.connect(SocketClient.java:290)
> >>   at org.apache.commons.net
> .SocketClient.connect(SocketClient.java:275)
> >>
> >> Under all earlier versions of the commons net jar mentioned, the
> >> connect() routine succeeds and no stack trace is printed.
> >>
> >> In my previous post, I had subbed in 'x' for the long string
> >> TQB... above, since I thought it might leak OAuth2 info. Given the above
> >> code doesn't get as far as offering any OAuth credentials, I can't see
> >> how the string above can be sensitive (famous last words!)
> >>
> >> I am running my code via 'mvn test'. My mvn set up is
> >>
> >> $ mvn -v
> >> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> >> Maven home: /home/stuart/Downloads/apache-maven-3.6.3
> >> Java version: 11.0.22, vendor: Ubuntu, runtime:
> >> /usr/lib/jvm/java-11-openjdk-amd64
> >> Default locale: en_US, platform encoding: UTF-8
> >> OS name: "linux", version: "5.15.0-107-generic", arch: "amd64", family:
> >> "unix"
> >>
> >> If I drive mvn with a Java 8 VM I get same results.
> >>
> >> Stuart
> >>
> >>
> >> On 5/31/24 13:39, Gary Gregory wrote:
> >>> Hello Stu,
> >>>
> >>> Thank you for your report.
> >>>
> >>> Does the issue occur using 3.9.0?
> >>>
> >>> What about 3.10.0?
> >>>
> >>> Do you have a way we can reproduce this issue?
> >>>
> >>> If not, you could run your test in a debugger and extract a
> reproducible
> >>> and a failing unit test.
> >>>
> >>> You could also use git bisect to find the first offending commit.
> >>>
> >>> TY!
> >>> Gary
> >>>
> >>> On Fri, May 31, 2024, 3:

Re: [ANNOUNCE] Apache Commons Net 3.11.0

2024-06-06 Thread Gary Gregory
Stuart,

The snapshot repository is here:
https://repository.apache.org/content/repositories/snapshots/

Gary

On Thu, Jun 6, 2024 at 5:56 AM Gary Gregory  wrote:
>
> Hi Stuart,
>
> You might have missed a reply in this thread, there were a few. I fixed the 
> issue in git master and 3.11.1-SNAPSHOT builds. Let us know.
>
> Thank you,
> Gary
>
> On Thu, Jun 6, 2024, 1:42 AM Stuart Maclean  
> wrote:
>>
>> Hi Gary, all,
>>
>> following up to my post last week...
>>
>> I managed to discount the OAuth2 part being the culprit.
>>
>> The simplest code I can write that FAILS under commons net 3.11.0 but
>> WORKS with 3.10.0, 3.9.0 and 3.8.0 is this
>>
>> AuthenticatingIMAPClient aic = new AuthenticatingIMAPClient(true);
>> String server = "imap-mail.outlook.com";
>> try {
>>   aic.connect( server );
>> } catch( Exception e ) {
>>   e.printStackTrace();
>> }
>>
>> When binding to the 3.11.0 commons net jar, the code above produces this
>> on my (Linux) terminal:
>>
>> org.apache.commons.net.MalformedServerReplyException: Received
>> unexpected IMAP protocol response from server: '* OK The Microsoft
>> Exchange IMAP4 service is ready.
>> [TQBXADQAUABSADAAMwBDAEEAMAAyADkAMwAuAG4AYQBtAHAAcgBkADAAMwAuAHAAcgBvAGQALgBvAHUAdABsAG8AbwBrAC4AYwBvAG0A]'.
>>  at
>> org.apache.commons.net.imap.IMAPReply.getReplyCode(IMAPReply.java:119)
>>  at
>> org.apache.commons.net.imap.IMAPReply.getUntaggedReplyCode(IMAPReply.java:130)
>>  at org.apache.commons.net.imap.IMAP.getReply(IMAP.java:288)
>>  at org.apache.commons.net.imap.IMAP._connectAction_(IMAP.java:152)
>>  at
>> org.apache.commons.net.imap.IMAPSClient._connectAction_(IMAPSClient.java:176)
>>  at org.apache.commons.net.SocketClient._connect(SocketClient.java:142)
>>  at org.apache.commons.net.SocketClient.connect(SocketClient.java:308)
>>  at org.apache.commons.net.SocketClient.connect(SocketClient.java:290)
>>  at org.apache.commons.net.SocketClient.connect(SocketClient.java:275)
>>
>> Under all earlier versions of the commons net jar mentioned, the
>> connect() routine succeeds and no stack trace is printed.
>>
>> In my previous post, I had subbed in 'x' for the long string
>> TQB... above, since I thought it might leak OAuth2 info. Given the above
>> code doesn't get as far as offering any OAuth credentials, I can't see
>> how the string above can be sensitive (famous last words!)
>>
>> I am running my code via 'mvn test'. My mvn set up is
>>
>> $ mvn -v
>> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
>> Maven home: /home/stuart/Downloads/apache-maven-3.6.3
>> Java version: 11.0.22, vendor: Ubuntu, runtime:
>> /usr/lib/jvm/java-11-openjdk-amd64
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "linux", version: "5.15.0-107-generic", arch: "amd64", family:
>> "unix"
>>
>> If I drive mvn with a Java 8 VM I get same results.
>>
>> Stuart
>>
>>
>> On 5/31/24 13:39, Gary Gregory wrote:
>> > Hello Stu,
>> >
>> > Thank you for your report.
>> >
>> > Does the issue occur using 3.9.0?
>> >
>> > What about 3.10.0?
>> >
>> > Do you have a way we can reproduce this issue?
>> >
>> > If not, you could run your test in a debugger and extract a reproducible
>> > and a failing unit test.
>> >
>> > You could also use git bisect to find the first offending commit.
>> >
>> > TY!
>> > Gary
>> >
>> > On Fri, May 31, 2024, 3:13 PM Stuart Maclean 
>> > wrote:
>> >
>> >> I have an app that uses Commons Net. It talks IMAP, via OAuth2, to a MS
>> >> Exchange Server.  With Commons Net 3.8.0 and 3.10.0, it works fine. I
>> >> just saw 3.11.0 was released, and wanted to try it. I was alarmed to see
>> >> it fail with my app. The ONLY change made to the build was in my
>> >> pom.xml, from this
>> >>
>> >>   
>> >> commons-net
>> >> commons-net
>> >> 3.8.0
>> >>   
>> >>
>> >>   
>> >> commons-net
>> >> commons-net
>> >> 3.11.0
>> >>   
>> >>
>> >> With 3.11.0, the app reports
>> >>
>> >> $ ./mailRetriever -e
>> >>
&

Re: [ANNOUNCE] Apache Commons Net 3.11.0

2024-06-06 Thread Gary Gregory
Hi Stuart,

You might have missed a reply in this thread, there were a few. I fixed the
issue in git master and 3.11.1-SNAPSHOT builds. Let us know.

Thank you,
Gary

On Thu, Jun 6, 2024, 1:42 AM Stuart Maclean 
wrote:

> Hi Gary, all,
>
> following up to my post last week...
>
> I managed to discount the OAuth2 part being the culprit.
>
> The simplest code I can write that FAILS under commons net 3.11.0 but
> WORKS with 3.10.0, 3.9.0 and 3.8.0 is this
>
> AuthenticatingIMAPClient aic = new AuthenticatingIMAPClient(true);
> String server = "imap-mail.outlook.com";
> try {
>   aic.connect( server );
> } catch( Exception e ) {
>   e.printStackTrace();
> }
>
> When binding to the 3.11.0 commons net jar, the code above produces this
> on my (Linux) terminal:
>
> org.apache.commons.net.MalformedServerReplyException: Received
> unexpected IMAP protocol response from server: '* OK The Microsoft
> Exchange IMAP4 service is ready.
>
> [TQBXADQAUABSADAAMwBDAEEAMAAyADkAMwAuAG4AYQBtAHAAcgBkADAAMwAuAHAAcgBvAGQALgBvAHUAdABsAG8AbwBrAC4AYwBvAG0A]'.
>  at
> org.apache.commons.net.imap.IMAPReply.getReplyCode(IMAPReply.java:119)
>  at
>
> org.apache.commons.net.imap.IMAPReply.getUntaggedReplyCode(IMAPReply.java:130)
>  at org.apache.commons.net.imap.IMAP.getReply(IMAP.java:288)
>  at org.apache.commons.net.imap.IMAP._connectAction_(IMAP.java:152)
>  at
>
> org.apache.commons.net.imap.IMAPSClient._connectAction_(IMAPSClient.java:176)
>  at org.apache.commons.net
> .SocketClient._connect(SocketClient.java:142)
>  at org.apache.commons.net.SocketClient.connect(SocketClient.java:308)
>  at org.apache.commons.net.SocketClient.connect(SocketClient.java:290)
>  at org.apache.commons.net.SocketClient.connect(SocketClient.java:275)
>
> Under all earlier versions of the commons net jar mentioned, the
> connect() routine succeeds and no stack trace is printed.
>
> In my previous post, I had subbed in 'x' for the long string
> TQB... above, since I thought it might leak OAuth2 info. Given the above
> code doesn't get as far as offering any OAuth credentials, I can't see
> how the string above can be sensitive (famous last words!)
>
> I am running my code via 'mvn test'. My mvn set up is
>
> $ mvn -v
> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> Maven home: /home/stuart/Downloads/apache-maven-3.6.3
> Java version: 11.0.22, vendor: Ubuntu, runtime:
> /usr/lib/jvm/java-11-openjdk-amd64
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "5.15.0-107-generic", arch: "amd64", family:
> "unix"
>
> If I drive mvn with a Java 8 VM I get same results.
>
> Stuart
>
>
> On 5/31/24 13:39, Gary Gregory wrote:
> > Hello Stu,
> >
> > Thank you for your report.
> >
> > Does the issue occur using 3.9.0?
> >
> > What about 3.10.0?
> >
> > Do you have a way we can reproduce this issue?
> >
> > If not, you could run your test in a debugger and extract a reproducible
> > and a failing unit test.
> >
> > You could also use git bisect to find the first offending commit.
> >
> > TY!
> > Gary
> >
> > On Fri, May 31, 2024, 3:13 PM Stuart Maclean  >
> > wrote:
> >
> >> I have an app that uses Commons Net. It talks IMAP, via OAuth2, to a MS
> >> Exchange Server.  With Commons Net 3.8.0 and 3.10.0, it works fine. I
> >> just saw 3.11.0 was released, and wanted to try it. I was alarmed to see
> >> it fail with my app. The ONLY change made to the build was in my
> >> pom.xml, from this
> >>
> >>   
> >> commons-net
> >> commons-net
> >> 3.8.0
> >>   
> >>
> >>   
> >> commons-net
> >> commons-net
> >> 3.11.0
> >>   
> >>
> >> With 3.11.0, the app reports
> >>
> >> $ ./mailRetriever -e
> >>
> >> org.apache.commons.net.MalformedServerReplyException: Received
> >> unexpected IMAP protocol response from server: '* OK The Microsoft
> >> Exchange IMAP4 service is ready.
> [x]'.
> >>   at
> >> org.apache.commons.net.imap.IMAPReply.getReplyCode(IMAPReply.java:119)
> >>   at
> >>
> >>
> org.apache.commons.net.imap.IMAPReply.getUntaggedReplyCode(IMAPReply.java:130)
> >>   at org.apache.commons.net.imap.IMAP.getReply(IMAP.java:288)
> >>   at org.apache.commons

[ANNOUNCE] Apache Commons JEXL 3.4.0

2024-06-05 Thread Gary Gregory
The Apache Commons team is pleased to announce Apache Commons JEXL 3.4.0.

Apache Commons JEXL is a library that facilitates the implementation
of scripting features in applications and frameworks written in Java.

Java 8 is required.

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

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

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

Download page: https://commons.apache.org/proper/commons-jexl/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: [ANNOUNCE] Apache Commons Validator 1.9.0

2024-06-04 Thread Gary Gregory
In this case, the dependency on 3.x will remain the same for the given
major release line for binary compatibility. When we want a Validator 2,
that when we can drop support for Collections 3.

HTH,
Gary

On Mon, Jun 3, 2024, 10:45 AM Amit Pande 
wrote:

> Hello Apache Commons Team,
>
> Reaching out to understand how to migrate to commons-collection4 from
> commons-collections3 given that commons-collection is transitive dependency
> of multiple other artifacts such as commons-validator, commons-beanutils.
>
>
> Thanks,
> Amit
>
>
>
> -Original Message-
> From: Gary Gregory 
> Sent: Tuesday, May 28, 2024 6:31 PM
> To: annou...@apache.org; Commons Developers List ;
> Commons Users List 
> Subject: [ANNOUNCE] Apache Commons Validator 1.9.0
>
>
> CAUTION: This email originated from outside the organization. Do not click
> links or open attachments unless you recognize the sender and know the
> content is safe. If you believe this is a phishing email, use the Report to
> Cybersecurity icon in Outlook.
>
>
>
> The Apache Commons Validator team is pleased to announce the release of
> Apache Commons Validator 1.9.0.
>
> Apache Commons Validator provides the building blocks for both client-side
> and server-side data validation. It may be used standalone or with a
> framework like Struts.
>
> This is a maintenance and bug fix release that requires Java 8.
>
> For complete information on Apache Commons Validator, including
> instructions on how to submit bug reports, patches, or suggestions for
> improvement, see the Apache Commons Validator website:
>
> http://commons.apache.org/proper/commons-validator/
>
> Download page:
> http://commons.apache.org/proper/commons-validator/download_validator.cgi
>
> Historical list of changes:
> http://commons.apache.org/proper/commons-validator/changes-report.html
>
> 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
>
>
> -
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
>
>


Re: [ANNOUNCE] Apache Commons Net 3.11.0

2024-05-31 Thread Gary Gregory
BTW, builds are here:
https://repository.apache.org/content/repositories/snapshots/

Gary

On Fri, May 31, 2024 at 5:26 PM Gary Gregory  wrote:
>
> Stu,
>
> What is the total length of the line?
>
> I've bumped it up in git master and 3.11.1-SNAPSHOT builds.
>
> TY,
> Gary
>
> On Fri, May 31, 2024, 5:04 PM Gary D. Gregory  wrote:
>>
>> Stu,
>>
>> Does the reply line read exactly:
>>
>> '* OK The Microsoft
>> Exchange IMAP4 service is ready. [x]'
>>
>> ?
>>
>> Are the x's really there or is that a placeholder? Are the spaces all plain 
>> spaces or tabs?
>>
>> TY,
>> Gary
>>
>> On 2024/05/31 19:11:11 Stuart Maclean wrote:
>> > I have an app that uses Commons Net. It talks IMAP, via OAuth2, to a MS
>> > Exchange Server.  With Commons Net 3.8.0 and 3.10.0, it works fine. I
>> > just saw 3.11.0 was released, and wanted to try it. I was alarmed to see
>> > it fail with my app. The ONLY change made to the build was in my
>> > pom.xml, from this
>> >
>> >  
>> >commons-net
>> >commons-net
>> >3.8.0
>> >  
>> >
>> >  
>> >commons-net
>> >commons-net
>> >3.11.0
>> >  
>> >
>> > With 3.11.0, the app reports
>> >
>> > $ ./mailRetriever -e
>> >
>> > org.apache.commons.net.MalformedServerReplyException: Received
>> > unexpected IMAP protocol response from server: '* OK The Microsoft
>> > Exchange IMAP4 service is ready. [x]'.
>> >  at
>> > org.apache.commons.net.imap.IMAPReply.getReplyCode(IMAPReply.java:119)
>> >  at
>> > org.apache.commons.net.imap.IMAPReply.getUntaggedReplyCode(IMAPReply.java:130)
>> >  at org.apache.commons.net.imap.IMAP.getReply(IMAP.java:288)
>> >  at org.apache.commons.net.imap.IMAP._connectAction_(IMAP.java:152)
>> >
>> > The app is trying to do an 'INBOX EXAMINE' request.
>> >
>> > I do see mention made of IMAPReply in the 3.11.0 release notes. Maybe I
>> > need to change my own code to use the IMAP objects differently?? Or
>> > maybe the flaw is the server end??
>> >
>> > Stu
>> >
>> >
>> > On 5/31/24 10:35, Gary Gregory wrote:
>> > > The Apache Commons Net team is pleased to announce the release of
>> > > Apache Commons Net 3.11.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 or above).
>> > >
>> > > 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
>> > >
>> >
>> > -
>> > 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: [ANNOUNCE] Apache Commons Net 3.11.0

2024-05-31 Thread Gary Gregory
Stu,

What is the total length of the line?

I've bumped it up in git master and 3.11.1-SNAPSHOT builds.

TY,
Gary

On Fri, May 31, 2024, 5:04 PM Gary D. Gregory  wrote:

> Stu,
>
> Does the reply line read exactly:
>
> '* OK The Microsoft
> Exchange IMAP4 service is ready. [x]'
>
> ?
>
> Are the x's really there or is that a placeholder? Are the spaces all
> plain spaces or tabs?
>
> TY,
> Gary
>
> On 2024/05/31 19:11:11 Stuart Maclean wrote:
> > I have an app that uses Commons Net. It talks IMAP, via OAuth2, to a MS
> > Exchange Server.  With Commons Net 3.8.0 and 3.10.0, it works fine. I
> > just saw 3.11.0 was released, and wanted to try it. I was alarmed to see
> > it fail with my app. The ONLY change made to the build was in my
> > pom.xml, from this
> >
> >  
> >commons-net
> >commons-net
> >3.8.0
> >  
> >
> >  
> >commons-net
> >commons-net
> >3.11.0
> >  
> >
> > With 3.11.0, the app reports
> >
> > $ ./mailRetriever -e
> >
> > org.apache.commons.net.MalformedServerReplyException: Received
> > unexpected IMAP protocol response from server: '* OK The Microsoft
> > Exchange IMAP4 service is ready.
> [x]'.
> >  at
> > org.apache.commons.net.imap.IMAPReply.getReplyCode(IMAPReply.java:119)
> >  at
> >
> org.apache.commons.net.imap.IMAPReply.getUntaggedReplyCode(IMAPReply.java:130)
> >  at org.apache.commons.net.imap.IMAP.getReply(IMAP.java:288)
> >  at org.apache.commons.net.imap.IMAP._connectAction_(IMAP.java:152)
> >
> > The app is trying to do an 'INBOX EXAMINE' request.
> >
> > I do see mention made of IMAPReply in the 3.11.0 release notes. Maybe I
> > need to change my own code to use the IMAP objects differently?? Or
> > maybe the flaw is the server end??
> >
> > Stu
> >
> >
> > On 5/31/24 10:35, Gary Gregory wrote:
> > > The Apache Commons Net team is pleased to announce the release of
> > > Apache Commons Net 3.11.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 or above).
> > >
> > > 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
> > >
> >
> > -
> > 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: [ANNOUNCE] Apache Commons Net 3.11.0

2024-05-31 Thread Gary Gregory
Hello Stu,

Thank you for your report.

Does the issue occur using 3.9.0?

What about 3.10.0?

Do you have a way we can reproduce this issue?

If not, you could run your test in a debugger and extract a reproducible
and a failing unit test.

You could also use git bisect to find the first offending commit.

TY!
Gary

On Fri, May 31, 2024, 3:13 PM Stuart Maclean 
wrote:

> I have an app that uses Commons Net. It talks IMAP, via OAuth2, to a MS
> Exchange Server.  With Commons Net 3.8.0 and 3.10.0, it works fine. I
> just saw 3.11.0 was released, and wanted to try it. I was alarmed to see
> it fail with my app. The ONLY change made to the build was in my
> pom.xml, from this
>
>  
>commons-net
>commons-net
>3.8.0
>  
>
>  
>commons-net
>commons-net
>3.11.0
>  
>
> With 3.11.0, the app reports
>
> $ ./mailRetriever -e
>
> org.apache.commons.net.MalformedServerReplyException: Received
> unexpected IMAP protocol response from server: '* OK The Microsoft
> Exchange IMAP4 service is ready. [x]'.
>  at
> org.apache.commons.net.imap.IMAPReply.getReplyCode(IMAPReply.java:119)
>  at
>
> org.apache.commons.net.imap.IMAPReply.getUntaggedReplyCode(IMAPReply.java:130)
>  at org.apache.commons.net.imap.IMAP.getReply(IMAP.java:288)
>  at org.apache.commons.net.imap.IMAP._connectAction_(IMAP.java:152)
>
> The app is trying to do an 'INBOX EXAMINE' request.
>
> I do see mention made of IMAPReply in the 3.11.0 release notes. Maybe I
> need to change my own code to use the IMAP objects differently?? Or
> maybe the flaw is the server end??
>
> Stu
>
>
> On 5/31/24 10:35, Gary Gregory wrote:
> > The Apache Commons Net team is pleased to announce the release of
> > Apache Commons Net 3.11.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 or above).
> >
> > 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
> >
>
> -
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
>
>


[ANNOUNCE] Apache Commons Net 3.11.0

2024-05-31 Thread Gary Gregory
The Apache Commons Net team is pleased to announce the release of
Apache Commons Net 3.11.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 or above).

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



[ANNOUNCE] Apache Commons Validator 1.9.0

2024-05-28 Thread Gary Gregory
The Apache Commons Validator team is pleased to announce the release
of Apache Commons Validator 1.9.0.

Apache Commons Validator provides the building blocks for both
client-side and server-side data validation. It may be used standalone
or with a framework like Struts.

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

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

http://commons.apache.org/proper/commons-validator/

Download page: 
http://commons.apache.org/proper/commons-validator/download_validator.cgi

Historical list of changes:
http://commons.apache.org/proper/commons-validator/changes-report.html

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: [NET] 451-Error during read from data connection

2024-05-28 Thread Gary Gregory
You can also test with a 3.11.0 snapshot build from git master or
https://repository.apache.org/content/repositories/snapshots/commons-net/commons-net/3.11.0-SNAPSHOT/

TY,
Gary

On Tue, Apr 23, 2024 at 7:14 AM Gary Gregory  wrote:
>
> 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

-
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.8.0

2024-05-23 Thread Gary Gregory
The Apache Commons Team is pleased to announce Apache Commons CLI Version 1.8.0.

Apache Commons CLI provides a simple API for presenting, processing,
and validating a Command Line Interface.

This release contains new features and bug fixes and requires Java 8 or above.

New Features


* CLI-332: Add optional HelpFormatter Function to document Deprecated
options #271. Thanks to Claude Warren, Gary Gregory.

* Add PMD check to default Maven goal. Thanks to Gary Gregory.

Fixed Bugs
--

* CLI-331: Handle reporting of deprecated options when parameters are
not String type. #270. Thanks to Claude Warren, Gary Gregory.

* Avoid throwing NullPointerException when calling CommandLineParser
will null array elements. Thanks to Claude Warren, Gary Gregory.

* Cleanup deprecation issues #272. Thanks to Claude Warren.

* Fix PMD UnnecessaryFullyQualifiedName issues. Thanks to Gary Gregory.

Updates
---

* Bump commons-parent from 69 to 70. Thanks to Gary Gregory.

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



Re: Why common-compress skip data by reading and discard?

2024-05-23 Thread Gary Gregory
Hello iseki,

The Javadoc explains all of this in detail.

Java 12 adds skipNBytes and IO is still based on Java 8.

Gary

On Thu, May 23, 2024, 6:30 AM iseki zero  wrote:

> Hello,
>
> When I reading the code of common-compress, I found it skip data using
> the `IOUtils.skip` in `commons-io` module.
>
> I found this method just reading the data and discard it directly. But
> in JDK there's an more effeciency method `InputStream.skip` and
> `InputStream.skipNBytes`.
>
> So why we read & discard data instead of call `skip*` directly?
>
> Thank you.
>
> iseki zero.
>
>
> -
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
>
>


Re: New release for commons jexl

2024-05-21 Thread Gary Gregory
Hello Lars,

We have two other release candidates in flight. I can push a release
candidate for JEXL soon though. Please make sure you test your app with git
master or a snapshot build.

TY!
Gary

On Tue, May 21, 2024, 4:21 AM Andringa, L.S.  wrote:

> Dear apache members,
>
> Would you happen to know when a new release is planned for Apache commons
> JEXL? There are a few features in the new release that we would love to
> use, however there has not been a release for a year now despite active
> development of new features/fixes.
>
> Kind regards,
> Lars
>


Re: Re: [CSV] Commons CSV Release Notes?

2024-05-16 Thread Gary Gregory
YW! :-)

Gary

On Thu, May 16, 2024, 7:11 PM Dan Rabe  wrote:

> Awesome, thank you!
>
> On 2024/05/16 20:06:37 Gary Gregory wrote:
> > Thanks for the report.
> >
> > I just re-published the site for 1.11.0.
> >
> > Gary
> >
> > On Thu, May 16, 2024 at 11:26 AM Dan Rabe  <mailto:da...@workday.com.inva>lid> wrote:
> > >
> > > Hi,
> > >
> > > It looks like a new release of Commons CSV (1.11.0) is available;
> however, the release notes at
> https://commons.apache.org/proper/commons-csv/changes-report.html have
> not been updated.
> > >
> > > Should we expect those to be updated soon?
> > >
> > > Thank you!
> > >
> >
> > -
> > To unsubscribe, e-mail: user-unsubscr...@commons.apache.org user-unsubscr...@commons.apache.org>
> > For additional commands, e-mail: user-h...@commons.apache.org user-h...@commons.apache.org>
> >
> >
>


Re: [CSV] Commons CSV Release Notes?

2024-05-16 Thread Gary Gregory
Thanks for the report.

I just re-published the site for 1.11.0.

Gary

On Thu, May 16, 2024 at 11:26 AM Dan Rabe  wrote:
>
> Hi,
>
> It looks like a new release of Commons CSV (1.11.0) is available; however, 
> the release notes at 
> https://commons.apache.org/proper/commons-csv/changes-report.html have not 
> been updated.
>
> Should we expect those to be updated soon?
>
> Thank you!
>

-
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.2

2024-05-15 Thread Gary Gregory
The Apache Commons Logging team is pleased to announce the release of
Apache Commons Logging 1.3.2.

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: [IMAGING] Cannot get to JavaDocs

2024-05-15 Thread Gary Gregory
That's odd, I'll have a look this week, in the meantime, you can use the
archives:

https://javadoc.io/doc/org.apache.commons/commons-imaging/latest/index.html

Gary



On Wed, May 15, 2024, 8:21 AM John Crowley  wrote:

> Hi all,
>
> Was thinking of using the Imaging library in a current project.
>
> Can find the project OK at
> https://commons.apache.org/proper/commons-imaging/ - but the latest API
> docs link results in a 404 not found
>
> Also went to https://github.com/apache/commons-imaging - but the JavaDoc
> link in the README also gives me a 404
>
> Thanks,
>
> John Crowley
> Charlotte, NC
> 203-856-2396
> j.crow...@computer.org
>
>
>
>
>
>
>


Re: [fileupload] FileUpload2 GA release soon?

2024-05-09 Thread Gary Gregory
You have to pick a Jakarta implementation version in M2, 5 or 6, please see

https://central.sonatype.com/search?q=fileupload2

Gary

On Thu, May 9, 2024, 1:11 PM Travis Boettcher
 wrote:

> Gary,
>
> There doesn’t appear to be a published artifact for
> “org.apache.commons:commons-fileupload2-jakarta:2.0.0-M2”, so we left
> everything on 2.0.0-M1. We haven’t gotten to the point of regression
> testing, so I can’t speak to any issues with either milestone release
> currently.
>
> Travis
>
> From: Gary Gregory 
> Date: Thursday, May 9, 2024 at 12:03 PM
> To: Commons Users List 
> Subject: Re: [fileupload] FileUpload2 GA release soon?
> Travis,
>
> I'd like to know if you are running into any issues running with 2.0.0-M2.
>
> Gary
>
>
> On Thu, May 9, 2024, 10:58 AM Travis Boettcher
>  wrote:
>
> > Hi!
> > I am wondering if there is any update on a fileupload2 GA release.
> > Thanks!
> > Travis
> >
> Caution: This email originated from outside of Jamf. DO NOT click on links
> or open attachments unless you were expecting, recognize, and know the
> content is safe.
>


Re: [fileupload] FileUpload2 GA release soon?

2024-05-09 Thread Gary Gregory
Travis,

I'd like to know if you are running into any issues running with 2.0.0-M2.

Gary


On Thu, May 9, 2024, 10:58 AM Travis Boettcher
 wrote:

> Hi!
> I am wondering if there is any update on a fileupload2 GA release.
> Thanks!
> Travis
>


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
> > > > com

[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:/

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&data=05%7C02%7Ccbrautigam%40icr-team.com%7Ce02533ac3d844a550c6408dc41f8fbd5%7C3d860a84424d44f9ab2bc61a036b4904%7C0%7C0%7C638457784848076395%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=l%2FPU0SIG1EftKyBiM4uV13PExBK%2FfPPThFePB5YGT1s%3D&reserved=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&data=05%7C02%7Ccbrautigam%40icr-team.com%7Ce02533ac3d844a550c6408dc41f8fbd5%7C3d860a84424d44f9ab2bc61a036b4904%7C0%7C0%7C638457784848076395%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=l%2FPU0SIG1EftKyBiM4uV13PExBK

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&data=05%7C02%7Ccbrautigam%40icr-team.com%7Cbb1041fe6b994488070808dc3d431216%7C3d860a84424d44f9ab2bc61a036b4904%7C0%7C0%7C638452605500058423%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=pV5bELVx3%2FwNJ0LADZVQHv4Mf0UZEWq5GdwTFJTTyP0%3D&reserved=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 202

[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&utm_medium=banner&utm_campaign=datacommandcenter
> >
> <
> https://datacommand.center/?utm_source=email_signature&utm_medium=banner&utm_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&utm_medium=banner&utm_campaign=datacommandcenter
> >
>
> <
> https://datacommand.center/?utm_source=email_signature&utm_medium=banner&utm_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



  1   2   3   4   5   6   7   >