No, cannot.
But I would suggest to version all your jars and maybe remove the versions at deployment if it is an issue.
We are using this technique and the jar compatibility nightmare (jars in cvs, versions clashing, etc) ended and never came back!
HTH. Eric.
[EMAIL PROTECTED] wrote:
What if some jar files are not versioned (and maybe will never be versioned). Is there a way to force Maven to always go to the remote repositories to resolve dependencies?
I've tried SNAPSHOT, but that does not reload a dependency every time a build is executed.
Thanks for your help. Tom
This message is intended for the recipient only and is not meant to be forwarded or distributed in any other format. This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument, or security, or as an official confirmation of any transaction. Putnam does not accept purchase or redemptions of securities, instructions, or authorizations that are sent via e-mail. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of Putnam, LLC (DBA Putnam Investments) and its subsidiaries and affiliates. If you are not the intended recipient of this e-mail, please delete the e-mail.
--------------------------------------------------------------------- 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]
