On Wed, October 31, 2007 2:38 pm, Michal Paluchowski wrote: > That was EXTREMELY helpful, thank you :) With that part done, there's > just one more issue I might need help on and that's dependencies > between plugins. Adding them to the MANIFEST.MF makes Eclipse compile > projects but obviously Maven (or PDE) isn't able to read from those.
We haven't gone this far, we just had one plugin depending on jars. One thing I do know is that maven-eclipse-plugin is under full control of the dependencies listed in MANIFEST.MF. If maven doesn't know about it, the dependency won't be included, even if you try and add it manually, maven will simply remove manually added dependencies again. That said, Eclipse plugins are effectively osgi bundles, which advertise their dependency needs (in the form of package prefixes[1]) and expect the container (Eclipse) to resolve the dependencies automatically. In other words, as long as plugin A and plugin B are in the same Eclipse directory structure (the plugins directory), and the dependency packages are defined correctly in MANIFEST.MF, then Eclipse (and eclipse PDE, and in turn pde-maven-plugin, and in turn maven) works this out automatically for itself. [1] This is one of the reasons why following the Eclipse naming conventions is important. Regards, Graham -- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
