Since I was positive I hadn't made a dumb mistake, I looked back over it... and of course had made a dumb mistake. :) I assumed project was null, but it was the Task I was trying to get from project: should've been "java", not "Java". Thanks anyway though.
On different note, I think the perforce tasks are special as well: but that's probably because they're going to help me a lot with converting Makefiles (thanks). -Brian -----Original Message----- From: Les Hughes To: '[EMAIL PROTECTED]' Sent: 1/18/01 6:13 AM Subject: RE: why does P4Base work? Brian, As Stefan says it's difficult without any code. But P4Base doesn't do anything special at all (well *I* think it's special but that's another story ;-), project is inherited from Task. But post an example and we'll have a look. Les > -----Original Message----- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: 18 January 2001 08:09 > To: [EMAIL PROTECTED] > Subject: Re: why does P4Base work? > > > Brian Deitte <[EMAIL PROTECTED]> wrote: > > > While I can think of a way around this, I'm more wondering why > > project isn't getting defined in JRunBase, but does in P4Base. > > Task's setProject method will be called right after the constructor > for each and every task. > > As you are not showing us any relevant source it's kind of difficult > to say why you code doesn't work. > > Stefan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
