You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Rafa Haro (JIRA)" <ji...@apache.org> on 2018/10/18 10:57:00 UTC

[jira] [Commented] (STANBOL-1471) Multiple installation problems

    [ https://issues.apache.org/jira/browse/STANBOL-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16655050#comment-16655050 ] 

Rafa Haro commented on STANBOL-1471:
------------------------------------

Hi Alex,

 

Thanks for your interest in Apache Stanbol. If you are still interested on this, I aim you to create bugs ticket for the issues you have found so we can work on them or even better, you can contribute the fixes if you are up to it. Regarding the issues, probably further information would needed for each of them

 

Thanks!

> Multiple installation problems
> ------------------------------
>
>                 Key: STANBOL-1471
>                 URL: https://issues.apache.org/jira/browse/STANBOL-1471
>             Project: Stanbol
>          Issue Type: Bug
>          Components: Build, Entityhub, Launcher , Web
>    Affects Versions: 1.0.0
>         Environment: Windows 10 and Ubuntu 18
>            Reporter: Alex Cameron
>            Priority: Major
>             Fix For: 1.0.0
>
>
> Is this (very cool) package not maintained anymore???
> I have an instance running on an Ubuntu machine 127.0.0.1:9000, which is proxied through Nginx, coming via Cloudflare - for adding SSL.
>  * Only JDK that will work is 1.8, on either Windows 10 or Ubuntu 18.
>  * Launcher hangs on Windows 10 first run (after compile), at DBpedia setup.
>  * Tests fail on both platforms, multiple exceptions when skipping tests.
>  * Can't run under HTTPS, as config manager makes hard-coded ajax calls to http:// URLs.
>  * EntityHub resources are shown as created in config manager, but result in 404 to any request (GET/PUT etc). They don't exist.
>  * DBpedia enhancement engines fail with exception: service has new URLs.
> Would really like to develop on the platform - if it's not going to be updated, can it be retired properly so people don't waste time trying to get it to work? Tickets here don't seem to have been touched for a long time.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)