Jörn Kottmann wrote:
How should we go on with this issue?
Does anyone know if these packages will go into the maven repository
in the future?
Is there a place to request these changes, so that the packages are
added to the maven repository?
If not we have to change the build, so that we use a local eclipse
version to compile the CasEditor project.
There are two options how to build and deploy the Cas Editor:
1. Its build like the other plugins and deployed as eclipse plugin.
2. Its build as RCP application (this requires an eclipse install) and
packaged for each
platform we want to support (win, linux and mac).
I would prefer the second option. The advantage is that it feels than
more
like an application and not like an eclipse plugin with many ui stuff
which does
not make sense for the Cas Editor.
Jörn
Sorry for my late response...
But from my point of view, I don't like the idea to build the CasEditor
as a RCP application. There are two reasons:
1) We already have eclipse plugins and swing applications, so I think we
should not create a third type of application for the UIMA SDK. For the
future I would like to have one tooling application for UIMA that
integrates all current available tooling apps that are available with
UIMA. That brings me to my next point.
2) The UIMA tooling from my point of view is often used when developing
an annotator or any other UIMA component. So I will use it in a UIMA
development environment which is from my point of view often eclipse. So
plugins fits best here. When having a RCP application, you cannot have
the tooling an the development env in one place, right?
-- Michael
