Rickard �berg <[EMAIL PROTECTED]> writes
>Hi!
>
>Justin Forder wrote:
>> Same thing happened to me today. It isn't because of any problems with
>> CVS - it goes away if you do a "build clean" followed by "build".
>
>Ok, I just did a clean checkout of jBoss from CVS and tried to build it.
>No problems whatsoever....
Of course - because a "clean checkout" (something you should never have
to do, if CVS is working properly) comes with nothing in the build
directories. It leaves you in the state you would get to by doing a
normal CVS update followed by "build clean".
If you always start clean, you will never test whether or not
dependencies are being handled properly in your makefiles (or build.xml,
in this case).
But getting the dependencies right is hard (unless you have a tool to do
it for you - Jikes is supposed to be able to do it for makefiles), and
it doesn't take long to do a clean build.
What *does* take a long time (and is rather anti-social in terms of
server and backbone bandwidth use) is doing a complete checkout from
CVS. (Speaking as a user of a 33.6 modem, often seeing congestion on the
Net that prevents me getting all of that 3kbytes/sec.)
>
>I have no idea why you're getting problems and I don't. Are you using
>jCVS? I'm using WinCVS anyway..
I hope the above explains it. As I said, a clean build works.
I'm using WinCVS. It is clunky but it's heart is in the right place. I
found jCVS unintuitive.
I remain baffled by why Koen Debruyckere ran into a problem, if, as he
said later, he was using a completely fresh download.
--
Justin Forder
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
