This is usually a problem in the case where Weka has never been able to connect to the internet and thus has not downloaded and established a cache of the central package metadata repository. If you are running Weka in offline mode, and the packages you are installing have some dependencies on one another, then there can still be some problems due to Weka not being able to verify the dependencies by checking against the central repository. zip file, open the WEKA package manager, and click on the File/URL button in the top-right corner of the package manager window (in the Unofficial panel).

zip files manually via your web browser, by navigating toĬlicking on the link for the package you want to install, then clicking on Latest, and finally clicking on the URL given next to PackageURL. However, if the package manager still cannot connect to the Internet, you can also force it to run in offline mode, by setting the above environment variable to =true This should allow the package manager to connect to the website that hosts the package meta-information. Your IT department should be able to give you these details. Where needs to be replaced by the name of your proxy server and port needs to be replaced by the appropriate port number on the proxy server. Set the value of this variable to -Dhttp.proxyHost= -Dhttp.proxyPort=port For Mac users, there is a nice program to set environment variables available here. Information on how to set environment variables in Windows is here. There is more information on this variable here. Which is read by Oracle Java virtual machines. The best way to achieve this is to configure an environment variable that provides the proxy details, e.g., _JAVA_OPTIONS The most likely reason for this is that your computer does not have direct access to the Internet and Java needs to be told to use a proxy server to access the web.

How to install weka in windows