By the way, I found in the FAQs for the javadoc plugin the information
on how to deploy the separate Javadoc JAR file, but it turned out that
doesn't help. That's mostly Eclipse's fault (for some reason you can't
use a path variable to indicate where to find Javadocs, only source?
WTF, Eclipse team?) But anyway, I would still really like to package the
Javadoc into the same JAR as the classes, if that's possible.

~DVA


-----Original Message-----
From: Allen, Daniel 
Sent: Friday, March 14, 2008 4:10 PM
To: Maven Users List
Subject: [m2] Javadoc packaged with deployed JAR

Hi, all.

I've created a small package of utilities that I'm deploying to the
company's local repository for reuse. However, a problem with that reuse
is that when we do our programming in Eclipse, the mouse-over javadoc
display doesn't work, so it's hard to tell what functionality I'm
actually providing. I know that I can create the javadocs as a Maven
report with the javadoc plugin, or generate the documents on their own
with "mvn javadoc:jar", but is there a way to include the javadoc
results in the same JAR file that's produced and deployed by "mvn
deploy"? I think that way, Eclipse would see them and helpfully display
arguments, comments, etc. one I add my package to the build path.
Failing that, how would I go about deploying the JAR that "mvn
javadoc:jar" creates?

Thanks,
~Dan Allen

-- 
This message may contain confidential, proprietary, or legally privileged 
information. No confidentiality or privilege is waived by any transmission to 
an unintended recipient. If you are not an intended recipient, please notify 
the sender and delete this message immediately. Any views expressed in this 
message are those of the sender, not those of any entity within the KBC 
Financial Products group of companies (together referred to as "KBC FP"). 

This message does not create any obligation, contractual or otherwise, on the 
part of KBC FP. It is not an offer (or solicitation of an offer) of, or a 
recommendation to buy or sell, any financial product. Any prices or other 
values included in this message are indicative only, and do not necessarily 
represent current market prices, prices at which KBC FP would enter into a 
transaction, or prices at which similar transactions may be carried on KBC FP's 
own books. The information contained in this message is provided "as is", 
without representations or warranties, express or implied, of any kind. Past 
performance is not indicative of future returns.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to