[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [tycho-user] [Fixed] Problems with i18n of 'eclipse-repository' projects
|
Ok, problem found.
Unlike to the 'eclipse-feature' build the category.xml file will be copied to the target folder in 'eclipse-repository' builds. Property files are not carried along and the p2 publisher can't find them and so can't include the properties into the content.xml.
Workaround: Simply copy the site.properties files to the target folder. I think it's worth to be done automatically by Tycho?!
<build>
<plugins>
<plugin>
<artifactId>maven-resources-plugin</artifactId>
<version>2.5</version>
<executions>
<execution>
<id>copy-site-properties</id>
<phase>process-resources</phase>
<goals>
<goal>copy-resources</goal>
</goals>
<configuration>
<outputDirectory>${project.build.directory}</outputDirectory>
<resources>
<resource>
<directory>${basedir}</directory>
<includes>
<include>site*.properties</include>
</includes>
</resource>
</resources>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
2011/8/7 Bernd Vogt
<berndvogt@xxxxxx>
Hello,
what is the correct way to i18n the labels of my category.xml files in 'eclipse-repository' projects? I'm familiar with the basic i18n mechanisms of eclipse, but since I switched from 'deployable features' to 'eclipse-repository', I have problems.
When I use a category.xml along with site_XX.properties files within a 'eclipse-feature' project and configure it to execute the goal 'category-p2-metadata', everything works fine. The generated content.xml will contain the language properties and in the 'Install new Software' wizard of eclipse shows the labels f my categories in the appropriate language. But using 'eclipse-repository' the language properties are missing and the labels in the wizard are broken..
Any ideas?
Kind regards,
Bernd