Re: [babel-dev] Problem exporting

[Kit Lo <kitlo@xxxxxxxxxx>]

Babel collects all the files for translation
by scanning for Java properties files in the CVS/SVN repositories defined
by the map files for the projects. The test plugins were defined in the
map files for the Eclipse project and therefore we had the Java properties
files in the plugins extracted for translation.

In the Babel p2 repository language
pack update sites we produced, we added the "non-greedy" attribute
to the plugins. That should avoid any error/warning messages during loading.

As you have figured out, if you want
to re-package the language packs for your own RCP app, you should modify
the NL features to include only the available plugins to avoid any error/warning
messages.

The Babel project recently added a plugin
exclusion capability when defining the map files or update site for the
projects. With the cooperation of the project committers, we can add those
test plugins to the exclude list. Then the Java properties files in the
test plugins will not be extracted for translation in the future.

Regards,
Kit Lo
IBM Eclipse SDK Globalization Technical Lead
Eclipse Babel Project Co-lead

From:	Aritz Dávila <aritz.davila@xxxxxxxx>
To:	Babel committers mailing list <babel-dev@xxxxxxxxxxx>
Date:	03/03/2010 05:30 AM
Subject:	Re: [babel-dev] Problem exporting
Sent by:	babel-dev-bounces@xxxxxxxxxxx

---

Also, can anyone answer why the test plugins are included
in the final product?
-- 
Aritz Dávila
www.axios.es


On Tuesday 02 March 2010 03:56:31 pm Aritz Dávila wrote:
> Hi all,
> 
> I got the next problem exporting an application based on eclipse RCP:
> 
> I had include this feature on me workspace:
> 
> BabelLanguagePack-eclipse-de_3.5.0.v20091121043401.zip which contains
this
> plugin: org.eclipse.ant.tests.core.nl_de_3.5.0.v20091121043401.jar
> 
> But when I try to export the product or the feature alone, I get this
>  error:
> 
>   Unable to find plug-in:
> org.eclipse.ant.tests.core.nl_de_3.5.0.v20091121043401. Please check
the
>  error log for more details.
> 
> That plugin exists, but eclipse can't reach it.
> 
> Any ideas? or do I need to create a new feature, include all the
>  "available" plugins from the babelLenguagePack and
them export that new
>  feature?
> 
> Cya
> 


_______________________________________________
babel-dev mailing list
babel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/babel-dev