Hi, I just tried to compile uimaj from trunk to check out the JSON
serialization, and I am getting build failures (on OSX 10.9):

Failed tests:
>
>   org.apache.uima.cas.impl.JsonCasSerializerTest#testNameSpaceCollision
> ComparisonFailure
>
>   org.apache.uima.cas.impl.JsonCasSerializerTest#testAllValues
> ComparisonFailure
>
>   org.apache.uima.cas.impl.JsonCasSerializerTest#testMultipleViews
> ComparisonFailure
>
>   org.apache.uima.cas.impl.JsonCasSerializerTest#testDelta
> ComparisonFailure exp...
>

In the surefire reports I see things that look related to Windows line
endings. What information would you need?

-- Jens


On Tue, Aug 19, 2014 at 9:33 PM, Marshall Schor (JIRA) <[email protected]>
wrote:

>
>      [
> https://issues.apache.org/jira/browse/UIMA-3969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Marshall Schor resolved UIMA-3969.
> ----------------------------------
>
>     Resolution: Fixed
>
> > Add JSON Serialization for CASs and UIMA Descriptors
> > ----------------------------------------------------
> >
> >                 Key: UIMA-3969
> >                 URL: https://issues.apache.org/jira/browse/UIMA-3969
> >             Project: UIMA
> >          Issue Type: New Feature
> >          Components: Core Java Framework
> >    Affects Versions: 2.6.0SDK
> >            Reporter: Marshall Schor
> >            Assignee: Marshall Schor
> >            Priority: Minor
> >             Fix For: 2.6.1SDK
> >
> >
> > Recent trends toward moving things into the cloud motivated me to
> consider what a JSON serialization of the CAS and descriptor metadata (more
> particularly, type systems) might look like.
> > I've put up a Wiki page with some of the thoughts so far in this
> exploration, here:
> https://cwiki.apache.org/confluence/display/UIMA/JSON+serialization+for+UIMA
> > I'm also fooling around with a proof-of-concept implementation, based on
> our current XMI serialization for the CAS, as well as our
> MetaDataObject_impl serialization for UIMA descriptors, in order to work
> out the details.  There are additional nits (like how to configure things)
> not yet worked out.
> > Comments and discussion appreciated; I've put this up as a Jira to
> record them together - but feel free to use email also for any comments you
> feel might be better being more ephemeral.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.2#6252)
>

Reply via email to