Community
Participate
Working Groups
Using Help->About Eclipse->Installation Details->Plugins shows very irregular results for the impact plugins. Correct plugin.properties. If the changes don't take make sure the manifest has Eclipse localization.
Created attachment 194455 [details] Patch updating the plugin.properties accordingly Not sure if I need a +1 for this. Do I?
No. They're your examples. This was one of the few respects in which they have a public imprint.
Committed to CVS HEAD
In M7, impactanalyzer.util and impactanalyzer.ui are still a problem.
Here are the .util and .ui build.properties in their 1.1 revision: # <copyright> # </copyright> # # $Id: plugin.properties,v 1.1 2011/05/01 20:04:58 auhl Exp $ pluginName = OCL Impact Analyzer Utilities providerName = Eclipse Modeling Project and # <copyright> # </copyright> # # $Id: plugin.properties,v 1.1 2011/05/01 20:05:00 auhl Exp $ pluginName = OCL Impact Analyzer UI Integration providerName = Eclipse Modeling Project respectively. Closing again. Maybe you're on the wrong revision?
I'm looking at M7. There is alot more than just plugin.properties. See the orignal report "If the changes don't take make sure the manifest has Eclipse localization."
(In reply to comment #6) > I'm looking at M7. There is alot more than just plugin.properties. > > See the orignal report "If the changes don't > take make sure the manifest has Eclipse localization." Ah, fixed by adding Bundle-Localization: plugin to the MANIFEST.MF files of org.eclipse.ocl.examples.impactanalyzer.tests org.eclipse.ocl.examples.impactanalyzer.testutils org.eclipse.ocl.examples.impactanalyzer.util org.eclipse.ocl.examples.impactanalyzer.ui