Thank you all for your answers, My intention was to have the ability configure the versions of the dependencies before the building, using a GUI. For example, when selecting to build using the eclipse maven plugin, the eclipse plugin will open a configuration dialog that contains for each dependency a combo box with all the available versions. After the user selects the versions, it presses on the 'build' button in this dialog and this will cause the new versions to take affect (propogate them to the maven) and only then continue with the building process.
-----Original Message----- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 01, 2006 8:30 AM To: Maven Users List Subject: Re: Additional features for maven2 plugin Defining the version for a dependency is one of the base features of Maven: <dependency> <artifactId/> <groupId/> <scope/> <version>[2.0.8]</version> </dependency> The [x.y.z] notation "locks" the artifact to that version. Use [x.y.z, ) to force a minimum but no maximum on the version number ie if a new feature is added in build 3.1.2 that you require for your code to work, etc. Is this not working for you, do you have some other requirement(s) which are not currently available, or what? Wayne On 11/1/06, Rahamim, Zvi (Zvi) <[EMAIL PROTECTED]> wrote: > Hi, > I think that a very important feature is to have the ability to > define, before maven starts building, the versions of the dependencies. > Is there an intention to add this feature? > Thanks! > Zvi. > > --------------------------------------------------------------------- > 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]
