Dear All,
Hey, daddies! It’s your turn! We’re investigating the impact of paternity
and maternity on your professional or academic life! Are you a developer or
work in a computing-related job? Answer our 10 minutes-survey! We need you!
All the best,
--
PhD Edna Dias Canedo
Associate Professor
Claude,
Do you need the API to be made public?
Gary
On Mon, Apr 17, 2023 at 2:53 PM Gary Gregory wrote:
>
> I am guessing that only what is required to be public is as to both maximize
> our flexibility in maintenance and minimize the public API surface to support.
>
> We could make it public
Hi Alex
niedz., 23 kwi 2023 o 18:02 Alex Herbert
napisał(a):
> +1
>
> Installed from the tag. Builds Statistics (multi-module) and Lang
> using Java 8 and 17.
>
> Note: I do get this error from several plugins (pmd, site, bundle,
> remote-resources):
>
> [WARNING] Parameter 'localRepository' is
That would be a typo, I meant Alex, sorry for the confusion.
Gary
On Sun, Apr 23, 2023, 14:24 Markus Spann wrote:
> Who's Albert?
>
>
> Am 23. April 2023 13:33:23 UTC schrieb Gary Gregory <
> garydgreg...@gmail.com>:
>
>> Thank you for reviewing Albert. Wow! What a fail on the part of the
>> m
If only for JPMS, we can compile module-info.java separately, which is
still compatible with Java 8.
If we really need to give up compatibility with Java 8, then I still
recommend skipping Java 11 and using Java 17.
Glavo
On Mon, Apr 24, 2023 at 1:32 AM Ralph Goers
wrote:
> The primary reason
The primary reason for moving to Java 11 is to fully support JPMS. Most
libraries have added an automatic module name to the Manifest but that doesn’t
really make it fully JPMS enabled.
To be honest, the number of people I’ve seen asking for full JPMS support is
quite small though.
Ralph
>
I don't think upgrading to Java 11 is a very attractive proposition.
There are not many language features introduced in Java 9~11,
so there are not enough benefits to upgrade to Java 11.
The lifecycle of Java 11 is much shorter than that of Java 8.
Premier support for Java 11 will end this year, a
This error message was introduced by Maven 3.9.1 IIRC and there might have
been talk of doing something about it in the upcoming 3.9.2 but I am not
100% sure.
Gary
On Sun, Apr 23, 2023, 12:02 Alex Herbert wrote:
> +1
>
> Installed from the tag. Builds Statistics (multi-module) and Lang
> using
Waiting until 2030? Surely you must be joking.
Gary
On Sun, Apr 23, 2023, 11:37 Alex Herbert wrote:
> Free commercial support for JDK 8 from Oracle ended in 2022.
> Non-commercial and extended commercial support ends in 2030. Other
> providers have free support for longer than 2023 [1]. I would
On Sun, 23 Apr 2023 at 16:37, Alex Herbert wrote:
>
> Free commercial support for JDK 8 from Oracle ended in 2022.
> Non-commercial and extended commercial support ends in 2030. Other
> providers have free support for longer than 2023 [1]. I would rather
> maintain Java 8 support when JDK 8 still
+1
Installed from the tag. Builds Statistics (multi-module) and Lang
using Java 8 and 17.
Note: I do get this error from several plugins (pmd, site, bundle,
remote-resources):
[WARNING] Parameter 'localRepository' is deprecated core expression;
Avoid use of ArtifactRepository type. If you need a
Free commercial support for JDK 8 from Oracle ended in 2022.
Non-commercial and extended commercial support ends in 2030. Other
providers have free support for longer than 2023 [1]. I would rather
maintain Java 8 support when JDK 8 still has broad support and usage.
Alex
[1] https://en.wikipedia.
We have fixed a few bugs and added some enhancements since Apache
Commons Parent 56 was released, so I would like to release Apache
Commons Parent 57.
Apache Commons Parent 57 RC2 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/57-RC2
(svn revision 6
On Sun, Apr 23, 2023 at 4:03 AM Alex Herbert wrote:
> Other notes:
>
> 1. I still get a warning from the SPDX plugin (same as previous versions of
> CP):
>
> [WARNING] Unable to map maven licenses to a declared license. Using
> NOASSERTION
>
> I do not know where this comes from. The ASF 2.0 l
Gary,
A few years ago I migrated commons crypto onto Java 11 in my local
environment. I haven't kept the code, but it wasn't a heavy lift and I'm
happy to do it again for the community version. Let me know how you'd like
me to proceed.
Alex
On Sun, Apr 23, 2023 at 9:47 AM Gary Gregory wrote:
Hi All,
In the year 2023, and with Java 21 in EA (https://jdk.java.net/21/), I
think it is time to start migrating our components from Java 8 to Java
11. I imagine this to happen slowly and surely over the course of this
whole year.
In addition, originally, it should also be time to update our Gi
IMO the name jvm.target is incorrect because it is not the JVM that is
the target it is the JRE API.
Gary
On Sun, Apr 23, 2023 at 4:03 AM Alex Herbert wrote:
>
> Installed from the git tag. I can build projects on JDK 11 and 17. But
> not on JDK 8.
>
> The new profile to conditionally configure
This vote for RC1 is canceled (see below).
Gary
On Sun, Apr 23, 2023 at 9:33 AM Gary Gregory wrote:
>
> Thank you for reviewing Albert. Wow! What a fail on the part of the
> maven compiler plugin! :-( I thought for sure I had tested that but I
> obviously fooled myself.
>
> I created https://iss
Thank you for reviewing Albert. Wow! What a fail on the part of the
maven compiler plugin! :-( I thought for sure I had tested that but I
obviously fooled myself.
I created https://issues.apache.org/jira/browse/MCOMPILER-534
I will cancel this RC.
Gary
On Sun, Apr 23, 2023 at 4:03 AM Alex Herbe
Installed from the git tag. I can build projects on JDK 11 and 17. But
not on JDK 8.
The new profile to conditionally configure the maven-compiler-release
plugin for JDK 9+ is incorrect. The parent pom defines the property:
8
Then activates it using:
jdk9-compiler
20 matches
Mail list logo
