Julia Boes schrieb am 27.08.2020 15:09 (GMT +07:00): >> I cannot say for sure, but probably you just copied & pasted my >> plugin configurations into the parent POM's <plugin> section instead >> of <pluginManagement> -> <plugins>, consequently kicking off test >> compilation from the parent. I guess you want to change that. > > That's exactly what I did. Moving the configuration to > pluginManagement makes sense, but how would you add profiles to it? Or > would you need to add the profile information in the child poms?
Yes, if you add/override plugin configuration which does not apply to the whole project but just to some modules, you should add it there. Just give it a try, I cannot test for you without an MCVE. >> BTW, if you can fork the original repo for me and just add enough >> commits to reproduce your situation, I can take a closer look. >> Currently, I have to speculate based on the information I have, which >> is less than ideal. > > I know it's not ideal but I can't share a public fork at the moment. Read again, please. I suggested to fork the *original* Kryo repo and add just enough Maven config to reproduce the problem. I did not request a fork of your internal repo. See also: https://stackoverflow.com/help/mcve -- Alexander Kriegisch https://scrum-master.de --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
