Eclipse Community Forums: Buckminster » internalization build

Help

Home

Home » Archived » Buckminster » internalization build

Show: Today's Messages :: Show Polls :: Message Navigator

internalization build [message #531315]

Tue, 04 May 2010 14:29

Alex Kravets

Messages: 561
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

Report message to a moderator

Re: internalization build [message #531368 is a reply to message #531315]

Tue, 04 May 2010 15:36

Henrik Lindberg

Messages: 2509
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

Report message to a moderator

Re: internalization build [message #531647 is a reply to message #531368]

Wed, 05 May 2010 16:48

Alex Kravets

Messages: 561
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

Report message to a moderator

Re: internalization build [message #531657 is a reply to message #531315]

Wed, 05 May 2010 17:38

Alex Kravets

Messages: 561
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.

Report message to a moderator

Re: internalization build [message #531731 is a reply to message #531657]

Wed, 05 May 2010 23:36

Henrik Lindberg

Messages: 2509
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

Report message to a moderator

Re: internalization build [message #531749 is a reply to message #531731]

Thu, 06 May 2010 02:27

Alex Kravets

Messages: 561
Registered: November 2009

Senior Member

Yes, scratch my last comment, this is exactly how it's suppose to work.

thanks,
Alex

Report message to a moderator

Re: internalization build [message #531938 is a reply to message #531749]

Thu, 06 May 2010 14:39

Alex Kravets

Messages: 561
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

Report message to a moderator