[AVRO-2860] More Closely Adhere to ASF Parent POM

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.11.0, 1.10.2
• Assignee: David Mollitor
• Reporter: David Mollitor
• Created: 04/Jun/20 17:36
• Updated: 05/Mar/21 16:38
• Resolved: 05/Mar/21 16:38

Description

So, I see that the project currently inherits from:

 <parent>
    <groupId>org.apache</groupId>
    <artifactId>apache</artifactId>
    <version>23</version>
  </parent>

That's great.

However, there are quite a few places where the values from this parent POM are being overrided and I'm not quite sure why. I would suggest that the Avro project should be pretty conservative here and be sticking as closely as possible to the parent POM. It will make things more maintainable, as long as the project updates the ASF Parent POM periodically, it will be pretty up to date with plugins and not have to manage each one individually.

I propose reverting some plugin versions so that the project more closely aligns with the POM and then the project need only stay in sync with the parent POM releases and not each plugin individually.

Issue Links

• links to: GitHub Pull Request #1072