Re: [commons-jexl] branch master updated: JEXL: Attempt to bump checkstyle from 9.3 to 10.3, add plugin profile for jdk8
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
something to consider for the parent POM if there are no issues...
Gary
On Mon, Jun 6, 2022, 06:31 wrote:
> This is an automated email from the ASF dual-hosted git repository.
>
> henrib pushed a commit to branch master
> in repository https://gitbox.apache.org/repos/asf/commons-jexl.git
>
>
> The following commit(s) were added to refs/heads/master by this push:
> new f909826e JEXL: Attempt to bump checkstyle from 9.3 to 10.3, add
> plugin profile for jdk8
> new 22d92e50 Merge remote-tracking branch 'origin/master'
> f909826e is described below
>
> commit f909826e96065db5c3e44a019e7e6e0abd60edca
> Author: henrib
> AuthorDate: Mon Jun 6 12:31:13 2022 +0200
>
> JEXL: Attempt to bump checkstyle from 9.3 to 10.3, add plugin profile
> for jdk8
> ---
> pom.xml | 17 +++--
> 1 file changed, 15 insertions(+), 2 deletions(-)
>
> diff --git a/pom.xml b/pom.xml
> index 88818ccf..68f79008 100644
> --- a/pom.xml
> +++ b/pom.xml
> @@ -52,7 +52,7 @@
> JEXL
> 12310479
> 3.1.2
> -9.3
> +10.3
> false
> 0.15.7
> 3.16.0
> @@ -90,6 +90,19 @@
>
> 4E066E0459CD109B
>
>
> +
> +
> +
> +jdk8-plugin-fix-version
> +
> +1.8
> +
> +
> +9.3
> +
> +
> +
> +
>
> scm:git:
> https://gitbox.apache.org/repos/asf/commons-jexl.git
> scm:git:
> https://gitbox.apache.org/repos/asf/commons-jexl.git
> @@ -227,7 +240,7 @@
>
> com.puppycrawl.tools
> checkstyle
> -${checksyle.version}
> +${checkstyle.version}
>
>
> com.sun
>
>
[collections] EOL 3.x?
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
[Validator] Update to Java 8 and from Apache Commons Collections 3.x to 4.x
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...@commons.apache.org
Re: [Validator] Update to Java 8 and from Apache Commons Collections 3.x to 4.x
+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-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [Validator] Update to Java 8 and from Apache Commons Collections 3.x to 4.x
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 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...@commons.apache.org >> > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org >
Re: [Validator] Update to Java 8 and from Apache Commons Collections 3.x to 4.x
+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-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
Re: [collections] EOL 3.x?
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 only expect security updates to 3.x if there are volunteers with time to work on the fixes, etc. So for future questions of this type, one could just point to this doc. WDYT? -Bruno On Tue, 7 Jun 2022 at 00:33, Gary Gregory wrote: > 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 > >
