[
https://issues.apache.org/jira/browse/UIMA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17029896#comment-17029896
]
Marshall Schor commented on UIMA-6185:
--------------------------------------
I agree that for a repeatable build, all versions should be locked down at some
level.
Individual projects can decide when to use a new plugin version, in their
individual POM. But I think for many projects, they would rather let these
progress as common shared POMs are updated.
The uima-wide pom factors out some common things. It has a dependency on a
specific version of the apache-wide pom. So when that dependency is updated,
it is "locked down" in the sense that the builds are repeatable.
For maven plugins, I think it is preferable to occasionally have these updated
to the apache-wide current versions, because these keep up to date with the
(slowly) evolving maven ecosystem.
Re: transparency: I was thinking this proposal should have been called out for
discussion explicitly in the dev list (I've done that...). I continue to feel
that we should be flexible on the PR/review model vs commit to master. I agree
with you that for significant changes, the PR/review model is appropriate,
provided there's someone suitable willing and able to do a good review job :) .
I continue to feel that for small / trivial changes, no review is needed, when
the likelyhood of needing to roll back is small.
> 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)
