Hi, I keep on seeing the below log every time I build my plug-in from command line:
[eclipse.buildScript] Some inter-plug-in dependencies have not been satisfied. [eclipse.buildScript] Bundle org.eclipse.gmf.bridge.ui.dashboard: [eclipse.buildScript] Another singleton version selected: org.eclipse.gmf.bridge.ui.dashboard_1.0.100.v20061222-1800 [eclipse.buildScript] Bundle org.eclipse.gmf.bridge.ui: [eclipse.buildScript] Another singleton version selected: org.eclipse.gmf.bridge.ui_1.0.100.v20061214-0000 [eclipse.buildScript] Bundle org.eclipse.gmf.codegen.edit: [eclipse.buildScript] Another singleton version selected: org.eclipse.gmf.codegen.edit_1.2.1.v20070103-0300 [eclipse.buildScript] Bundle org.eclipse.gmf.codegen.ui: [eclipse.buildScript] Another singleton version selected: org.eclipse.gmf.codegen.ui_1.1.0.v20061222-1800 [eclipse.buildScript] Optional plug-in org.eclipse.gmf.bridge.trace_[1.0.0 ,2.0.0) is not availble. [eclipse.buildScript] Bundle org.eclipse.gmf.codegen: [eclipse.buildScript] Another singleton version selected: org.eclipse.gmf.codegen_1.2.1.v20070103-0300 [eclipse.buildScript] Bundle org.eclipse.gmf.doc.ui: [eclipse.buildScript] Another singleton version selected: org.eclipse.gmf.doc.ui_1.0.0.v20061214-0000 [eclipse.buildScript] Bundle org.eclipse.gmf.doc: [eclipse.buildScript] Another singleton version selected: org.eclipse.gmf.doc_1.0.0.v20061214-0000 [eclipse.buildScript] Bundle org.eclipse.gmf.ecore.editor: [eclipse.buildScript] Another singleton version selected: org.eclipse.gmf.ecore.editor_1.0.100.v20070103-0300 [eclipse.buildScript] Bundle org.eclipse.gmf.graphdef.codegen.ui: [eclipse.buildScript] Another singleton version selected: org.eclipse.gmf.graphdef.codegen.ui_1.0.102.v20061214-0000 [eclipse.buildScript] Bundle org.eclipse.gmf.graphdef.codegen: .. .. .. Would this create any problem at the run-time? I am facing problems with the build plugin at the the time of testing, its behaving weird. Does this has something to do with the above log messages? Thanks in advance. Been stuck on this for two days now :( Regards, Amit On Fri, Feb 22, 2008 at 7:18 PM, amit kumar <[EMAIL PROTECTED]> wrote: > Hi, > But I had checked some plugins that gets shipped with eclipse (3.3) for > instance org.apache.batik_1.6.0.v20061222-1222, they do have a lib folder > inside them but their Manifest.mf file looks a little different, it > doesn't have an entry for Bundle.classpath, rather it has mentioned many > packages in Export Packages. > > What could be the case with that plugin? Is it because they are not using > maven? or something else? Just curious. > > > Regards, > Amit > > > On Fri, Feb 22, 2008 at 6:37 PM, Graham Leggett <[EMAIL PROTECTED]> wrote: > > > amit kumar wrote: > > > > > Copying the dependencies to the root file is what has worked till now. > > But > > > the ultimate packaged plug in looks a little messy. So I was just > > trying to > > > do accomplish the copying of dependency to the lib folder as an > > > improvisation. > > > > The need to copy the dependencies to the root folder comes about due to > > an Eclipse bug - The Eclipse IDE has a feature that allows you to add > > "links" to dependencies, and the Eclipse IDE puts these in links in the > > root of the project. > > > > Unfortunately this linked dependencies feature is not mirrored in the > > ant based Eclipse PDE build code, which takes the existence of the files > > literally. If the files aren't physically in the root directory, then > > the PDE build will fail. > > > > You may also encounter this in Eclipse on it's own: your project may > > build and run fine from within the IDE, but when you run "export your > > product" the Eclipse build mysteriously fails. > > > > Regards, > > Graham > > -- > > > >
