ojunit with 0.7b

[Martin Häcker]

Hi there,

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.

Could somebody verify that this is the case?

Here's my .gitmodules file:
-- snip --
% cat .gitmodules
[submodule "Tools/ojunit"]
path = Tools/ojunit
url = git://github.com/280north/ojunit.git
-- snap --

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.

Regards,
Martin

[Ross Boucher]

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).

[Philippe Laval]

Well,

I did this : http://www.nice-panorama.com/Programmation/cappuccino/Tutorial-objj-and-ojunit.html

It is working for me.
Philippe

Le 20 avr. 09 à 16:31, Martin Häcker a écrit :

[Martin Häcker]

> I did this : http://www.nice-panorama.com/Programmation/cappuccino/Tutorial-objj-and-ojunit.html

Thanks for the link! Your manuals have helped me quite a bit since I
started fulltime on cappuccino again.

:)

I ended up going with a submodule, as I really want to track both
repositories.

Thanks a lot,
Martin

[Martin Häcker]

> 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.

Regards,
Martin

[Tom Robinson]

It should just be a warning. If it's actually failing its probably
because of something else. If you really want, take ojunit out of

subprojects = %w{bake capp nib2cib press ojunit}

in Tools/Rakefile.

[Martin Häcker]

> It should just be a warning. If it's actually failing its probably
> because of something else. If you really want, take ojunit out of
>
> subprojects = %w{bake capp nib2cib press ojunit}
>
> in Tools/Rakefile.

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.

Regards,
Martin

[Ross Boucher]

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"

[Martin Häcker]

> 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.

Regards,
Martin