Jörn Kottmann wrote:
Sorry that it did not had time to respond to this mail.
I was quite busy the last few days.
What do you think is missing for the PEAR package? With the latest
fix in the CasEditor you can run an installed pear package.
Additionally with less programming effort, it will also be no problem
to upload at PEAR package and install it internally.
Let me first explain how I think it should be.
A user should be able to copy or share (maybe in a svn repository) a
cas editor project.
Currently this does not work cause the AE is either deployed as
eclipse runtime plugin or
as a PEAR which is somewhere in the filesystem.
To solve this the AE artifacts should be installed inside the cas
editor project.
Can we do this with PEAR ? Is it a problem if the path of the PEAR
install location
is modified ?
Sure you can use the PEAR API to install a PEAR file to a location of
your choice. So you can select as installation directory a path that
exists inside of your cas editor project.
After the PEAR file is installed to the specified location, the
installation location should not be changed, this means the the
workspace where your cas editor lives should not be moved. This is
because during the PEAR installation some path names in the PEAR are
replaced with absolute path names.
To work around this issue, you can add a PEAR file to your cas editor
project and install it on demand and then check if the PEAR file is
already installed or not. When doing this, you can also check if the
installation location for your PEAR has changed (if the workspace has
been moved to another place) and in such a case reinstall the PEAR again
to the new location.
The UIMA documentation contains an example that explains how to install
and run PEAR files using the PEAR API. Please use the UIMA 2.2 release
for this kind of PEAR processing, it has some advanced features that are
not available in 2.1.
-- Michael
