headers
Jörn Kottmann (JIRA | 1 Jun 2011 12:37
Picon
Favicon

[jira] [Closed] (UIMA-2119) Cas Editor should prefix names of contributions with UIMA


     [
https://issues.apache.org/jira/browse/UIMA-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jörn Kottmann closed UIMA-2119.
-------------------------------

    Assignee: Jörn Kottmann  (was: Marshall Schor)

> Cas Editor should prefix names of contributions with UIMA
> ---------------------------------------------------------
>
>                 Key: UIMA-2119
>                 URL: https://issues.apache.org/jira/browse/UIMA-2119
>             Project: UIMA
>          Issue Type: Improvement
>          Components: CasEditor
>    Affects Versions: 2.3.1SDK
>            Reporter: Jörn Kottmann
>            Assignee: Jörn Kottmann
>            Priority: Trivial
>             Fix For: 2.3.2SDK
>
>
> The Cas Editor should prefix contribution names with UIMA.
> - Rename view category from "Cas Editor" to "UIMA Cas Editor"
> - Rename "Annotation Editor" to "UIMA Annotation Editor" (or a different name)

--
This message is automatically generated by JIRA.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jörn Kottmann (JIRA | 1 Jun 2011 12:37
Picon
Favicon

[jira] [Closed] (UIMA-2012) Handling of imported type systems causes error


     [
https://issues.apache.org/jira/browse/UIMA-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jörn Kottmann closed UIMA-2012.
-------------------------------

> Handling of imported type systems causes error
> ----------------------------------------------
>
>                 Key: UIMA-2012
>                 URL: https://issues.apache.org/jira/browse/UIMA-2012
>             Project: UIMA
>          Issue Type: Bug
>          Components: CasEditor
>            Reporter: Peter Klügl
>            Assignee: Jörn Kottmann
>            Priority: Minor
>             Fix For: 2.3.2SDK
>
>
> When opening a XMI with a type system that imports other type systems (by location), the editor displays an
error. This problem occurs, if XMI contains data of types that are specified in the imported type systems.
May be related to UIMA-2011.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
(Continue reading)

Permalink | Reply | 0 comments |
headers
Apache Jenkins Server | 1 Jun 2011 13:16
Picon

Build failed in Jenkins: UIMA-SDK #58

See <https://builds.apache.org/hudson/job/UIMA-SDK/58/changes>

Changes:

[joern] No jira, removed unused import.

------------------------------------------
Started by an SCM change
Building remotely on solaris1
Updating https://svn.apache.org/repos/asf/uima/uimaj/trunk
U         uimaj-ep-cas-editor/src/main/java/org/apache/uima/caseditor/editor/AnnotationEditor.java
U         uimaj-ep-cas-editor/src/main/java/org/apache/uima/caseditor/CasEditorPlugin.java
U         uimaj-ep-cas-editor/plugin.xml
At revision 1130096
Found mavenVersion 3.0.2 from file jar:file:/home/hudson/tools/maven/apache-maven-3.0.2/lib/maven-core-3.0.2.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties
Parsing POMs
ERROR: Failed to parse POMs
hudson.util.IOException2: remote file operation failed:
<https://builds.apache.org/hudson/job/UIMA-SDK/ws/trunk> at hudson.remoting.Channel <at> 690613b3:solaris1
	at hudson.FilePath.act(FilePath.java:752)
	at hudson.FilePath.act(FilePath.java:738)
	at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:817)
	at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:617)
	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:429)
	at hudson.model.Run.run(Run.java:1374)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:467)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:145)
Caused by: hudson.remoting.ProxyException:
hudson.maven.MavenModuleSetBuild$MavenExecutionException:
(Continue reading)

Permalink | Reply | 2 comments |
headers
Jörn Kottmann | 1 Jun 2011 14:18
Picon

Cas Editor split for easy RCP app integration

Hi all,

I am proposing that we split the Cas Editor into two parts,
one core part and one part which deals with eclipse ide integration.

The core part will be designed to be reusable by RCP applications which
need to perform CAS viewing/editing. An example for such an application
is an annotation tool which is connected to document repository.

The ide part will ensure that the Cas Editor is integrated into the eclipse
ide as it is now.

As part of the split I would like to work with the community to define 
an API which
can be used to integrate and extend the Cas Editor in various ways.

Any opinions?

Jörn
Permalink | Reply | 7 comments |
headers
Michael Tanenblatt | 1 Jun 2011 14:25

Re: Cas Editor split for easy RCP app integration

I think t his would be an excellent thing to do

On Jun 1, 2011, at 8:18 AM, Jörn Kottmann wrote:

