it may help to explicitly override the version of the wrapper so it is no
longer a snapshot, the version attribute inherented from the parent.
kind regards,
Pieter
Op ma 22 mei 2023 22:54 schreef Jerome Lelasseux
:
> I did some more testing and discovered mvn -X...
>
> So I used mvn -X compile a
Thank you Martin that was my problem ! Switching OFF
useIncrementalCompilation did the trick, it's really counter-intuitive...
Le lundi 22 mai 2023 à 23:17:38 UTC+2, Martin Desruisseaux
a écrit :
Hello Jerome
Le 22/05/2023 à 22:53, Jerome Lelasseux a écrit :
On my NB
Hello Jerome
Le 22/05/2023 à 22:53, Jerome Lelasseux a écrit :
On my NB platform app, if I open a single module and build it, it
recompiles only when source files are modified, as expected. But when
I run Build on the parent project, maven always recompiles all
modules. Is it normal ?
I do no
I did some more testing and discovered mvn -X...
So I used mvn -X compile and mvn -X install to check the differences (it seems
that the IDE 'Build' action uses the install goal).
I found that only with the install goal the recompilation of my module is
triggered by this dependency:
[DEBUG] New
Eric,
Sorry I was not clear. I expected the behavior you describe but it's not the
case in my project:
If I build a child module twice in a row, the 2nd time it will say "nothing to
compile", as expected.
But if I build the parent project (all modules) twice, it always says "changes
detected,
Hi,
Maven will build all children, but should be faster on the compilation plugin
part you should have something like that :
Nothing to compile - all classes are up to date.
Best Regards
Eric
De : Jerome Lelasseux
Envoyé : vendredi 19 mai 2023 21:04
À : NetBeans Mailing List
Objet
