Hervé BOUTEMY schrieb am 09.05.2021 03:31 (GMT +07:00):
> Le samedi 8 mai 2021, 17:03:05 CEST Alexander Kriegisch a écrit :
>
>> My question was how to achieve reliably predictable ordering. That
>> question is yet to be answered.
>
> it is answered: you currently can't.
Actually, your first re
Then I kindly request to put this topic into the Maven 5 backlog
already, referring to this thread as a resource. How the team shall
prioritise it is another topic, but that way at least it would not get
lost.
One more question: If I would copy the plugin configuration from 'build'
redundantly (ug
That is a lot of ceremony (as in boilerplate), but at least a viable
workaround for certain shortcomings in Maven. Thank your very much, this
shall be my last resourt approach the next time this situation comes up
and I have no more unused phases to escape to. :-)
Delany schrieb am 09.05.2021 00:
Le samedi 8 mai 2021, 17:03:05 CEST Alexander Kriegisch a écrit :
> Nooo! I don't need extra phases, nor do I have any desire to create
> custom lifecycles, even though I know this is possible. My point was: If
> we cannot rely on a specific order when executing plugins and executions
> within them
If two plugins with the same phase appear in the build section of one POM,
then their order matters.
If they split in build and a profile, then the order is not guaranteed
because there are no in one XML section and so the order cannot be
determined.
This might be possible in Maven 5. Let's ask suc
Well you might have asked the question, but the answers are for everyone to
learn from.
I don't have trouble with execution order since doing 2 things. One is
implementing the sortpom maven plugin. The other is configuring all plugin
executions in pluginManagement as early as possible, but with ph
Nooo! I don't need extra phases, nor do I have any desire to create
custom lifecycles, even though I know this is possible. My point was: If
we cannot rely on a specific order when executing plugins and executions
within them in the same phase, the logical consequence for deterministic
behaviour wo
Hi. In case you really need custom phases, it is possible to add them. See
https://github.com/raydac/mvn-finisher for an example for adding new
phases. But I would say this is the last resort in case no other solutions
work for you.
la 8. toukok. 2021 klo 10.40 Alexander Kriegisch (alexan...@krieg
Hello Maven users,
first of all, I hope that you are well. Recently, I've been working on a
Java API for Minecraft plugin developers (that, however, does not matter at
all).
I have a multimodule project, consisting of 3 modules: core, proxy and
backend. The core module is the API itself. The othe
The Apache Maven team is pleased to announce the release of the Maven
Resolver version 1.6.3.
https://maven.apache.org/resolver/
Release Notes - Maven Resolver - Version 1.6.3
** Bug
* [MRESOLVER-153] - resolver-status.properties file is corrupted
due to concurrent writes
* [MRESOLVER
>> Can anybody enlighten me on what is happening here and if this
>> behaviour is documented anywhere? Or is this just the "read the
>> freakin' source code, pal" kind of detail?
> order in the same phase is not expected to be guaranteed: that's a
> design choice (even if "choice" is not the best
11 matches
Mail list logo
