Re: [ALL] pom.xml should not contain RM details

2023-10-05 Thread sebb
On Thu, 5 Oct 2023 at 00:13, Phil Steitz wrote: > > On Tue, Oct 3, 2023 at 1:26 AM sebb 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

Re: [ALL] pom.xml should not contain RM details

2023-10-04 Thread Phil Steitz
On Tue, Oct 3, 2023 at 1:26 AM sebb 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? Why do they need to be there at all? Can't they just be provided on the

Re: [ALL] pom.xml should not contain RM details

2023-10-03 Thread sebb
I've already made a start on that. I'm replacing the entries with comments so people know where to defined them. On Tue, 3 Oct 2023 at 12:44, Bruno Kinoshita wrote: > > Thank you Sebb and thank you Gary! > > On Tue, 3 Oct 2023 at 13:42, Gary Gregory wrote: > > > FYI, I'll do a pass over all

Re: [ALL] pom.xml should not contain RM details

2023-10-03 Thread Bruno Kinoshita
Thank you Sebb and thank you Gary! On Tue, 3 Oct 2023 at 13:42, Gary Gregory wrote: > FYI, I'll do a pass over all poms and remove those properties... > > Gary > > On Mon, Oct 2, 2023, 6:58 PM sebb wrote: > > > As the subject says, please do not use the pom to store RM details such > as > > >

Re: [ALL] pom.xml should not contain RM details

2023-10-03 Thread Gary Gregory
FYI, I'll do a pass over all poms and remove those properties... Gary On Mon, Oct 2, 2023, 6:58 PM sebb 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,

Re: [ALL] pom.xml should not contain RM details

2023-10-03 Thread sebb
On Tue, 3 Oct 2023 at 09:48, Bruno Kinoshita wrote: > > I recall seeing these properties in the commons-release-plugin docs I use > as reference whenever I need to release a component (which the last time > was a long time ago, sorry). > > The commons-release-plugin links to this page: > >

Re: [ALL] pom.xml should not contain RM details

2023-10-03 Thread Bruno Kinoshita
I recall seeing these properties in the commons-release-plugin docs I use as reference whenever I need to release a component (which the last time was a long time ago, sorry). The commons-release-plugin links to this page: https://commons.apache.org/releases/prepare.html Maybe we need to update

Re: [ALL] pom.xml should not contain RM details

2023-10-03 Thread sebb
The properties are used by the release plugin. But since they are unique to the user, they do not belong in the shared pom. On Tue, 3 Oct 2023 at 02:33, Phil Steitz wrote: > > +1 but why then are those properties there? > > Phil > > > On Oct 2, 2023, at 3:58 PM, sebb wrote: > > > > As the

Re: [ALL] pom.xml should not contain RM details

2023-10-02 Thread Phil Steitz
+1 but why then are those properties there? Phil > On Oct 2, 2023, at 3:58 PM, sebb 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

[ALL] pom.xml should not contain RM details

2023-10-02 Thread sebb
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