Hi Martin, Thanks a lot for your response. This is a handy feature I have already used during my investigations.
It shows the recognized behavior (that the profiles of the parent pom modules are not available in the project). My current question is, should it be like this, or should the profiles defined in a parent pom module also be available in a project like those defined in the parent pom directly? Best Norman On 2024/11/26 13:22:37 Martin Höller wrote: > Hi! > > Sorry for my previous (empty) mail. Sent it unintentionally. > > Problably the maven-help-plugin [0] could be of help for you. It provides > the active-profiles and all-profiles Goals, which could be handy. > > hth, > - martin > > [0] https://maven.apache.org/plugins/maven-help-plugin/plugin-info.html > > Am 26. Nov. 2024 schrieb nor...@gies.team: > > > Good day, > > > > I am trying to use maven profiles separated into modules (<modules> in a > > parent pom). > > > > After successfully installing the parent pom (and the modules), I tried to > > use the profiles. > > > > Profiles located in the parent POM still work as before, but new profiles > > located in a module do not. > > > > I tried to activate the profiles with the command parameter -P, e.g., > > Pmy-profile-name-in-parent-pom, or, e.g., Pmy-profile-name-in-module-a. > > > > The command mvn help:all-profiles also lists only the profiles directly in > > the parent pom. > > > > I wanted to figure out whether this should or should not work. It would be > > great if you could give me a hint. > > > > Best > > Norman > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
