[
https://issues.apache.org/jira/browse/UIMA-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431643#comment-15431643
]
Marshall Schor commented on UIMA-5066:
--------------------------------------
I noticed what appears to be a bug in the semantic versioning code. Adding an
exclude for org.apache.uima.cas.CAS also seems to exclude all the other classes
giving errors; removing that one exclude caused the errors in the other classes
to re-appear. I noted this in the POM, and "tested" without the CAS exclusion
to verify there were no other issues other than the ones we're allowing in
2.9.0 (which are: adding the CasIOUtils class, adding the CasLoadMode enum,
adding enums to SerialiVersion, adding error messages to CasRuntimeException,
and fixing the spelling error in CAS.)
> fix issues in 2.9.0 re: semantic versioning
> -------------------------------------------
>
> Key: UIMA-5066
> URL: https://issues.apache.org/jira/browse/UIMA-5066
> Project: UIMA
> Issue Type: Task
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Fix For: 2.9.0SDK
>
>
> Remove the exclude element in uimaj-parent pom for semantic versioning that
> should not be needed anymore. The following issues then show up:
> 1) exclude added classes - these have a small chance of causing backward
> incomatibility (they would do so if the class already existed in the users
> code, but this is unlikely due to the package naming conventions):
> CasIOUtils, CasLoadMode.
> 2) change internal use only methods from public, remove unused ones, and
> remove change to Interface: XmlCasDeserializer (deserializerR, 2x),
> getImportUrlsCache.
> 3) exclude change to CAS interface fixing spelling issue in
> FEATURE_FULL_NAME_SOFA.
> 4) exclude changes adding error messages to CASRuntimeException and enums to
> SerialiFormat
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
