Re: Why would maven look for a newer version of a plugin?

2010-11-12 Thread Frederic Camblor
is not used in section... it is only build section scoped. Provide a version in your reporting plugin, and it will solve your problem (for the moment, no version is provided for your reporting plugin, that's why maven is gathering last plugin version from your enterprise repository). Frédéric

Re: Why would maven look for a newer version of a plugin?

2010-11-12 Thread Sanjeeb Sahoo
No, that snippet is part of pluginManagement. The actual usage is inside , but there is no version specified at the point of use. Why should version be specified there if it is already present in pluginManagement? BTW, in case I didn't make it clear, I am looking at effective pom. Our project P

Re: Why would maven look for a newer version of a plugin?

2010-11-12 Thread Frederic Camblor
Hi, Is your snippet extracted from the or the pom section ? Check that your version is provided on both of these sections (even if you provided it in /project/build/pluginManagement) Frédéric On Fri, Nov 12, 2010 at 3:29 PM, Sanjeeb Sahoo wrote: > I would like someone to help us understand

Why would maven look for a newer version of a plugin?

2010-11-12 Thread Sanjeeb Sahoo
I would like someone to help us understand a behavior that we recently observed in our build system. In our project POM, we don't explicitly mention the versions for these plugins, as we expect the versions to be inherited from SuperPOM. When I look at the effective POM for the project, it show