On Mon, 14 Mar 2022 at 11:55, Tibor Digana wrote:
> In case of the user property *maven.test.failure.ignore* the MOJO must not
> throw any exception which is interpreted by the Maven Core as BUILD
> SUCCESS.
>
This is a very simple reduction of the problem description.
The documentation here
In case of the user property *maven.test.failure.ignore* the MOJO must not
throw any exception which is interpreted by the Maven Core as BUILD SUCCESS.
We have received an internal requirement to change the behavior of the user
property *maven.test.failure.ignore* so that the behavior will have
+1
Thanks for bringing this up
Enrico
Il giorno dom 13 mar 2022 alle ore 20:58 Elliotte Rusty Harold
ha scritto:
>
> What do all the various package managers install? I'm pretty sure I've
> seen one lately whose default was 3.3.1. Debian perhaps?
>
> I think before we make any such move it
What do all the various package managers install? I'm pretty sure I've
seen one lately whose default was 3.3.1. Debian perhaps?
I think before we make any such move it would make sense to audit what
people who don't manually install Maven are likely to have. First we
should raise all those to
Olivier opened a Jira issue about this [1]
let's work here
Regards,
Hervé
[1] https://issues.apache.org/jira/browse/MNG-7430
Le dimanche 13 mars 2022, 15:29:01 CET Tibor Digana a écrit :
> Hello Maven developers,
>
> I want to inform you about some compliance issues between the Javadoc of
>
Am 2022-03-13 um 20:26 schrieb Slawomir Jaranowski:
Hi,
Another plugins that have newer versions:
maven-deploy-plugin . 2.8.2 -> 3.0.0-M1
maven-install-plugin 2.5.2 -> 3.0.0-M1
Both are problematic if you create Maven plugins, see
Hi,
Another plugins that have newer versions:
maven-deploy-plugin . 2.8.2 -> 3.0.0-M1
maven-install-plugin 2.5.2 -> 3.0.0-M1
maven-scm-plugin ... 1.12.2 -> 2.0.0-M1
maven-failsafe-plugin
Hi,
+100 for 3.5.4 as minimum.
We should even consider 3.8.x.
It is the fact that we only support the latest release version.
We know how much work is in Maven core and how many plugins / components we
support. And we know how many active maintainers we have.
It should be clearly announced in
+1 to upgrade to Maven 3.5.4 prerequisite for future plugins releases
what I'd like is that we better document compatibility updates:
- on Java prerequisites for components
- on Java and Maven prerequisites for plugins
I found one community plugin that does a really excellent job at that [1]
I
Technically, you are right. We request to verify issues with 3.8.x and
move to if the issue is resolved. But that does not happen very often,
IMHO. I wouldn't even object to raise to 3.8.1, but this is another
discussion.
Am 2022-03-13 um 16:45 schrieb Sylwester Lachiewicz:
Everything before
Everything before 3.8.x now it's obsolete, because we no longer provide or
plan any patches to the 3.5x or 3.6x line (bugfix or security)
Sylwester
niedz., 13 mar 2022, 12:48 użytkownik Michael Osipov
napisał:
> Folks,
>
> as you might now we are dragging old luggage over and over with every
>
Hello Maven developers,
I want to inform you about some compliance issues between the Javadoc of
Maven Plugin API and the Maven Core 3.x behavior. I am only a messenger
providing the facts and I would like the community to post the opinions and
finally a concrete fix(es).
The Maven 3 reports
+1
On Sun, Mar 13, 2022, 12:48 Michael Osipov wrote:
> Folks,
>
> as you might now we are dragging old luggage over and over with every
> new year. We are making (little) progress with cleansing, skimming and
> updating of our components.
>
> I'll will make a radical proposal I have already
The Apache Maven team is pleased to announce the release of the Apache
Maven 3.8.5
Apache Maven is a software project management and comprehension tool.
Based on the concept
of a project object model (POM), Maven can manage a project's build,
reporting and documentation
from a central piece
I don't think this is so easy. While working on Doxia we have noticed
that a lot of intertwined and as soon as you touch on component you need
to touch the rest also.
At least a one time pain we must go.
Am 2022-03-13 um 12:52 schrieb Romain Manni-Bucau:
Hi,
No big issue with me but I would
Hi,
No big issue with me but I would also consider letting v3 as it is and
start working on v4 with an alpha coming soon maybe?
Can be a way to reach these goals without impacting twice end users too.
Le dim. 13 mars 2022 à 12:48, Michael Osipov a écrit :
> Folks,
>
> as you might now we are
Folks,
as you might now we are dragging old luggage over and over with every
new year. We are making (little) progress with cleansing, skimming and
updating of our components.
I'll will make a radical proposal I have already discussed privately
with other fellow committers over Slack:
Raise
Hi,
The vote has passed with the following result:
+1: Dan Tran, Christoph Läubrich, Tamás Cservenák, Hervé Boutemy,
Olivier Lamy, Tibor Digana, Arnaud Héritier, Romain Manni-Bucau, Karl
Heinz Marbaise
PMC quorum: reached
I will promote the artifacts to the central repo, the source release
18 matches
Mail list logo
