> Do you mean with osi-ified that someone added the manifest and possibly > other stuff? I do not really like this practice. It means that every new > version has to be "bundled" again.
It totally depends on the agency that is turning the plain old jar into a bundle. > I think the best but slowest way is to get the original projects to make > their deployments to central osgi ready. +1 > So what I would prefer is some kind of proxy for maven that reads from the > normal repos and add the osgi specifics on the fly by using an additional > database or repo. This proxy could even fail your build if a dependency can > not be made osgi ready. This way your poms would be clean and you could > still build fresh from an empty local repository. That's a neat idea - but it probably would be better just to have all jars be OSGi jars, since you can use an OSGi jar as a normal jar, the only additions are in the manifest, which is usually not that much overhead. --oh
