[in reply to http://forums.pragprog.com/forums/106/topics/8785]
Hi Dan, thanks for the reply. I've just dug a little further and found out that the "-o" at the end of launch command caused FitNesse to skip its file installation run on startup. This caused the stacktrace about the missing file, and was also the reason why the short URL did not work. So, at least one FitNesse start must be done without -o to complete the installation. Unfortunately, when I try to run the tests it simply hangs. So I'm still not where I want to be. The option to have FitNesse as apache-extras.org part on Isis is much more interesting to me than having it with NO4. The reason for this is, that I am currently using NO4 for prototyping. Scenario tests become important if we actually develop applications with it -- and this is something for which I would like to switch to Isis. What is currently keeping me from using Isis is that there is no release yet, and that your book makes it so very easy to start with NO4. I really appreciate the work you have put into there: the areas you cover and the level of detail you provide for them are really great. Even though I never used Maven2, Eclipse, or NO4 before I was able to get things working within hours. Given my current time constraints, for prototyping I want to go with something that is stable and avoid the risk of running into new and interesting problems. As for FitNesse vs Concordion: I need something that is accessible to non-developers as well. FitNesse running as a standlone Wiki server, and also the simplified Wiki syntax, makes this possible. Correct me if I'm wrong, but Concordion seems to be run within a development environment and is based on XHTML syntax. This would make it much harder to tie in a part of the team. When you say "supporting FitNesse within Apache Isis", are you talking about the Fit adapters or the SLIM code you mention in one of your blogs? From what little experience I have with FitNesse, the SLIM error reporting seems to be better. -- mva
