incubator-ctakes-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chen, Pei" <>
Subject RE: ctakes-resources
Date Tue, 25 Sep 2012 21:22:27 GMT
I think Brandyn and others had a reasonable suggestion to use the name instead of location
paths in those pesky descriptor xml files- Assuming they're in the classpath (placed in src/main/resources).
I'll take a stab at this later this week if I get a chance.  But trunk *should* compile now
in case other want to start working on it.  Apologies in advanced if I broke someone's build
at this point- it was a pretty large change...

Troy: If we do this correctly, this should be transparent (if not easier) to end-users.

> -----Original Message-----
> From: Coarr, Matt []
> Sent: Tuesday, September 25, 2012 11:16 AM
> To:
> Subject: Re: ctakes-resources
> Trying to distill some of the suggestions...
> Could we have two top level directories in svn -- main-modules and
> resource-modules?  And then below resource-modules we could have
> dictionary-lookup-resources, lvg-resources, etc.
> * (ctakes svn trunk)
>   * main-modules
>     * core
>     * clinical-documents-pipeline
>     * dictionary-lookup
>     * lvg
>   * resource-modules
>     * dictionary-lookup-resources
>     * lvg-resources
> This means you could just checkout main-modules and keep it pretty small
> (mostly just code and descriptors).  Then you can checkout "main-modules"
> a a few times to have different working directories without taking up too
> much space (perhaps a working copy for trunk development, another for
> clean copy of latest release, a third for an experimental branch, and perhaps
> a fourth for a branch to patch the last release).  But they could all use the
> same resources.
> And ideally, most users and developers could pull those resources from the
> maven repository as an artifact, unless they were working on packaging up a
> new version of those resources.
> Matt

View raw message