Eclipse Community Forums: Plugin Development Environment (PDE) » Product Export Wizard fails to replace target parameters in <launcher>.ini

Home » Eclipse Projects » Plugin Development Environment (PDE) » Product Export Wizard fails to replace target parameters in <launcher>.ini(Defective variable replacement mechanism?)

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

Product Export Wizard fails to replace target parameters in <launcher>.ini [message #538984]

Wed, 09 June 2010 09:21

Jörn Guy Süß

Messages: 320
Registered: July 2009
Location: Anstead, Brisbane, Queens...

Senior Member

I am building a product and export it using the product export wizard. the product has a single windows configuration, and the platform arguments are defined in the target definition that I use.

The product is exported correctly, including platform-specific fragments, but the variables in the <launcher>.ini file are not replaced with the values of the target definition. Consequently, the file looks like this:

-os
${target.os}
-ws
${target.ws}
-arch
${target.arch}
-nl
${target.nl}
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms40m
-Xmx512m

If I replace

${target.os}

with

win32

${target.ws}

with

win32

${target.arch}

with

x86

${target.nl}

with

en_AU

my product runs immediately.

These are the values specified in my current target definition.

Maybe this is due to the fact that my launcher is called

mint

, not

eclipse

.

Questions:

Has anyone experienced this phenomenon before?
Can anyone point me to the place where the behaviour of the export wizard is defined, so I can debug?

Report message to a moderator

Re: Product Export Wizard fails to replace target parameters in <launcher>.ini [message #539084 is a reply to message #538984]

Wed, 09 June 2010 15:20

Andrew Niefer

Messages: 990
Registered: July 2009

Senior Member

The export process has no support for replacing any arguments from
the .product file. (Except for .qualifier in the product version).

Those os/ws/arch/nl arguments are not required and should not have been in
the .product file to start with. See bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=278598

-Andrew

Joerr Guy Suess wrote:

> I am building a product and export it using the product export wizard. the
> product has a single windows configuration, and the platform arguments are
> defined in the target definition that I use.
>
> The product is exported correctly, including platform-specific fragments,
> but the variables in the <launcher>.ini file are not replaced with the
> values of the target definition. Consequently, the file looks like this:
>
>
> -os
> ${target.os}
> -ws
> ${target.ws}
> -arch
> ${target.arch}
> -nl
> ${target.nl}
> -vmargs
> -Dosgi.requiredJavaVersion=1.5
> -Xms40m
> -Xmx512m
>
>
>
> If I replace
> ${target.os} with win32
> ${target.ws} with win32
> ${target.arch} with x86
> ${target.nl} with en_AU
> my product runs immediately.
>
> These are the values specified in my current target definition.
>
> Maybe this is due to the fact that my launcher is called mint, not
> eclipse.
>
> Questions:
>
>
> Has anyone experienced this phenomenon before?
> Can anyone point me to the place where the behaviour of the export wizard
> is defined, so I can debug?

Report message to a moderator

Re: Product Export Wizard fails to replace target parameters in <launcher>.ini [message #539203 is a reply to message #539084]

Wed, 09 June 2010 22:57

Jörn Guy Süß

Messages: 320
Registered: July 2009
Location: Anstead, Brisbane, Queens...

Senior Member

Top answer! Worked like a charm! Cool

Feels like there is a fundamental article to be written here, beyond your nice blogpost on delta pack.

(I tried delta pack as well, but ended up with a consistency error between launcher plugin version and delta pack... There is always somethng!)

Report message to a moderator

Re: Product Export Wizard fails to replace target parameters in <launcher>.ini [message #605969 is a reply to message #539084]

Wed, 09 June 2010 22:57

Jörn Guy Süß

Messages: 320
Registered: July 2009
Location: Anstead, Brisbane, Queens...

Senior Member

:) Top answer! Worked like a charm! 8)
Feels like there is a fundamental article to be written here, beyond your nice blogpost on delta pack.

(I tried delta pack as well, but ended up with a consistency error between launcher plugin version and delta pack... There is always somethng!)

Report message to a moderator

Previous Topic:	org.eclipse.pde.ui.samples contribution
Next Topic:	p2-enabled PDE build fails when p2.category.definition is set (seemingly valid categories.xml file)

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 06:53:07 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter