Not sure. Give it a try and report back.

Wayne

On 5/17/06, Piéroni Raphaël <[EMAIL PROTECTED]> wrote:
Hi Wayne,

I already know there is no reportManagement, what i'd like to know is
" is the pluginManagement part of the pom also affect the reports for
configuration and version purpose ."

;)

Raphaël

2006/5/17, Wayne Fay <[EMAIL PROTECTED]>:
>
> No, there is no reportingManagement node in 2.0. If you check Jira,
> this is on the list for 2.1.
>
> Wayne
>
> On 5/17/06, Piéroni Raphaël <[EMAIL PROTECTED]> wrote:
> > Hello,
> >
> > Do the pluginManagement also ensure the versions and configurations of
> > reports ?
> >
> > Raphaël
> >
> > 2006/5/17, Tim Kettler <[EMAIL PROTECTED]>:
> > >
> > > You can specify a default configuration for your plugins that the
> plugin
> > > definitions in
> > > child poms then pick up. This includes but is not limited to the
> version
> > > element. You can
> > > use all elements available in a 'normal' plugin definition.
> > >
> > > -Tim
> > >
> > > Wayne Fay schrieb:
> > > > As far as I know, <pluginManagement> is essentially identical in
> > > > purpose to <dependencyManagement> with no additional functionality.
> > > >
> > > > It specifies the plugin version to use when building the project.
> > > >
> > > > /pom.xml
> > > > <pluginManagement>
> > > > <plugins>
> > > >      <plugin>
> > > >        <groupId>org.codehaus.mojo</groupId>
> > > >        <artifactId>jspc-maven-plugin</artifactId>
> > > >        <version>1.4.1</version>
> > > >      </plugin>
> > > > </plugins>
> > > > </pluginManagement>
> > > >
> > > > /subA/pom.xml
> > > > <build>
> > > > <plugins>
> > > >      <plugin>
> > > >        <groupId>org.codehaus.mojo</groupId>
> > > >        <artifactId>jspc-maven-plugin</artifactId>
> > > >      </plugin>
> > > > </plugins>
> > > > </build>
> > > >
> > > > Basically, this node simply guarantees that all of your modules will
> > > > use the same plugin versions during the build phase.
> > > >
> > > > Wayne
> > > >
> > > > On 5/16/06, David Smiley <[EMAIL PROTECTED]> wrote:
> > > >> Is there documentation anywhere on how the <pluginManagement>
> element
> > > is
> > > >> utilized?  What differentiates it from <plugins>?
> > > >>
> > > >> ~ David Smiley
> > > >>
> > > >>
> > > >>
> ---------------------------------------------------------------------
> > > >> 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]
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to