#164 Connect to repo.aduna-software.org failed: connection timeout

[Sergey Zaytsev]

Hello! I can not build Aperture project - it hangs up on trying to download a lib from http://repo.aduna-software.org repository (connection times out). It won't success in offline build, so we really need that repo to serve requests. Is that repo still actual or you moved to another location ?

Issue lasts for a weeks...

[Sergey Zaytsev]

Please, guys from dev-team!

I can't believe you do not build the project. It is obvious that build wont succeed if you try. Repo is absolutely out of service. It is also impossible to download a single library from it.

[Antoni Mylka]

Two days after the last release on 29.12.2011 my contract with DFKI expired. Since then nobody that I know tried to build this project. It's pretty much dead. I've outlined the history on https://sourceforge.net/p/aperture/feature-requests/118/#e875

I took a close look. It's non-trivial. If you really need to build that code, or to actually refer to it from your pom file, you'd need to:

1. Release a new aperture root pom, without references to the Aduna repo.
2. Do a new release of the vocabulary maven plugin and the datasource maven plugin. Ensure that their poms refer the new aperture root pom and have no reference to the old aduna repo. In the process fix the <scm> and <distributionmanagement> sections in the poms. They refer to sourceforge URLs that were valid in 2011 or earlier. Both the SVN and the web content is now available under different URLs.</distributionmanagement></scm>
3. In the aperture codebase:
   • fix the version numbers in the aperture-assembly module. They got broken. INclude the aperture-assembly module in the default profile.
   • drop all references to NRL validator. It was a neat idea but now it's very closely tied to sesame 2.3 innards. You might try to port the aperture rdf tools (infsail, unionsail and nrlvalidator) to a recent version of Sesame, but IMHO validation is something we can live without.
   • update <scm> and <distributionmanagement></distributionmanagement></scm>
   • make a new release of Aperture (1.6.1, no new features, just buildable in 2014)

... in the process keep an eye on all dependencies and the maven repositories they refer, so that you don't include anything that refers to any other non-existent repository.

... or find someone who has those dependencies on some internal Nexus. I can perhaps upload them to the aperture maven repo, to make it self-contained.

[Sergey Zaytsev]

Thanks for advice! I'll defenetely devote my time to make it buildable back. Project is really good, worth using !