It would be interesting to have Maven natively understand OSGi metadata. This is interesting in two places/ways:
- Built bundles have a manifest.mf that fully specifies what the bundle can supply and what it needs. If Maven could read the manifest directly, you would not need a POM for the bundle when buliding it. This in turn would allow people to build against products and other delivered software which does not live in an accessible maven repo. - At development time, some people prefer to specify their dependencies in manifests rather than poms. Having Maven read dependency info from the manifest would eliminate the need to duplicate that information. Jeff Jason van Zyl <[EMAIL PROTECTED]> 09/28/2006 01:41 PM Please respond to felix-dev@incubator.apache.org To felix-dev@incubator.apache.org cc Subject Creating OSGi bundles with the Maven JAR Plugin I'm thinking about ApacheCon again so I remember that at the last ApacheCon we talked about modifying the JAR plugin to create OSGi bundles for you guys automatically. I'm hoping that I can try and demo something for ApacheCon (not for any preso, but just to show it can work) so I'm wondering where this ended up. I'm now subscribed to the list so maybe I dropped the ball. Thanks, Jason.
