I completely agree with that. I'm fed-up to handcraft jar files to include a couple of classes, then update and repeat the process each time a new release is available, but I don't want a 2 MB jar inside my own bundle to use 10 utility classes...
-- Manuel Santillán <[EMAIL PROTECTED]> http://www.dit.upm.es/santillan Departamento de Ingeniería de Sistemas Telemáticos Escuela Técnica Superior de Ingenieros de Telecomunicación Universidad Politécnica de Madrid Avda. Complutense, s/n 28040 Madrid SPAIN Tel. +34 913367366 ext.3034 -----Mensaje original----- De: Marcel Offermans [mailto:[EMAIL PROTECTED] Enviado el: jueves, 13 de julio de 2006 18:04 Para: [email protected] Asunto: Re: OSGi Plugin for Maven 2.0 - add support for individual class dependencies I welcome such an extension. In general I would like to have the possibility, when creating a bundle, to specify which dependencies should be provided at runtime and which ones will be embedded. When embedding dependencies, I'd like to have the choice to either "embed for private use" or "embed and export". An option when embedding would definitely be to embed only those parts of a dependency that you actually use (which mainly applies to the "embed for private use" case. This extension seems to be heading in the above direction, so to me it's a very nice first step. Greetings, Marcel On Jul 13, 2006, at 17:10 , Richard S. Hall wrote: > Well, let's try to solicit a little more feedback (people?) and if > no one complains too loudly, then you can attach a patch to the a > JIRA issue and I will commit it.
