Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[question] ner-module location #5

Open
duncdrum opened this issue Feb 18, 2020 · 6 comments
Open

[question] ner-module location #5

duncdrum opened this issue Feb 18, 2020 · 6 comments

Comments

@duncdrum
Copy link
Collaborator

see #4
the ner-module.xqm is located at /exist/etc/../data/expathrepo/stanford-nlp-0.5.8/content/ner-module.xqm shouldn't that be inside /db/system/repo instead?

@lcahlander
Copy link
Collaborator

Run it within the DB. It is accessible by just

import module namespace ner = "http://exist-db.org/xquery/stanford-nlp/ner";

There is no need for an at location, because it is registered.

@duncdrum
Copy link
Collaborator Author

exist finds it just fine, it's just a petty that i can't get to the functions during development. There is also a possibility that the app-archetype is doing something funky here.

@adamretter
Copy link
Member

adamretter commented Mar 1, 2020

@duncdrum because the exist-stanford-nlp declares that it is an application and not a library (see https://github.com/lcahlander/exist-stanford-nlp/blob/master/xar-assembly.xml#L11) its files are all installed under /db/apps/stanford-nlp instead of /db/system/repo.

I think that /db/system/repo only holds the content of EXPath packages which are of type library.

For some reason a copy of the .xar file is left in /db/system/repo only when uploading via the Dashboard's Package Manager, I have opened a separate issue for that - eXist-db/existdb-packageservice#13.

I think this is now resolved?

@duncdrum
Copy link
Collaborator Author

duncdrum commented Mar 1, 2020

Dooh, although I think that speaks for splitting the package into a library and an application (with the front end stuff)

@adamretter
Copy link
Member

@duncdrum Sure. Can we close this issue now?

@duncdrum
Copy link
Collaborator Author

duncdrum commented Mar 2, 2020

@adamretter i ll close this after i had a go at refactoring the repo to contain separate library and app modules, either via PR or via giving up.

lcahlander added a commit that referenced this issue Dec 18, 2021
….efficient-java-matrix-library-ejml-0.25

build(deps): bump ejml from 0.23 to 0.25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants