Hi Anuj,
I'm not sure what the problem is - maybe others more familiar with the
assembler can help - but would it be helpful to work on a fork of the
Jena source tree instead of a separate project? Then all the scaffolding
to load the right classes etc. would already be in place. Maybe you are
already doing it that way (I see that the package declaration is
"package org.apache.jena.query.text;") but it's not obvious from the
files you posted to GitHub.
If you make a good implementation of jena-text with ES (including
writing unit tests), I don't see why it couldn't later be merged to Jena
itself. If you were working on a fork, you could then do a pull request
so that it can be reviewed and, if appropriate, merged.
-Osma
14.02.2017, 14:06, anuj kumar kirjoitti:
Thanks Lorenz for the quick headsup. Here is the Github link to the listed
files : https://github.com/EaseTech/jena-text
Thanks,
Anuj Kumar
On Tue, Feb 14, 2017 at 12:46 PM, Lorenz B. <
[email protected]> wrote:
Attachments do not work on this mailing list, thus, it's better to share
resources via some service like Github etc.
*Anuj Kumar*
--
Lorenz Bühmann
AKSW group, University of Leipzig
Group: http://aksw.org - semantic web research center
--
Osma Suominen
D.Sc. (Tech), Information Systems Specialist
National Library of Finland
P.O. Box 26 (Kaikukatu 4)
00014 HELSINGIN YLIOPISTO
Tel. +358 50 3199529
[email protected]
http://www.nationallibrary.fi
