On a side note, 2.0.7 didn't fix it.
Man all I got in my POM is this:
<reporting>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
</plugin>
</plugins>
</reporting>
And javadoc:javadoc does absolutely nothing. Basically it starts Velocity
successfully and just quits. Weirdness.
-aps
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
>
--
"What lies behind us and what lies in front of us is of little concern to
what lies within us." -Ralph Waldo Emerson
