Hi Gary,
No objections from me. I can't recall if we did that for other components.
We could also, I think, have a document for Commons to reference when
releasing a major version update of a component. In that document we could
explain we are a team of volunteers, that if 4.x is out, users can o
+1
On Tue, 7 Jun 2022 at 01:43, Gary Gregory wrote:
> Hi All:
>
> I propose that we migrate Validator from Java 7 to 8 and from Apache
> Commons Collections 3.x to 4.x.
>
> Thoughts?
>
> Gary
>
> -
> To unsubscribe, e-mail: dev-
Seems reasonable to me. Anyone still using Java 7 probably isn’t too concerned
about CVEs as I hope that type of software is not internet connected!
—
Matt Sicker
> On Jun 6, 2022, at 09:09, Melloware wrote:
>
> +1 from me on that Gary!
>
>
>> On 6/6/2022 9:43 AM, Gary Gregory wrote:
>> Hi
+1 from me on that Gary!
On 6/6/2022 9:43 AM, Gary Gregory wrote:
Hi All:
I propose that we migrate Validator from Java 7 to 8 and from Apache
Commons Collections 3.x to 4.x.
Thoughts?
Gary
-
To unsubscribe, e-mail: dev-uns
Hi All:
I propose that we migrate Validator from Java 7 to 8 and from Apache
Commons Collections 3.x to 4.x.
Thoughts?
Gary
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@
Hi All:
Should we formally announce that the 3.x line is EOL and encourage
users to migrate to 4.x?
Gary
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
FYI: I've been closing PRs from Dependabot for Checkstyle bumps that depend
on Java 11. I find it simpler than forcing the use of profiles that add
complexity to the build and cause different build behavior depending on the
Java version. I will be interesting to see how this works out... Maybe
some
