On Thu, 5 Oct 2023 at 00:13, Phil Steitz <phil.ste...@gmail.com> wrote: > > On Tue, Oct 3, 2023 at 1:26 AM sebb <seb...@gmail.com> wrote: > > > > The properties are used by the release plugin. > > > > But since they are unique to the user, they do not belong in the shared pom. > > So they should be blank in the component pom?
No, they must be absent. > Why do they need to be there at all? It seems they are used by the vote-text goal. > Can't they just be provided on the command line? Yes. > I detest settings.xml, btw. Not under source control, throw-back to the old > special local voodoo build days. Most (all?) of it can be provided on the command line. However, that gets tedious; settings.xml provides useful short-cuts. It should only be used for settings specific to the user. It cannot therefore be added to shared source control. However, you could always keep your copy under source control. > Phil > > > > On Tue, 3 Oct 2023 at 02:33, Phil Steitz <phil.ste...@gmail.com> wrote: > > > > > > +1 but why then are those properties there? > > > > > > Phil > > > > > > > On Oct 2, 2023, at 3:58 PM, sebb <seb...@gmail.com> wrote: > > > > > > > > As the subject says, please do not use the pom to store RM details > > > > such as > > > > > > > > commons.releaseManagerName > > > > commons.releaseManagerKey > > > > > > > > These properties are personal to the user, and should be defined in > > > > ~/.m2/settings.xml. > > > > See https://commons.apache.org/proper/commons-release-plugin/index.html > > > > > > > > Or you can define them on the command line. > > > > > > > > If the RM details are stored in the pom, then it is all too easy for > > > > the wrong values to be used. > > > > > > > > Thanks, > > > > Sebb > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
