[
https://issues.apache.org/jira/browse/UIMA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17029855#comment-17029855
]
Marshall Schor commented on UIMA-6185:
--------------------------------------
I think these kinds of proposals/changes should be discussed more transparently.
It seems to me that locking down versions is only (historically) needed very
occasionally.
If a version needs to be locked down, I would rather see it done at the project
level, rather than at a uima-wide level, unless there is a known issue that
affects everything.
And then, for those issues, I would suggest a big comment in the file locking
it down, pointing to the reasons ( a Jira issue or other explanation) as to why
this is being done.
So my view is not to lock these down in the uima-wide pom, unless we know of a
requirement that spans all (or at least most) of our projects.
Other views pro / con ?
> 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)
