Running 'mvn help:effective-pom' will show you the pom that will be used
by your project. It also includes stuff that if inherited from a parent
or the super-pom. It's a great way to find out your real configuration.
Dimitris Kapanidis wrote:
Wayne Fay wrote:
Actually, I lock down all version
esday, November 07, 2007 4:04 PM
To: Maven Users List
Subject: Re: Alpha plugin
That has been discussed and I believe something along those lines is
in-progress. I'm unsure who is working on it, but I believe the intent
is that we can use (a new?) plugin to lock them down and then enforcer
That has been discussed and I believe something along those lines is
in-progress. I'm unsure who is working on it, but I believe the intent
is that we can use (a new?) plugin to lock them down and then enforcer
plugin to verify all plugins and dependencies etc are locked down, to
guarantee repeatab
Can you create an issue with a description and a way to reproduce?
Stéphane
On 11/6/07, Jean-Yves LEBLEU <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> Is there any way to avoid using alpha version of plugins with maven.
>
> I have some builds which used to run fine and as the plugin is updated
> to
Wayne Fay wrote:
Actually, I lock down all versions of all plugins and all
dependencies. Unless I need a new feature in a new release of a
plugin, or I run into a bug that's been fixed in a newer version, the
"old" version works just fine for me.
Is there a way (a plugin for example) that can
Understood, I will lock the plugins, thanks for your answers.
Jean-Yves
On Nov 6, 2007 4:18 PM, olivier lamy <[EMAIL PROTECTED]> wrote:
> Hi,
> Yes you can lock the plugin version in your poms.
> Use xml element.
>
> --
> Olivier
>
> 2007/11/6, Jean-Yves LEBLEU <[EMAIL PROTECTED]>:
>
> >
> > Hel
Hi,
Yes you can lock the plugin version in your poms.
Use xml element.
--
Olivier
2007/11/6, Jean-Yves LEBLEU <[EMAIL PROTECTED]>:
>
> Hello all,
>
> Is there any way to avoid using alpha version of plugins with maven.
>
> I have some builds which used to run fine and as the plugin is updated
>
Actually, I lock down all versions of all plugins and all
dependencies. Unless I need a new feature in a new release of a
plugin, or I run into a bug that's been fixed in a newer version, the
"old" version works just fine for me.
The "Maven should not use alpha/beta automatically" issue has been
d
It is what I do when I detect the problem but it is a bit "heavy" to
lock the version for every plugin you use don't you think so ?
This is one of the advantage of maven that everything is working with
a minimal pom. IMO the alpha / beta versions of plugins should not be
updated automatically
Jean
You can/should lock down your version numbers in the pom.
Wayne
On 11/6/07, Jean-Yves LEBLEU <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> Is there any way to avoid using alpha version of plugins with maven.
>
> I have some builds which used to run fine and as the plugin is updated
> to alpha versi
Hello all,
Is there any way to avoid using alpha version of plugins with maven.
I have some builds which used to run fine and as the plugin is updated
to alpha version they are not running properly anymore
(war plugin alpha 2.1 does not filter ressources correctly), had the
same pb with the assem
11 matches
Mail list logo