Thanks for the 'heads up'.

I am going to start testing a new jsptagrefdoclet.jar this week.  If this 
doesn't solve the warning, it may be something to do with JDK5.  I have seen 
this warning pop up intermittently since moving to JDK5, and the javadoc devs 
at Sun are already aware of it.

-----Original Message-----
From: Eddie O'Neil 
Sent: Tuesday, January 11, 2005 10:07 AM
To: Beehive Developers
Subject: Re: Problem building taglib documentation


Greg--

   Looks like this is happening because we've switched the NetUI TLDs 
over to the JSP 2.0 taglib xsd.

   Seems like we may need to re-generate the jsptagrefdoclet.jar in 
order to get this running again.  Steve, can you take a look at this?

Eddie



McCarty, Greg wrote:
> I searched to dev mailing list and found nothing about this so I thought
> I'd pass it along.
> 
>  
> 
> I did an 'ant docs' command.  During the run, I noticed the following
> error from the generate-taglib-ref target in netui/ant/javadoc.xml:
> 
>  
> 
>     .
> 
>     .
> 
>   [javadoc] Constructing Javadoc information...
> 
>   [javadoc] javadoc: warning - Multiple sources of package comments
> found for 
> 
>      package "org.apache"
> 
>   [javadoc] javadoc: warning - Multiple sources of package comments
> found for 
> 
>      package "org"
> 
>   [javadoc] javadoc: error - Exception while parsing into XML the files
> at 
> 
>    c:\development\e-beehive\netui\build\docs\temp\tld: error: The
> document is not a 
> 
>    [EMAIL PROTECTED]://apache.org/beehive/netui/tools/doclet/schema: document
> element 
> 
>    namespace mismatch expected
> "http://apache.org/beehive/netui/tools/doclet/schema"; got "
> 
>    http://java.sun.com/xml/ns/j2ee";
> 
>   [javadoc] 1 error
> 
>   [javadoc] 2 warnings
> 
>  
> 
> I'd love to help fix it (since I want the latest taglib docs), but I
> don't understand the process well enough to figure out where the problem
> is.
> 
>  
> 
> Greg McCarty
> 
> Senior Technical Advisor / ManTech IST
> 
> ph:  410-480-9000 x2804 or 703-674-2804    fx: 410-480-0916
> 
>  
> 
> 

Reply via email to