You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Adam Lally (JIRA)" <ui...@incubator.apache.org> on 2007/01/08 19:49:27 UTC
[jira] Created: (UIMA-165) Need JCAS fixes for DocumentatAnnotation
and type merging
Need JCAS fixes for DocumentatAnnotation and type merging
---------------------------------------------------------
Key: UIMA-165
URL: https://issues.apache.org/jira/browse/UIMA-165
Project: UIMA
Issue Type: Bug
Components: Core Java Framework
Reporter: Adam Lally
Assigned To: Adam Lally
Fix For: 2.1
The current build has the DocumentAnnotation JCas cover class in uima-core.jar. This creates a problem for anyone who has added features to this type and run JCasGen.
Fixes as suggested by Marshall and agreed by Adam:
> a) Do the work to make it easy to get singletons (or whatever we're
> calling this feature) out of the CAS
>
> b) Change JCasGen to not generate DocumentAnnotation if the merged
> version = the base
>
> c) Add the DocumentAnnotation jar back to the build, with instructions
> to remove it from the
> deployment and substitute a JCasGenerated one if the application needs a
> special one.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (UIMA-165) Need JCAS fixes for
DocumentatAnnotation and type merging
Posted by "Adam Lally (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Lally resolved UIMA-165.
-----------------------------
Resolution: Fixed
> Need JCAS fixes for DocumentatAnnotation and type merging
> ---------------------------------------------------------
>
> Key: UIMA-165
> URL: https://issues.apache.org/jira/browse/UIMA-165
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Reporter: Adam Lally
> Assigned To: Adam Lally
> Fix For: 2.1
>
>
> The current build has the DocumentAnnotation JCas cover class in uima-core.jar. This creates a problem for anyone who has added features to this type and run JCasGen.
> Fixes as suggested by Marshall and agreed by Adam:
> > a) Do the work to make it easy to get singletons (or whatever we're
> > calling this feature) out of the CAS
> >
> > b) Change JCasGen to not generate DocumentAnnotation if the merged
> > version = the base
> >
> > c) Add the DocumentAnnotation jar back to the build, with instructions
> > to remove it from the
> > deployment and substitute a JCasGenerated one if the application needs a
> > special one.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work started: (UIMA-165) Need JCAS fixes for
DocumentatAnnotation and type merging
Posted by "Adam Lally (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on UIMA-165 started by Adam Lally.
> Need JCAS fixes for DocumentatAnnotation and type merging
> ---------------------------------------------------------
>
> Key: UIMA-165
> URL: https://issues.apache.org/jira/browse/UIMA-165
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Reporter: Adam Lally
> Assigned To: Adam Lally
> Fix For: 2.1
>
>
> The current build has the DocumentAnnotation JCas cover class in uima-core.jar. This creates a problem for anyone who has added features to this type and run JCasGen.
> Fixes as suggested by Marshall and agreed by Adam:
> > a) Do the work to make it easy to get singletons (or whatever we're
> > calling this feature) out of the CAS
> >
> > b) Change JCasGen to not generate DocumentAnnotation if the merged
> > version = the base
> >
> > c) Add the DocumentAnnotation jar back to the build, with instructions
> > to remove it from the
> > deployment and substitute a JCasGenerated one if the application needs a
> > special one.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (UIMA-165) Need JCAS fixes for DocumentatAnnotation
and type merging
Posted by "Adam Lally (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Lally closed UIMA-165.
---------------------------
> Need JCAS fixes for DocumentatAnnotation and type merging
> ---------------------------------------------------------
>
> Key: UIMA-165
> URL: https://issues.apache.org/jira/browse/UIMA-165
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Reporter: Adam Lally
> Assigned To: Adam Lally
> Fix For: 2.1
>
>
> The current build has the DocumentAnnotation JCas cover class in uima-core.jar. This creates a problem for anyone who has added features to this type and run JCasGen.
> Fixes as suggested by Marshall and agreed by Adam:
> > a) Do the work to make it easy to get singletons (or whatever we're
> > calling this feature) out of the CAS
> >
> > b) Change JCasGen to not generate DocumentAnnotation if the merged
> > version = the base
> >
> > c) Add the DocumentAnnotation jar back to the build, with instructions
> > to remove it from the
> > deployment and substitute a JCasGenerated one if the application needs a
> > special one.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira