Hi Jörg. Thanks for the reply. Can you please elaborate with examples? Option 1 is what I need, but that does not work. Or maybe we have a misunderstanding about the term "property". Are we talking about a simple Maven property or a mojo configuration property?
Regards -- Alexander Kriegisch https://scrum-master.de Jörg Schaible schrieb am 03.02.2024 17:59 (GMT +07:00): > There are several approaches, depending on the use case: > > 1/ It is always the same dependency, the user just wants to use different > versions. Solution: Use a property for the version. The user can then > overwrite the property in his pom. > > 2/ The user should be able to use a different dependency. The approach with > the > > property works here also, just use it also for the groupId and artifactId. > > 3/ The user must not use a single dependency that varies, but several. Here > you may take an approach with different profiles. Best practice here is to > activate the profiles by existing of a (relative) file e.g. in a local > profile > folder. > > And you may combine these approaches. Check the result with > help:effective-pom > where you can see, what Maven internally generates as pom for an individual > project. > > Regards, > Jörg > > Regards, > Jörg > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
