On 6/28/06, Clifton Craig <[EMAIL PROTECTED]> wrote:
I have a questiono that I'm too lazy to do the full research on. (Actually I don't have time.) I looked for the answer on the site briefly but couldn't find it so I'm asking here. How do I set a dependency on the latest version of an API? For example, if I want the latest version of Xalan how do I declare that in my pom without using a specific version number?
I have an answre but I'm too lazy to do the full typing. (Actually I don't have time.) :) I am not aware of a <version>latest</version> and I don't think it is possible to use version ranges to achieve that. I would first wonder why you want to have such a requirement. I think having the full control of a build and its exact 3rd party dependencies is critical. Each time I change the version of a dependency that is not produced in-house, I try to isolate the change and run my tests again. Beeing able to know what is the reason for a breakage is critical. And if it was possible, I've seen too many issues with xml libraries, that I would especially not do this with xalan... As for in house dependencies, you can always use SNAPSHOTS. Jerome --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
