THANK YOU Tama, you rock !
I've downloaded latest SNAPSHOT from here (
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/apache-maven/3.9.10-SNAPSHOT/
) and on a very simple example this works as expected.
My test is really simple so I do not pretend to validate the who
Maven4 fixes this issue, yes, it is "aware" differently than Maven3 is
(where excluded projects are fully removed from line of sight).
In Maven3 is not doable sadly, at least not with some simple change. I
did some experiments about this long time ago, see
https://github.com/apache/maven/pull/1406
Eh, sorry, am a bit overwhelmed
It seems this is FIXED in Maven-3.9.x branch? :)
https://github.com/apache/maven/commit/45201347c417896b57159221130333f5fa4bbfb6
So once 3.9.10 is out, it should be workable? Can you test the
maven-3.9.x branch?
Thanks
T
On Thu, Nov 14, 2024 at 3:14 PM Tamás
Thanks for the info Tamás.
Do you know if:
1- a workaround is planned ?
2- Maven 4 will solve this problem ?
3- commands like "-pl :myModule -am " also suffer from this kind of problem
?
I'm trying to convince everyone at work to move to a large Monorepo and my
argument is "learn how to use Maven
Howdy,
This is a problem with Maven 3 and how it "reduces" the reactor (when
using -rf, -pl etc, basically when reactor < full project).
This was already discussed once on this ML but let me shortly explain
what happens:
You basically "moved" B out of the reactor, and your "snake" looks like this
Hello,
I just faced a problem and would like your input if it is really a problem
or not.
I have a multimodule project where dependencies are like:
A --> B --> C --> D(A depends upon B which depends upon C and so on...)
I would have expected those 2 commands to exhibit the exact same behavio
