The Apache Maven team is pleased to announce the release of the Maven
Parent POMs Version 37.
Maven Parent POMs include Maven Parent POM itself, but also Maven Plugins
Parent POM, Maven Shared Components Parent POM, Maven Skins Parent POM and
Maven Doxia Tools Parent POM.
Am 2022-07-23 um 20:08 schrieb Michael Osipov:
Hi,
We solved 11 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317827=12348676
There are still a couple of issues left in JIRA:
Hi,
The vote has passed with the following result:
+1 : Michael Osipov, Tamás Cservenák, Karl Heinz Marbaise, Sylwester
Lachiewicz, Olivier Lamy, Guillaume Nodet,
PMC quorum: reached
I will promote the source release zip file to Apache distribution area and
the artifacts to the central repo.
Fwiw:
Romain, I think you're exaggerating. The answer is, like in most cases: "it
depends".
Most people, we're most likely talking 95-99% here, will happily use JDK 17
with Maven 4.
Some people might need to compile for lower sources and targets, but running
tests for those builds in JDK 17
Am 2022-07-22 um 19:21 schrieb Michael Osipov:
Hi,
We solved 2 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12352119
There are still a couple of issues left in JIRA:
Hi,
We solved 11 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317827=12348676
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOURCES%20AND%20resolution%20%3D%20Unresolved
Staging repo:
Le sam. 23 juil. 2022 à 17:25, Benjamin Marwell a
écrit :
> No, 2 JDKs are not required by default. Only if you use --release={<17} and
> don't trust running tests on 17 are the same as running tests on 8.
> Yes, there are changes (certificates, XML libs, rhino, etc).
>
As explained it means
Hi,
On 23.07.22 09:36, Romain Manni-Bucau wrote:
So to get started you must install maven, 2 jdk and configure it instead of
maven+jdk? Sounds like a usability killer for most projects IMHO - issue is
not the pom ;).
Can you imagine about how many of projects we are talking about?
My
Hi,
On 23.07.22 10:13, Delany wrote:
I tried toolchains but dropped it because of the exorbitant performance
costs.
A multi-module build that normally built in 3:50 took 10:34, and that's
with toolchaining only maven-compiler-plugin.
Delany
Can you tell when you have tested that? How many
Let's not forget checksum validation by default. I think it's already
planned, but just wanted to mention it.
On Fri, 22 Jul 2022, 07:55 Olivier Lamy, wrote:
> On Fri, 22 Jul 2022 at 05:59, Guillaume Nodet wrote:
>
> > I would propose to add the -e flag by default and also the
> >
>
> +1
>
No, 2 JDKs are not required by default. Only if you use --release={<17} and
don't trust running tests on 17 are the same as running tests on 8.
Yes, there are changes (certificates, XML libs, rhino, etc).
So, for most projects that's probably not needed. For those who think it is
needed, I don't
Hi,
The vote has passed with the following result:
+1 : Karl Heinz Marbaise, Michael Osipov, Olivier Lamy, Václav Haisman,
Guillaume Nodet, Tamás Cservanák, slawomir Jaranowski, Arnaud Héritier,
PMC quorum: reached.
I will promote the source release zip file to Apache distribution area
and
The Apache Maven team is pleased to announce the release of the Maven
Assembly Plugin version 3.4.2.
https://maven.apache.org/plugins/maven-assembly-plugin/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
maven-assembly-plugin
3.4.2
Hi,
The vote has passed with the following result:
+1: Michael Osipov, Karl Heinz Marbaise, Sylwester Lachiewicz, Tamás
Cservenák, Slawomir Jaranowski
PMC quorum: reached
I will promote the artifacts to the central repo, the source release ZIP
file
and add this release the board report.
Using mvnd with toolchains doesn't improve the situation, in fact
toolchains seem to invalidate any benefit of using mvnd.
Even if this was resolved, is it fair to require mvnd?
Delany
On Sat, 23 Jul 2022 at 10:17, Mark Derricutt wrote:
> Is that due to cold starting the JVM each time?
>
> I
That's why I suggested a way to configure/require/fetch/... a JDK in the
pom then you need only install maven and a JVM.
For some products it is even that they ship a JVM, e.g. maven could
create a stripped down JVM only contain what maven requires with Java
11, then it would only be a matter
Is that due to cold starting the JVM each time?
I wonder if mvnd supports toolchains effectively? Or if that could be an
avenue to try.
--
"Great artists are extremely selfish and arrogant things" — Steven Wilson,
Porcupine Tree
On 23/07/2022 at 8:13:23 PM, Delany wrote:
> I tried
I tried toolchains but dropped it because of the exorbitant performance
costs.
A multi-module build that normally built in 3:50 took 10:34, and that's
with toolchaining only maven-compiler-plugin.
Delany
On Sat, 23 Jul 2022 at 00:21, Benjamin Marwell wrote:
> KH just released a video on
So to get started you must install maven, 2 jdk and configure it instead of
maven+jdk? Sounds like a usability killer for most projects IMHO - issue is
not the pom ;).
Le sam. 23 juil. 2022 à 00:21, Benjamin Marwell a
écrit :
> KH just released a video on toolchains.
> It's much easier than I
I'm currently struggling a bit with extension.xml descriptor there is
https://maven.apache.org/ref/3.8.4/maven-core/extension.html
that roughly describes the elements and there is
https://maven.apache.org/ref/3.6.3/maven-core/core-extensions.html
what list what maven do exports.
What I'm
20 matches
Mail list logo
