I have been quite confused with getting ojunit to work with 0.7b. The readme mentions none of it, and on the irc chanel somebody mentioned to me that I should run "rake submodule" to set it up.
However it didn't work - I suspect because the .gitmodules file is not checked in to the branch.
In the end, I just added ojunit myself "git submodule add git:// github.com/280north/ojunit.git Tools/ojunit" (after rake submodule) - and that seems to have done the trick.
We're not using git submodules anymore, because they were causing all
kinds of problems switching between branches. We're still looking into
a better solution.
In the meantime, you can just check out ojunit in Tools/ojunit. If you
run rake install after that, it should install it with the other tools.
rake test should run all the cappuccino tests (and will let you know
if its working or not).
> I have been quite confused with getting ojunit to work with 0.7b. The
> readme mentions none of it, and on the irc chanel somebody mentioned
> to me that I should run "rake submodule" to set it up.
> However it didn't work - I suspect because the .gitmodules file is not
> checked in to the branch.
> In the end, I just added ojunit myself "git submodule add git://
> github.com/280north/ojunit.git Tools/ojunit" (after rake submodule) -
> and that seems to have done the trick.
> I have been quite confused with getting ojunit to work with 0.7b. The
> readme mentions none of it, and on the irc chanel somebody mentioned
> to me that I should run "rake submodule" to set it up.
> However it didn't work - I suspect because the .gitmodules file is not
> checked in to the branch.
> In the end, I just added ojunit myself "git submodule add git://
> github.com/280north/ojunit.git Tools/ojunit" (after rake submodule) -
> and that seems to have done the trick.
> We're not using git submodules anymore, because they were causing all > kinds of problems switching between branches. We're still looking into > a better solution.
> In the meantime, you can just check out ojunit in Tools/ojunit. If you > run rake install after that, it should install it with the other > tools.
I think the problem is that ojunit is still in the Rakefile - so building anything just fails without an explanation when ojunit is not present. My Rake-Fu is not really up to par, so I can't provide a patch, but rake should either just ignore ojunit if it's not present, present a nice error message explaining what to do or just check it out with git (however the best practice is right now).
To repeat: What was really irritating me was that I couldn't build cappuccino and neither the error message, nor the build file, nor the wiki or the mailing list had any clue on what the recomended way to go forward was.
>> We're not using git submodules anymore, because they were causing all
>> kinds of problems switching between branches. We're still looking
>> into
>> a better solution.
>> In the meantime, you can just check out ojunit in Tools/ojunit. If
>> you
>> run rake install after that, it should install it with the other
>> tools.
> I think the problem is that ojunit is still in the Rakefile - so
> building anything just fails without an explanation when ojunit is not
> present. My Rake-Fu is not really up to par, so I can't provide a
> patch, but rake should either just ignore ojunit if it's not present,
> present a nice error message explaining what to do or just check it
> out with git (however the best practice is right now).
> To repeat: What was really irritating me was that I couldn't build
> cappuccino and neither the error message, nor the build file, nor the
> wiki or the mailing list had any clue on what the recomended way to go
> forward was.
That would be a very short term solution - I would much prefer it to be built if available, and also be available as a dependency if rake tests is run.
That's what Tom is saying, it does build, but only if available. If
not, you just get a warning message. We could turn off the warning,
but I don't think that would make any tangible difference. Perhaps a
more clear message "You do not have ojunit installed. Skipping"
> That would be a very short term solution - I would much prefer it to
> be built if available, and also be available as a dependency if rake
> tests is run.
> That's what Tom is saying, it does build, but only if available. If > not, you just get a warning message. We could turn off the warning, > but I don't think that would make any tangible difference. Perhaps a > more clear message "You do not have ojunit installed. Skipping"
Now I get it. We always thought that rake died - but instead its actually the last output and the build went through ok.
You should really do something about the error message - I'm sure more people who are not used to rake will trip over this.
|
