Re: Eclise Annotation Editor
All the code is owned by my employer Calcucare GmbH (www.calcucare.com). I think we have to sign the CCLA too. CCLA and ICLA are now signed and send via facsimile. How show we proceed now ? I can prepare the code at sourceforge for moving to apache this would be: + changing the license form cpl to apache license + clean code from eclipse source code + adapt your code guideline + make a last release at sourceforge + clean-up code Jörn
Re: Eclise Annotation Editor
thanks, I'll take a look over the holidays. Sorry if things seems a bit slow here right now, blame it on the approaching holidays ;-) Here are a couple of things we need to take care of for your code to be able to move to Apache. I assume/hope you will want to move with your code and keep contributing to UIMA. To be able to do that, you will need to sign and send in an Individual Contributor License Agreement (ICLA, http://www.apache.org/licenses/#clas). Only when you're CLA is listed can we start accepting substantial contributions from you. You can check if your CLA has been processed here: http:// people.apache.org/~jim/committers.html. If you have any questions about this process, feel free to ask. Did you write all the code you're planning to contribute yourself? If yes, then things are (hopefully) fairly simple. If other people have contributed, or if you have reused other people's code (be it open source or not), we'll need to look into that. Some source files ( 10) are derived from eclipse code. I have always documented this in the header. All other code was written by me. I can just remove theses files for the contribution and than rewrite them. Derived files are e.g. drag handler, drop handler, copy action and paste actions of the Corpus Explorer. All the code is owned by my employer Calcucare GmbH (www.calcucare.com). I think we have to sign the CCLA too. Jörn
Re: Eclise Annotation Editor
Jörn Kottmann wrote: snip Some source files ( 10) are derived from eclipse code. I have always documented this in the header. All other code was written by me. I can just remove theses files for the contribution and than rewrite them. Derived files are e.g. drag handler, drop handler, copy action and paste actions of the Corpus Explorer. Yes, I see you've been doing your homework on this :-) Source files derived from Eclipse source cannot be part of an Apache distribution because of license incompatibilities. So your suggested approach is a good one. It would also be possible to leave these particular files outside of our Apache project, and just include the binaries, together with a pointer to where to get the source. That way, Apache is not distributing this source. But then, you would have a split project, with some source on Apache, and other source elsewhere. That's probably not such a good thing. All the code is owned by my employer Calcucare GmbH (www.calcucare.com). I think we have to sign the CCLA too. Right, that's correct. -Marshall
Re: Eclise Annotation Editor
On 12/18/06, Jörn Kottmann [EMAIL PROTECTED] wrote: The new release is out now. I suggest to to take a look at the sample workspace. When I run the tae.exe and select the sample-workspace, I see an error in the Corpus Explorer view: java.lang.NullPointerException at net.sf.tae.ui.corpusview.CorpusExplorerView.createPartControl(CorpusExplorerView.java:91) at org.eclipse.ui.internal.ViewReference.createPartHelper(ViewReference.java:332) at org.eclipse.ui.internal.ViewReference.createPart(ViewReference.java:197) ... Also if I try to open one of the XCAS files I get: java.lang.NullPointerException at net.sf.tae.editor.AnnotationDocumentProvider.setDocumentContent(AnnotationDocumentProvider.java:65) at org.eclipse.ui.editors.text.StorageDocumentProvider.createDocument(StorageDocumentProvider.java:228) at org.eclipse.ui.editors.text.FileDocumentProvider.createElementInfo(FileDocumentProvider.java:717) -Adam
Re: Eclise Annotation Editor
Hmmm.. I tried adding a MANIFEST.MF file including this line, but no luck. I guess I'll wait for the next release. The new release is out now. I suggest to to take a look at the sample workspace. To add an annotation mark a piece of text and press shit + enter in the editor or delete to remove it. The annotation type can be changed in the context menu of the editor (change it to see the different annotations or use Show Annotations, colors and type can be configured at project properties). The outline and properties view shows information about the annotations, there is also a special view for feature structures. The release also contains OpenNLP annotators (cvs head of the new official openlp.uima package). The sample workspace includes descriptors for sentence detector, tokenizer and pos-tagger. They can be run from the context menu of the xcas file. Please note if the editor currently shows this file, that the editor must be reopened to show the new annotations. Jörn
Re: Eclise Annotation Editor
I got this from SourceForge but was unable to run it. The net.sf.tae plugins show up with red X's in the plugin registry, even though I've installed GEF and UIMA 1.3.2. There's nothing in the error log. What might I be doing wrong? There is a compatibility issue with the plugin loading mechanism used by uima and the OSGi Runtime used by eclipse. UIMA uses its current classloader (Class.forName(...)) to load extensions like Annotators, CASConsumer, etc. This behavior is not well supported inside the OSGI Runtime inside OSGi a plugin defines a so called extension-points. These extension-points than can be extended by other plugins. All class loading issues are handled by the OSGi Runtime. For the uima case there is a work-around (Eclipse-BuddyPolicy: dependent) inside eclipse, but this must be enabled in the uima eclipse plugin descriptor. Currently it is not. Maybe it would be a great to use OSGi for uima too. The next tae release will include everything that is necessary to run it out of the box. Jörn
Re: Eclise Annotation Editor
This is an un-popular issue that pop-ups from time to time ! Need to create a new manifest.mf that includes Eclipse-BuddyPolicy: registered for any UIMA 1.x. Regards, Tong On 12/15/06, Jörn Kottmann [EMAIL PROTECTED] wrote: I got this from SourceForge but was unable to run it. The net.sf.tae plugins show up with red X's in the plugin registry, even though I've installed GEF and UIMA 1.3.2. There's nothing in the error log. What might I be doing wrong? There is a compatibility issue with the plugin loading mechanism used by uima and the OSGi Runtime used by eclipse. UIMA uses its current classloader (Class.forName(...)) to load extensions like Annotators, CASConsumer, etc. This behavior is not well supported inside the OSGI Runtime inside OSGi a plugin defines a so called extension-points. These extension-points than can be extended by other plugins. All class loading issues are handled by the OSGi Runtime. For the uima case there is a work-around (Eclipse-BuddyPolicy: dependent) inside eclipse, but this must be enabled in the uima eclipse plugin descriptor. Currently it is not. Maybe it would be a great to use OSGi for uima too. The next tae release will include everything that is necessary to run it out of the box. Jörn
Re: Eclise Annotation Editor
Jörn Kottmann wrote: snip For the uima case there is a work-around (Eclipse-BuddyPolicy: dependent) inside eclipse, but this must be enabled in the uima eclipse plugin descriptor. Currently it is not. Version 2 releases of UIMA include in the UIMA Eclipse Runtime plugin manifest this line: Eclipse-BuddyPolicy: registered (Note: this is not part of UIMA Version 1) Can you explain more about using dependent? -Marshall
Re: Eclise Annotation Editor
Version 2 releases of UIMA include in the UIMA Eclipse Runtime plugin manifest this line: Eclipse-BuddyPolicy: registered (Note: this is not part of UIMA Version 1) Can you explain more about using dependent? OK, I did not noticed that it changed in version 2. If you use dependent it searches for a class in plugins which depend on the uima plugin.
Re: Eclise Annotation Editor
Hi Joern, is this your Text Analysis Environment on SourceForge (https://sourceforge.net/projects/tae/)? Looks pretty cool! This would be a nice addition to our Eclipse-based tooling. --Thilo Jörn Kottmann wrote: Hello, I have developed an eclipse editor to edit xcas files, it can add, remove and change Annotations and FeatureStructures. This is done within the editor and some views. The plugin also defines its own project and has an special explorer for it like the package explorer in JDT. Its also supports the execution of Annotators and CASConsumers against the xcas files stored inside the project. If you are interested to add this or parts of it to the UIMA project I would like to sponsor the code and time to integrate it. Let me know what you think, Jörn
Re: Eclise Annotation Editor
yes, there are some still compatibility issues with UIMA. The current release has many smaller issues, many of them are already fixed. I will make the next release soon. On Dec 14, 2006, at 10:27 AM, Thilo Goetz wrote: Hi Joern, is this your Text Analysis Environment on SourceForge (https:// sourceforge.net/projects/tae/)? Looks pretty cool! This would be a nice addition to our Eclipse-based tooling. --Thilo Jörn Kottmann wrote: Hello, I have developed an eclipse editor to edit xcas files, it can add, remove and change Annotations and FeatureStructures. This is done within the editor and some views. The plugin also defines its own project and has an special explorer for it like the package explorer in JDT. Its also supports the execution of Annotators and CASConsumers against the xcas files stored inside the project. If you are interested to add this or parts of it to the UIMA project I would like to sponsor the code and time to integrate it. Let me know what you think, Jörn
Re: Eclise Annotation Editor
On 12/14/06, Thilo Goetz [EMAIL PROTECTED] wrote: Hi Joern, is this your Text Analysis Environment on SourceForge (https://sourceforge.net/projects/tae/)? Looks pretty cool! This would be a nice addition to our Eclipse-based tooling. --Thilo I got this from SourceForge but was unable to run it. The net.sf.tae plugins show up with red X's in the plugin registry, even though I've installed GEF and UIMA 1.3.2. There's nothing in the error log. What might I be doing wrong? Anway, it sounds like this would be a useful addition. Thanks, Joern, for offering to contribute it. What do the other commiters think -- would this make a good first project for our UIMA sandbox? -Adam
Re: Eclise Annotation Editor
Adam Lally wrote: What do the other commiters think -- would this make a good first project for our UIMA sandbox? Yes I think this is good first component for the UIMA sandbox. But first we have to clarify the details for the submission... I seems that we need an Apache Software Grant for this code. If found the following at: www.apache.org/licenses Software Grants When an individual or corporation decides to donate a body of existing software or documentation to one of the Apache projects, they need to execute a formal Software Grant http://www.apache.org/licenses/software-grant.txt agreement with the ASF. Typically, this is done after negotiating approval with the ASF Incubator http://incubator.apache.org/ or one of the PMCs, since the ASF will not accept software unless there is a viable community available to support a collaborative project. -- Michael
