On 14/06/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> On Mon, 2010-06-14 at 16:28 +0100, sebb wrote:
>  > On 14/06/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
>  > > On Mon, 2010-06-14 at 11:45 +0000, s...@apache.org wrote:
>  > >  > Author: sebb
>  > >  > Date: Mon Jun 14 11:45:02 2010
>  > >  > New Revision: 954415
>  > >  >
>  > >  > URL: http://svn.apache.org/viewvc?rev=954415&view=rev
>  > >  > Log:
>  > >  > Sort the pluginManagement section
>  > >  >
>  > >  > Modified:
>  > >  >     httpcomponents/project/pom.xml
>  > >  >
>  > >  > Modified: httpcomponents/project/pom.xml
>  > >  > URL: 
> http://svn.apache.org/viewvc/httpcomponents/project/pom.xml?rev=954415&r1=954414&r2=954415&view=diff
>  > >  > 
> ==============================================================================
>  > >  > --- httpcomponents/project/pom.xml (original)
>  > >  > +++ httpcomponents/project/pom.xml Mon Jun 14 11:45:02 2010
>  > >  > @@ -272,6 +272,32 @@
>  > >  >      </plugins>
>  > >  >      <pluginManagement>
>  > >  >        <plugins>
>  > >  > +        <!-- org.apache.maven.plugins, alpha order by artifact id -->
>  > >  > +        <plugin>
>  > >  > +          <groupId>org.apache.maven.plugins</groupId>
>  > >  > +          <artifactId>maven-assembly-plugin</artifactId>
>  > >  > +          <version>2.2-beta-5</version>
>  > >  > +        </plugin>
>  > >  > +        <plugin>
>  > >  > +          <groupId>org.apache.maven.plugins</groupId>
>  > >  > +          <artifactId>maven-antrun-plugin</artifactId>
>  > >  > +          <version>1.4</version>
>  > >  > +        </plugin>
>  > >  > +        <plugin>
>  > >  > +          <groupId>org.apache.maven.plugins</groupId>
>  > >  > +          <artifactId>maven-clean-plugin</artifactId>
>  > >  > +          <version>2.4.1</version>
>  > >  > +        </plugin>
>  > >  > +        <plugin>
>  > >  > +          <groupId>org.apache.maven.plugins</groupId>
>  > >  > +          <artifactId>maven-compiler-plugin</artifactId>
>  > >  > +          <version>2.3.1</version>
>  > >  > +        </plugin>
>  > >  > +        <plugin>
>  > >  > +          <groupId>org.apache.maven.plugins</groupId>
>  > >  > +          <artifactId>maven-deploy-plugin</artifactId>
>  > >  > +          <version>2.5</version>
>  > >  > +        </plugin>
>  > >  >          <plugin>
>  > >  >            <groupId>org.apache.maven.plugins</groupId>
>  > >  >            <artifactId>maven-gpg-plugin</artifactId>
>  > >
>  > >  Sebastian
>  > >
>  > >  While it is certainly a good idea to have versions of non-core Maven
>  > >  plugins explicitly set in POM, I am not sure it is the case for core
>  > >  plugins unless we also somehow enforce a very _specific_ Maven version
>  > >  that matches those core plugin version.
>  > >
>  > >  Maven releases are tested against specific versions of core plugins and
>  > >  mixing things up may be as ugly as letting Maven always pick up the
>  > >  newest version.
>  >
>  > OK, but how does one know what is a core plugin and what is not?
>  >
>
>
> Please see
>
>  http://maven.apache.org/plugins/index.html
>

Thanks.

So in theory one should omit all plugin version specifications for
plugins that are in that list?

Sounds reasonable.

Unfortunately it just does not work; AFAICT the site plugin that is
provided with Maven 2.2.1 is 2.0-beta-7 whereas
maven-project-info-reports-plugin needs 2.1

AFAICT the only way to get the mpirp plugin to work is to specify the
site plugin version, overriding the one provided by Maven 2.1.0.

See also

http://maven.apache.org/guides/mini/guide-configuring-plugins.html

which says:

"Important Note: It is recommended to always defined each version of
the plugins used by the build to guarantee the build reproducibility.
A good practice is to specify them in the
<build><pluginManagement/></build>  elements for each build plugins
(generally, you will define a <pluginManagement/> element in a parent
POM). For reporting plugins, you should specify each version in the
<reporting><plugins/></reporting>  elements (and surely in the
<build><pluginManagement/></build>  elements too)."

This does not specifically exclude "core" plugins.

>  Oleg
>
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
>  For additional commands, e-mail: dev-h...@hc.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org

Reply via email to