Re: [DISCUSS] New Maven Core API for 4.x

Le lundi 14 mars 2022, 16:43:51 CET Michael Osipov a écrit : > MASSIVE! Nothing else to say. +1 > The very rough goal would be to to have multiple phases: > * continue the work on this API so that it can actually cover all use > cases for plugins, create a new project with the new API and models,

Re: Dependencies from profiles broken in 3.8.5?

Can you expose some reproducer of the issue you have, or maybe the project that fails with maven 3.8.5? T On Mon, Mar 14, 2022 at 8:06 PM Falko Modler wrote: > Thanks for checking! In fact, I would have been very surprised if that was > broken in general. > > Right now I'm suspecting user prope

Re: Dependencies from profiles broken in 3.8.5?

Thanks for checking! In fact, I would have been very surprised if that was broken in general. Right now I'm suspecting user property parsing but I have yet to take a closer look... - To unsubscribe, e-mail: dev-unsubscr...@mave

Re: Dependencies from profiles broken in 3.8.5?

Howdy, I tried but could not reproduce this with 3.8.5: when I do `-PmyProfile` with dependencies declared in profile, the dependencies ARE there (tried with full GAV but also managed dependencies, where profile had only GA but version came from depMgt). IMHO, this is somewhere else HTH T

Test scope and transitive dependencies in compile scope

Hi, We have open issue MDEP-791 [1] for maven dependency plugin There are also connected issues for Maven core MNG-6058 [2] and probably others. Do we have any idea how this should be resolved ... fix in m-dependency-p or in Maven core? I'm afraid that even if we fix in core ... we should have s

Dependencies from profiles broken in 3.8.5?

Hi everyone, before I invest (a lot of) time, is it just me or are dependencies from profiles broken in Maven 3.8.5? In my Quarkus project, two usecases broke with 3.8.5 but they are fine with 3.8.4 and before. One is described briefly here: https://github.com/quarkusio/quarkus/pull/24285#issue

Re: issues with the user property "maven.test.failure.ignore" and new proposals

Hi First sentence: Set this to "true" to ignore a failure during testing. It is clear for me - we want to ignore a failure during testing ... So if the testing process is not starting for any reason or was broken for reasons other than test failure this property should not be considered. Most of

Re: issues with the user property "maven.test.failure.ignore" and new proposals

pon., 14 mar 2022 o 10:52 Tibor Digana napisał(a): > Romain, it is not a bug. > Don't consider this as a bug. It was a feature request for change by > Olivier, and not a bug. > I closed both issues years ago but not because of ignorance but because the > appearance of the exceptional behavior is

Re: [DISCUSS] Radical Fast Forward to 3.5.4

