[
https://issues.apache.org/jira/browse/UIMA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17029947#comment-17029947
]
Marshall Schor commented on UIMA-6185:
--------------------------------------
That comment was just to document which maven plugins versions we were
inheriting from the apache-wide pom.
We always have a choice *not* to update the parent-pom of the uima-wide pom, to
avoid checking if it's ok to update these. If people didn't want to do that
work, it would seem the right answer would be to not update the parent-pom.
I agree that if there was a use case, where (a) we needed to update to the
current apache-wide pom as the parent, but (b) didn't want to change the
version numbers of the maven plugins we were using, then we could lock these
down in the uima-wide pom. But I don't think we have that use case... ? I
would have thought the reason to upgrade to the more recent apache-wide pom was
to "pickup" the updates to the maven plugin tooling.
> Upgrade parent POM plugins
> --------------------------
>
> Key: UIMA-6185
> URL: https://issues.apache.org/jira/browse/UIMA-6185
> Project: UIMA
> Issue Type: Improvement
> Components: Build, Packaging and Test
> Reporter: Richard Eckart de Castilho
> Assignee: Richard Eckart de Castilho
> Priority: Minor
> Fix For: parent-pom-14
>
>
> * upgrade to Apache parent POM 23
> * upgrade Maven plugin versions where feasible
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
