apache-release profile is configured in Apache parent [1], then inherited in every Maven parent POM
the only question I can see currently is if overriding the inherited config makes sense, or even eventually cause some sort of conflict (because IIUC the style of profile activation configuration with maven-release-plugin changed over time) But i don't see any question regarding activating the profile in more parent POMs Regards, Hervé [1] https://github.com/apache/maven-apache-parent/blob/apache-23/pom.xml#L226 Le vendredi 29 mai 2020, 17:59:24 CEST Karl Heinz Marbaise a écrit : > Hi, > > I have observed that we have differernt usage of release profiles. > > In maven-plugins parent we have the configuration > > <releaseProfiles>apache-release,run-its</releaseProfiles > > whereas we have in maven-skins: > > <arguments>-Papache-release,run-its</arguments> > > and the maven-parent itself has a configuration: > > <releaseProfiles>apache-release</releaseProfiles> > > which brings me to the question: > > If I corretly see it at the moment the "apache-release" profile is > needed in the apache-parent to activate the signing of the artifacts. > > So this brings me to the question: > > Shouldn't that been activated in all parents? (of course only > maven-parent) ? > > WDYT ? > > Kind regards > Karl Heinz Marbaise > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
