[
https://issues.apache.org/jira/browse/UIMA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17029872#comment-17029872
]
Richard Eckart de Castilho commented on UIMA-6185:
--------------------------------------------------
IMHO for a repeatable build, all versions should be locked down at some level.
IMHO we should decide when to use a new plugin version, not the plugin
provider. We also lock down dependency versions, right?
A comment would be warranted if there is a specific reason to stay at a
particular version rather than allowing upgrading to the latest version.
I'd rather lock them down at a level we control than at a level we do not
control - but my opinion about that is not too strong.
Regarding transparency: this is why I much prefer the PR/review model instead
of the commit-to-master-and-maybe-discuss-later model because review **is**
build-in. Had we not been using the PR/review model, I may never have
made/proposed these changes.
> 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)
