[
https://issues.apache.org/jira/browse/UIMA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17016981#comment-17016981
]
Richard Eckart de Castilho commented on UIMA-5936:
--------------------------------------------------
Changes that should end up in v2 should always go to master-v2 first. If you
made a change in v3 and later figure out it should have been in v2 as well,
you'd create a new branch based on v2, cherry-pick the changes from v3 into
that branch and then do a PR. After the PR has been merged into v2, v2 should
once again be merged into v3 to go back to the desired situation where v2 can
easily be merged into v3.
> PearSpecifier should be able to store every parametertype that
> analysisEngines support
> --------------------------------------------------------------------------------------
>
> Key: UIMA-5936
> URL: https://issues.apache.org/jira/browse/UIMA-5936
> Project: UIMA
> Issue Type: Improvement
> Affects Versions: 2.10.3SDK
> Reporter: Matthias Koch
> Assignee: Richard Eckart de Castilho
> Priority: Major
> Attachments: UIMA-5936.diff
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The pearSpecifier currently holds a Parameter_impl(String, String). This
> limits the fields of application. Therefore we changed the specifier to store
> an array of nameValuePairs, so all possible analysisEngine parameters are
> supported.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
