You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Richard Eckart de Castilho <ec...@tk.informatik.tu-darmstadt.de> on 2011/08/03 21:59:07 UTC
Re: [jira] [Commented] (UIMA-2141) Annotations Styles view - filter field
Hi folks,
>> Thanks Jörn, I'll have a try.
>
> Let us know about any problems, so I can help you.
finally, I found a few minutes to have another stab at UIMA. I have reverted all changes that I may have had and updated to the latest version from SVN. Everything seems to compile fine, but I still have 33 plug-in errors in the following projects:
uimaj-ep-cas-editor
uimaj-ep-configurator
uimaj-ep-jcasgen
uimaj-ep-pear-packager
All are of the type "No available bundle exports package 'org.apache.uima...'" - the packages seems always to be from uimaj-core.
Do I get these errors occur because the uimaj-core project has no OSGi metadata?
I do have the uimaj-ep-runtime 2.3.2.SNAPSHOT plugin installed in my Eclipse. Shouldn't Eclipse be able to locate the packages exported by that?
Cheers,
Richard
Btw.: I find it interesting that m2eclipse now seems to support Eclipse plugin projects. When I last tried to mix Maven with RCP quite some time ago and had both the Plug-in Dependencies Libaray and the Maven Dependencies Library in the classpath, Eclipse kept on complaining about duplicate classes. This seems to work fine now.
--
-------------------------------------------------------------------
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab
FB 20 Computer Science Department
Technische Universität Darmstadt
Hochschulstr. 10, D-64289 Darmstadt, Germany
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckartde@tk.informatik.tu-darmstadt.de
www.ukp.tu-darmstadt.de
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------
Re: Solved: Eclipse is unable to resolve UIMA Eclipse tooling bundles
Posted by Richard Eckart de Castilho <ec...@tk.informatik.tu-darmstadt.de>.
Am 09.08.2011 um 21:27 schrieb Marshall Schor:
> Ah, yes... now makes sense...
>
> But of course, you can do both :-) Just configure the launching the test
> version of Eclipse to use the plugin(s) you're developing, and otherwise use the
> installed ones.
I could do that. But I intentionally would like to keep the IDE instance clear of the plugins that I am working on. I can already imagine myself spending hours trying to figure out why changes don't work out and finally finding that I was testing the plugin installed in the IDE and not the one from the workspace.
Well, before I would start any serious development efforts with PDE, I'd probably set up a platform definition file and clean set of Eclipse bundles anyway. I never liked inheriting bundles from the IDE very much. Since UIMA doesn't ship with a platform definition file, however, making a note of installing the EMF stuff should help potential contributors in getting started. Unless of course, you'd like to ship a platform definition ;)
Cheers,
Richard
--
-------------------------------------------------------------------
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab
FB 20 Computer Science Department
Technische Universität Darmstadt
Hochschulstr. 10, D-64289 Darmstadt, Germany
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckartde@tk.informatik.tu-darmstadt.de
www.ukp.tu-darmstadt.de
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------
Re: Solved: Eclipse is unable to resolve UIMA Eclipse tooling bundles
Posted by Marshall Schor <ms...@schor.com>.
Ah, yes... now makes sense...
But of course, you can do both :-) Just configure the launching the test
version of Eclipse to use the plugin(s) you're developing, and otherwise use the
installed ones.
-Marshall
On 8/9/2011 1:56 PM, Richard Eckart de Castilho wrote:
> Hello Marshal,
>
>> The issue with EMF - can you confirm it works for you in a brand-new-unzipped
>> Eclipse 3.6 or 3.7 where you install just the UIMA plugins from the update site,
>> but leave (or have) the box checked on the install page which says: "Contact all
>> update sites during install to find required software", *without* you having to
>> manually install EMF?
> When I install the UIMA plugins into Eclipse and I contact all update sites it should work fine. I never experienced problems with this.
>
> My point is, that if I do not want to *use* UIMA, but to *develop* UIMA itself, then I do *not* want to have to install the Eclipse UIMA plugins into my development instance. I only want to run them in my testing instance. And since I do not install the plugins in my development instance, the EMF plugin is not available to the testing instance.
>
> Cheers,
>
> Richard
>
Re: Solved: Eclipse is unable to resolve UIMA Eclipse tooling bundles
Posted by Richard Eckart de Castilho <ec...@tk.informatik.tu-darmstadt.de>.
Hello Marshal,
> The issue with EMF - can you confirm it works for you in a brand-new-unzipped
> Eclipse 3.6 or 3.7 where you install just the UIMA plugins from the update site,
> but leave (or have) the box checked on the install page which says: "Contact all
> update sites during install to find required software", *without* you having to
> manually install EMF?
When I install the UIMA plugins into Eclipse and I contact all update sites it should work fine. I never experienced problems with this.
My point is, that if I do not want to *use* UIMA, but to *develop* UIMA itself, then I do *not* want to have to install the Eclipse UIMA plugins into my development instance. I only want to run them in my testing instance. And since I do not install the plugins in my development instance, the EMF plugin is not available to the testing instance.
Cheers,
Richard
--
-------------------------------------------------------------------
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab
FB 20 Computer Science Department
Technische Universität Darmstadt
Hochschulstr. 10, D-64289 Darmstadt, Germany
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckartde@tk.informatik.tu-darmstadt.de
www.ukp.tu-darmstadt.de
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------
Re: Solved: Eclipse is unable to resolve UIMA Eclipse tooling bundles
Posted by Marshall Schor <ms...@schor.com>.
Hi Richard,
Thanks for digging down to root causes :-)
The issue with EMF - can you confirm it works for you in a brand-new-unzipped
Eclipse 3.6 or 3.7 where you install just the UIMA plugins from the update site,
but leave (or have) the box checked on the install page which says: "Contact all
update sites during install to find required software", *without* you having to
manually install EMF?
(I think it goes and installs EMF automatically in this case).
If you can confirm that, we can add that info to the 1 time setup info for
Eclipse: something like: "Either check the Contact all ... or manually install EMF.
-Marshall
On 8/8/2011 6:16 PM, Richard Eckart de Castilho wrote:
> Am 07.08.2011 um 17:00 schrieb Richard Eckart de Castilho:
>
>> Its still now there. OSGi says that the bundle is installed, but it is not resolved:
>>
>> org.apache.uima.desceditor (2.3.2.SNAPSHOT) "UIMA Eclipse: uimaj-ep-configurator: Descriptor Editor" [Installed]
>>
>> When I try to start it from the OSGi host console, I get:
>>
>> The bundle "org.apache.uima.desceditor_2.3.2.SNAPSHOT [258]" could not be resolved. Reason: Missing Constraint: Import-Package: org.apache.uima.jcas.jcasgenp; version="2.3.0"
>>
>> Looking at the MANIFEST.MF of uimaj-ep-configurator I find several odd things:
>>
>> - there are imports for a version 2.3 while it should be 2.3.2-SNAPSHOT (the exports are correct btw.!)
>> - even packages from uimaj-ep-configurator are imported in version 2.3
>>
>> That is the end of my story so far, because I currently can't figure out at the moment, why the MANIFEST.MF files are broken.
>>
>> BLOCKER: As a last measure, I tried running a "mvn clean install" after removing my ~/.m2/repository on a completely fresh checkout of UIMA. But this also generates the broken package imports in the MANIFEST.MF. A JAR I had downloaded from Jenkins with the build timestamp 20110606-1443 still contains the correct import statements.
> Solution: installed the feature "EMF - Eclipse Modelling Framework SDK"
>
>
> It looks like the MANIFEST.MF files are generated "as desired" after all. I found some documentation on Import-Package and versioning here
>
> http://fusesource.com/docs/esb/4.4/esb_deploy_osgi/BestPractices-BuildBundles.html
>
> A short resume:
>
> - per default the Import-Package uses a truncated version, e.g. 2.3.2.SNAPSHOT becomes 2.3
> - an Import-Package with a version=1.2 is equivalent to a version range [2.3, infinity)
>
> So far so good.
>
> Digging further, I found that one of the packages that Eclipse could not resolve was an EMF package. I installed the feature "EMF - Eclipse Modelling Framework SDK" version "2.6.1.v20100914-1218" and after that all plugins were able to resolve.
>
> I think it would be a good idea to mention the need to install the "EMF - Eclipse Modelling Framework SDK" in the Eclipse section of the "One time setup" page.
>
> Looks like I am finally set up and learned a lot in the process.
>
> Thanks for your support so far!
>
> -- Richard
>
Solved: Eclipse is unable to resolve UIMA Eclipse tooling bundles
Posted by Richard Eckart de Castilho <ec...@tk.informatik.tu-darmstadt.de>.
Am 07.08.2011 um 17:00 schrieb Richard Eckart de Castilho:
> Its still now there. OSGi says that the bundle is installed, but it is not resolved:
>
> org.apache.uima.desceditor (2.3.2.SNAPSHOT) "UIMA Eclipse: uimaj-ep-configurator: Descriptor Editor" [Installed]
>
> When I try to start it from the OSGi host console, I get:
>
> The bundle "org.apache.uima.desceditor_2.3.2.SNAPSHOT [258]" could not be resolved. Reason: Missing Constraint: Import-Package: org.apache.uima.jcas.jcasgenp; version="2.3.0"
>
> Looking at the MANIFEST.MF of uimaj-ep-configurator I find several odd things:
>
> - there are imports for a version 2.3 while it should be 2.3.2-SNAPSHOT (the exports are correct btw.!)
> - even packages from uimaj-ep-configurator are imported in version 2.3
>
> That is the end of my story so far, because I currently can't figure out at the moment, why the MANIFEST.MF files are broken.
>
> BLOCKER: As a last measure, I tried running a "mvn clean install" after removing my ~/.m2/repository on a completely fresh checkout of UIMA. But this also generates the broken package imports in the MANIFEST.MF. A JAR I had downloaded from Jenkins with the build timestamp 20110606-1443 still contains the correct import statements.
Solution: installed the feature "EMF - Eclipse Modelling Framework SDK"
It looks like the MANIFEST.MF files are generated "as desired" after all. I found some documentation on Import-Package and versioning here
http://fusesource.com/docs/esb/4.4/esb_deploy_osgi/BestPractices-BuildBundles.html
A short resume:
- per default the Import-Package uses a truncated version, e.g. 2.3.2.SNAPSHOT becomes 2.3
- an Import-Package with a version=1.2 is equivalent to a version range [2.3, infinity)
So far so good.
Digging further, I found that one of the packages that Eclipse could not resolve was an EMF package. I installed the feature "EMF - Eclipse Modelling Framework SDK" version "2.6.1.v20100914-1218" and after that all plugins were able to resolve.
I think it would be a good idea to mention the need to install the "EMF - Eclipse Modelling Framework SDK" in the Eclipse section of the "One time setup" page.
Looks like I am finally set up and learned a lot in the process.
Thanks for your support so far!
-- Richard
--
-------------------------------------------------------------------
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab
FB 20 Computer Science Department
Technische Universität Darmstadt
Hochschulstr. 10, D-64289 Darmstadt, Germany
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckartde@tk.informatik.tu-darmstadt.de
www.ukp.tu-darmstadt.de
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------
Re: Getting the checkout of the core to work: Finding Eclipse dependencies
Posted by Marshall Schor <ms...@schor.com>.
we tried that once, and didn't get it to work. Perhaps things have changed; but
I find these kinds of investigations are a big time sink with little reward :-(
-Marshall
On 8/7/2011 1:36 PM, Richard Eckart de Castilho wrote:
> Do you think it would be worth investigating if the Eclipse dependencies could be covered from http://repo1.maven.org/maven2 ?
>
> -- Richard
>
> Am 07.08.2011 um 19:33 schrieb Marshall Schor:
>
>> looks like your repo1.maven.org is being redirected to uk.maven.org.
>>
>> I'll post a query on maven-dev about this.
>>
>> -Marshall
>>
>> On 8/7/2011 1:22 PM, Richard Eckart de Castilho wrote:
>>> There is definitely an issue here.
>>>
>>> HighFire:~ bluefire$ ping repo1.maven.org
>>> PING gslb.maven.org (89.167.251.252): 56 data bytes
>>>
>>> When I use the IP, it works.
>>>
>>> http://207.223.241.90/eclipse/org/eclipse/core/org.eclipse.core.variables/3.1.100/
>>>
>>> -- Richard
>>>
>>> Am 07.08.2011 um 19:19 schrieb Marshall Schor:
>>>
>>>> puzzled...
>>>>
>>>> I wonder if somehow the website is different in Europe vs US...
>>>>
>>>> Here's what I get if I ping this:
>>>>
>>>> ping repo1.maven.org
>>>>
>>>> Pinging gslb.maven.org [207.223.241.90]
>>>>
>>>>
>>>>
>>>> Just tried this again, worked again for me. View Source on that page shows:
>>>>
>>>> <html>
>>>> <head><title>Index of
>>>> /eclipse/org/eclipse/core/org.eclipse.core.variables/3.1.100/</title></head>
>>>> <body bgcolor="white">
>>>> <h1>Index of
>>>> /eclipse/org/eclipse/core/org.eclipse.core.variables/3.1.100/</h1><hr><pre><a
>>>> href="../">../</a>
>>>> <a
>>>> href="org.eclipse.core.variables-3.1.100.jar">org.eclipse.core.variables-3.1.100.jar</a>
>>>> 26-Oct-2006 08:05 25344
>>>> <a
>>>> href="org.eclipse.core.variables-3.1.100.jar.md5">org.eclipse.core.variables-3.1.100.jar.md5</a>
>>>> 26-Oct-2006 12:23 127
>>>> <a
>>>> href="org.eclipse.core.variables-3.1.100.jar.sha1">org.eclipse.core.variables-3.1.100.jar.sha1</a>
>>>> 26-Oct-2006 12:23 135
>>>> <a
>>>> href="org.eclipse.core.variables-3.1.100.pom">org.eclipse.core.variables-3.1.100.pom</a>
>>>> 26-Oct-2006 08:05 658
>>>> <a
>>>> href="org.eclipse.core.variables-3.1.100.pom.md5">org.eclipse.core.variables-3.1.100.pom.md5</a>
>>>> 26-Oct-2006 12:23 127
>>>> <a
>>>> href="org.eclipse.core.variables-3.1.100.pom.sha1">org.eclipse.core.variables-3.1.100.pom.sha1</a>
>>>> 26-Oct-2006 12:23 135
>>>> </pre><hr></body>
>>>> </html>
>>>>
>>>> Do you have the same ping result?
>>>>
>>>> I think some "research" on the maven mailing lists might be needed to figure
>>>> this out.
>>>>
>>>> -Marshall
>>>>
>>>> On 8/7/2011 1:02 PM, Richard Eckart de Castilho wrote:
>>>>> Am 07.08.2011 um 18:42 schrieb Marshall Schor:
>>>>>
>>>>>> I see it exactly where it should be in the http://repo1.maven.org/eclipse; you
>>>>>> should see it here:
>>>>>>
>>>>>> http://repo1.maven.org/eclipse/org/eclipse/core/org.eclipse.core.variables/3.1.100/
>>>>> I know this trick and it works with http://repo1.maven.org/maven2. But if I click on that link you provided, I get a 404 Not Found page:
>>>>>
>>>>> <html>
>>>>> <head><title>404 Not Found</title></head>
>>>>> <body bgcolor="white">
>>>>> <center><h1>404 Not Found</h1></center>
>>>>> <hr><center>nginx/1.0.1</center>
>>>>> </body>
>>>>> </html>
>>>>>
>>>>> -- Richard
>>>>>
>>> Richard Eckart de Castilho
>>>
> Richard Eckart de Castilho
>
Re: Getting the checkout of the core to work: Finding Eclipse dependencies
Posted by Richard Eckart de Castilho <ec...@tk.informatik.tu-darmstadt.de>.
Do you think it would be worth investigating if the Eclipse dependencies could be covered from http://repo1.maven.org/maven2 ?
-- Richard
Am 07.08.2011 um 19:33 schrieb Marshall Schor:
> looks like your repo1.maven.org is being redirected to uk.maven.org.
>
> I'll post a query on maven-dev about this.
>
> -Marshall
>
> On 8/7/2011 1:22 PM, Richard Eckart de Castilho wrote:
>> There is definitely an issue here.
>>
>> HighFire:~ bluefire$ ping repo1.maven.org
>> PING gslb.maven.org (89.167.251.252): 56 data bytes
>>
>> When I use the IP, it works.
>>
>> http://207.223.241.90/eclipse/org/eclipse/core/org.eclipse.core.variables/3.1.100/
>>
>> -- Richard
>>
>> Am 07.08.2011 um 19:19 schrieb Marshall Schor:
>>
>>> puzzled...
>>>
>>> I wonder if somehow the website is different in Europe vs US...
>>>
>>> Here's what I get if I ping this:
>>>
>>> ping repo1.maven.org
>>>
>>> Pinging gslb.maven.org [207.223.241.90]
>>>
>>>
>>>
>>> Just tried this again, worked again for me. View Source on that page shows:
>>>
>>> <html>
>>> <head><title>Index of
>>> /eclipse/org/eclipse/core/org.eclipse.core.variables/3.1.100/</title></head>
>>> <body bgcolor="white">
>>> <h1>Index of
>>> /eclipse/org/eclipse/core/org.eclipse.core.variables/3.1.100/</h1><hr><pre><a
>>> href="../">../</a>
>>> <a
>>> href="org.eclipse.core.variables-3.1.100.jar">org.eclipse.core.variables-3.1.100.jar</a>
>>> 26-Oct-2006 08:05 25344
>>> <a
>>> href="org.eclipse.core.variables-3.1.100.jar.md5">org.eclipse.core.variables-3.1.100.jar.md5</a>
>>> 26-Oct-2006 12:23 127
>>> <a
>>> href="org.eclipse.core.variables-3.1.100.jar.sha1">org.eclipse.core.variables-3.1.100.jar.sha1</a>
>>> 26-Oct-2006 12:23 135
>>> <a
>>> href="org.eclipse.core.variables-3.1.100.pom">org.eclipse.core.variables-3.1.100.pom</a>
>>> 26-Oct-2006 08:05 658
>>> <a
>>> href="org.eclipse.core.variables-3.1.100.pom.md5">org.eclipse.core.variables-3.1.100.pom.md5</a>
>>> 26-Oct-2006 12:23 127
>>> <a
>>> href="org.eclipse.core.variables-3.1.100.pom.sha1">org.eclipse.core.variables-3.1.100.pom.sha1</a>
>>> 26-Oct-2006 12:23 135
>>> </pre><hr></body>
>>> </html>
>>>
>>> Do you have the same ping result?
>>>
>>> I think some "research" on the maven mailing lists might be needed to figure
>>> this out.
>>>
>>> -Marshall
>>>
>>> On 8/7/2011 1:02 PM, Richard Eckart de Castilho wrote:
>>>> Am 07.08.2011 um 18:42 schrieb Marshall Schor:
>>>>
>>>>> I see it exactly where it should be in the http://repo1.maven.org/eclipse; you
>>>>> should see it here:
>>>>>
>>>>> http://repo1.maven.org/eclipse/org/eclipse/core/org.eclipse.core.variables/3.1.100/
>>>> I know this trick and it works with http://repo1.maven.org/maven2. But if I click on that link you provided, I get a 404 Not Found page:
>>>>
>>>> <html>
>>>> <head><title>404 Not Found</title></head>
>>>> <body bgcolor="white">
>>>> <center><h1>404 Not Found</h1></center>
>>>> <hr><center>nginx/1.0.1</center>
>>>> </body>
>>>> </html>
>>>>
>>>> -- Richard
>>>>
>> Richard Eckart de Castilho
>>
Richard Eckart de Castilho
--
-------------------------------------------------------------------
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab
FB 20 Computer Science Department
Technische Universität Darmstadt
Hochschulstr. 10, D-64289 Darmstadt, Germany
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckartde@tk.informatik.tu-darmstadt.de
www.ukp.tu-darmstadt.de
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------
Re: Getting the checkout of the core to work: Finding Eclipse dependencies
Posted by Marshall Schor <ms...@schor.com>.
looks like your repo1.maven.org is being redirected to uk.maven.org.
I'll post a query on maven-dev about this.
-Marshall
On 8/7/2011 1:22 PM, Richard Eckart de Castilho wrote:
> There is definitely an issue here.
>
> HighFire:~ bluefire$ ping repo1.maven.org
> PING gslb.maven.org (89.167.251.252): 56 data bytes
>
> When I use the IP, it works.
>
> http://207.223.241.90/eclipse/org/eclipse/core/org.eclipse.core.variables/3.1.100/
>
> -- Richard
>
> Am 07.08.2011 um 19:19 schrieb Marshall Schor:
>
>> puzzled...
>>
>> I wonder if somehow the website is different in Europe vs US...
>>
>> Here's what I get if I ping this:
>>
>> ping repo1.maven.org
>>
>> Pinging gslb.maven.org [207.223.241.90]
>>
>>
>>
>> Just tried this again, worked again for me. View Source on that page shows:
>>
>> <html>
>> <head><title>Index of
>> /eclipse/org/eclipse/core/org.eclipse.core.variables/3.1.100/</title></head>
>> <body bgcolor="white">
>> <h1>Index of
>> /eclipse/org/eclipse/core/org.eclipse.core.variables/3.1.100/</h1><hr><pre><a
>> href="../">../</a>
>> <a
>> href="org.eclipse.core.variables-3.1.100.jar">org.eclipse.core.variables-3.1.100.jar</a>
>> 26-Oct-2006 08:05 25344
>> <a
>> href="org.eclipse.core.variables-3.1.100.jar.md5">org.eclipse.core.variables-3.1.100.jar.md5</a>
>> 26-Oct-2006 12:23 127
>> <a
>> href="org.eclipse.core.variables-3.1.100.jar.sha1">org.eclipse.core.variables-3.1.100.jar.sha1</a>
>> 26-Oct-2006 12:23 135
>> <a
>> href="org.eclipse.core.variables-3.1.100.pom">org.eclipse.core.variables-3.1.100.pom</a>
>> 26-Oct-2006 08:05 658
>> <a
>> href="org.eclipse.core.variables-3.1.100.pom.md5">org.eclipse.core.variables-3.1.100.pom.md5</a>
>> 26-Oct-2006 12:23 127
>> <a
>> href="org.eclipse.core.variables-3.1.100.pom.sha1">org.eclipse.core.variables-3.1.100.pom.sha1</a>
>> 26-Oct-2006 12:23 135
>> </pre><hr></body>
>> </html>
>>
>> Do you have the same ping result?
>>
>> I think some "research" on the maven mailing lists might be needed to figure
>> this out.
>>
>> -Marshall
>>
>> On 8/7/2011 1:02 PM, Richard Eckart de Castilho wrote:
>>> Am 07.08.2011 um 18:42 schrieb Marshall Schor:
>>>
>>>> I see it exactly where it should be in the http://repo1.maven.org/eclipse; you
>>>> should see it here:
>>>>
>>>> http://repo1.maven.org/eclipse/org/eclipse/core/org.eclipse.core.variables/3.1.100/
>>> I know this trick and it works with http://repo1.maven.org/maven2. But if I click on that link you provided, I get a 404 Not Found page:
>>>
>>> <html>
>>> <head><title>404 Not Found</title></head>
>>> <body bgcolor="white">
>>> <center><h1>404 Not Found</h1></center>
>>> <hr><center>nginx/1.0.1</center>
>>> </body>
>>> </html>
>>>
>>> -- Richard
>>>
> Richard Eckart de Castilho
>
Re: Getting the checkout of the core to work: Finding Eclipse dependencies
Posted by Richard Eckart de Castilho <ec...@tk.informatik.tu-darmstadt.de>.
There is definitely an issue here.
HighFire:~ bluefire$ ping repo1.maven.org
PING gslb.maven.org (89.167.251.252): 56 data bytes
When I use the IP, it works.
http://207.223.241.90/eclipse/org/eclipse/core/org.eclipse.core.variables/3.1.100/
-- Richard
Am 07.08.2011 um 19:19 schrieb Marshall Schor:
> puzzled...
>
> I wonder if somehow the website is different in Europe vs US...
>
> Here's what I get if I ping this:
>
> ping repo1.maven.org
>
> Pinging gslb.maven.org [207.223.241.90]
>
>
>
> Just tried this again, worked again for me. View Source on that page shows:
>
> <html>
> <head><title>Index of
> /eclipse/org/eclipse/core/org.eclipse.core.variables/3.1.100/</title></head>
> <body bgcolor="white">
> <h1>Index of
> /eclipse/org/eclipse/core/org.eclipse.core.variables/3.1.100/</h1><hr><pre><a
> href="../">../</a>
> <a
> href="org.eclipse.core.variables-3.1.100.jar">org.eclipse.core.variables-3.1.100.jar</a>
> 26-Oct-2006 08:05 25344
> <a
> href="org.eclipse.core.variables-3.1.100.jar.md5">org.eclipse.core.variables-3.1.100.jar.md5</a>
> 26-Oct-2006 12:23 127
> <a
> href="org.eclipse.core.variables-3.1.100.jar.sha1">org.eclipse.core.variables-3.1.100.jar.sha1</a>
> 26-Oct-2006 12:23 135
> <a
> href="org.eclipse.core.variables-3.1.100.pom">org.eclipse.core.variables-3.1.100.pom</a>
> 26-Oct-2006 08:05 658
> <a
> href="org.eclipse.core.variables-3.1.100.pom.md5">org.eclipse.core.variables-3.1.100.pom.md5</a>
> 26-Oct-2006 12:23 127
> <a
> href="org.eclipse.core.variables-3.1.100.pom.sha1">org.eclipse.core.variables-3.1.100.pom.sha1</a>
> 26-Oct-2006 12:23 135
> </pre><hr></body>
> </html>
>
> Do you have the same ping result?
>
> I think some "research" on the maven mailing lists might be needed to figure
> this out.
>
> -Marshall
>
> On 8/7/2011 1:02 PM, Richard Eckart de Castilho wrote:
>> Am 07.08.2011 um 18:42 schrieb Marshall Schor:
>>
>>> I see it exactly where it should be in the http://repo1.maven.org/eclipse; you
>>> should see it here:
>>>
>>> http://repo1.maven.org/eclipse/org/eclipse/core/org.eclipse.core.variables/3.1.100/
>> I know this trick and it works with http://repo1.maven.org/maven2. But if I click on that link you provided, I get a 404 Not Found page:
>>
>> <html>
>> <head><title>404 Not Found</title></head>
>> <body bgcolor="white">
>> <center><h1>404 Not Found</h1></center>
>> <hr><center>nginx/1.0.1</center>
>> </body>
>> </html>
>>
>> -- Richard
>>
Richard Eckart de Castilho
--
-------------------------------------------------------------------
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab
FB 20 Computer Science Department
Technische Universität Darmstadt
Hochschulstr. 10, D-64289 Darmstadt, Germany
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckartde@tk.informatik.tu-darmstadt.de
www.ukp.tu-darmstadt.de
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------
Re: Getting the checkout of the core to work: Finding Eclipse dependencies
Posted by Marshall Schor <ms...@schor.com>.
puzzled...
I wonder if somehow the website is different in Europe vs US...
Here's what I get if I ping this:
ping repo1.maven.org
Pinging gslb.maven.org [207.223.241.90]
Just tried this again, worked again for me. View Source on that page shows:
<html>
<head><title>Index of
/eclipse/org/eclipse/core/org.eclipse.core.variables/3.1.100/</title></head>
<body bgcolor="white">
<h1>Index of
/eclipse/org/eclipse/core/org.eclipse.core.variables/3.1.100/</h1><hr><pre><a
href="../">../</a>
<a
href="org.eclipse.core.variables-3.1.100.jar">org.eclipse.core.variables-3.1.100.jar</a>
26-Oct-2006 08:05 25344
<a
href="org.eclipse.core.variables-3.1.100.jar.md5">org.eclipse.core.variables-3.1.100.jar.md5</a>
26-Oct-2006 12:23 127
<a
href="org.eclipse.core.variables-3.1.100.jar.sha1">org.eclipse.core.variables-3.1.100.jar.sha1</a>
26-Oct-2006 12:23 135
<a
href="org.eclipse.core.variables-3.1.100.pom">org.eclipse.core.variables-3.1.100.pom</a>
26-Oct-2006 08:05 658
<a
href="org.eclipse.core.variables-3.1.100.pom.md5">org.eclipse.core.variables-3.1.100.pom.md5</a>
26-Oct-2006 12:23 127
<a
href="org.eclipse.core.variables-3.1.100.pom.sha1">org.eclipse.core.variables-3.1.100.pom.sha1</a>
26-Oct-2006 12:23 135
</pre><hr></body>
</html>
Do you have the same ping result?
I think some "research" on the maven mailing lists might be needed to figure
this out.
-Marshall
On 8/7/2011 1:02 PM, Richard Eckart de Castilho wrote:
> Am 07.08.2011 um 18:42 schrieb Marshall Schor:
>
>> I see it exactly where it should be in the http://repo1.maven.org/eclipse; you
>> should see it here:
>>
>> http://repo1.maven.org/eclipse/org/eclipse/core/org.eclipse.core.variables/3.1.100/
> I know this trick and it works with http://repo1.maven.org/maven2. But if I click on that link you provided, I get a 404 Not Found page:
>
> <html>
> <head><title>404 Not Found</title></head>
> <body bgcolor="white">
> <center><h1>404 Not Found</h1></center>
> <hr><center>nginx/1.0.1</center>
> </body>
> </html>
>
> -- Richard
>
Re: Getting the checkout of the core to work: Finding Eclipse dependencies
Posted by Richard Eckart de Castilho <ec...@tk.informatik.tu-darmstadt.de>.
Am 07.08.2011 um 18:42 schrieb Marshall Schor:
> I see it exactly where it should be in the http://repo1.maven.org/eclipse; you
> should see it here:
>
> http://repo1.maven.org/eclipse/org/eclipse/core/org.eclipse.core.variables/3.1.100/
I know this trick and it works with http://repo1.maven.org/maven2. But if I click on that link you provided, I get a 404 Not Found page:
<html>
<head><title>404 Not Found</title></head>
<body bgcolor="white">
<center><h1>404 Not Found</h1></center>
<hr><center>nginx/1.0.1</center>
</body>
</html>
-- Richard
--
-------------------------------------------------------------------
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab
FB 20 Computer Science Department
Technische Universität Darmstadt
Hochschulstr. 10, D-64289 Darmstadt, Germany
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckartde@tk.informatik.tu-darmstadt.de
www.ukp.tu-darmstadt.de
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------
Getting the checkout of the core to work: Finding Eclipse dependencies
Posted by Marshall Schor <ms...@schor.com>.
Re: Blocker: http://repo1.maven.org/eclipse not existing.
What seems to be true is that if you go here, you get a message saying that
browsing has been replaced by searching.
However, if you do the normal translation of maven <groupId> to directory
levels, in other words, if you look at one of the dependencies, for instance,
one you said wasn't found:
For example uimaj-ep-configurator depends on "org.eclipse.core:org.eclipse.core.variables:jar" in version "3.1.100"
I see it exactly where it should be in the http://repo1.maven.org/eclipse; you
should see it here:
http://repo1.maven.org/eclipse/org/eclipse/core/org.eclipse.core.variables/3.1.100/
If the build is not getting this (which I'm guessing is the case, because you
say "lots of errors because artifacts cannot be found" , then perhaps there is
some other issue?
-Marshall
On 8/7/2011 11:00 AM, Richard Eckart de Castilho wrote:
> Thanks for your exhaustive answer. Marshal. To avoid unnecessary discussions I won't reply directly to most of the questions. Instead, I'll try to focus on repeating and documenting the steps suggested by Marshal and try to use clearer language to avoid misunderstandings. I have divided this mail into three sections:
>
> I) Checking out UIMA - reproducing the steps Marshal explained in his last mail
> II) Running the CAS Editor - (trying to) run CAS Editor to run
> III) Resume
>
> === I) Checking out UIMA ===
>
> I've repeated your steps:
>
> 1) Just to make everything as clean as possible, I moved my settings.xml and ~/.m2/repository out of the way.
>
>> * Marshal: get a brand new install of Eclipse 3.6.2. I put into it the subclipse plugin and the m2eclipse plugin.
> 2) I fetched the Eclipse 3.6.2 Classic OS X 64bit Cocoa distribution from http://www.eclipse.org/downloads/packages/eclipse-classic-362/heliossr2
> 3) I installed subclipse from http://subclipse.tigris.org/update_1.6.x
> 4) I installed m2eclipse from http://m2eclipse.sonatype.org/sites/m2e
> - Maven Integration for Eclipse (Required) 0.12.20110112-1712
>
> Note: Eclipse 3.6.2 Classic is the one that includes all the PDE stuff, but does not come with Subversive.
>
>> * Marshal: use a svn command-line client (not Eclipse) to check out ...uima/uimaj/trunk.
> 5) I started a fresh workspace
> 6) I checked the stuff out on the command line using
>
> svn checkout http://svn.apache.org/repos/asf/uima/uimaj/trunk uimaj-root
>
>> * Marshal: use Eclipse -> Import -> Maven -> Existing Maven Projects, and select the checkout directory.
> 7) I started Eclipse and waited until the "Updating indexes" had completed.
> 8) I imported the "uimaj-root" folder into which I had done the checking out.
>
>> * Marshal: after a while, it was all in, except that uimaj-core had an "error".
> Now after a while Eclipse is done and there are lots of errors because artifacts cannot be found.
>
> BLOCKER: A blocker for a new user at the moment seems to be that the repository at "http://repo1.maven.org/eclipse" does no longer exist, and that "http://repo1.maven.org/maven2" does not have the necessary versions of the Eclipse JARs. For example uimaj-ep-configurator depends on "org.eclipse.core:org.eclipse.core.variables:jar" in version "3.1.100" but only the version "3.2.400.v20100505" is available (http://search.maven.org/#search%7Cga%7C1%7Corg.eclipse.core.variables). I'll work around this blocker by setting up a global mirror to our Artifactory in Darmstadt which still has the necessary artifacts in its cache.
>
> 9) I remove the ~/.m2/repository, set up a global mirror in the settings.xml accessing our Artifactory and repeat the steps 5-8.
>
> Now (after step 9) I have mostly the same experience as you, Marshal: there are two errors, one in "uimaj-core" and one in "uimaj-tools", both due to UimaVersion missing.
>
>> * Marshal: This I "corrected" by right clicking it, and saying maven -> update project configuration. This is because the "default" m2eclipse install doesn't run the step needed to generate some classes that project needs, but does run it when you say update-project-configuration. At this point, everything is showing no-errors.
> 10) I run "Maven->Update project configuration".
>
> Now there are no build errors anymore.
> This is the end of Marshal's story.
>
> I would like to point out, that there are errors in the Maven console though, e.g. the one I had previously reported:
>
> 07.08.11 14:25:09 MESZ: Maven Builder: FULL_BUILD requireFullBuild
> 07.08.11 14:25:09 MESZ: [INFO] Unpacking /Users/bluefire/UKP/Workspaces/uima-experiment/uimaj-root/jVinci/target/classes to
> /Users/bluefire/UKP/Workspaces/uima-experiment/uimaj-root/uimaj-ep-runtime/target/classes
> with includes null and excludes:null
> 07.08.11 14:25:09 MESZ: Build errors for uimaj-ep-runtime; org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.1:unpack-dependencies (unpackDependentJars) on project uimaj-ep-runtime: Error unpacking file: /Users/bluefire/UKP/Workspaces/uima-experiment/uimaj-root/jVinci/target/classes to: /Users/bluefire/UKP/Workspaces/uima-experiment/uimaj-root/uimaj-ep-runtime/target/classes
> org.codehaus.plexus.archiver.ArchiverException: The source must not be a directory.
>
> I get this error in the Maven Console view whenever I do a "Project Clean/Rebuild" in Eclipse on the uimaj-ep-runtime plugin. Try it and you'll get it as well.
>
> === II) Running the CAS Editor ===
>
> Now comes the part where I want to run the uimaj-ep-cas-editor project as an Eclipse application.
>
> Step 11 (see below) does not work yet because the option "Run As->Eclipse application" is not available. I had expected this, because m2eclipse did not generate the PDE nature into the uimaj-ep-* projects. This also explains why there are no plugin errors even though are no MANIFEST.MF files in the uimaj-ep-* projects yet. There are two ways of fixing this:
>
> a) manually adding the PDE nature to the projects
> b) running "mvn eclipse:eclipse"
> c) installing the M2Eclipse OSGi development support, a.k.a "m2eclipse-tycho" from http://m2eclipse.sonatype.org/sites/m2e-extras
>
> I chose c) because I don't like the way that "eclipse:eclipse" configures the workspace.
>
> 10a) I installed "Tycho Project Configurators" from http://m2eclipse.sonatype.org/sites/m2e-extras - 0.4.3.20101103-1630
> 10b) I run "Maven->Update project configuration". After the dust settles, there are interestingly still no errors in the workspace.
> Interestingly there are still no errors now, even though there are no MANIFEST.MF files yet.
> Now to step 11.
>
> 11) I right-click on the uimaj-ep-cas-editor project and select "Run As->Eclipse application".
> 12) Create a new project "test"
> 13) Create a folder "text"
> 14) Create a text file "test1.txt" in that folder with the content "This is a test."
> 15) Use "Import->UIMA Cas Editor/Document" to import the text file...
>
> Uh! There is no "UIMA Cas Editor" section in the imports. The CAS Editor isn't there either. Looks like the bundles could not be resolved.
> I open the run configuration "Eclipse Application" that was created in step 11
> I select "Launch with: plug-ins selected below only"
> I select all of the plugins using the "Select All" button
> I select "Validate Plug-ins" and get a number of problems like "Missing Constraint: Import-Package: org.apache.uima...."
> That's reasonable, because there are no MANIFEST.MF files yet. To generate them, I have to run at least some "mvn process-classes". I choose to run the full "mvn clean install" without tests and without docbook as mentioned in one of my last mails.
>
> 10c) Right-click on the "uimaj" project and select "Run As->Maven build...".
> - Enter as goal "clean install". Enter the profile "!process-docbook" to disable docbook generation (unnecessary time any memory hog).
> - Select "skip Tests". On the "Refresh" tab enable "Refresh resources upon completion" and select "the entire workspace".
> Interestingly there are still no errors now, even though the MANIFEST.MF contain errors, but more on that later.
> Now back to step 15.
>
> 15) Use "Import->UIMA Cas Editor/Document" to import the text file and select "test/text" as the target folder
> 16) Use "New->UIMA..." to create a type system descriptor so that we can open the XMI file
>
> Ah, wait! We only ran the UIMA CAS Editor plugin. The Type System Editor Plugin is not part of that setup. Closing the CAS Editor Eclipse application to create a new run configuration that also includes the UIMA Tooling.
>
> 10d) Remove the "runtime-EclipseApplication" workspace
> 10e) Open the run configuration "Eclipse Application" that was created in step 11
> 10f) select "Launch with: plug-ins selected below only"
> 10g) select all of the plugins using the "Select All" button
> 10h) select "run"
> Now back to step 16)
>
> 16) Use "New->UIMA..." to create a type system descriptor so that we can open the XMI file
>
> Its still now there. OSGi says that the bundle is installed, but it is not resolved:
>
> org.apache.uima.desceditor (2.3.2.SNAPSHOT) "UIMA Eclipse: uimaj-ep-configurator: Descriptor Editor" [Installed]
>
> When I try to start it from the OSGi host console, I get:
>
> The bundle "org.apache.uima.desceditor_2.3.2.SNAPSHOT [258]" could not be resolved. Reason: Missing Constraint: Import-Package: org.apache.uima.jcas.jcasgenp; version="2.3.0"
>
> Looking at the MANIFEST.MF of uimaj-ep-configurator I find several odd things:
>
> - there are imports for a version 2.3 while it should be 2.3.2-SNAPSHOT (the exports are correct btw.!)
> - even packages from uimaj-ep-configurator are imported in version 2.3
>
> That is the end of my story so far, because I currently can't figure out at the moment, why the MANIFEST.MF files are broken.
>
> BLOCKER: As a last measure, I tried running a "mvn clean install" after removing my ~/.m2/repository on a completely fresh checkout of UIMA. But this also generates the broken package imports in the MANIFEST.MF. A JAR I had downloaded from Jenkins with the build timestamp 20110606-1443 still contains the correct import statements.
>
> === III) Resume ===
>
> I managed to get a workspace without build errors using Marshal's procedure described in section I).
> I managed to run the CAS Editor after installing the M2Eclipse OSGi development support (Tycho Project Configurators) and running mvn clean install (without tests and docbook) to generate the MANIFEST.MF files.
>
> I could identify two real blockers that need to be addressed:
> - Core dependencies of the UIMA Eclipse tooling seem to no longer available on repo1, probably due to restructuring happening lately on Maven Central.
> - Import-Package entries in the MANIFEST.MF files are generated with broken versions (2.3 instead of 2.3.2-SNAPSHOT).
>
> The UIMA SDK build on Apache Jenkins is failed on 22.07.2011 13:01:25 and did not run since then. I would have liked to download a build from there to see if the Import-Package entries are correct there.
>
> Currently it seems not to be possible to checkout and run UIMA Tooling Eclipse plugins or the CAS Editor without running "mvn clean install" or at least "mvn process-classes" at some point.
> It seems as running "mvn clean install" would also be necessary whenever changes at the UIMA core framework are done, so that the changes are picked up and repackaged into uimaj-ep-runtime. This is due to the fact that the "unpackDependentJars" mojo of uimaj-ep-runtime produces an error when running as part of an incremental m2eclipse build. It might be worth to consider adding OSGi metadata to the core UIMA modules (uimaj-core, uimaj-tools, etc.) and obsolete the uimaj-ep-runtime module and the "unpackDependentJars" mojo in this way. It would also be good to have an integration test running as part of the build to see at least if the Eclipse plugins all install and resolve properly.
>
> -- Richard
>
Trigger UIMA SDK build on Jenkins
Posted by Richard Eckart de Castilho <ec...@tk.informatik.tu-darmstadt.de>.
Am 07.08.2011 um 17:00 schrieb Richard Eckart de Castilho:
> The UIMA SDK build on Apache Jenkins is failed on 22.07.2011 13:01:25 and did not run since then. I would have liked to download a build from there to see if the Import-Package entries are correct there.
Could anybody please trigger a build of the UIMA SDK on builds.apache.org? The reason for the last build failure seems to be temporary but since then no changes have been made to the source code. I would like to know if the UIMA Core Eclipse Plugins built on Jenkins are ok.
Building remotely on solaris2
FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
Cheers,
Richard
--
-------------------------------------------------------------------
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab
FB 20 Computer Science Department
Technische Universität Darmstadt
Hochschulstr. 10, D-64289 Darmstadt, Germany
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckartde@tk.informatik.tu-darmstadt.de
www.ukp.tu-darmstadt.de
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------
Re: [jira] [Commented] (UIMA-2141) Annotations Styles view - filter field
Posted by Richard Eckart de Castilho <ec...@tk.informatik.tu-darmstadt.de>.
Thanks for your exhaustive answer. Marshal. To avoid unnecessary discussions I won't reply directly to most of the questions. Instead, I'll try to focus on repeating and documenting the steps suggested by Marshal and try to use clearer language to avoid misunderstandings. I have divided this mail into three sections:
I) Checking out UIMA - reproducing the steps Marshal explained in his last mail
II) Running the CAS Editor - (trying to) run CAS Editor to run
III) Resume
=== I) Checking out UIMA ===
I've repeated your steps:
1) Just to make everything as clean as possible, I moved my settings.xml and ~/.m2/repository out of the way.
> * Marshal: get a brand new install of Eclipse 3.6.2. I put into it the subclipse plugin and the m2eclipse plugin.
2) I fetched the Eclipse 3.6.2 Classic OS X 64bit Cocoa distribution from http://www.eclipse.org/downloads/packages/eclipse-classic-362/heliossr2
3) I installed subclipse from http://subclipse.tigris.org/update_1.6.x
4) I installed m2eclipse from http://m2eclipse.sonatype.org/sites/m2e
- Maven Integration for Eclipse (Required) 0.12.20110112-1712
Note: Eclipse 3.6.2 Classic is the one that includes all the PDE stuff, but does not come with Subversive.
> * Marshal: use a svn command-line client (not Eclipse) to check out ...uima/uimaj/trunk.
5) I started a fresh workspace
6) I checked the stuff out on the command line using
svn checkout http://svn.apache.org/repos/asf/uima/uimaj/trunk uimaj-root
> * Marshal: use Eclipse -> Import -> Maven -> Existing Maven Projects, and select the checkout directory.
7) I started Eclipse and waited until the "Updating indexes" had completed.
8) I imported the "uimaj-root" folder into which I had done the checking out.
> * Marshal: after a while, it was all in, except that uimaj-core had an "error".
Now after a while Eclipse is done and there are lots of errors because artifacts cannot be found.
BLOCKER: A blocker for a new user at the moment seems to be that the repository at "http://repo1.maven.org/eclipse" does no longer exist, and that "http://repo1.maven.org/maven2" does not have the necessary versions of the Eclipse JARs. For example uimaj-ep-configurator depends on "org.eclipse.core:org.eclipse.core.variables:jar" in version "3.1.100" but only the version "3.2.400.v20100505" is available (http://search.maven.org/#search%7Cga%7C1%7Corg.eclipse.core.variables). I'll work around this blocker by setting up a global mirror to our Artifactory in Darmstadt which still has the necessary artifacts in its cache.
9) I remove the ~/.m2/repository, set up a global mirror in the settings.xml accessing our Artifactory and repeat the steps 5-8.
Now (after step 9) I have mostly the same experience as you, Marshal: there are two errors, one in "uimaj-core" and one in "uimaj-tools", both due to UimaVersion missing.
> * Marshal: This I "corrected" by right clicking it, and saying maven -> update project configuration. This is because the "default" m2eclipse install doesn't run the step needed to generate some classes that project needs, but does run it when you say update-project-configuration. At this point, everything is showing no-errors.
10) I run "Maven->Update project configuration".
Now there are no build errors anymore.
This is the end of Marshal's story.
I would like to point out, that there are errors in the Maven console though, e.g. the one I had previously reported:
07.08.11 14:25:09 MESZ: Maven Builder: FULL_BUILD requireFullBuild
07.08.11 14:25:09 MESZ: [INFO] Unpacking /Users/bluefire/UKP/Workspaces/uima-experiment/uimaj-root/jVinci/target/classes to
/Users/bluefire/UKP/Workspaces/uima-experiment/uimaj-root/uimaj-ep-runtime/target/classes
with includes null and excludes:null
07.08.11 14:25:09 MESZ: Build errors for uimaj-ep-runtime; org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.1:unpack-dependencies (unpackDependentJars) on project uimaj-ep-runtime: Error unpacking file: /Users/bluefire/UKP/Workspaces/uima-experiment/uimaj-root/jVinci/target/classes to: /Users/bluefire/UKP/Workspaces/uima-experiment/uimaj-root/uimaj-ep-runtime/target/classes
org.codehaus.plexus.archiver.ArchiverException: The source must not be a directory.
I get this error in the Maven Console view whenever I do a "Project Clean/Rebuild" in Eclipse on the uimaj-ep-runtime plugin. Try it and you'll get it as well.
=== II) Running the CAS Editor ===
Now comes the part where I want to run the uimaj-ep-cas-editor project as an Eclipse application.
Step 11 (see below) does not work yet because the option "Run As->Eclipse application" is not available. I had expected this, because m2eclipse did not generate the PDE nature into the uimaj-ep-* projects. This also explains why there are no plugin errors even though are no MANIFEST.MF files in the uimaj-ep-* projects yet. There are two ways of fixing this:
a) manually adding the PDE nature to the projects
b) running "mvn eclipse:eclipse"
c) installing the M2Eclipse OSGi development support, a.k.a "m2eclipse-tycho" from http://m2eclipse.sonatype.org/sites/m2e-extras
I chose c) because I don't like the way that "eclipse:eclipse" configures the workspace.
10a) I installed "Tycho Project Configurators" from http://m2eclipse.sonatype.org/sites/m2e-extras - 0.4.3.20101103-1630
10b) I run "Maven->Update project configuration". After the dust settles, there are interestingly still no errors in the workspace.
Interestingly there are still no errors now, even though there are no MANIFEST.MF files yet.
Now to step 11.
11) I right-click on the uimaj-ep-cas-editor project and select "Run As->Eclipse application".
12) Create a new project "test"
13) Create a folder "text"
14) Create a text file "test1.txt" in that folder with the content "This is a test."
15) Use "Import->UIMA Cas Editor/Document" to import the text file...
Uh! There is no "UIMA Cas Editor" section in the imports. The CAS Editor isn't there either. Looks like the bundles could not be resolved.
I open the run configuration "Eclipse Application" that was created in step 11
I select "Launch with: plug-ins selected below only"
I select all of the plugins using the "Select All" button
I select "Validate Plug-ins" and get a number of problems like "Missing Constraint: Import-Package: org.apache.uima...."
That's reasonable, because there are no MANIFEST.MF files yet. To generate them, I have to run at least some "mvn process-classes". I choose to run the full "mvn clean install" without tests and without docbook as mentioned in one of my last mails.
10c) Right-click on the "uimaj" project and select "Run As->Maven build...".
- Enter as goal "clean install". Enter the profile "!process-docbook" to disable docbook generation (unnecessary time any memory hog).
- Select "skip Tests". On the "Refresh" tab enable "Refresh resources upon completion" and select "the entire workspace".
Interestingly there are still no errors now, even though the MANIFEST.MF contain errors, but more on that later.
Now back to step 15.
15) Use "Import->UIMA Cas Editor/Document" to import the text file and select "test/text" as the target folder
16) Use "New->UIMA..." to create a type system descriptor so that we can open the XMI file
Ah, wait! We only ran the UIMA CAS Editor plugin. The Type System Editor Plugin is not part of that setup. Closing the CAS Editor Eclipse application to create a new run configuration that also includes the UIMA Tooling.
10d) Remove the "runtime-EclipseApplication" workspace
10e) Open the run configuration "Eclipse Application" that was created in step 11
10f) select "Launch with: plug-ins selected below only"
10g) select all of the plugins using the "Select All" button
10h) select "run"
Now back to step 16)
16) Use "New->UIMA..." to create a type system descriptor so that we can open the XMI file
Its still now there. OSGi says that the bundle is installed, but it is not resolved:
org.apache.uima.desceditor (2.3.2.SNAPSHOT) "UIMA Eclipse: uimaj-ep-configurator: Descriptor Editor" [Installed]
When I try to start it from the OSGi host console, I get:
The bundle "org.apache.uima.desceditor_2.3.2.SNAPSHOT [258]" could not be resolved. Reason: Missing Constraint: Import-Package: org.apache.uima.jcas.jcasgenp; version="2.3.0"
Looking at the MANIFEST.MF of uimaj-ep-configurator I find several odd things:
- there are imports for a version 2.3 while it should be 2.3.2-SNAPSHOT (the exports are correct btw.!)
- even packages from uimaj-ep-configurator are imported in version 2.3
That is the end of my story so far, because I currently can't figure out at the moment, why the MANIFEST.MF files are broken.
BLOCKER: As a last measure, I tried running a "mvn clean install" after removing my ~/.m2/repository on a completely fresh checkout of UIMA. But this also generates the broken package imports in the MANIFEST.MF. A JAR I had downloaded from Jenkins with the build timestamp 20110606-1443 still contains the correct import statements.
=== III) Resume ===
I managed to get a workspace without build errors using Marshal's procedure described in section I).
I managed to run the CAS Editor after installing the M2Eclipse OSGi development support (Tycho Project Configurators) and running mvn clean install (without tests and docbook) to generate the MANIFEST.MF files.
I could identify two real blockers that need to be addressed:
- Core dependencies of the UIMA Eclipse tooling seem to no longer available on repo1, probably due to restructuring happening lately on Maven Central.
- Import-Package entries in the MANIFEST.MF files are generated with broken versions (2.3 instead of 2.3.2-SNAPSHOT).
The UIMA SDK build on Apache Jenkins is failed on 22.07.2011 13:01:25 and did not run since then. I would have liked to download a build from there to see if the Import-Package entries are correct there.
Currently it seems not to be possible to checkout and run UIMA Tooling Eclipse plugins or the CAS Editor without running "mvn clean install" or at least "mvn process-classes" at some point.
It seems as running "mvn clean install" would also be necessary whenever changes at the UIMA core framework are done, so that the changes are picked up and repackaged into uimaj-ep-runtime. This is due to the fact that the "unpackDependentJars" mojo of uimaj-ep-runtime produces an error when running as part of an incremental m2eclipse build. It might be worth to consider adding OSGi metadata to the core UIMA modules (uimaj-core, uimaj-tools, etc.) and obsolete the uimaj-ep-runtime module and the "unpackDependentJars" mojo in this way. It would also be good to have an integration test running as part of the build to see at least if the Eclipse plugins all install and resolve properly.
-- Richard
--
-------------------------------------------------------------------
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab
FB 20 Computer Science Department
Technische Universität Darmstadt
Hochschulstr. 10, D-64289 Darmstadt, Germany
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckartde@tk.informatik.tu-darmstadt.de
www.ukp.tu-darmstadt.de
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------
Re: [jira] [Commented] (UIMA-2141) Annotations Styles view - filter
field
Posted by Marshall Schor <ms...@schor.com>.
On 8/4/2011 6:07 PM, Richard Eckart de Castilho wrote:
> Am 04.08.2011 um 03:08 schrieb Marshall Schor:
>
>> Do you use m2eclipse? (see http://uima.apache.org/one-time-setup.html - the
>> Eclipse part especially). I'm using the m2eclipse plugin at version 0.12.1.20110112-1712.
> I use the same version of m2eclipse also in Eclipse 3.6.2.
>
>> In my Eclipse 3.6.2, the .classpath for uima-ep-jcasgen looks like:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <classpath>
>> <classpathentry kind="src" output="target/classes" path="src/main/java"/>
>> <classpathentry excluding="**" kind="src" output="target/classes"
>> path="src/main/resources"/>
>> <classpathentry kind="con"
>> path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5"/>
>> <classpathentry kind="con"
>> path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
>> <classpathentry kind="output" path="target/classes"/>
>> </classpath>
> This looks like the .classpath file generated by m2eclipse which contains both, the Plug-in Dependencies Libaray and the Maven Dependencies Library. I prefer this classpath setup. When I run "mvn eclipse:eclipse" this is changed, however, so that links are generated in the plugin projects pointing to the jars in the .m2/repository folder and these are added as "References Libraries" to the build path. I have re-run "Maven->Update project configuration" to restore the m2eclipse style.
So - I'm missing some fundamental point (probably from not reading this email
chain very carefully, over a long period... :-) ).
If you're saying that you have the same set up when using m2eclipse, why change
to use eclipse:eclipse - which apparently makes things not compile?
>
> After a lot of trial and error, I came up with this set of steps to get UIMA imported into my Eclipse (ignoring mvn eclipse:eclipse at the moment):
>
> * Turn off automatic building (saves some time while UIMA cannot properly build yet)
> * Add "http://svn.apache.org/repos/asf/uima/uimaj" as a SVN repository in Eclipse
> * Check out "trunk" as a project (not as a Maven project)
Here's what I did:
I got a brand new install of Eclipse 3.6.2. I put into it the subclipse plugin
and the m2eclipse plugin.
I then used a svn command-line client (not Eclipse) to check out
...uima/uimaj/trunk.
Then I used Eclipse -> Import -> Maven -> Existing Maven Projects, and selected
the checkout directory.
It showed all the projects, and I said proceed.
After a while, it was all in, except that uimaj-core had an "error". This I
"corrected" by right clicking it, and saying maven -> update project
configuration. This is because the "default" m2eclipse install doesn't run the
step needed to generate some classes that project needs, but does run it when
you say update-project-configuration.
At this point, everything is showing no-errors.
> * Select "Check out as a project in the workspace" and set the project name to "uimaj-root"
> * Right-click on the "uimaj" folder within the "uimaj-root" project and select "Run As->Maven build...".
> - Enter as goal "clean install". Enter the profile "!process-docbook" to disable docbook generation (unnecessary time any memory hog).
> - Select "skip Tests". On the "Refresh" tab enable "Refresh resources upon completion" and select "the entire workspace".
> - Now run (this may take a while).
> - Check the progress by opening a Maven Console from the Eclipse Console View (small symbol with a "+" at the top right corner).
> * Right-click on the "uimaj-root" project and select "Import->Existing Maven Project"
> * After the import is complete, the launch configurations in uimaj-examples are dirty - revert the changes.
> * Right-click on all UIMA projects except "uimaj-root" and select "Maven->Update project configuration" so the additional source files generated by Maven are added to the classpath.
> * Now build the workspace.
I think that you don't need to do things that way. With the import, and the one
update-maven-configuration, it all should compile in Eclipse without running any
maven things (beyond what m2eclipse does). Of course, that doesn't do
everything the "mvn install" command would do (such as building the docbooks
etc). But it does compile all the java code.
Having done this, I did one other thing - just to see if it would also work
without messing things up.
I went to a command window, into the uimaj project directory, and ran maven install.
It built everything and said "BUILD SUCCESS" at the end:
In case it's helpful, here's the last bit of output:
[INFO] Reactor Summary:
[INFO]
[INFO] UIMA Java SDK: uimaj-parent ....................... SUCCESS [1.185s]
[INFO] UIMA Base: uimaj-test-util: JUnit utilities ....... SUCCESS [2.983s]
[INFO] UIMA Base: uimaj-core ............................. SUCCESS [56.493s]
[INFO] UIMA Base: jVinci: Vinci Transport Library ........ SUCCESS [0.966s]
[INFO] UIMA Base: uimaj-adapter-vinci: Vinci Adapter ..... SUCCESS [3.253s]
[INFO] UIMA Base: uimaj-cpe: Collection Processing Engine SUCCESS [26.088s]
[INFO] UIMA Base: uimaj-document-annotation .............. SUCCESS [1.204s]
[INFO] UIMA Base: uimaj-tools: Tools ..................... SUCCESS [5.837s]
[INFO] UIMA Base: uimaj-examples: SDK Examples ........... SUCCESS [1.094s]
[INFO] UIMA Base: uimaj-adapter-soap: SOAP Adapter ....... SUCCESS [0.865s]
[INFO] UIMA Base: uimaj-component-test-util: for JUnit ... SUCCESS [0.797s]
[INFO] UIMA Eclipse: uimaj-ep-debug ...................... SUCCESS [13.826s]
[INFO] UIMA Eclipse: uimaj-ep-jcasgen .................... SUCCESS [1.962s]
[INFO] UIMA Eclipse: uimaj-ep-configurator: Descriptor Editor SUCCESS [4.065s]
[INFO] UIMA Eclipse: uimaj-ep-pear-packager .............. SUCCESS [2.090s]
[INFO] UIMA Eclipse: uimaj-ep-launcher ................... SUCCESS [2.518s]
[INFO] UIMA Eclipse: uimaj-ep-cas-editor ................. SUCCESS [3.965s]
[INFO] UIMA Eclipse: uimaj-ep-cas-editor-ide ............. SUCCESS [2.050s]
[INFO] UIMA Eclipse: uimaj-ep-runtime .................... SUCCESS [16.829s]
[INFO] UIMA Eclipse: uimaj-eclipse-feature-tools ......... SUCCESS [0.701s]
[INFO] UIMA Eclipse: uimaj-eclipse-feature-runtime ....... SUCCESS [0.644s]
[INFO] UIMA Aggregate: aggregate-uimaj-eclipse-plugins ... SUCCESS [0.057s]
[INFO] Apache UIMA SDK Documentation - overview and setup SUCCESS [19.136s]
[INFO] Apache UIMA SDK Documentation - references ........ SUCCESS [10.408s]
[INFO] Apache UIMA SDK Documentation - tools ............. SUCCESS [9.889s]
[INFO] Apache UIMA SDK Documentation - tutorials and user's guides SUCCESS
[22.763s]
[INFO] UIMA Aggregate POM aggregate-uimaj-docbooks: UIMA Base SUCCESS [0.071s]
[INFO] UIMA Maven Plugin PearPackagingMavenPlugin ........ SUCCESS [4.408s]
[INFO] UIMA Base: uimaj-bootstrap: Bootstrap launcher .... SUCCESS [0.714s]
[INFO] UIMA Aggregate: aggregate-uimaj: UIMA Base ........ SUCCESS [0.065s]
[INFO] UIMA Base: uimaj-distr ............................ SUCCESS [58.816s]
[INFO] UIMA Java SDK: uimaj .............................. SUCCESS [0.090s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4:37.560s
[INFO] Finished at: Sat Aug 06 21:53:12 EDT 2011
[INFO] Final Memory: 32M/191M
[INFO] ------------------------------------------------------------------------
Then I went back into Eclipse and clicked "Refresh" on all projects.
The refresh happened, and all the projects were still OK - no errors.
>
> Now I am getting this error:
>
> 04.08.11 23:57:56 MESZ: Build errors for uimaj-ep-runtime; org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.1:unpack-dependencies (unpackDependentJars) on project uimaj-ep-runtime: Error unpacking file: /Users/bluefire/UKP/Workspaces/dkpro-primary/uimaj-root/jVinci/target/classes to: /Users/bluefire/UKP/Workspaces/dkpro-primary/uimaj-root/uimaj-ep-runtime/target/classes
> org.codehaus.plexus.archiver.ArchiverException: The source must not be a directory.
> 04.08.11 23:57:56 MESZ: [ERROR] An internal error occurred null
>
> Do you also get this error with your m2eclipse-based setup, Marshal?
no - I don't get any errors for my install (other than uimaj-core initial import
build, needed that update-maven-configuration step).
>
> I didn't try yet to "run" the CAS Editor from within Eclipse. To really test that, I would need to set up another Eclipse which does not have the UIMA runtime bundle installed. Since CAS Editor and UIMA-J are currently one "project",
I don't understand this. In my setup, uimaj and the cas editor are 2 Eclipse
projects, not one.
> I would expect/desire to be able to run the CAS Editor without previously installing the UIMA runtime plugin into the Eclipse instance.
Eclipse has a mechanism for doing debug (or regular) launches of "Eclipse
Applications", which does just what you want - launches a "child" version of
Eclipse, and lets you pick which plugins to have as pre-installed, and which
ones should be the ones under test and come from the "parent" Eclipse.
-Marshall
>
> -- Richard
>
Re: uima-ep-runtime vs. OSGi metadata in uimaj-core?
Posted by Marshall Schor <ms...@schor.com>.
I tried using Eclipse 3.7, with the m2e plugin from the main Eclipse update site.
This is a different plugin than m2eclipse at 0.12.xxx. It does quite a few
things differently, it seems, and we'll need to investigate.
It installed some other plugins, like one call m2e connector for
build-helper-maven-plugin, and "Tycho Project Configurators". I don't know what
these do.
I then tried a brand-new unzipped Eclipse 3.7, and installed into it m2eclipse
from http://m2eclipse.sonatype.org/installing-m2eclipse.html (not m2e) . With
that version, I had the same behavior as 3.6.2 - after importing, it compiled
everything except uimaj-core, and it compiled that after I did (right-click on
uimaj-core) -Maven -Update project configuration.
So - I think until we figure this out, we have to say that the m2e plugin
doesn't do the job - continue to use m2eclipse from that url above, in 3.7.
-Marshall
On 8/5/2011 9:06 PM, Richard Eckart de Castilho wrote:
> I am still trying to get an UIMA workspace set up in Eclipse with m2eclipse and still fail - mostly. I feel a bit odd here about why it's so non-trivial to get a proper Eclipse workspace for UIMA with m2eclipse. Probably I'm just plain stubborn because I believe that I should not have to run external tools (like mvn eclipse:eclipse or even clean install) when developing software in an IDE... I mean it should be an "integrated development environment", right?
>
> Anyway...
>
> One problem seems to be the uimaj-ep-runtime module. It uses a "unpack-depencendies" goal which throws an error in Eclipse 3.6.2 and which is completely unsupported in Eclipse 3.7 (m2e).
>
> I finally managed to "run" the uima-ep-cas-editor" module from Eclispe (3.7), but only after I had turned uimaj-core itself into an Eclipse plugin project by adding the "marker-file-identifying-eclipse-plugin", adding a "plugin.xml", and adding a minimal maven-bundle-plugin configuration in the POM.
>
> I wonder, is there a special reason to unpack and re-package the core UIMA JARs into a single "UIMA Runtime" plugin? Since OSGi bundles are just like regular jars plus a bit of meta-data, how about not having uimaj-ep-runtime and add the OSGi metadata directly to uimaj-core and friends?
>
> I also did disable the uima-helper-maven-plugin because it produced error markers all over the place with m2e(lipse) from Eclipse 3.7.
>
> Also m2e produces a number of Maven-related warnings about managed dependency versions being overridden in modules and superfluous groupIds and versions.
>
> Cheers,
>
> Richard
>
Re: uima-ep-runtime vs. OSGi metadata in uimaj-core?
Posted by Marshall Schor <ms...@schor.com>.
On 8/5/2011 9:06 PM, Richard Eckart de Castilho wrote:
> I am still trying to get an UIMA workspace set up in Eclipse with m2eclipse and still fail - mostly. I feel a bit odd here about why it's so non-trivial to get a proper Eclipse workspace for UIMA with m2eclipse. Probably I'm just plain stubborn because I believe that I should not have to run external tools (like mvn eclipse:eclipse or even clean install) when developing software in an IDE... I mean it should be an "integrated development environment", right?
Right. Something very strange is happening. See my earlier post.
I started with a brand new, freshly unzipped version of Eclipse 3.6.2, installed
just 2 plugins (Subversion and m2Eclipse), and then got things going by
1) checking out of SVN (using a svn command line client, using the command:
svn checkout http://svn.apache.org/repos/asf/uima/uimaj/trunk
myLocalWorkingDirectory
2) in Eclipse, using File -> Import -> Maven -> Existing Maven projects, and
imported things.
>
> Anyway...
>
> One problem seems to be the uimaj-ep-runtime module. It uses a "unpack-depencendies" goal which throws an error in Eclipse 3.6.2 and which is completely unsupported in Eclipse 3.7 (m2e).
>
> I finally managed to "run" the uima-ep-cas-editor" module from Eclispe (3.7), but only after I had turned uimaj-core itself into an Eclipse plugin project by adding the "marker-file-identifying-eclipse-plugin", adding a "plugin.xml", and adding a minimal maven-bundle-plugin configuration in the POM.
>
> I wonder, is there a special reason to unpack and re-package the core UIMA JARs into a single "UIMA Runtime" plugin? Since OSGi bundles are just like regular jars plus a bit of meta-data, how about not having uimaj-ep-runtime and add the OSGi metadata directly to uimaj-core and friends?
>
> I also did disable the uima-helper-maven-plugin because it produced error markers all over the place with m2e(lipse) from Eclipse 3.7.
>
> Also m2e produces a number of Maven-related warnings about managed dependency versions being overridden in modules and superfluous groupIds and versions.
Some of these may be issues with 3.7 - I haven't tried that yet.
-Marshall
>
> Cheers,
>
> Richard
>
uima-ep-runtime vs. OSGi metadata in uimaj-core?
Posted by Richard Eckart de Castilho <ec...@tk.informatik.tu-darmstadt.de>.
I am still trying to get an UIMA workspace set up in Eclipse with m2eclipse and still fail - mostly. I feel a bit odd here about why it's so non-trivial to get a proper Eclipse workspace for UIMA with m2eclipse. Probably I'm just plain stubborn because I believe that I should not have to run external tools (like mvn eclipse:eclipse or even clean install) when developing software in an IDE... I mean it should be an "integrated development environment", right?
Anyway...
One problem seems to be the uimaj-ep-runtime module. It uses a "unpack-depencendies" goal which throws an error in Eclipse 3.6.2 and which is completely unsupported in Eclipse 3.7 (m2e).
I finally managed to "run" the uima-ep-cas-editor" module from Eclispe (3.7), but only after I had turned uimaj-core itself into an Eclipse plugin project by adding the "marker-file-identifying-eclipse-plugin", adding a "plugin.xml", and adding a minimal maven-bundle-plugin configuration in the POM.
I wonder, is there a special reason to unpack and re-package the core UIMA JARs into a single "UIMA Runtime" plugin? Since OSGi bundles are just like regular jars plus a bit of meta-data, how about not having uimaj-ep-runtime and add the OSGi metadata directly to uimaj-core and friends?
I also did disable the uima-helper-maven-plugin because it produced error markers all over the place with m2e(lipse) from Eclipse 3.7.
Also m2e produces a number of Maven-related warnings about managed dependency versions being overridden in modules and superfluous groupIds and versions.
Cheers,
Richard
--
-------------------------------------------------------------------
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab
FB 20 Computer Science Department
Technische Universität Darmstadt
Hochschulstr. 10, D-64289 Darmstadt, Germany
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckartde@tk.informatik.tu-darmstadt.de
www.ukp.tu-darmstadt.de
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------
Re: [jira] [Commented] (UIMA-2141) Annotations Styles view - filter field
Posted by Richard Eckart de Castilho <ec...@tk.informatik.tu-darmstadt.de>.
Am 04.08.2011 um 03:08 schrieb Marshall Schor:
> Do you use m2eclipse? (see http://uima.apache.org/one-time-setup.html - the
> Eclipse part especially). I'm using the m2eclipse plugin at version 0.12.1.20110112-1712.
I use the same version of m2eclipse also in Eclipse 3.6.2.
> In my Eclipse 3.6.2, the .classpath for uima-ep-jcasgen looks like:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <classpath>
> <classpathentry kind="src" output="target/classes" path="src/main/java"/>
> <classpathentry excluding="**" kind="src" output="target/classes"
> path="src/main/resources"/>
> <classpathentry kind="con"
> path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5"/>
> <classpathentry kind="con"
> path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
> <classpathentry kind="output" path="target/classes"/>
> </classpath>
This looks like the .classpath file generated by m2eclipse which contains both, the Plug-in Dependencies Libaray and the Maven Dependencies Library. I prefer this classpath setup. When I run "mvn eclipse:eclipse" this is changed, however, so that links are generated in the plugin projects pointing to the jars in the .m2/repository folder and these are added as "References Libraries" to the build path. I have re-run "Maven->Update project configuration" to restore the m2eclipse style.
After a lot of trial and error, I came up with this set of steps to get UIMA imported into my Eclipse (ignoring mvn eclipse:eclipse at the moment):
* Turn off automatic building (saves some time while UIMA cannot properly build yet)
* Add "http://svn.apache.org/repos/asf/uima/uimaj" as a SVN repository in Eclipse
* Check out "trunk" as a project (not as a Maven project)
* Select "Check out as a project in the workspace" and set the project name to "uimaj-root"
* Right-click on the "uimaj" folder within the "uimaj-root" project and select "Run As->Maven build...".
- Enter as goal "clean install". Enter the profile "!process-docbook" to disable docbook generation (unnecessary time any memory hog).
- Select "skip Tests". On the "Refresh" tab enable "Refresh resources upon completion" and select "the entire workspace".
- Now run (this may take a while).
- Check the progress by opening a Maven Console from the Eclipse Console View (small symbol with a "+" at the top right corner).
* Right-click on the "uimaj-root" project and select "Import->Existing Maven Project"
* After the import is complete, the launch configurations in uimaj-examples are dirty - revert the changes.
* Right-click on all UIMA projects except "uimaj-root" and select "Maven->Update project configuration" so the additional source files generated by Maven are added to the classpath.
* Now build the workspace.
Now I am getting this error:
04.08.11 23:57:56 MESZ: Build errors for uimaj-ep-runtime; org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.1:unpack-dependencies (unpackDependentJars) on project uimaj-ep-runtime: Error unpacking file: /Users/bluefire/UKP/Workspaces/dkpro-primary/uimaj-root/jVinci/target/classes to: /Users/bluefire/UKP/Workspaces/dkpro-primary/uimaj-root/uimaj-ep-runtime/target/classes
org.codehaus.plexus.archiver.ArchiverException: The source must not be a directory.
04.08.11 23:57:56 MESZ: [ERROR] An internal error occurred null
Do you also get this error with your m2eclipse-based setup, Marshal?
I didn't try yet to "run" the CAS Editor from within Eclipse. To really test that, I would need to set up another Eclipse which does not have the UIMA runtime bundle installed. Since CAS Editor and UIMA-J are currently one "project", I would expect/desire to be able to run the CAS Editor without previously installing the UIMA runtime plugin into the Eclipse instance.
-- Richard
--
-------------------------------------------------------------------
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab
FB 20 Computer Science Department
Technische Universität Darmstadt
Hochschulstr. 10, D-64289 Darmstadt, Germany
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckartde@tk.informatik.tu-darmstadt.de
www.ukp.tu-darmstadt.de
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------
Re: [jira] [Commented] (UIMA-2141) Annotations Styles view - filter
field
Posted by Marshall Schor <ms...@schor.com>.
Hi Richard,
Do you use m2eclipse? (see http://uima.apache.org/one-time-setup.html - the
Eclipse part especially)
In my Eclipse 3.6.2, the .classpath for uima-ep-jcasgen looks like:
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry kind="src" output="target/classes" path="src/main/java"/>
<classpathentry excluding="**" kind="src" output="target/classes"
path="src/main/resources"/>
<classpathentry kind="con"
path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5"/>
<classpathentry kind="con"
path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
<classpathentry kind="output" path="target/classes"/>
</classpath>
I'm using the m2eclipse plugin at version 0.12.1.20110112-1712.
What version are you using, and do you have this MAVEN2_CLASSPATH_CONTAINER kind
of classpath entry?
-Marshall
On 8/3/2011 3:59 PM, Richard Eckart de Castilho wrote:
> Hi folks,
>
>>> Thanks Jörn, I'll have a try.
>> Let us know about any problems, so I can help you.
> finally, I found a few minutes to have another stab at UIMA. I have reverted all changes that I may have had and updated to the latest version from SVN. Everything seems to compile fine, but I still have 33 plug-in errors in the following projects:
>
> uimaj-ep-cas-editor
> uimaj-ep-configurator
> uimaj-ep-jcasgen
> uimaj-ep-pear-packager
>
> All are of the type "No available bundle exports package 'org.apache.uima...'" - the packages seems always to be from uimaj-core.
> Do I get these errors occur because the uimaj-core project has no OSGi metadata?
> I do have the uimaj-ep-runtime 2.3.2.SNAPSHOT plugin installed in my Eclipse. Shouldn't Eclipse be able to locate the packages exported by that?
>
> Cheers,
>
> Richard
>
> Btw.: I find it interesting that m2eclipse now seems to support Eclipse plugin projects. When I last tried to mix Maven with RCP quite some time ago and had both the Plug-in Dependencies Libaray and the Maven Dependencies Library in the classpath, Eclipse kept on complaining about duplicate classes. This seems to work fine now.
>
Re: [jira] [Commented] (UIMA-2141) Annotations Styles view - filter field
Posted by Richard Eckart de Castilho <ec...@tk.informatik.tu-darmstadt.de>.
Am 04.08.2011 um 09:44 schrieb Jörn Kottmann:
> On 8/3/11 9:59 PM, Richard Eckart de Castilho wrote:
>> All are of the type "No available bundle exports package 'org.apache.uima...'" - the packages seems always to be from uimaj-core.
>> Do I get these errors occur because the uimaj-core project has no OSGi metadata?
>> I do have the uimaj-ep-runtime 2.3.2.SNAPSHOT plugin installed in my Eclipse. Shouldn't Eclipse be able to locate the packages exported by that?
> We have an uimaj-ep-runtime project which exports all the UIMA jars for
> the usage
> inside eclipse tools.
>
> I usually do the following to get everything compiling:
>
> - go to uimaj/uimaj folder
> - mvn clean install
> - mvn eclipse:eclipse (Some also use the maven eclipse plugin)
This process generates the feature.xml files in the projects
uimaj-eclipse-feature-runtime
uimaj-eclipse-feature-tools
After refreshing and rebuilding in Eclipse, all errors are gone, but the two projects mentioned above are dirty because the ".project" files have been changed.
Cheers,
Richard
--
-------------------------------------------------------------------
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab
FB 20 Computer Science Department
Technische Universität Darmstadt
Hochschulstr. 10, D-64289 Darmstadt, Germany
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckartde@tk.informatik.tu-darmstadt.de
www.ukp.tu-darmstadt.de
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------
Re: [jira] [Commented] (UIMA-2141) Annotations Styles view - filter
field
Posted by Jörn Kottmann <ko...@gmail.com>.
On 8/3/11 9:59 PM, Richard Eckart de Castilho wrote:
> All are of the type "No available bundle exports package 'org.apache.uima...'" - the packages seems always to be from uimaj-core.
> Do I get these errors occur because the uimaj-core project has no OSGi metadata?
> I do have the uimaj-ep-runtime 2.3.2.SNAPSHOT plugin installed in my Eclipse. Shouldn't Eclipse be able to locate the packages exported by that?
We have an uimaj-ep-runtime project which exports all the UIMA jars for
the usage
inside eclipse tools.
I usually do the following to get everything compiling:
- go to uimaj/uimaj folder
- mvn clean install
- mvn eclipse:eclipse (Some also use the maven eclipse plugin)
Then it should work, you may need a refresh in eclipse, especially
for all these MANIFEST.MF files.
Hope that helps,
Jörn