Hi Vincent, in Maven 2.0.x, it is not possible to add a dependency to a plugin in the reporting section. And if you put it in the pluginManagement section, this doesn't work either. (see bug MNG-1931)
So that's why I don't see a solution to that... :-( Cheers, Fabrice. On 9/19/07, Vincent Siveton <[EMAIL PROTECTED]> wrote: > > Hi Fabrice, > > PLXUTILS-34 is included in p-u:1.4.6, so try to add it as dependency > in the javadoc-plugin. > > Cheers, > > Vincent > > 2007/9/19, Fabrice Bellingard <[EMAIL PROTECTED]>: > > Hi guys, > > > > I've just updated some projects that now use Maven 2.0.7 along with the > > Javadoc plugin 2.3, and now my build fails because the UNIX platform > where > > the integrations happen doesn't have bash. > > The reason is the following: the Javadoc plugin creates a default > > Commandline object to run the javadoc process, but with the last > versions of > > Plexus Utils, the default constructor sets "/bin/bash" as the default > shell. > > For what I've found in the code of both the Javadoc plugin and Plexus > Utils, > > it seems to me that there is no way to specify another shell for UNIX > > systems. > > > > Do you have any idea of how I could handle that? The problem is that I > don't > > have root privileges on the UNIX server... :-( > > > > Thanks in advance for any anwser! > > > > Cheers, > > Fabrice. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
