Hi Brett, (Sorry for the delayed response)
Putting the assembly report in project info reports is the logical way. To do this change, we need to change the visibility of some methods/attributes in the AssemblyMojo and AbstractUnpackingMojo classes (depending the package choose) Also, projectinfos plugins needs to have new deps. I ll try to do this shift ASAP, if, of course, everybody is ok. WDYT? Thanks. Cheers, Vincent 2005/10/23, Brett Porter <[EMAIL PROTECTED]>: > Vincent Massol wrote: > > > > What does it do? Same as the download report in the m1 xdoc plugin? > > That's my understanding. > > > > > It certainly doesn't go into the assembly plugin IMO. However it could > > possibly go in the release plugin or in the changes report or in the info > > plugin or ... > > I agree that it shouldn't be in assembly (nor release). I'd prefer to > keep functional plugins separate from report plugins within reason (due > to it requiring additional deps to be downloaded). > > For me, the project info report is the most natural home. IIRC there was > an issue with obtaining the correct location of the download though. > > - Brett > > --------------------------------------------------------------------- > 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]
