project-structure

I'm after an overview/clarification of the ideal project structure for a ruby (non-rails/merb/etc) project. I'm guessing it follows app/ bin/ #Files for command-line execution lib/ appname.rb appname/ #Classes and so on Rakefile #Running tests README test,spec,features/ #Whichever means of testing you go for appname.gemspec #If it's a gem Have I got something wrong? What parts have I missed out? I think that is pretty much spot on. By default, Rubygems will add the lib directory to the loadpath, but you can push any directory you want onto that using the $: variable. i.e. $:.push File.expand

How would you find a particular class name inside lots of jar files? (Looking for the actual class name, not the classes that reference it.) Eclipse can do it, just create a (temporary) project and put your libraries on the projects classpath. Then you can easily find the classes. Another tool, that comes to my mind, is Java Decompiler. It can open a lot of jars at once and helps to find classes as well. Unix Use the jar (or unzip -v ), grep , and find commands. For example, the following will list all the class files that match a given name: for i in *.jar; do jar -tvf "$i" | grep -Hsi

I know there are at least 10 different ways to structure project in version control. I'm curious what some methods being used are and which ones work for you. I've worked with SVN, TFS, and currently/unfortunately VSS. I've seen version control implemented very poorly and just OK, but never great. Just to get the ball rolling, here is a review of things I've seen. This example is SVN-based, but applies to most VCS's (not so much to distributed version control). branch the individual projects that are part of site /division/web/projectName/vb/src/[trunk|branches|tags] branch the whole site, in