Community
Participate
Working Groups
The org.polarsys.kitalpha.doc.doc2model.tikaparsing provides extensions for the org.polarsys.kitalpha.doc.doc2model.tikaparsing.tikaParser extension point, but not for every possible parser available in the tika-app-1.5.jar library. While this is perfectly understandable, it would be nice not to limit the using developers to these parsers. By re-exporting the packages of this labrary (particularly org.apache.tika.parser and its sub-packages), we let external developers the possibility to contribute their own parsers, using the tika parsers which have not yet been exploited by doc2model (at their own risks). For example, I had to re-export org.apache.tika.parser and org.apache.tika.parser.odf to be able to make a new external contribution to org.polarsys.kitalpha.doc.doc2model.tikaparsing.tikaParser, with a class like this : public class ODFTikaParser extends AbstractTikaParser { @Override public Parser getParser() { return new OpenDocumentParser(); } } in order to parse ODF files (though this one could be used for any Libre/Open Office document. One could also probably embed the tika-app-1.5.jar in the external contributing plugin, but I feel quite unconfortable with having this library twice in the platform and I'm not sure what will happen with the Parser interface usage from the other jar contribution... Exporting these packages looks like a much cleaner solution to me.
KitAlpha plugins shall normally leave ReqCycle project and go to KitAlpha project. We will inform on this bug when refactoring is done