[
https://issues.apache.org/jira/browse/AVRO-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17275390#comment-17275390
]
ASF subversion and git services commented on AVRO-2860:
-------------------------------------------------------
Commit 41587a9099eae06ceb615ec440ed70e767af02b6 in avro's branch
refs/heads/dependabot/maven/lang/java/org.apache.felix-maven-bundle-plugin-5.1.1
from Fokko Driesprong
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=41587a9 ]
AVRO-2860: More Closely Adhere to ASF Parent POM (#1072)
* AVRO-2860: More Closely Adhere to ASF Parent POM
* Remove superfluous overrides
* AVRO-2860: Fix the missing property
Co-authored-by: David Mollitor <[email protected]>
> More Closely Adhere to ASF Parent POM
> -------------------------------------
>
> Key: AVRO-2860
> URL: https://issues.apache.org/jira/browse/AVRO-2860
> Project: Apache Avro
> Issue Type: Improvement
> Reporter: David Mollitor
> Assignee: David Mollitor
> Priority: Major
>
> So, I see that the project currently inherits from:
> {code:xml}
> <parent>
> <groupId>org.apache</groupId>
> <artifactId>apache</artifactId>
> <version>23</version>
> </parent>
> {code}
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
