I have wondered for some time if a binary release makes sense for uimaFIT at all. uimaFIT 1.4.x included a binary release as convenience for those people that do not use Maven. The idea was to provide them with all the libraries that uimaFIT needs to run, so they do not have to chase them down on the web. The purpose of the uimaFIT binary release is therefore quite different from that of the UIMA SDK or of UIMA-AS. uimaFIT is a (set of) libraries, not an application or tool.
A note in the README is easily added. But I would not want to add more from the standard UIMA SDK release. Rather, I'd completely forego the binary release and just distribute uimaFIT via Maven. After all, there doesn't seem to be a binary release or zipped update site for Ruta either. Personally, I don't really need the binary release. I just wanted to keep it because looking at the download numbers on Google Code, people apparently used it. -- Richard Am 19.08.2013 um 17:52 schrieb Marshall Schor <[email protected]>: > The uimaFIT binary packaging has some, but not all, of the uimaj sdk jars, > included. (jars not included are: uima-adapter-soap, uima-document-annotation, > uima-examples, uimaj-bootstrap (used by the uimaj launching scripts), and > uima-tools (includes the CVD, document analyzer, etc.). Other things missing > include the "config" directory (has the standard logging configurations), the > scripts in the bin directory, and eclipse plugins (for those who aren't using > the Eclipse Install mechanism) > > I think this partial inclusion of some of the uimaj sdk jars has the potential > to confuse a new user of uimaFIT, who may think it comes bundled with UIMA > Java > SDK. I think a short description of this should be in the README, or > preferably, either include all of uimaj sdk, or none of it. > > -Marshall
