You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@maven.apache.org by David Smiley <ds...@mitre.org> on 2006/05/16 21:12:14 UTC

pluginManagement, purpose?

Is there documentation anywhere on how the <pluginManagement> element is 
utilized?  What differentiates it from <plugins>?

~ David Smiley


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: pluginManagement, purpose?

Posted by Wayne Fay <wa...@gmail.com>.

Not sure. Give it a try and report back.

Wayne

On 5/17/06, Piéroni Raphaël <ra...@gmail.com> 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 <wa...@gmail.com>:
> >
> > 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 <ra...@gmail.com> wrote:
> > > Hello,
> > >
> > > Do the pluginManagement also ensure the versions and configurations of
> > > reports ?
> > >
> > > Raphaël
> > >
> > > 2006/5/17, Tim Kettler <ti...@udo.edu>:
> > > >
> > > > 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 <ds...@mitre.org> wrote:
> > > > >> Is there documentation anywhere on how the <pluginManagement>
> > element
> > > > is
> > > > >> utilized?  What differentiates it from <plugins>?
> > > > >>
> > > > >> ~ David Smiley
> > > > >>
> > > > >>
> > > > >>
> > ---------------------------------------------------------------------
> > > > >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > >> For additional commands, e-mail: users-help@maven.apache.org
> > > > >>
> > > > >>
> > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: pluginManagement, purpose?

Posted by Piéroni Raphaël <ra...@gmail.com>.

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 <wa...@gmail.com>:
>
> 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 <ra...@gmail.com> wrote:
> > Hello,
> >
> > Do the pluginManagement also ensure the versions and configurations of
> > reports ?
> >
> > Raphaël
> >
> > 2006/5/17, Tim Kettler <ti...@udo.edu>:
> > >
> > > 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 <ds...@mitre.org> wrote:
> > > >> Is there documentation anywhere on how the <pluginManagement>
> element
> > > is
> > > >> utilized?  What differentiates it from <plugins>?
> > > >>
> > > >> ~ David Smiley
> > > >>
> > > >>
> > > >>
> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > >> For additional commands, e-mail: users-help@maven.apache.org
> > > >>
> > > >>
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

Re: pluginManagement, purpose?

Posted by Wayne Fay <wa...@gmail.com>.

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 <ra...@gmail.com> wrote:
> Hello,
>
> Do the pluginManagement also ensure the versions and configurations of
> reports ?
>
> Raphaël
>
> 2006/5/17, Tim Kettler <ti...@udo.edu>:
> >
> > 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 <ds...@mitre.org> wrote:
> > >> Is there documentation anywhere on how the <pluginManagement> element
> > is
> > >> utilized?  What differentiates it from <plugins>?
> > >>
> > >> ~ David Smiley
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > >> For additional commands, e-mail: users-help@maven.apache.org
> > >>
> > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: pluginManagement, purpose?

Posted by Piéroni Raphaël <ra...@gmail.com>.

Hello,

Do the pluginManagement also ensure the versions and configurations of
reports ?

Raphaël

2006/5/17, Tim Kettler <ti...@udo.edu>:
>
> 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 <ds...@mitre.org> wrote:
> >> Is there documentation anywhere on how the <pluginManagement> element
> is
> >> utilized?  What differentiates it from <plugins>?
> >>
> >> ~ David Smiley
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

Re: pluginManagement, purpose?

Posted by Tim Kettler <ti...@udo.edu>.

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 <ds...@mitre.org> wrote:
>> Is there documentation anywhere on how the <pluginManagement> element is
>> utilized?  What differentiates it from <plugins>?
>>
>> ~ David Smiley
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: pluginManagement, purpose?

Posted by Wayne Fay <wa...@gmail.com>.

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 <ds...@mitre.org> wrote:
> Is there documentation anywhere on how the <pluginManagement> element is
> utilized?  What differentiates it from <plugins>?
>
> ~ David Smiley
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org