Is there a particular reason why pluginManagement does not work for reporting plugins? I would like to manage reporting plugins just as much as any other plugin.
I am curious if there is a design reason, or if this was a simply an oversight that could possibly be changed in the future? thanks. Jason ________________________________________ From: David C. Hicks [[email protected]] Sent: Saturday, July 25, 2009 12:05 PM To: Maven Users List Subject: Re: [ANN] Maven Project Info Reports Plugin 2.1.2 Released Dennis Lundberg wrote: > David C. Hicks wrote: > >> Maybe I misunderstand the meaning of some of this message. MPIR-160 is >> listed in the release notes. Does this mean it should be fixed in this >> release? >> I bumped the version of this plugin in my current project. It still >> seems to be fetching artifacts remotely. >> > > Yes, it's supposed to be fixed. Are you sure that you are using the new > version? Remember that pluginManagement doesn't work for reporting > plugins, so you need to specify the version number in the reporting > section of your POM. > Ah! That's probably it. I was not aware that reporting plugins didn't obey the plugin management rules. Thanks for the tip! --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
