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

Bug 316873

Summary:	Package multiple languages together
Product:	[Technology] Babel	Reporter:	Udo Walker <Udo.Walker>
Component:	Server	Assignee:	Babel server inbox <babel.server-inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	kitlo
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Udo Walker

2010-06-15 05:24:49 EDT

Build Identifier: I20100603-1500

At the moment each plugin has for each language a different fragment bundle jar. If you have 1000 plugins and 10 languages to support you normally add all fragments to the distribution which means for the packaging method you use you have to add 10000 (!!!) extra bundles which is in every step from development to execution very slowly to handle.

It would be much better to package some of the languages together in 1 fragment. E.g. all european languages in 1 fragment. So for the example above you would need only 1000 extra fragment bundles to support all european languages.

Reproducible: Always

Steps to Reproduce:
The structure of such a composite language fragment could be like this.

fragment_root:
src/<package>/messages_de.properties
src/<package>/messages_en.properties
src/<package>/messages_fr.properties
src/<package>/messages_it.properties
src/<package>/messages_tr.properties
plugin_de.properties
plugin_en.properties
plugin_fr.properties
plugin_it.properties
plugin_tr.properties
fragment.xml

Comment 1 Udo Walker

2010-06-15 05:27:27 EDT

Especially to handle a target platform with 3000 fragment bundles only for adding the different languages is very very slowly, even on a fast machine.

Comment 2 Udo Walker

2010-12-20 12:13:01 EST

Is there a need to change this?

Comment 3 Denis Roy

2010-12-21 14:45:37 EST

I'll move this to server since 'plugins' refers to the Editor plugins that Babel has (and for which we have no active committers).