Re: Alpha plugin
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 version 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 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 assembly plugin Thanks for any answer. Jean-Yves - 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]
Re: Alpha plugin
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 automate version lockdown for all plugins and dependencies? There are some plugins that are being used implicitly as far as I understand and there is no clear way of encountering all used plugins (except cleaning repository and checking the downloaded versions) For example maven-war-plugin is used when packaging is war, but it is not defined in the pom anywhere as a plugin. The Maven should not use alpha/beta automatically issue has been discussed on dev@ but I'm not sure what if any changes will come in 2.1. Wayne On 11/6/07, Jean-Yves LEBLEU [EMAIL PROTECTED] wrote: 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-Yves On Nov 6, 2007 4:22 PM, Wayne Fay [EMAIL PROTECTED] wrote: 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 version they are not running properly anymore (war plugin alpha 2.1 does not filter ressources correctly), had the same pb with the assembly plugin Thanks for any answer. Jean-Yves - 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]
Re: Alpha plugin
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 alpha version they are not running properly anymore (war plugin alpha 2.1 does not filter ressources correctly), had the same pb with the assembly plugin Thanks for any answer. Jean-Yves - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck -- S.Yegge - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 plugin to verify all plugins and dependencies etc are locked down, to guarantee repeatability of your build. Wayne On 11/7/07, Dimitris Kapanidis [EMAIL PROTECTED] wrote: 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 automate version lockdown for all plugins and dependencies? There are some plugins that are being used implicitly as far as I understand and there is no clear way of encountering all used plugins (except cleaning repository and checking the downloaded versions) For example maven-war-plugin is used when packaging is war, but it is not defined in the pom anywhere as a plugin. The Maven should not use alpha/beta automatically issue has been discussed on dev@ but I'm not sure what if any changes will come in 2.1. Wayne On 11/6/07, Jean-Yves LEBLEU [EMAIL PROTECTED] wrote: 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-Yves On Nov 6, 2007 4:22 PM, Wayne Fay [EMAIL PROTECTED] wrote: 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 version they are not running properly anymore (war plugin alpha 2.1 does not filter ressources correctly), had the same pb with the assembly plugin Thanks for any answer. Jean-Yves - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Alpha plugin
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 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 automate version lockdown for all plugins and dependencies? There are some plugins that are being used implicitly as far as I understand and there is no clear way of encountering all used plugins (except cleaning repository and checking the downloaded versions) For example maven-war-plugin is used when packaging is war, but it is not defined in the pom anywhere as a plugin. The Maven should not use alpha/beta automatically issue has been discussed on dev@ but I'm not sure what if any changes will come in 2.1. Wayne On 11/6/07, Jean-Yves LEBLEU [EMAIL PROTECTED] wrote: 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-Yves On Nov 6, 2007 4:22 PM, Wayne Fay [EMAIL PROTECTED] wrote: 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 version they are not running properly anymore (war plugin alpha 2.1 does not filter ressources correctly), had the same pb with the assembly plugin Thanks for any answer. Jean-Yves - 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] -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Alpha plugin
The next release of enforcer has a rule to make sure plugins are locked down. Dependencies must already be specified, but there is also a rule to make sure snapshots aren't included (similar to release plugin). -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, 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 plugin to verify all plugins and dependencies etc are locked down, to guarantee repeatability of your build. Wayne On 11/7/07, Dimitris Kapanidis [EMAIL PROTECTED] wrote: 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 automate version lockdown for all plugins and dependencies? There are some plugins that are being used implicitly as far as I understand and there is no clear way of encountering all used plugins (except cleaning repository and checking the downloaded versions) For example maven-war-plugin is used when packaging is war, but it is not defined in the pom anywhere as a plugin. The Maven should not use alpha/beta automatically issue has been discussed on dev@ but I'm not sure what if any changes will come in 2.1. Wayne On 11/6/07, Jean-Yves LEBLEU [EMAIL PROTECTED] wrote: 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-Yves On Nov 6, 2007 4:22 PM, Wayne Fay [EMAIL PROTECTED] wrote: 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 version they are not running properly anymore (war plugin alpha 2.1 does not filter ressources correctly), had the same pb with the assembly plugin Thanks for any answer. Jean-Yves - 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] - 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]
Alpha plugin
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 assembly plugin Thanks for any answer. Jean-Yves - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Alpha plugin
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 version they are not running properly anymore (war plugin alpha 2.1 does not filter ressources correctly), had the same pb with the assembly plugin Thanks for any answer. Jean-Yves - 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]
Re: Alpha plugin
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-Yves On Nov 6, 2007 4:22 PM, Wayne Fay [EMAIL PROTECTED] wrote: 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 version they are not running properly anymore (war plugin alpha 2.1 does not filter ressources correctly), had the same pb with the assembly plugin Thanks for any answer. Jean-Yves - 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]
Re: Alpha plugin
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 discussed on dev@ but I'm not sure what if any changes will come in 2.1. Wayne On 11/6/07, Jean-Yves LEBLEU [EMAIL PROTECTED] wrote: 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-Yves On Nov 6, 2007 4:22 PM, Wayne Fay [EMAIL PROTECTED] wrote: 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 version they are not running properly anymore (war plugin alpha 2.1 does not filter ressources correctly), had the same pb with the assembly plugin Thanks for any answer. Jean-Yves - 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]
Re: Alpha plugin
Hi, Yes you can lock the plugin version in your poms. Use version 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 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 assembly plugin Thanks for any answer. Jean-Yves - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
