I try to use the Java3d plug-in in a RCP application.
But there are some errors at runtime about missing bundles.
It seems to be caused by the required plug-ins in your feature.xml.
I wonder why there are these dependencies on org.eclipse.core.variables, org.eclipse.core.filebuffers, etc. Are they really needed?
Thanks,
--
Patrick
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just for clarification: are you talking about the java3dplugin (basic java3d functionality) alone or with core.java3declipse.org?
I will have to look into this, it might happen that I have included some unnecessary dependencies, but as far as I remember, I tried to keep only the absolute minimum.
However, org.eclipse.core.* packages are quite fundamental and it may happen they get pulled in by very basic RCP plugins (but I am not sure).
If you find out something new about the dependencies, please post it here.
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
PS: I confirm that the dependencies on org.eclipse.core.variables, org.eclipse.core.filebuffers, etc., are not needed for a RCP application. So I think they should be removed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, please download the new update site. Note that it has exactly the same name as the previous one, as well as the version numbers. Therefore, you must first remove the previous feature/plugins. To that, refer to this page: http://java3d-eclipse.wiki.sourceforge.net/Removing+java3d-eclipse+plug-in
Let me know if all worked fine for you.
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It works better now, I could remove most unnecessary dependencies.
However, I still don't understand everything, for example why I must include plugin java3d_windows_i586 in my feature for my app to build, I would expect it comes automatically with java3d feature. Then the java3d_windows_i586 plugin is included in the Linux build. Eclipse dependencies are still a mystery to me.
Thank you!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The dependencies - a feature is merely a means for Eclipse to organize plugins. However, plugins are the ones that are important.
Java3d plugin contains one plugin (Plug-in id: "java3d") and a fragment per supported platform (where platform is defined as OS/cpu combination). While plugin contains declarations of what the plugin contains (but none of the binaries), features specify that they are dependent upon that plugin and, of course, contain the binaries (jars and native libs). Jars are required for java compiler to comiple your java3d code.
Luckily, java3d API is the same regardless of the platform and your app should work the same whether you are developing it on windows, linux or something else (providing, of course, you provide appropriate fragment when running on another platform).
Please check out the "demoapp" from svn and take a look at the launch configuration. The configuration does not deal with features, it gives you an option to select plug-ins and fragmetns needed for your app.
I hope this clarifies dependencies in Eclpse RCP a bit.
Finally, including windows fragment for linux is a bug and I will open a tracker issue and fix it. Eclipse works very well for most of the stuff, but deployment of fragments is flaky. I have to export them manually (it exports only the fragment related to the running platform) and there is no way to know if things went well without actually trying out each supported platform. Therefore, I thank you for your feedback - please notify me of any issues you have with the plugin.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I try to use the Java3d plug-in in a RCP application.
But there are some errors at runtime about missing bundles.
It seems to be caused by the required plug-ins in your feature.xml.
I wonder why there are these dependencies on org.eclipse.core.variables, org.eclipse.core.filebuffers, etc. Are they really needed?
Thanks,
--
Patrick
Hello Patrick,
Just for clarification: are you talking about the java3dplugin (basic java3d functionality) alone or with core.java3declipse.org?
I will have to look into this, it might happen that I have included some unnecessary dependencies, but as far as I remember, I tried to keep only the absolute minimum.
However, org.eclipse.core.* packages are quite fundamental and it may happen they get pulled in by very basic RCP plugins (but I am not sure).
If you find out something new about the dependencies, please post it here.
Thanks
Hi,
I'm talking about the java3dplugin alone (java3declipse-1.5.1.zip).
The dependencies are in the file feature.xml.
PS: I confirm that the dependencies on org.eclipse.core.variables, org.eclipse.core.filebuffers, etc., are not needed for a RCP application. So I think they should be removed.
Thanks for looking into this.
I will remove dependencies and post the update.
Great, thank you :)
Please tell us when the update is out, so that I can build my application.
Ok, please download the new update site. Note that it has exactly the same name as the previous one, as well as the version numbers. Therefore, you must first remove the previous feature/plugins. To that, refer to this page: http://java3d-eclipse.wiki.sourceforge.net/Removing+java3d-eclipse+plug-in
Let me know if all worked fine for you.
Thanks!
Hello Aleksandar,
It works better now, I could remove most unnecessary dependencies.
However, I still don't understand everything, for example why I must include plugin java3d_windows_i586 in my feature for my app to build, I would expect it comes automatically with java3d feature. Then the java3d_windows_i586 plugin is included in the Linux build. Eclipse dependencies are still a mystery to me.
Thank you!
The dependencies - a feature is merely a means for Eclipse to organize plugins. However, plugins are the ones that are important.
Java3d plugin contains one plugin (Plug-in id: "java3d") and a fragment per supported platform (where platform is defined as OS/cpu combination). While plugin contains declarations of what the plugin contains (but none of the binaries), features specify that they are dependent upon that plugin and, of course, contain the binaries (jars and native libs). Jars are required for java compiler to comiple your java3d code.
Luckily, java3d API is the same regardless of the platform and your app should work the same whether you are developing it on windows, linux or something else (providing, of course, you provide appropriate fragment when running on another platform).
Please check out the "demoapp" from svn and take a look at the launch configuration. The configuration does not deal with features, it gives you an option to select plug-ins and fragmetns needed for your app.
I hope this clarifies dependencies in Eclpse RCP a bit.
Finally, including windows fragment for linux is a bug and I will open a tracker issue and fix it. Eclipse works very well for most of the stuff, but deployment of fragments is flaky. I have to export them manually (it exports only the fragment related to the running platform) and there is no way to know if things went well without actually trying out each supported platform. Therefore, I thank you for your feedback - please notify me of any issues you have with the plugin.