On 20/03/2009, James Carman <ja...@carmanconsulting.com> wrote: > On Fri, Mar 20, 2009 at 1:50 PM, sebb <seb...@gmail.com> wrote: > > > > Take 2: > > > > Just found a problem when using compile+optional in HC: > > > > The generated bundle: > > org.apache.httpcomponents.httpcore_4.1-SNAPSHOT.jar > > contains a valid DEPENDENCIES file. > > The MANIFEST looks OK too, no mention of jcip > > > > However, the included archive: > > httpcore-nio-4.1-SNAPSHOT.jar > > has a DEPENDENCIES file which refers to JCIP. > > > > Not sure if this is a problem for OSGI or not, but it is not consistent. > > > Ok, I understand that we want to make sure OSGi bundles work > correctly. But, misusing maven's dependency declaration because one > specific plugin doesn't work properly with the correct way to do it > doesn't seem right to me.
Agreed - I think! > How about we fix the felix plugin? We? > Or can't we tell it to ignore that stuff somehow via configuration? So long as the configuration override works for other projects that declare dependencies on such projects - and so on - that seems like a possible work-round. However - given that the problem appears to be due to incorrect handling of non-transitive dependencies - that may not work. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