> Hi all,
> 
> I am proposing that we split the Cas Editor into two parts,
> one core part and one part which deals with eclipse ide integration.
> 
> The core part will be designed to be reusable by RCP applications which
> need to perform CAS viewing/editing. An example for such an application
> is an annotation tool which is connected to document repository.
> 
> The ide part will ensure that the Cas Editor is integrated into the eclipse
> ide as it is now.
> 
> As part of the split I would like to work with the community to define an API which
> can be used to integrate and extend the Cas Editor in various ways.
> 
> Any opinions?
> 
> Jörn
Permalink | Reply | 5 comments |
headers
Richard Eckart de Castilho | 1 Jun 2011 15:48
Picon
Favicon

Re: Cas Editor split for easy RCP app integration

Sounds good to me. That way the Eclipse integration could also take care of resolving imports via the Java
Classpath if a XMI resides within a Java project.

Cheers,

Richard

Am 01.06.2011 um 14:25 schrieb Michael Tanenblatt:

> I think t his would be an excellent thing to do
> 
> On Jun 1, 2011, at 8:18 AM, Jörn Kottmann wrote:
> 
>> Hi all,
>> 
>> I am proposing that we split the Cas Editor into two parts,
>> one core part and one part which deals with eclipse ide integration.
>> 
>> The core part will be designed to be reusable by RCP applications which
>> need to perform CAS viewing/editing. An example for such an application
>> is an annotation tool which is connected to document repository.
>> 
>> The ide part will ensure that the Cas Editor is integrated into the eclipse
>> ide as it is now.
>> 
>> As part of the split I would like to work with the community to define an API which
>> can be used to integrate and extend the Cas Editor in various ways.
>> 
>> Any opinions?
>>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Tommaso Teofili | 1 Jun 2011 17:59
Picon
Gravatar

Re: Cas Editor split for easy RCP app integration

+1, really a nice idea Jörn , that may help other existing platforms (like
IntelliJ) developing a specialized CAS Editor (or create new UI tool for
UIMA).
Tommaso

2011/6/1 Michael Tanenblatt <slothrop@...>

> I think t his would be an excellent thing to do
>
> On Jun 1, 2011, at 8:18 AM, Jörn Kottmann wrote:
>
> > Hi all,
> >
> > I am proposing that we split the Cas Editor into two parts,
> > one core part and one part which deals with eclipse ide integration.
> >
> > The core part will be designed to be reusable by RCP applications which
> > need to perform CAS viewing/editing. An example for such an application
> > is an annotation tool which is connected to document repository.
> >
> > The ide part will ensure that the Cas Editor is integrated into the
> eclipse
> > ide as it is now.
> >
> > As part of the split I would like to work with the community to define an
> API which
> > can be used to integrate and extend the Cas Editor in various ways.
> >
> > Any opinions?
> >
(Continue reading)

Permalink | Reply | 3 comments |
headers
Jörn Kottmann | 2 Jun 2011 08:37
Picon

Re: Cas Editor split for easy RCP app integration

On 6/1/11 5:59 PM, Tommaso Teofili wrote:
> +1, really a nice idea Jörn , that may help other existing platforms (like
> IntelliJ) developing a specialized CAS Editor (or create new UI tool for
> UIMA).
  I cannot see how that helps the development of Cas Editors for other
non-eclipse platforms?

The core part will still depend on eclipse and contains the Annotation
Editor together with the views.

Jörn
Permalink | Reply | 2 comments |
headers
Tommaso Teofili | 2 Jun 2011 09:49
Picon
Gravatar

Re: Cas Editor split for easy RCP app integration

2011/6/2 Jörn Kottmann <kottmann@...>

> On 6/1/11 5:59 PM, Tommaso Teofili wrote:
>
>> +1, really a nice idea Jörn , that may help other existing platforms (like
>> IntelliJ) developing a specialized CAS Editor (or create new UI tool for
>> UIMA).
>>
>  I cannot see how that helps the development of Cas Editors for other
> non-eclipse platforms?
>
> The core part will still depend on eclipse and contains the Annotation
> Editor together with the views.
>

from what you said in the first email I understood the core wouldn't have
contained Eclipse dependencies, however I still think this refactoring is a
good thing.
Tommaso
Permalink | Reply | 1 comment |
headers
Jörn Kottmann | 2 Jun 2011 11:27
Picon

Re: Cas Editor split for easy RCP app integration

On 6/2/11 9:49 AM, Tommaso Teofili wrote:
> 2011/6/2 Jörn Kottmann<kottmann@...>
>
>> On 6/1/11 5:59 PM, Tommaso Teofili wrote:
>>
>>> +1, really a nice idea Jörn , that may help other existing platforms (like
>>> IntelliJ) developing a specialized CAS Editor (or create new UI tool for
>>> UIMA).
>>>
>>   I cannot see how that helps the development of Cas Editors for other
>> non-eclipse platforms?
>>
>> The core part will still depend on eclipse and contains the Annotation
>> Editor together with the views.
>>
> from what you said in the first email I understood the core wouldn't have
> contained Eclipse dependencies, however I still think this refactoring is a
> good thing.

No, that is a misunderstanding, almost any code inside the Cas Editor 
depends
on eclipse APIs.

Jörn
Permalink | Reply | 0 comments |

Gmane