2008/7/11 Alexandre Sauvé <[EMAIL PROTECTED]>: > OK... so forget all my previous questions! >
actually I'll answer them in another note, as others might find the answers useful :) I have seen the light! A very interesting thread is the following between > Stuart and Marshall-> > http://www.mail-archive.com/[email protected]/msg00949.html > > Finally I have another question though... when I embed a dependency and I > say that it should be treated as transitive, why are the transitive > dependencies includes on the Import-Package directive in the manifest but > the jars are not included in the bundle and the appropriate additions to > the > Bundle-Classpath done? could you provide more info - like the dependency details (scope, etc.) as well as the complete bundleplugin instructions? also which version of the bundleplugin are you using? Are we assuming that these packages may be provided > by another bundle? Is that a safe assumption? > well any packages referred to in the bundle, but not included inside it, will be imported - so if for some reason the dependency isn't being embedded (which sounds like a bug) then you'll find the packages will be imported I usually mark dependent bundles as provided scope, and any embeddable dependencies as compile / runtime, but that's just my personal convention (ie. you can embed provided deps with Embed-Dependency if you want) Thanks, > Alex > > On Mon, Jul 7, 2008 at 2:52 PM, Alexandre Sauvé <[EMAIL PROTECTED]> > wrote: > > > So I have figured out the SWT thing... > > > > http://blambi.blogspot.com/2007/07/maven2-swt-builds.html > > > > And when you strip the Eclipse installation you will get a win32 > directory > > under the SWT. You can use that for your SWT dependency! > > > > Question 1 & 3 have not been solved as of yet! I will keep you updated! > > > > Thanks, > > Alex > > > > > > On Mon, Jul 7, 2008 at 2:10 PM, Alexandre Sauvé <[EMAIL PROTECTED]> > > wrote: > > > >> Hey gang, > >> > >> I was reading the thread between Stuart and Fabio ( > >> http://www.mail-archive.com/[email protected]/msg00896.html) > >> regarding Maven Bundle and Eclipse RCP and I have read the documentation > >> regarding Eclipse PDE ( > >> http://felix.apache.org/site/maven-bundle-plugin-bnd.html). But now I > >> have a couple of questions... > >> > >> 1. So Fabio attached his POM and upon Stuart's suggestion he included > the > >> RCP dependencies that he required. However Fabio made all the Eclipse > >> dependencies at the 'compile' scope. I would have thought these > >> dependencies would need to be at the 'provided' scope. Otherwise the > embed > >> feature of the maven-bundle plugin would try to embed these jars. If I > am > >> wrong and the dependencies could be 'compile' then does he need to > specify > >> them all or can he rely on the transitive dependencies? > >> > >> 2. When you scrape Eclipse using the eclipe:maven-to goal the SWT jar > that > >> is created at org.eclipse.swt doesn't contain any code. I imagine it is > >> like this as swt is platform dependent? Does this mean I have to use > the > >> 'system' scope and specify the jar? Finally out of curiosity why > doesn't > >> the SWT jar have the interfaces included? > >> > >> 3. I am new to RCP so this may be a stupid question. When you generate > an > >> example RCP plugin with a view in the Manifest file they have the > >> Require-Bundle tag where you specify the bundles that you depend on. I > >> don't see a way of populating that list with the maven-bundle plugin > other > >> than in the instruction section. But this means that there will be 2 > places > >> to specify plugins or bundles we depend on: in the dependencies and in > the > >> instructions. > >> > >> Hopefully someone can help this newbie out! > >> Thanks, > >> Alex > >> > >> > >> > > > -- Cheers, Stuart
