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

Bug 344535

Summary:	[generator] LanguageConfig file extension check too strict
Product:	[Modeling] TMF	Reporter:	Knut Wannheden <knut.wannheden>
Component:	Xtext	Assignee:	Project Inbox <tmf.xtext-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	Flags:	sven.efftinge: kepler+
Version:	2.0.0
Target Milestone:	M4
Hardware:	All
OS:	All
Whiteboard:

Description Knut Wannheden

2011-05-03 04:07:54 EDT

LanguageConfig#checkConfiguration() checks the language's file extensions based on #isCheckFileExtension() (which can't be set using a property, but must be handled in a subclass). The check seems a bit too strict however. For instance it does not allow for URI encoded characters (e.g. ' ' -> '%20').

Comment 1 Sven Efftinge

2012-11-21 04:45:06 EST

I don't think whitespace is allowed in a file extension. However I've introduced a property to disable the check for people who think they know what they do :-)

Comment 2 Knut Wannheden

2012-11-21 06:47:36 EST

Great, thanks!

Spaces in the file extension is indeed odd. But EMF URIs and Eclipse's IResource and IPath seem to have no problem with that.

Comment 3 Eclipse Webmaster

2017-10-31 11:05:18 EDT

Requested via bug 522520.

-M.

Comment 4 Eclipse Webmaster

2017-10-31 11:16:39 EDT

Requested via bug 522520.

-M.