Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » internalization build
internalization build [message #531315] Tue, 04 May 2010 10:29 Go to next message
Alex Kravets is currently offline Alex Kravets
Messages: 370
Registered: November 2009
Senior Member
Hi,

I want to build my RCP application for a specific language, is there facility present in Buckminster to help with this or do I need to take care of this myself?

thanks,
Alex
Re: internalization build [message #531368 is a reply to message #531315] Tue, 04 May 2010 11:36 Go to previous messageGo to next message
Henrik Lindberg is currently offline Henrik Lindberg
Messages: 2498
Registered: July 2009
Senior Member
Afaik,
The steps are to create a p2 repository for the combinations you are
interested in (platforms, window systems, languages, etc.).
Then, when creating the product zip (or equivalent), create the product
with the appropriate constraints set.

Does that help?
- henrik

On 5/4/10 4:29 PM, Alex wrote:
> Hi,
>
> I want to build my RCP application for a specific language, is there
> facility present in Buckminster to help with this or do I need to take
> care of this myself?
>
> thanks,
> Alex
Re: internalization build [message #531647 is a reply to message #531368] Wed, 05 May 2010 12:48 Go to previous messageGo to next message
Alex Kravets is currently offline Alex Kravets
Messages: 370
Registered: November 2009
Senior Member
Thanks Henrik,

In my target platform I added the babel plugins for my language. When I build p2 site all the nl_ru plugins make it there, but when I create the actual product I only see org.eclipse.equinox.launcher.nl_ru plugin there. Any ideas what am I doing wrong?

thanks,
Alex
Re: internalization build [message #531657 is a reply to message #531315] Wed, 05 May 2010 13:38 Go to previous messageGo to next message
Alex Kravets is currently offline Alex Kravets
Messages: 370
Registered: November 2009
Senior Member
May be putting translated plugins in target platform is not the right way to go because regardless of target.nl setting it builds for all languages in target.
Re: internalization build [message #531731 is a reply to message #531657] Wed, 05 May 2010 19:36 Go to previous messageGo to next message
Henrik Lindberg is currently offline Henrik Lindberg
Messages: 2498
Registered: July 2009
Senior Member
On 5/5/10 7:38 PM, Alex wrote:
> May be putting translated plugins in target platform is not the right
> way to go because regardless of target.nl setting it builds for all
> languages in target.

Confused... don't you want all the language configurations in your
target platform to enable building results that are for different languages?

It is the step when you create the RCP application in installed form
(i.e. a ready to run zip) where you want to state the language that
should be used in the finished product.

Alternatively, you can run the director against the p2 repository and
produce an installation (i.e. "install") with any valid configuration.

Does this help?

- henrik
Re: internalization build [message #531749 is a reply to message #531731] Wed, 05 May 2010 22:27 Go to previous messageGo to next message
Alex Kravets is currently offline Alex Kravets
Messages: 370
Registered: November 2009
Senior Member
Yes, scratch my last comment, this is exactly how it's suppose to work.

thanks,
Alex
Re: internalization build [message #531938 is a reply to message #531749] Thu, 06 May 2010 10:39 Go to previous messageGo to next message
Alex Kravets is currently offline Alex Kravets
Messages: 370
Registered: November 2009
Senior Member
Henrik,

About my second question...

I changed my ant script to include target.nl parameter:
<java jar="${equinox.launcher.jar}" fork="true" failonerror="true" >
			<arg value="-application"/>
			<arg value="org.eclipse.equinox.p2.director"/>
			<arg value="-artifactRepository"/>
			<arg value="file:${repository}"/>
			<arg value="-metadataRepository"/>
			<arg value="file:${repository}"/>
			<arg value="-destination"/>
			<arg value="${destination}"/>
			<arg value="-bundlepool"/>
			<arg value="${destination}"/>
			<arg value="-profile"/>
			<arg value="${profile}"/>
			<arg value="-profileProperties" />
			<arg value="org.eclipse.update.install.features=true" />
			<arg value="-installIU"/>
			<arg value="${iu}"/>
			<arg value="-p2.os" />
			<arg value="${target.os}" />
			<arg value="-p2.ws" />
			<arg value="${target.ws}" />
			<arg value="-p2.arch" />
			<arg value="${target.arch}" />
			<arg value="-p2.nl" />
			<arg value="${target.nl}" />
			<arg value="-consoleLog"/>
			<jvmarg value="-Declipse.p2.data.area=${destination}/p2"/>
			<jvmarg value="-Declipse.p2.profile=${profile}"/>
		</java>


I am not sure if -p2.nl is the right parameter or even if this is the right place to put parameter, but when I run create.product action with target.nl=ru in supplied properties file only org.eclipse.equinox.launcher.nl_ru_3.5.0.v20091121043401 makes into plugins folder of the product. Why are other nl plugins don't make into the product?

thanks for your help,
Alex
Re: internalization build [message #531944 is a reply to message #531938] Thu, 06 May 2010 10:49 Go to previous message
Alex Kravets is currently offline Alex Kravets
Messages: 370
Registered: November 2009
Senior Member
Also, p2 repository is build with all nl plugins in place.
Previous Topic:XML weirdness in buckminster.cspex
Next Topic:team --> commit integration
Goto Forum:
  


Current Time: Tue Jul 22 19:46:57 EDT 2014

Powered by FUDForum. Page generated in 0.02216 seconds