Yeah Wayne. Its not like my env is really that atypical. The only issue is I'm using 1.6.0_02 as my JDK and hence my javadoc. I believe I am using 2.3but let me make sure that's explicit. I'm wondering if its my POM organization of the project but I've had zero issues with plugins (minus native2ascii which has a nasty bug with respect to tools.jar - relies on the Java vendor string to be Sun or something like that to pick it up which is not right for all platforms).
This is very weird and unexpected. The good news is mvn site does indeed work so this SEEMS to me a mvn/plugin bug (based on that datapoint). -aps On 8/22/07, Wayne Fay <[EMAIL PROTECTED]> wrote: > > I'm not really sure if this was broken in 2.0.6 or what exactly you're > running into. I do have 2.0.6 here and just tried, and javadoc:javadoc > ran just fine. That was with jdk 1.5.0_06 and javadoc plugin 2.2. > > Of course, my environment is probably rather different from yours, so > the fact that it worked here and not there is not really worth much. > Check your jdk version, your m-javadoc-p version, etc. > > Also, try: > mvn org.apache.maven.plugins:maven-javadoc-plugin:2.2:javadoc > and > mvn org.apache.maven.plugins:maven-javadoc-plugin:2.3:javadoc > > Here are the other valid versions, I'd assume you've simply got a buggy > m-j-p: > > http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-javadoc-plugin/ > > Wayne > > On 8/22/07, Alexander Sack <[EMAIL PROTECTED]> wrote: > > I'm looking at mod1/target/etc. > > > > outputDirectory is set to c:\workspace\<projectname>\target\apidocs but > none > > is generated. > > > > This seems like a real bug. Again mvn site works but mvn > javadoc:javadoc > > does not. Do I have to bind something to one of the build phases? Also > I > > couldn't get reportSets to work either (DING...as I was writing this I > > realized my MAVEN_HOME is set to maven-2.0.6 not 2.0.7). > > > > Was this broke in 2.0.6? > > > > Sorry Wayne, I feel really stupid since I'm using Maven left and right > these > > days with little issue and this seems dumb to me... > > > > -aps > > > > On 8/22/07, Wayne Fay <[EMAIL PROTECTED]> wrote: > > > > > > Not sure why its not working for you. > > > > > > Try "mvn -X javadoc:javadoc" and see what happens. You might to do > > > "mvn clean" first to clean up target. > > > > > > Also, how are you sure that "nothing is generated"? Where did you look > > > for output? > > > > > > Wayne > > > > > > On 8/22/07, Alexander Sack <[EMAIL PROTECTED]> wrote: > > > > Weird I tried before I SWEAR and it didn't work. Now it generates > the > > > > javadoc. Thanks Wayne. Alright, so why doens't javadoc:javadoc > > > work? I > > > > really only want to generate that report for my project? > > > > > > > > -aps > > > > > > > > On 8/22/07, Wayne Fay < [EMAIL PROTECTED]> wrote: > > > > > > > > > > Try mvn site. > > > > > > > > > > Wayne > > > > > > > > > > On 8/22/07, Alexander Sack <[EMAIL PROTECTED] > wrote: > > > > > > I'm trying to generate javadoc using maven instead of ant and > > > nothing > > > > > seems > > > > > > to be working. I have a project like so: > > > > > > > > > > > > Project > > > > > > pom > > > > > > Mod 1 > > > > > > pom-mod1.xml > > > > > > Mod 2 > > > > > > pom-mod2.xml > > > > > > etc. > > > > > > > > > > > > I just want to generate javadoc for Mod1. Now I tried adding > under > > > a > > > > > > <reporting> section the javadoc plugin defintion (artifact, > group > > > ,etc.) > > > > > to > > > > > > the global pom and the individual pom with no success. > > > > > > > > > > > > When I run: > > > > > > > > > > > > mvn javadoc:javadoc > > > > > > > > > > > > It downloads the plugin, kickstarts velocity and nothing is > > > > > generated. What > > > > > > else do I need to do to get this to work? Consulting the > Javadoc > > > pages > > > > > > didn't really give me any obvious answers. Its claims there are > no > > > > > goals > > > > > > for each module and claims it was skipping. This must be > something > > > very > > > > > > basic but I'm clueless rightnow. > > > > > > > > > > > > Any help would come much appreciated, > > > > > > > > > > > > -aps > > > > > > > > > > > > -- > > > > > > "What lies behind us and what lies in front of us is of little > > > concern > > > > > to > > > > > > what lies within us." -Ralph Waldo Emerson > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > -- > > > > "What lies behind us and what lies in front of us is of little > concern > > > to > > > > what lies within us." -Ralph Waldo Emerson > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > "What lies behind us and what lies in front of us is of little concern > to > > what lies within us." -Ralph Waldo Emerson > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- "What lies behind us and what lies in front of us is of little concern to what lies within us." -Ralph Waldo Emerson
