nice blog link :-) My personal preference is to be perhaps more up-front/transparent, and state in the README what you say here - that it's there as a proof-of-concept etc.
-Marshall On 8/19/2013 4:13 PM, Richard Eckart de Castilho wrote: > uimafit-spring is an experimental module. I built it as a proof of concept, > but never used it myself. Still, it has been made public (even to Maven > Central) in case somebody finds it useful. Apparently, it has found some > users (and even somebody to blog about it!) [1], but I have never considered > it as finished or an official part of the package. It has been released with > past releases with the same version number as the rest of uimaFIT to > Maven Central. It wasn't part of the binary distribution though. > > Personally, I'd stick to that strategy. Put it on Maven for the hardcore > few that may find it useful, but keep it out of the binary distribution, > at least until it has received some more attention. Currently, it uses > reflection to patch itself into the UIMA framework and then passes all > components created through UIMA through Spring to provide for the wiring > of Spring context dependencies. > > -- Richard > > [1] http://agibsonccc.tumblr.com > > Am 19.08.2013 um 21:59 schrieb Marshall Schor <[email protected]>: > >> missed one: >> >> The build builds uimafit-spring, but that's not a dependency by anything? >> Is it needed? >> >> -Marshall >> >> On 8/19/2013 3:26 PM, Marshall Schor wrote: >>> The binary release includes 3 jars from uimafit: >>> >>> uimafit-core >>> uimafit-cpe >>> uimafit-legacy-support >>> >>> I looked through the readme and the documentation for mentions of the last >>> 2. >>> The readme says you only need uimafit-core. The docbook doesn't mention >>> cpe or >>> legacy. I also looked in the uimafit-core pom and uimafit-parent pom for >>> references to thes last 2 and didn't find any (maybe it's there and I just >>> missed it...) >>> >>> Are these last 2 jars needed? If so, should they be documented somewhere? >>> >>> -Marshall
