Bug 494142 - logError called with problematic arguments -> message not correctly generated.
Summary: logError called with problematic arguments -> message not correctly generated.
Status: CLOSED WONTFIX
Alias: None
Product: Sphinx
Classification: Automotive
Component: Core (show other bugs)
Version: 0.10.0   Edit
Hardware: PC Windows NT
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-20 07:44 EDT by Andreas Graf CLA
Modified: 2024-05-06 23:25 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Graf CLA 2016-05-20 07:44:45 EDT 
In org.eclipse.sphinx.emf.check.CheckValidatorRegistry.findAffectedEPackages(Set<Class<?>>, EPackageMappings)

we have the code 

	logError("Unable to find EPackage for ", classUnderCheck.getName()); //$NON-NLS-1$

but that does not seem to produce the correct error output, because somewhere don the line, this will call 

NLS.bind(msg,objects)

and this expects msg to be formatted according to some message argument convention.
The name of the problematic class is never reported.

This should be fixed.
Comment 1 Balazs Grill CLA 2024-05-06 23:25:43 EDT 
Closed stale issue before migration