Skip to content
This repository has been archived by the owner on Mar 11, 2021. It is now read-only.

Hello,your site is not avaliable~ #8

Closed
wamdy opened this issue Feb 27, 2020 · 6 comments
Closed

Hello,your site is not avaliable~ #8

wamdy opened this issue Feb 27, 2020 · 6 comments
Assignees

Comments

@wamdy
Copy link

wamdy commented Feb 27, 2020

No description provided.

@Tiliavir
Copy link
Member

Hi @wamdy,
what site do you refer to? Could you provide some more information?
Thanks for a short update,
Markus

@MarkusTiede
Copy link
Member

Broken builds have been fixed with 6d0af4b

@Tiliavir
Copy link
Member

Tiliavir commented Mar 6, 2020

Closed due to lack of further information.

@Tiliavir Tiliavir closed this as completed Mar 6, 2020
@wamdy
Copy link
Author

wamdy commented Mar 7, 2020

I can‘t visit the eclipse plugin update site. http://www.massedynamic.org/eclipse/zookeeper
it returned that:

500 Internal Privoxy Error
Privoxy encountered an error while processing your request:

Could not load template file no-server-data or one of its included components.

Please contact your proxy administrator.

If you are the proxy administrator, please put the required file(s)in the (confdir)/templates directory. The location of the (confdir) directory is specified in the main Privoxy config file. (It's typically the Privoxy install directory).

@Tiliavir Tiliavir reopened this Mar 7, 2020
@MarkusTiede
Copy link
Member

Hi @wamdy - thanks for noticing: the project has been (in the not-recent past) transferred / donated to us.

As far as I know there is currently (no longer) a public update site with pre-compiled binarys / p2-dependencies available.

At the moment you can / have to do that manually e.g. by cloning and building locally:

Something like this could work

git clone https://github.com/baloise/eZooKeeper.git && cd eZooKeeper && mvn clean verify

After that you should find the p2-Repo within org.massedynamic.eclipse.zookeeper.repo/target/repository

Hope that helps a bit. We need to implement #6 for a proper resolution of this issue.

@MarkusTiede
Copy link
Member

Hence resolving as duplicate of #6.

@wamdy : did you had any chance to check whether the proposed local workaround is sufficient for you?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants