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

RDF-izer build fails due to nxparser 1.2.3 dependency #172

Open
osma opened this issue Sep 13, 2016 · 3 comments
Open

RDF-izer build fails due to nxparser 1.2.3 dependency #172

osma opened this issue Sep 13, 2016 · 3 comments

Comments

@osma
Copy link

osma commented Sep 13, 2016

Hi, I'm trying to build aliada-tool (current master). I'm using Maven 3.3.9 on an Ubuntu 14.04 machine with OpenJDK 8. I'm running the command mvn package in the aliada subdirectory.

The build stops at RDF-izer due to a dependency resolution issue:

[ERROR] Failed to execute goal on project aliada-rdfizer: Could not resolve dependencies for project eu.aliada:aliada-rdfizer:war:2.0: Could not find artifact org.semanticweb.yars:nxparser:jar:1.2.3 in nxparser-repo (http://nxparser.googlecode.com/svn/repository) -> [Help 1]

The problem is that nxparser 1.2.3 is not available in the Google Code repository anymore (because Google Code has shut down). The project has moved to GitHub. But the GitHub site also does not have the 1.2.3 release, only more recent 2.x versions.

After some detective work I was able to find the commit corresponding to the 1.2.3 release in the nxparser git history and install it manually:

  git clone https://github.com/nxparser/nxparser.git
  cd nxparser
  git checkout 543e4141d5fc89ac32519c30e4e8b88568401347
  mvn install

After this workaround I could resume the Aliada build and it was successful.

The real solution would be to upgrade to a more recent nxparser in the RDF-izer module. I'm not sure how much the nxparser API has changed between versions 1.2.3 and 2.x.

@agazzarini
Copy link
Member

Hi Osma,
many thanks for pointing this. Do you want to provide a patch? Let me
know, otherwise I will change that dependency

Best,
Andrea

On 13/09/16 09:01, Osma Suominen wrote:

Hi, I'm trying to build aliada-tool (current master). I'm using Maven
3.3.9 on an Ubuntu 14.04 machine with OpenJDK 8. I'm running the
command |mvn package| in the |aliada| subdirectory.

The build stops at RDF-izer due to a dependency resolution issue:

|[ERROR] Failed to execute goal on project aliada-rdfizer: Could not
resolve dependencies for project eu.aliada:aliada-rdfizer:war:2.0:
Could not find artifact org.semanticweb.yars:nxparser:jar:1.2.3 in
nxparser-repo (http://nxparser.googlecode.com/svn/repository) -> [Help
1] |

The problem is that nxparser 1.2.3 is not available in the Google Code
repository anymore (because Google Code has shut down). The project
has moved to GitHub. But the GitHub site
https://github.com/nxparser/nxparser also does not have the 1.2.3
release, only more recent 2.x versions.

After some detective work I was able to find the commit corresponding
to the 1.2.3 release in the nxparser git history and install it manually:

|git clone https://github.com/nxparser/nxparser.git cd nxparser git
checkout 543e4141d5fc89ac32519c30e4e8b88568401347 mvn install |

After this workaround I could resume the Aliada build and it was
successful.

The real solution would be to upgrade to a more recent nxparser in the
RDF-izer module. I'm not sure how much the nxparser API has changed
between versions 1.2.3 and 2.x.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#172, or mute the thread
https://github.com/notifications/unsubscribe-auth/AHOA4HCWWuVfvzpOLztKLhtR14UdvEEwks5qpkoxgaJpZM4J7Wg7.

@osma
Copy link
Author

osma commented Sep 13, 2016

If you can simply update the dependency, that would help a lot. At this point I'm just exploring and evaluating Aliada and I'm not sure yet whether we will start using it. I was able to get it working with the above workaround, so I don't have a patch ready.

@agazzarini
Copy link
Member

ok

On 13/09/16 13:25, Osma Suominen wrote:

If you can simply update the dependency, that would help a lot. At
this point I'm just exploring and evaluating Aliada and I'm not sure
yet whether we will start using it. I was able to get it working with
the above workaround, so I don't have a patch ready.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#172 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHOA4CXoVySFdMMJt0ZeDXT3wPR3vyA_ks5qpogdgaJpZM4J7Wg7.

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

2 participants