I am aware of two resolution strategies: use the most recent of the conflicting versions; present the user with an error message in the event of a conflict. However, neither of these are suitable for my use case. I would like to be able to specify ‘yes, I know there are conflicting versions and I want to use both’.
I appreciate that this might not make any sense for certain types of artifact (e.g. Jars) for which an application can only really use one version, but my use case is:
- a multi-project environment * some projects depend on different versions of the same artifact * the artifact in question could be a zip file containing header files and static libraries * the artifact in question could be a DLL which does behave nicely when loaded into an application which uses other versions of that DLL
Any suggestions as to how I can achieve this kind of resolution strategy, either on a per dependency basis or globally?