Re: RMIC Unable to Verify Classes

2006-05-02 Thread Aaron Davies
I suppose that's one solution, but wouldn't fixing the problem be a better one? On 5/2/06, Steve Loughran <[EMAIL PROTECTED]> wrote: Aaron Davies wrote: > AFAICT it's always been like this. This is a warning, not a fatal > error, but it's an annoying one that clutters up the build logs. we coul

Re: RMIC Unable to Verify Classes

2006-05-02 Thread Steve Loughran
Aaron Davies wrote: AFAICT it's always been like this. This is a warning, not a fatal error, but it's an annoying one that clutters up the build logs. we could downgrade it. I have to ignore it on a regular basis too. - To uns

Re: RMIC Unable to Verify Classes

2006-05-02 Thread Aaron Davies
AFAICT it's always been like this. This is a warning, not a fatal error, but it's an annoying one that clutters up the build logs. On 5/2/06, Alexey N. Solofnenko <[EMAIL PROTECTED]> wrote: Hmm... How did they build it before? Maybe there is a list somewhere in IDE project files. - Alexey. Aar

Re: RMIC Unable to Verify Classes

2006-05-02 Thread Alexey N. Solofnenko
Hmm... How did they build it before? Maybe there is a list somewhere in IDE project files. - Alexey. Aaron Davies wrote: Well sure, if you know ahead of time what needs stubs it's going to work! :-) I'm trying to fix the build file for a large team project where I have no idea what's implement

Re: RMIC Unable to Verify Classes

2006-05-02 Thread Aaron Davies
Well sure, if you know ahead of time what needs stubs it's going to work! :-) I'm trying to fix the build file for a large team project where I have no idea what's implementing Remote and what isn't. Isn't this what the verify attribute is *for*? On 5/2/06, Alexey N. Solofnenko <[EMAIL PROTECTED]

Re: RMIC Unable to Verify Classes

2006-05-02 Thread Alexey N. Solofnenko
This is what I do, and it works fine with ANT nightly (but 1.6.5 should be fine too): includes="${rmic-sources}" base="${classes-output}" stubversion="1.2" /> ${rmic-sources} - a list of all .class files that need stubs. - Alexey. Aaron Davies wrote: I'm not having any luck. I recall from t

Re: RMIC Unable to Verify Classes

2006-05-02 Thread Aaron Davies
I'm not having any luck. I recall from the message referenced below that at the time, the verify stage read CLASSPATH, not the classpath attribute of the rmic task. Is that still true? On 4/27/06, Alexey N. Solofnenko <[EMAIL PROTECTED]> wrote: 's classpath should be the whole classpath from an

Re: RMIC Unable to Verify Classes

2006-04-27 Thread Alexey N. Solofnenko
's classpath should be the whole classpath from and output directory. - Alexey. Aaron Davies wrote: Hi, I'm having trouble getting the rmic messages about "Unable to verify class It is not defined." to go away. My problem is almost exactly like the one described in

RMIC Unable to Verify Classes

2006-04-27 Thread Aaron Davies
Hi, I'm having trouble getting the rmic messages about "Unable to verify class It is not defined." to go away. My problem is almost exactly like the one described in , except that adding . to CLASSPATH (the shell path defined when