Phil Steitz wrote: > On 12/4/05, Brett Porter <[EMAIL PROTECTED]> wrote: >> Dennis Lundberg wrote: >>> Brett said that this *should* work, so I decided to try it myself. I >>> received the same results as you did Phil, regarding maven --info, but I >>> think I understand what is going on now. I have posted a question about >>> this on the maven-users list to see if I can get some confirmation. >>> >> Sorry this went over my head earlier, but Dennis' analysis on the usres >> list is correct. Maven --info doesn't reflect the difference as it >> reports what's installed. Plugin dependencies are only used for the life >> of the project's build, not installed. >> >> So the dependency should work regardless of what maven --info says. Is >> that the case? > > Then the solution to add the necessary dependencies to commons-build > won't work and what we need to do is something like pluginUpdate > (bunch of explicit plugin installs from the command line). Correct?
No, I think it should work - unless I missed something. The problem is, I thought, that a lot of the projects don't extend commons-build? What happens when a project that extends commons-build has the plugin dependency? I know maven --info is "incorrect", but does running xdoc actually do what you expect? - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
