Discussion:
RMIC Unable to Verify Classes
Aaron Davies
2006-04-27 21:59:51 UTC
Permalink
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
<http://marc.theaimsgroup.com/?l=ant-user&m=97069041417063&w=2>,
except that adding . to CLASSPATH (the shell path defined when I call
ant) doesn't help. I'm running ant under Win2k and have tried this
from both CMD and ZSH under cygwin. Any ideas?

--
Aaron Davies
***@gmail.com
Alexey N. Solofnenko
2006-04-27 22:28:01 UTC
Permalink
<rmic>'s classpath should be the whole classpath from <javac> and
<javac> output directory.

- Alexey.
Post by 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
<http://marc.theaimsgroup.com/?l=ant-user&m=97069041417063&w=2>,
except that adding . to CLASSPATH (the shell path defined when I call
ant) doesn't help. I'm running ant under Win2k and have tried this
from both CMD and ZSH under cygwin. Any ideas?
--
Aaron Davies
---------------------------------------------------------------------
Aaron Davies
2006-05-02 18:34:37 UTC
Permalink
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?
Post by Alexey N. Solofnenko
<rmic>'s classpath should be the whole classpath from <javac> and
<javac> output directory.
- Alexey.
Post by 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
<http://marc.theaimsgroup.com/?l=ant-user&m=97069041417063&w=2>,
except that adding . to CLASSPATH (the shell path defined when I call
ant) doesn't help. I'm running ant under Win2k and have tried this
from both CMD and ZSH under cygwin. Any ideas?
--
Aaron Davies
---------------------------------------------------------------------
---------------------------------------------------------------------
--
Aaron Davies
***@gmail.com
Alexey N. Solofnenko
2006-05-02 18:43:35 UTC
Permalink
This is what I do, and it works fine with ANT nightly (but 1.6.5 should
be fine too):

<rmic classpath="${javac-classpath}" debug="true"
includes="${rmic-sources}" base="${classes-output}" stubversion="1.2" />

${rmic-sources} - a list of all .class files that need stubs.

- Alexey.
Post by 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?
Post by Alexey N. Solofnenko
<rmic>'s classpath should be the whole classpath from <javac> and
<javac> output directory.
- Alexey.
Post by 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
<http://marc.theaimsgroup.com/?l=ant-user&m=97069041417063&w=2>,
except that adding . to CLASSPATH (the shell path defined when I call
ant) doesn't help. I'm running ant under Win2k and have tried this
from both CMD and ZSH under cygwin. Any ideas?
--
Aaron Davies
---------------------------------------------------------------------
---------------------------------------------------------------------
--
Aaron Davies
---------------------------------------------------------------------
Aaron Davies
2006-05-02 20:06:56 UTC
Permalink
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*?
Post by Alexey N. Solofnenko
This is what I do, and it works fine with ANT nightly (but 1.6.5 should
<rmic classpath="${javac-classpath}" debug="true"
includes="${rmic-sources}" base="${classes-output}" stubversion="1.2" />
${rmic-sources} - a list of all .class files that need stubs.
- Alexey.
Post by 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?
Post by Alexey N. Solofnenko
<rmic>'s classpath should be the whole classpath from <javac> and
<javac> output directory.
- Alexey.
Post by 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
<http://marc.theaimsgroup.com/?l=ant-user&m=97069041417063&w=2>,
except that adding . to CLASSPATH (the shell path defined when I call
ant) doesn't help. I'm running ant under Win2k and have tried this
from both CMD and ZSH under cygwin. Any ideas?
--
Aaron Davies
---------------------------------------------------------------------
---------------------------------------------------------------------
--
Aaron Davies
---------------------------------------------------------------------
---------------------------------------------------------------------
--
Aaron Davies
***@gmail.com
Alexey N. Solofnenko
2006-05-02 20:13:33 UTC
Permalink
Hmm... How did they build it before? Maybe there is a list somewhere in
IDE project files.

- Alexey.
Post by 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*?
Post by Alexey N. Solofnenko
This is what I do, and it works fine with ANT nightly (but 1.6.5 should
<rmic classpath="${javac-classpath}" debug="true"
includes="${rmic-sources}" base="${classes-output}" stubversion="1.2" />
${rmic-sources} - a list of all .class files that need stubs.
- Alexey.
Post by 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?
Post by Alexey N. Solofnenko
<rmic>'s classpath should be the whole classpath from <javac> and
<javac> output directory.
- Alexey.
Post by 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
Post by Aaron Davies
Post by Alexey N. Solofnenko
Post by Aaron Davies
exactly like the one described in
<http://marc.theaimsgroup.com/?l=ant-user&m=97069041417063&w=2>,
except that adding . to CLASSPATH (the shell path defined when I
call
Post by Aaron Davies
Post by Alexey N. Solofnenko
Post by Aaron Davies
ant) doesn't help. I'm running ant under Win2k and have tried this
from both CMD and ZSH under cygwin. Any ideas?
--
Aaron Davies
---------------------------------------------------------------------
Post by Aaron Davies
Post by Alexey N. Solofnenko
---------------------------------------------------------------------
--
Aaron Davies
---------------------------------------------------------------------
---------------------------------------------------------------------
--
Aaron Davies
---------------------------------------------------------------------
Aaron Davies
2006-05-02 20:58:42 UTC
Permalink
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.
Post by Alexey N. Solofnenko
Hmm... How did they build it before? Maybe there is a list somewhere in
IDE project files.
- Alexey.
Post by 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*?
Post by Alexey N. Solofnenko
This is what I do, and it works fine with ANT nightly (but 1.6.5 should
<rmic classpath="${javac-classpath}" debug="true"
includes="${rmic-sources}" base="${classes-output}" stubversion="1.2" />
${rmic-sources} - a list of all .class files that need stubs.
- Alexey.
Post by 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?
Post by Alexey N. Solofnenko
<rmic>'s classpath should be the whole classpath from <javac> and
<javac> output directory.
- Alexey.
Post by 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
Post by Aaron Davies
Post by Alexey N. Solofnenko
Post by Aaron Davies
exactly like the one described in
<http://marc.theaimsgroup.com/?l=ant-user&m=97069041417063&w=2>,
except that adding . to CLASSPATH (the shell path defined when I
call
Post by Aaron Davies
Post by Alexey N. Solofnenko
Post by Aaron Davies
ant) doesn't help. I'm running ant under Win2k and have tried this
from both CMD and ZSH under cygwin. Any ideas?
--
Aaron Davies
---------------------------------------------------------------------
Post by Aaron Davies
Post by Alexey N. Solofnenko
---------------------------------------------------------------------
--
Aaron Davies
---------------------------------------------------------------------
---------------------------------------------------------------------
--
Aaron Davies
---------------------------------------------------------------------
---------------------------------------------------------------------
--
Aaron Davies
***@gmail.com
Aaron Davies
2006-05-02 21:55:55 UTC
Permalink
I suppose that's one solution, but wouldn't fixing the problem be a better one?
Post by 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.
we could downgrade it. I have to ignore it on a regular basis too.
---------------------------------------------------------------------
--
Aaron Davies
***@gmail.com
Steve Loughran
2006-05-02 21:18:16 UTC
Permalink
Post by 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.
we could downgrade it. I have to ignore it on a regular basis too.
Loading...