Hi,
On 12/22/2011 12:31 PM, Ghazall Aghaei wrote:
Thanks for shedding some light on this. I'm just wondering why this happened out of the blue. Are these changes related to the recent restructuring?
Yes, most definitely. Sorry for that.
So I have to amend my CMakeLists.txt files accordingly to create a valid provisioning file for all my plugins.
Just to clarify things: Provisioning files are needed for each application, not for individual plug-ins. If you can (and I see not reason why you couldn't), you should use the FunctionCreateBlueBerryApplication() CMake macro in your application's CMakeLists.txt file. It *should* be just as easy as adding this one macro call.
What bugs me is that I had created one plugin using the MITK Bundelgenerator and it shows the very same error and no privisioning file present :(
Are you talking about the deprecated, CMake-based "Bundle Generator" (which generated legacy BlueBerry-style bundles) or the newer command line program, the "MITK Plugin Generator" which creates CTK-style plug-ins?
It seems I also ran into the plug-in ordering problem within the provisioning file. Are the fixes part of the library preloading commits you pushed yesterday?
Symptoms of this problem were missing extensions for certain extension-points, so you could have been affected. Yes, the changes have been pushed to the MITK master (just updated your MITK source tree and issue a build command in the superbuild directory).
Hope that helps, Sascha
Ghazall2011/12/21 Sascha Zelzer <[email protected] <mailto:[email protected]>>Hi Ghazall, I doubt that the BlueBerry.provisioning file contains an entry for the org.mitk.gui.qt.common plug-in. Therefore, I'm not surprised that your error stays ;-) Anyway, manually editing provisioning files is not recommended. Have a look how the MITK ProjectTemplate creates it's provisioning file (it is created implicitly during the FunctionCreateBlueBerryApplication macro call: https://github.com/MITK/MITK-ProjectTemplate/blob/master/Apps/AwesomeApp/CMakeLists.txt You can also read the documentation for the macros here: http://docs.mitk.org/nightly-qt4/BlueBerry/reference/api/html/namespaceCMake.html#a9f16f167e718f5d68edf4c12f6ed320c http://docs.mitk.org/nightly-qt4/BlueBerry/reference/api/html/namespaceCMake.html#a97dc556f99612dcbbf97603df4d87670 Declaring extension-points is still optional. However, the BlueBerry Workbench assumes that there is at least one extension for the org.blueberry.osgi.applications extension point. It has to know which "application" to start. I guess your provisioning file is missing plug-ins. Or you might be running into a plug-in ordering problem which I fixed today but did not push yet. - Sascha On 12/20/2011 06:46 PM, Ghazall Aghaei wrote:Hi Sascha, thanks for the pointer. I've added my local Blueberry provisioning file there ( E:\MITK-superbuild\MITK-build\bin\BlueBerry.provisioning ) which seems to include all necessary files. Just a relevant excerpt: START file:///E:/MITK-superbuild/MITK-build/bin/plugins/liborg_blueberry_ui.dll START file:///E:/MITK-superbuild/MITK-build/bin/plugins/liborg_blueberry_ui_qt.dll Now when starting my plugin it still shows the old error and two additional lines (highlighted in blue): blueberry.osgi.bundleloader ERROR: Bundle resolve failed: Cannot resolve bundle: The bundle de.iccas.tumoroperator depends on missing bundle:: org.mitk.gui.qt.common blueberry.osgi.starter FATAL: No extensions configured into extension-point 'org.blueberry.osgi.applications' found. Aborting. blueberry.osgi.starter ERROR: Could not create executable application extension for id: org.mitk.qt.extapplication declaring extension points for my plugin via plugin.xml used to to be optional. Do I need to create one now? Does this affect all plugins upgrading to the new plugin model? Ghazall 2011/12/20 Sascha Zelzer <[email protected] <mailto:[email protected]>> Hi Ghazall, the plug-ins available at runtime for a specific application are defined in the <your-app-name>.provisioning file (located in your project's bin directory). The provisioning file must contain an entry to the org.mitk.gui.qt.common plug-in (or point to a file containing such an entry). The provisioning file itself is referenced either in the <your-app-name>.ini file (if it exists) or by specifying an application property in <your-app-name>.cpp (the .ini file takes precedence). Could you please check these points? Thanks, Sascha On 12/20/2011 01:58 PM, Ghazall Aghaei wrote:Hi list, I went through the joy of updating MITK superbuild once again and this time MITK built all fine and dandy (thanks for fixing the recent problems there) Yet running my own-built plugins (recompiled against the new MITK) outputs the following error in the MITK console: blueberry.osgi.bundleloader ERROR: Bundle resolve failed: Cannot resolve bundle: The bundle de.iccas.tumoroperator depends on missing bundle:: org.mitk.gui.qt.common I've checked via CMake in the MITK-build directory that "mitk.gui.qt.common" is actually built and I've also read through Sascha's last week's mail "Recent changes in MITK" but my CMakeCache.txt did not contain any "CTK_PLUGIN_LIBRARIES" entry. Any ideas? Ghazall
------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev
_______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
