Hi,

a snapshot update site is here:

http://people.apache.org/~pkluegl/temp/2.0.1-SNAPSHOT/eclipse-update-site/
<http://people.apache.org/%7Epkluegl/temp/2.0.1-SNAPSHOT/eclipse-update-site/>

The parent folder contains also ruta-core-2.0.1-SNAPSHOT.jar and the
documentation since the jenkins build just failed.

Best,

Peter

On 06.05.2013 07:53, armin.weg...@bka.bund.de wrote:
> Hi Peter,
>
> That is fine. I'm using 2.0.0 core jar from maven central. Can you give me a 
> snapshot update site, please?
>
> Thank you,
> Armin
>
> -----Ursprüngliche Nachricht-----
> Von: Peter Klügl [mailto:pklu...@uni-wuerzburg.de] 
> Gesendet: Freitag, 3. Mai 2013 15:04
> An: user@uima.apache.org
> Betreff: Re: Textmarker - Qualification of Types
>
> Hi,
>
> it's fixed now in the trunk.
>
> Which version do you use? Just let me know if you need a snapshot update site 
> or help with the new projects.
>
> Best,
>
> Peter
>
>
> On 03.05.2013 14:28, Peter Klügl wrote:
>> Hi,
>>
>> On 03.05.2013 13:52, armin.weg...@bka.bund.de wrote:
>>> Hi,
>>>
>>> I'm running Textmarker on a CAS XMI file with a lot of annotations from 
>>> different annotators and different type systems. There are some type names 
>>> used more than once, but with different name spaces. All types are defined 
>>> in the type system included with TYPESYSTEM. Prepending the namespace to a 
>>> type name in a Textmarker script does not work. How to tell Textmarker 
>>> which namespace to use?
>> I just checked it and found a bug. I will fix it ASAP and commit it to 
>> the trunk. Please mind that the name textmarker was replaced by ruta 
>> in the trunk.
>>
>> Normally, you should be able to use the complete namespace for 
>> referencing a type and a shortcut with type variables since adding the 
>> complete namespace is tedious and confusing.
>>
>> // some imports...
>>
>> TYPE NUM_DKPro =
>> de.tudarmstadt.ukp.dkpro.core.api.syntax.type.dependency.NUM;
>> TYPE NUM_Ruta = org.apache.uima.ruta.type.NUM;
>>
>> NUM_Ruta PERIOD NUM_Ruta{-> MARK(...)};
>>
>> Thanks for reporting this.
>>
>> Best,
>>
>> Peter
>>
>>
>>> Thanks,
>>> Armin

Reply via email to