[
https://issues.apache.org/jira/browse/UIMA-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740135#action_12740135
]
Jörn Kottmann commented on UIMA-1479:
-------------------------------------
I would love to learn what add-on packaging actually means ?
UIMA AS runs usually on a server and maybe it makes sense to optimize its
packaging for this purpose.
In my case I just grab the distribution file and unarchive it, install an AE
and deploy the installed AE.
On some setups its distributed with rsync between a few servers, which right
now takes quite a while
because there are many things in the distribution which are not needed on a
server e.g. eclipse plugins,
examples, tools, html and pdf documentation, etc.
There are also many scripts which makes using it a bit confusing, because most
of them are not needed
e.g. scripts to start ui tools.
We could have the UIMA AS eclipse plugins, documentation, samples in the main
distribution and maybe have a small UIMA AS runtime distribution as a separate
download which people deploy on their servers.
> Move UIMA-AS out of sandbox, change to an "add-on" packaging style to the core
> ------------------------------------------------------------------------------
>
> Key: UIMA-1479
> URL: https://issues.apache.org/jira/browse/UIMA-1479
> Project: UIMA
> Issue Type: Task
> Components: Async Scaleout
> Reporter: Marshall Schor
> Assignee: Marshall Schor
>
> UIMA-AS was voted to graduate from the sandbox. Make the needed changes to
> effect this, including:
> 1) moving it to uimaj node in SVN (eclipse plugins I think are already there)
> 2) changing the build so that its assembler builds an add-on-to-uima-base
> bin/src distribution. (It used to include most of base UIMA
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
