FYI, maven core tests fail for me (Java 1.8. Maven 3.8.7) when
building at head like so. I'm not sure what to do about this:
[INFO] Unpacking
/Users/elharo/.m2/repository/org/codehaus/plexus/plexus-utils/3.5.0/plexus-utils-3.5.0.jar
to /Users/elharo/maven/plexus-utils/target/classes with includes
+1
pt., 24 lut 2023, 16:37 użytkownik Tamás Cservenák
napisał:
> Howdy,
>
> We solved 10 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317523&version=12352530
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MINDEXER/issues
>
> S
dependabot[bot] opened a new pull request, #21:
URL: https://github.com/apache/maven-shared-incremental/pull/21
Bumps
[apache/maven-gh-actions-shared](https://github.com/apache/maven-gh-actions-shared)
from 2 to 3.
Commits
See full diff in https://github.com/apache/maven-gh-ac
+1
pt., 24 lut 2023 o 16:37 Tamás Cservenák napisał(a):
> Howdy,
>
> We solved 10 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317523&version=12352530
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MINDEXER/issues
>
> Staging
Le ven. 24 févr. 2023 à 17:31, Delany a écrit :
> I turned on -e as default last month and had to turn it off again.
> When a change causes a group of tests to fail I get the stack trace for
> each test failure first up in the project and then repeated as the cause of
> the reactor failing.
> I d
I turned on -e as default last month and had to turn it off again.
When a change causes a group of tests to fail I get the stack trace for
each test failure first up in the project and then repeated as the cause of
the reactor failing.
I don't mind it on by default, but then how do I turn it off?
Howdy,
We solved 10 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317523&version=12352530
There are still some issues in JIRA:
https://issues.apache.org/jira/projects/MINDEXER/issues
Staging repository:
https://repository.apache.org/content/repositories/maven-1879/
+1 for -e default
From: Romain Manni-Bucau
Sent: Friday, February 24, 2023 9:15:15 PM
To: Maven Developers List
Subject: Re: And while I'm on the subject of logging
Hi Elliotte,
I agree -e should be the default, I don't see the point to not have the
error cause
Hi Elliotte,
I agree -e should be the default, I don't see the point to not have the
error cause when it fails.
Your point 2 is only relevant if you never built the project nor a project
with the same dependencies so I guess we can assume it is a corner case - I
was also often checkouting projects
Hi Elliot,
did you try to use mvnDebug?
> Am 24.02.2023 um 13:26 schrieb Elliotte Rusty Harold :
>
> Real world example from the non-Apache project built with Maven I'm
> working on this morning.
>
> 1. Build fails
> 2. 591 lines of log output in my console, almost all of which are
> artifacts
Real world example from the non-Apache project built with Maven I'm
working on this morning.
1. Build fails
2. 591 lines of log output in my console, almost all of which are
artifacts being downloaded.
3. Relevant lines: 1
4. Percentage useful content: .17%
That's bad. But wait. It gets worse.
T
Howdy,
just an update of Maven status (links will assume you are logged in to
JIRA):
* 3.9.1 all done
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.1
* 3.9.1 candidates
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersio
The Apache Maven team is pleased to announce the release of the Apache Maven
Assembly Plugin, version 3.5.0
This plugin builds an assembly (distribution) of sources and/or binaries.
https://maven.apache.org/plugins/maven-assembly-plugin/
You should specify the version in your project's plugin c
13 matches
Mail list logo
