Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 341103

Summary:	i18n key missing in dialog "project import failed"
Product:	[Technology] Jubula	Reporter:	Tim Winselmann <tim.winselmann>
Component:	Core	Assignee:	Project Inbox <jubula.core-inbox>
Status:	CLOSED WONTFIX	QA Contact:	Oliver Goetz <Oliver.Goetz>
Severity:	minor
Priority:	P5	CC:	alexandra.schladebeck, zeb.ford-reitz
Version:	0.9.0
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Tim Winselmann

2011-03-28 09:31:16 EDT

If you import a not supported file type via the Import Project Dialog into GUIdancer, an Error Messages is shown:
"ErrorMessages.IMPORT_PROJECT_XML_FAILED"

Comment 1 Zeb Ford-Reitz

2011-03-28 10:28:47 EDT

partial fix:
http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=486c3fdacbfdb8140d44c0939b48eb383d7b46ab

As mentioned in the changeset comment, this is definitely only a partial fix:
 * The displayed message includes "{0}" because a parameter is not
properly set. Unparameterized values are ugly, but arguably less ugly than the raw keys.
 * We are still using our own custom i18n system here.

Due to the factors mentioned above, I cannot yet close the bug.

Comment 2 Alexandra Schladebeck

2012-11-19 07:41:50 EST

After discussing this in a meeting, I'm closing as wontfix:
- The really ugly error is gone
- Importing non-projects as a project is certainly possible, but somewhat academic, I would argue.