I have never used Weka, but for my GAE Project I'm going to need it. I checked jar files on Weka website to use in Eclipse but I'm not sure which one should be downloaded. So I checked another web site and there are lots of jar files about Weka. I'm looking for a basic version of it. Could you please tell me which one is best for me. Here the links for download:
http://grepcode.com/snapshot/repo1.maven.org/maven2/nz.ac.waikato.cms.weka/weka-dev/3.7.5
http://www.cms.waikato.ac.nz/ml/weka/
All files of Weka:
http://sourceforge.net/projects/weka/files/
Thank you.
You should download all project, then build it by maven.
You can use SVN to checkout code from this link:
https://svn.cms.waikato.ac.nz/svn/weka/trunk/weka
Related
I know that I can download the sources/java-doc for my dependencies using the update-classifiers task.
But it would also be interesting to be able to download the sbt sources/java-doc, as Intellij is not showing me any kind of documentation for sbt-related stuff. I've already checked on their website and they seem to only provide the binaries. I would like to avoid having to download their github project, if possible.
Thanks
I've noticed that in eclipse if you Right click on a project -> Grails Tools -> You have the option to 'Download Source Jars'.
What is the point of this and what are some common reasons as to why you would want to do this?
Grails 2.2.3
Edit:
I'm not even sure what grails does instead of that.
Many (most) libraries (JARs, "artifacts" in the Maven terminology) publish a sources archive alongside their binary artifacts in the repositories. This can be useful for Eclipse to show you the Javadoc and source code when you're using the library in your projects. As #JonSkeet commented above, it's very useful to have source code available directly in the IDE when using a library.
By default, Grails does not download the sources for artifacts; this option triggers it to do so and attach the sources to the binary JARs.
Agreed with E-Riz.
Here are the reasons I use the sources:
i want to have a deeper understanding of how the library works when debugging my own depending code
i want to find a possible bug in the library, so I can fork it and apply my own patch. i will possibly share this with the maintainers as a pull request if I'm willing to spend that much time on it.
i want to find out what logging systems it uses that might be poorly documented, so I can see better what their code is doing during runtime, to troubleshooting complicated problems.
I would need to use Eclipse to find code coverage of a test file generated by an automated tool with respect to a certain project.
I am thinking of using the "Emma" plugin but, as the project was not originally an Eclipse one, am having some difficulties importing it. I can open individual files, but that is not of much use as I can't run the plugin then.
Any ideas? :)
Thanks!
everyone.
I am new to Go language and currently I am trying to understand the basics of building Go applications. I met the following problem.
For example, I am using other libraries in my project. I have them locally, on my computer, so my project works fine.
I am loading my code on github and another programmer download it. As I understand, my code won't work, because this programmer doesn't have the libraries I used.
So the question is: What is the best way to share my project with all libraries it has? Should I upload these libraries in the separate repositories? Then to use my project, people need to look inside the code to detect which libraries I am using to download them one by one?
For example, in Java there is such thing like Maven or Ant, which downloads all required dependencies. Is there any tools like this for Go?
Let's call the main file of my project main.go
And I am using my own library: mathutil.go
what is the best way to make this project run on other computers?
Go's dependencies work very much like using Maven or IVY transitive dependencies. When someone does "go get" of your package, anything you depend on will automatically download.
For example, in your source:
import "github.com/foo/bar"
go will automatically download that to your $GOPATH/src/github.com/foo/bar along with your code.
Assuming the third party libs you use are hosted in a public repo (ie: github) then people don't need to do anything.
If the libraries you used are not available on a public repo, you will need to post them somewhere assuming their licensing allows.
Take a look at golang.org/doc/code.html for more details
i have checked similar posts and have googled but could not find an eligible answer to this. When ever i import a jsf project from some other system (where its working fine) OR delete the tomcat server in eclipse and add new server back again...there are lots of tag libs and imports that go "unresolved". Such applications are often not created by me and i dont exactly know which libraries are to be added to configure and fix project in eclipse.
I want to ask, is there any general way to find out all the required libraries for any imported jsf project and then add them.
Thanks in advance.
Download the javax.faces.jar file and drop it in project's /WEB-INF/lib folder.
That's all.