Hello, I really think no sane developer should use stable distributions like EL or Debian für Java/Maven toolchains. But if they do, they do know they have old software and their vendor will do the maintenance. I would not be concerned with that (besides maybe clearly communicating EOLs, minimu

Re: [DISCUSS] New Maven Core API for 4.x

I suppose you could raise PRs to the origin/mvn4 branch ? Maybe even commit changes directly, if that makes sense. Le lun. 14 mars 2022 à 16:43, Michael Osipov a écrit : > Am 2022-03-14 um 08:59 schrieb Guillaume Nodet: > > Hi everyone, > > > > As Michael hinted at this new API in the "[DISCUSS]

Re: [DISCUSS] Radical Fast Forward to 3.5.4

Hi, As I and others wrote - we should have clear documentation about release and version policy. Maintainers / contributors of package managers should take care about updating their products. It can not be our responsibility and moreover a blocker for us. We have basic instructions on how to ins

Re: [DISCUSS] New Maven Core API for 4.x

Am 2022-03-14 um 08:59 schrieb Guillaume Nodet: Hi everyone, As Michael hinted at this new API in the "[DISCUSS] Radical Fast Forward to 3.5.4" thread, I'd like to start the discussion around it. Over the past weeks, I've worked on an experimental API for Maven 4.x. The goals are multiple :

Re: [DISCUSS] Radical Fast Forward to 3.5.4

FYI, it looks like RHEL-based 7 uses maven 3.0.5, RHEL-based 8 uses 3.5.4 and 3.6.3. My guess is that even if the new upgraded plugins depend on Maven 3.5.4 it wouldn't cause major issues as if anyone is using an olver Maven version they will likely use older versions of the plugins/components. A

Re: [DISCUSS] Radical Fast Forward to 3.5.4

FYI Debian Stable is at 3.6.3 as is Ubuntu. Homebrew is at 3.8. I've only checked the websites for this, not tried to install from there. However neither looks like a blocker. What other package managers should we check? What does Red Hat use? Windows? Also, are there any older versions of OS's l

Re: issues with the user property "maven.test.failure.ignore" and new proposals

@Tibor: I never said it was a bug, my point is that you never needs it so we should keep that deprecated/not recommended and enable people having too constrained env to work on it through a SPI as proposed by Guillaume. So proposal was to drop that property support and add a SPI if anyone think thi

Re: issues with the user property "maven.test.failure.ignore" and new proposals

Just wondering but maybe it would be better to configure the severity instead of a true/false, something like: maven.test.failure=WARN maven.test.error=ERROR would only warn about failing tests but thrw exception if starting the test fails? Am 14.03.22 um 10:52 schrieb Tibor Digana: Romain,

Re: issues with the user property "maven.test.failure.ignore" and new proposals

Romain, it is not a bug. Don't consider this as a bug. It was a feature request for change by Olivier, and not a bug. I closed both issues years ago but not because of ignorance but because the appearance of the exceptional behavior is a wrong compromise and which does not help anyone and even it m

Re: issues with the user property "maven.test.failure.ignore" and new proposals

+1 if it is to investigate a CI issue, it is generally easy to add debug insights (by code or agent) so a SPI sounds like the sanest for the plugin to me. Romain Manni-Bucau @rmannibucau | Blog | Old Blog

Re: issues with the user property "maven.test.failure.ignore" and new proposals

If that's not currently possible, maybe a SPI should be provided so that people can use plug in extensions to analyze the test result and override it if necessary (transforming an error into a warning, storing results in a way which is easier to use by other tools later...) ? Guillaume Le lun. 14

Re: [DISCUSS] New Maven Core API for 4.x

Hi Guillaume, +1, also +1 to add a hint in the mojo descriptor if the plugin is mvn4 compatible (version=xxx) to fully isolate it from the maven.core class realm except the API which will avoid some headache in our tooling and at runtime! think it is the way we should priviledge to have a smoother

Re: [DISCUSS] Radical Fast Forward to 3.5.4

+1 to upgrade plugins / components Le dim. 13 mars 2022 à 12:48, Michael Osipov a écrit : > 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

[DISCUSS] New Maven Core API for 4.x

Hi everyone, As Michael hinted at this new API in the "[DISCUSS] Radical Fast Forward to 3.5.4" thread, I'd like to start the discussion around it. Over the past weeks, I've worked on an experimental API for Maven 4.x. The goals are multiple : * fix some problems with designs that do not work w

Re: [DISCUSS] Radical Fast Forward to 3.5.4

Le lun. 14 mars 2022 à 08:43, Hervé BOUTEMY a écrit : > Le lundi 14 mars 2022, 08:01:11 CET Maarten Mulders a écrit : > > Just to clarify: "Raise the entire baseline to Maven 3.5.4" means that > > the official Maven plugins will only work from Maven Core 3.5.4 onwards? > yes > > > In that case, +

Re: [DISCUSS] Radical Fast Forward to 3.5.4

Le lundi 14 mars 2022, 08:01:11 CET Maarten Mulders a écrit : > Just to clarify: "Raise the entire baseline to Maven 3.5.4" means that > the official Maven plugins will only work from Maven Core 3.5.4 onwards? yes > In that case, +1 to move the baseline to 3.5.4. > > Point of concern/question: t

Re: [DISCUSS] Radical Fast Forward to 3.5.4

Just to clarify: "Raise the entire baseline to Maven 3.5.4" means that the official Maven plugins will only work from Maven Core 3.5.4 onwards? In that case, +1 to move the baseline to 3.5.4. Point of concern/question: this may be a breaking change in some cases - how do we communicate that in