Bug 344406

Comment 1 Axel Uhl 2011-05-01 13:48:53 EDT

Created attachment 194455 [details]
Patch updating the plugin.properties accordingly

Not sure if I need a +1 for this. Do I?

Comment 2 Ed Willink 2011-05-01 14:20:33 EDT

No. They're your examples. This was one of the few respects in which they have a public imprint.

Comment 3 Axel Uhl 2011-05-01 16:05:07 EDT

Committed to CVS HEAD

Comment 4 Ed Willink 2011-05-03 12:26:30 EDT

In M7, impactanalyzer.util and impactanalyzer.ui are still a problem.

Comment 5 Axel Uhl 2011-05-03 16:07:56 EDT

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?

Comment 6 Ed Willink 2011-05-03 16:37:57 EDT

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."

Comment 7 Axel Uhl 2011-05-03 17:07:55 EDT

(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