Hi Paul, 2008/7/31 Paul Benedict <[EMAIL PROTECTED]>: > Would it behoove the Javadoc plugin developers to test for the CLASSPATH > variable? Issue a warning instead of blowing up? I know it's not a plugin > problem, per se, but it obviously leads some people to believe it is.
The last entry in the FAQ [1] already explains that: if your CLASSPATH env var has incorrect env variable, the javadoc will crash on windows. It is a known Sun issue (6219854). IMHO it is enough from an user point of view (we have also jira so the user could found it easily). I don't think that Javadoc Plugin needs to display warning for a given Sun issue (even less to make a workaround). Cheers, Vincent [1] https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-javadoc-plugin/src/site/fml/faq.fml > Paul > > On Thu, Jul 31, 2008 at 12:43 PM, Stephen Connolly < > [EMAIL PROTECTED]> wrote: > >> check if the CLASSPATH environment variable is set. it blows up javadoc if >> it is >> >> Sent from my iPod >> >> On 31 Jul 2008, at 18:06, John Casey <[EMAIL PROTECTED]> wrote: >> >> Hi Vincent, >>> >>> I can't even get the javadoc plugin to run on my machine under Maven >>> 2.0.9, not with JDK 1.4 or JDK 1.6...so I'm afraid I'm of little use on >>> these issues. I can give you some time to distill a failing test case that I >>> can pursue, if you like... >>> >>> Let me know. Maybe I'll cut the RC4 and we can test vs. that. >>> >>> -john >>> >>> > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
