I decided to do it with antrun instead since I want a clean javadoc run without Velocity chatter and maven warning messages. Your POM entry below works for me with mvn 2.0.6. The aggregate config indicates you have a multi-module POM. I haven't tried the javadoc plugin in the package phase in that situation.

On 6/25/2007 10:21 AM, Lara Brian wrote:
Hi Paul,
I am also trying to run the javadoc in the package phase and it is not
generating the javadoc. Looks like you did it sucessfully. Can you tell me
what iam doing wrong? My POM is like this:


<build>
        <plugins>
                <plugin>
                        <groupId>org.apache.maven.plugins</groupId>
                        <artifactId>maven-javadoc-plugin</artifactId>
                        <configuration>
                                <aggregate>true</aggregate>
                        </configuration>
                        <executions>
                                <execution>
                                        <id>create-javadocs</id>
                                        <phase>package</phase>
                                        <goals>
                                                <goal>javadoc</goal>
                                        </goals>
                                </execution>
                        </executions>
                </plugin>
                <plugin>
                        <artifactId>maven-assembly-plugin</artifactId>
                        <configuration>
                                <outputDirectory>.</outputDirectory>
                                <appendAssemblyId>true</appendAssemblyId>
                                <descriptors>
                                        
<descriptor>cmp-client-javadoc.xml</descriptor>                                 
                                                    
</descriptors>
                        </configuration>
                        <executions>
                                <execution>
                                        <id>make-assembly</id>
                                        <phase>package</phase>
                                        <goals>
                                                <goal>attached</goal>
                                        </goals>
                                </execution>
                        </executions>
                </plugin>
        </plugins>
</build>

I need to run javadoc and then assemble the javadoc created uisng assembly
descriptor (cmp-client-javadoc.xml).

Thanks a lot,
Shankar.




Paul Copeland wrote:
I'm generating javadoc within a webapp context. I put the maven-javadoc-plugin:javadoc goal into the package phase rather than in the usual the generation <reporting> lifecycle. It is doing the right thing but I get this message -

[WARNING] Removing: javadoc from forked lifecycle, to prevent recursive invocation

Then I get a bunch of velocity messages (irrelevant for javadoc AFAIK)

Why do I get the message and can I get rid of velocity since this is a plain vanilla javadoc tool run?

TIA  - Paul Copeland, Jot Object Technologies http://www.jotobjects.com/


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





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

Reply via email to