as you reported, reportSets vs executions strategy has never been really 
defined.
m-javadoc-p did extensive documentation, with both forms: it's the first plugin 
I know that did show the dual forms
But now that everything is clearly documented, I'm convinced that we should 
promote reportSets
But that's my opinion: having other input would be helpful

Regards,

Hervé

Le mardi 23 août 2011, Benson Margulies a écrit :
> OK, I begin to see. report sets map to goals.
> 
> So, I wonder, why is the IT for the javadoc plugin written to do both
> instead of using a report set?
> 
> That would make my recent fixes less urgent. Let me go try this.
> 
> On Tue, Aug 23, 2011 at 4:34 PM, Hervé BOUTEMY <[email protected]> 
wrote:
> > from what I see, it should work
> > 
> > but if you look at the way it is actually done in Maven core [1] with
> > success [2], the aggregation feature is defined in reporting section
> > (with reportSets instead of execution)
> > 
> > Regards,
> > 
> > Hervé
> > 
> > [1]
> > http://svn.apache.org/viewvc/maven/maven-3/trunk/pom.xml?revision=1155273
> > &view=markup
> > 
> > [2] http://maven.apache.org/ref/3.0.4-SNAPSHOT/
> > 
> > Le mardi 23 août 2011, Benson Margulies a écrit :
> >> In spite of having run the most recent release, and implemented the
> >> aggregation feature, I'm seemingly unable to use it myself.
> >> 
> >> In build/plugins I have
> >> 
> >>               <plugin>
> >>                 <groupId>org.apache.maven.plugins</groupId>
> >>                 <artifactId>maven-jxr-plugin</artifactId>
> >>                 <version>2.3</version>
> >>               <executions>
> >>                 <execution>
> >>                   <id>aggregate</id>
> >>                  
> >> <goals><goal>aggregate</goal><goal>test-aggregate</goal></goals>
> >> <phase>site</phase>
> >>                 </execution>
> >>               </executions>
> >>             </plugin>
> >> 
> >> and then in reporting I have:
> >> 
> >> 
> >>           <plugin>
> >>             <groupId>org.apache.maven.plugins</groupId>
> >>             <artifactId>maven-jxr-plugin</artifactId>
> >>             <version>2.3</version>
> >>           </plugin>
> >> 
> >> 
> >> First, the report page fails to substitute for ${project.version}. I
> >> literally see that in the HTML.
> >> 
> >> More to the point, I get no output at all on the page.
> >> 
> >> ---------------------------------------------------------------------
> >> 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]
> 
> ---------------------------------------------------------------------
> 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