Re: ASF Maven parent pom and use properties to define the versions of plugins

Hi Currently we have two propositions: 1. Versions - like mavenCleanPluginVersion [1] 2. version. - like version.maven-clean-plugin [2] As I see from comments on PR more people is for option 2 [1] https://github.com/apache/maven-apache-parent/pull/155 [2]

Re: ASF Maven parent pom and use properties to define the versions of plugins

> On Jun 7, 2023, at 9:36 PM, Christopher wrote: > > I think your concern about the risks of updating plugin versions is > valid, but I don't think it has anything to do with how those plugin > versions are expressed in the parent POM. If anything, using > properties to express these versions

Re: ASF Maven parent pom and use properties to define the versions of plugins

On Wed, Jun 7, 2023 at 8:26 PM Allen Wittenauer wrote: > > > > > On Jun 7, 2023, at 11:46 AM, Karl Heinz Marbaise wrote: > > > > Hi, > > On 07.06.23 19:23, Allen Wittenauer wrote: > >> > >> > >>> On Jun 5, 2023, at 3:28 PM, Slawomir Jaranowski > >>> wrote: > >>> > >>> Hi, > >>> > >>> I want to

Re: ASF Maven parent pom and use properties to define the versions of plugins

> On Jun 7, 2023, at 11:46 AM, Karl Heinz Marbaise wrote: > > Hi, > On 07.06.23 19:23, Allen Wittenauer wrote: >> >> >>> On Jun 5, 2023, at 3:28 PM, Slawomir Jaranowski >>> wrote: >>> >>> Hi, >>> >>> I want to introduce properties to define versions of plugins. >>> I have prepared PR

Re: ASF Maven parent pom and use properties to define the versions of plugins

I agree with Christopher FWIW, I don't see the technical reason to not do this. I'd use this feature in Apache Commons Parent and other POMs when needed for example. Gary On Wed, Jun 7, 2023, 18:42 Christopher wrote: > It doesn't matter that some projects are stuck on old versions, or > their

Re: ASF Maven parent pom and use properties to define the versions of plugins

Forgive my typo there should be an extra layer of ` ... ` in the latter example. On Wed, Jun 7, 2023 at 6:41 PM Christopher wrote: > > It doesn't matter that some projects are stuck on old versions, or > their reasons why. That's not a valid technical reason to -1 the > proposed changes, as

Re: ASF Maven parent pom and use properties to define the versions of plugins

It doesn't matter that some projects are stuck on old versions, or their reasons why. That's not a valid technical reason to -1 the proposed changes, as it has nothing to do with the proposed changes. The proposal was to use properties in the Apache parent POM (MPOM) to make it easier for

Re: ASF Maven parent pom and use properties to define the versions of plugins

Hi, On 07.06.23 19:23, Allen Wittenauer wrote: On Jun 5, 2023, at 3:28 PM, Slawomir Jaranowski wrote: Hi, I want to introduce properties to define versions of plugins. I have prepared PR [1] and we have a discussion about properties schema for such purposes. Because AFS Maven parent is

Re: ASF Maven parent pom and use properties to define the versions of plugins

> On Jun 5, 2023, at 3:28 PM, Slawomir Jaranowski > wrote: > > Hi, > > I want to introduce properties to define versions of plugins. > I have prepared PR [1] and we have a discussion about properties schema for > such purposes. > > Because AFS Maven parent is used by other ASF projects,

Re: ASF Maven parent pom and use properties to define the versions of plugins

> I want to introduce properties to define versions of plugins. Have you considered publishing a BOM with versions instead? Then the ones who need the versions could import the BOM. I believe the task of "sharing a set of versions among projects" should better be approached with