We have developed a number of DNN modules some of which rely on a common module that we also developed. Is there anyway to apply dependencies on specific versions of modules?

For example, module X 1.1 depends on common features in module Y 1.1, I want to prevent people from installing X 1.1 if they have a lesser version of Y (like 1.0). Does this already exist in DNN? If so, how is it done?

I know that dependencies can be created by specifying the fully-qualified class path in the dependencies section of the .dnn file. However, this doesn't take into account of different versions of the same file. Plus, I'm finding that this method is not working in my case. I can still install modules that are dependent on other modules (e.g. Forums ) that are not present.

I might add that I also include common javascript files, web services, images, and other resources in my Common module.  This allows for a single point for literally ALL common functionality instead of duplicating them across modules.  This is where my comment about possibly putting into a set of common modules might be more appropriate if you have a very large set of potentially common items and don't want to load down another installation with something they don't need.

One neat thing I do with my javascript is I have a generic handler (ASHX) that I can pass a querystring to and it first caches the results for the query string, but additionally behind the scenes is it combines all the javascript files per the querystring into a single request in the order they were requested.  Pretty suave.  It also allows me to update the javascript versions but not need to change the querystring to reference them (like when loading in jQuery, for example).