[
https://issues.apache.org/jira/browse/AVRO-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Mollitor updated AVRO-2860:
---------------------------------
Description:
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. The Avro project should be pretty
conservative here and be sticking as closely as possible to the parent POM in
the same spirit that Avro is build with Java 1.8 (which is EOL).
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.
was:
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. The Avro project should be pretty
conservative here and be sticking as closely as possible to the parent POM in
the same spirit that Avro is build with Java 1.8 (which is EOL). This will
make Avro easier to consume for upstream projects that also inherit from the
ASF Parent POM. They shouldn't have to be doing anything special to allow for
Avro overrided values.
I propose reverting some plugin versions so that the project more closely
aligns with the POM.
> 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. The Avro project should be
> pretty conservative here and be sticking as closely as possible to the parent
> POM in the same spirit that Avro is build with Java 1.8 (which is EOL).
> 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)
