Le sam. 27 nov. 2021 à 21:58, Falko Modler <f.mod...@gmx.net> a écrit :
> Am 27.11.2021 um 20:25 schrieb Romain Manni-Bucau: > > 1. Profiles dont work by design since they must be activated and have the > > same issue that plugin flag > > In what I proposed the activation happens automatically via > <file>...</file> activation, so I don't get your point. > Sure, if you don't have a suitable file or directory in each child > module to use for the activation then this approach is not an option. > I see - didn't t think to <file> - but it is not always there at mvn command time (profile resolution) or files are ambiguous - first run can generate the build descriptor - and I guess the best test is src/main/java for other kind of modules (thinking to servers/ subtree) but it is not that neat at the end - indeed marker files ".build" are a no-go here - and it is easy to break so I prefer a more robust approach, either the hierarchy extension or pluginMgt trick for now, but right <file> is a workaround too, got it. > > Artificial flagfiles can be an option when you want to activate a > profile only for a subset of child modules, but I wouldn't use this > approach unless there is no other option. > > I can show you (working) examples for both in the Quarkus codebase. > > Cheers, > > Falko > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
