1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 <2012> 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 <2012> 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: [CSS] 'Epics' menu in Preferences disappeared!!! |
From: | Pavel Masloff <[email protected]> |
To: | "Kasemir, Kay" <[email protected]> |
Cc: | "[email protected]" <[email protected]> |
Date: | Wed, 25 Jan 2012 17:17:28 +0300 |
Hello:
I believe the "lucene" dependencies changed with Eclipse versions.
So depending on which version of Eclipse you are using,
you need those or don't have those.
I put those plugins that I have to include from Eclipse in an "eclipse"
feature to separate them from the plugins that I want to include
from CSS core, CSS applications etc.
You use the IDE's "Run Configuration/Plug-Ins" tab to determine which plugins you want/need,
try that by starting the product from within the IDE,
and once you like the result, you enter those into the features which are
then used to "export" the product.
Date: Tue, 24 Jan 2012 16:16:31 -0500
To: Kasemir Kay <[email protected]<mailto:[email protected]>>
Cc: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>
Subject: Re: [CSS] 'Epics' menu in Preferences disappeared!!!
Kay!
I have launched the original KEK 3.0.1 versions from IDE (Sync-> Launch as an Eclipse application) and epics doesn't show up in the prefs! So the original sources have this error!!!
I have tried to launch it the other way - through Run Configurations. When I click Validate plug-ins - it says that two plugins are missing (lucene,lucene.analysis). Then I add the requiered plugins. And it works - I can see EPICS in the Preferences.
The only thing I don't understand. How to make it work through features.
> When you open the META-INF/MANIFEST.MF, you'll
> see "Require-Bundle: ..." entries in there.
> Also displayed in the "Dependencies" tab
> of the editor for plugin.xml and MANIFEST.MF.
> To get a plugin into a product, all its dependencies
> need to be included as well.
I presume, you mean the Manifest.mf of org.csstudio.platform.libs.epics.ui.
I can assure you that all the required plugins are included in css-kek.product, namely:
org.eclipse.help, (in org.csstudio.kek.eclipse.feature)
org.eclipse.help.appserver, (in org.csstudio.kek.eclipse.feature)
org.eclipse.help.base, (in org.csstudio.kek.eclipse.feature)
org.eclipse.help.ui, (in org.csstudio.kek.eclipse.feature)
org.eclipse.help.webapp, (in org.csstudio.kek.eclipse.feature)
org.csstudio.platform.libs.epics (in org.csstudio.kek.core.feature)
I am confused.
Pavel
On Wed, Jan 25, 2012 at 12:23 AM, Kasemir, Kay <[email protected]<mailto:[email protected]>> wrote:
>I checked in Help, About, Installation Details, Plug-Ins:
>org.csstudio.platform.libs.epics.ui - does NOT show up
>org.csstudio.ui.preferences - does show up
OK, so that explains why you don't have the 'EPICS'
section in the preference GUI.
So now the Q is: Why isn't it included?
>Plugin.xml looks exactly how you described!
>Silly question: how to check the dependencies?
If your product is assembled from features,
one one such feature includes some plugin like
org.csstudio.platform.libs.epics.ui,
then that plugin should be in the product.
Except if that plugin depends on other plugins,
which are missing from the product.
When you open the META-INF/MANIFEST.MF, you'll
see "Require-Bundle: ..." entries in there.
Also displayed in the "Dependencies" tab
of the editor for plugin.xml and MANIFEST.MF.
To get a plugin into a product, all its dependencies
need to be included as well.
When you build your product directly based on a list
of plugins, without features, there's a "add dependencies"
button in the plugin editor that automatically adds
all dependencies.
When you build your product based on features, there's
no such button because the system cannot automatically determine
in which feature you would like to add the missing plugins.
Besides, the pure dependencies are not all:
Many tools depend on org.csstudio.utility.pv to get the API
for PV support. It's up to you to also include either
org.csstudio.utility.pv.epics to access EPICS PVs,
or org.csstudio.utility.simu to access simulated PVs,
or both.
So beyond the "required" plugins you may really need additional
ones to get the product to do what you want.
But back to org.csstudio.platform.libs.epics.ui not loading,
that probably means you are missing some required dependency.
When running the product from within the Eclipse IDE,
you can use the Run Configurations/Plug-Ins/Validate Plug-Ins button.
See also http://cs-studio.sourceforge.net/docbook/, chapter "Site-Specific
Products",
section "Fix Dependencies".
-Kay
--
Best regards,
Pavel Maslov, MS
Controls Engineer at Pulsed power Lab
Efremov Institute for Electro-Physical Apparatus
St. Petersburg, Russia
Mobile: +7 (951) 672 22 19
Phone: +7 (812) 461 01 01