This is a small but important design decision of colony, I hope I could explain it correctly.
This makes sense and you are right, it is much simpler and cleaner,
and I do like the fact that it is platform and implementation
independent....definitely cant say the same thing for OSGi
> Because of this the "library exporting" is just no "implementable". The correct way of using libraries is to use it at a platform level, for this you should declare the package dependency that is intepreted according to each implementation. For example, In python it will make sure that the refered module is available in the current python path.
> This is a small but important design decision of colony, I hope I could explain it correctly.
Yes, this makes sense. However, what if 2 plugins require different
versions of a particular library? How could this be handled? I don't
imagine I will run into this with my situation but I could see in the
future where plugins from different people are getting mixed together
that this could cause problems. Also, there is no way to specify a
range of versions of a required library that would be
acceptable....and as far as I can tell, the package version you give a
PackageDependency does not get enforced. Perhaps you could use
pkg_resources from setuptools to do this verification or
something?...again, I'm not too worried about this in my situation but
I could see it being a problem later.