| [news.eclipse.platform.swt] Re: Standalone SWT/JFace application packaging, essential jars |
boot.jar is empty now. Adding workbench.jar won't hurt you but is not necessary. The lack of the osgi.jar should be problematic. Its possible you just haven't any JFace that references the osgiclasses. I don't know what book you are using but it may be referring to 2.1 not 3.0. -Chris "Hugo A. Garcia" <hugo.a.garcia@xxxxxxxxx> wrote in message news:cslegs$pko$1@xxxxxxxxxxxxxxxxxx > Interesting. I am learning from a book and it uses the following: > > swt.jar > runtime.jar > boot.jar > workbench.jar > > Both list work. Why? > > -H > > Chris wrote: >> Now: >> swt.jar >> jface.jar >> runtime.jar >> osgi.jar >> >> If 49497 comes to fruition it would be: >> swt.jar >> jface.jar >> utility.jar >> >> -Chris >> >> "Hugo A. Garcia" <hugo.a.garcia@xxxxxxxxx> wrote in message >> news:cshoeh$8ru$1@xxxxxxxxxxxxxxxxxx >> >>>Hi >>> >>>I came accross https://bugs.eclipse.org/bugs/show_bug.cgi?id=49497 and it >>>is a work in progress I am interested in. But until that work in progress >>>is complete, I really need to now the essential jars that are needed in >>>order to package an independent app that uses SWT/JFace. These jars would >>>reside in the /lib of the app I would like to distribute. This way once >>>the above mentioned work is complete then I can just update the /lib. >>> >>>Thanks >>> >>>-H >> >>