The thing is that having the possibility of change a dependency version during build time would/could sound as a good thing. BUT, you have to remember that your pom gets deployed to a repo and will be consumed by other people. If the pom does not have pinned downed versions but would change depending on what profiles are specified. Something that will work for someone will not work for someone else.
If you would write a new release plugin that would update the pom that gets deployed to specify the exact versions used during build, it would be fine. But that's not the case with the current release plugin. /Anders On Fri, Mar 16, 2012 at 18:18, <[email protected]> wrote: > > >> >> Not good. >> Dependency versions should be deterministic. For the same reason avoid >> version ranges. >> > > > That's pretty definitive, and I think I agree on a gut level. Can you > articulate any specific issues? I'd appreciate it if you could. > > --------------------------------------------------------------------- > 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]
