Again, I think you are assuming that I "own" the entire space. More often than not, I don't.
<TG>Well, I commented on your example. In Gradle, if you declare a project dependency you own the project; otherwise you would declare a dependency against a module or artifact. If you want to use external modules in your OSGi application you either find an OSGi-aware version of it or bundleize it yourself. Simply embedding everything that is not available as a bundle is not a very OSGi like approach.</TG> Simple question; Do you agree that building a WAB which is also a deployable WAR, as Kriens suggest on http://www.aqute.biz/Bnd/Format (subheading Web Archive Bundles), is a desirable option? If not, we can stop this discussion. <TG>Absolutely; if I recall correctly then I proposed the WAB use case as the perfect sample as it has all the requirements of an OSGi container application. However the new osgi-plugin MUST support all other target containers equally, being them more simple or more complicated.</TG> --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
