Eclipse Community Forums: Equinox » passing artifact location to jvm argument

Help

Home

Home » Eclipse Projects » Equinox » passing artifact location to jvm argument

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

passing artifact location to jvm argument [message #129737]

Wed, 22 April 2009 21:01

Jonathan Albrecht

Messages: 2
Registered: July 2009

Junior Member

I have a binary artifact which is the standalone native engine of my app.
I have it zipped up. I have a touchpoint that unzips it at install time.
That part is working. I need to set a jvm argument so that the java
plugins portion of the product can find where the engine was installed.
I'd like to do something like I have outlined below where I add a jvmArg
which points to the artifact that I just unzipped. In 3.4, I just end up
with the line:

-Dengine.home=@artifact

in the eclipse.ini. Is there a way I can get the installed location of the
artifact to a jvm arg in 3.4? How about 3.5?

<artifacts size='1'>
<artifact classifier='binary' id='engine.win32.x86'
version='1.0.0' />
</artifacts>

<touchpoint
id='org.eclipse.equinox.p2.osgi'
version='1.0.0' />
<touchpointData size='1'>
<instructions size='3'>
<instruction key='zipped'>
true
</instruction>
<instruction key='configure'>
addJvmArg(jvmArg:-Dengine.home=@artifact);
</instruction>
<instruction key='unconfigure'>
removeJvmArg(jvmArg:-Dengine.home=@artifact);
</instruction>
</instructions>
</touchpointData>

Jon

Report message to a moderator

Re: passing artifact location to jvm argument [message #129836 is a reply to message #129737]

Thu, 23 April 2009 15:10

Andrew Niefer

Messages: 990
Registered: July 2009

Senior Member

The "@artifact" needs to be specifically handled by the action you are
trying to use it with.

It looks like the addJvmArg actions does not handle it (though the
addProgramArg does). You should raise a bug if you want this.

-Andrew

Jonathan Albrecht wrote:
> I have a binary artifact which is the standalone native engine of my
> app. I have it zipped up. I have a touchpoint that unzips it at install
> time. That part is working. I need to set a jvm argument so that the
> java plugins portion of the product can find where the engine was
> installed. I'd like to do something like I have outlined below where I
> add a jvmArg which points to the artifact that I just unzipped. In 3.4,
> I just end up with the line:
>
> -Dengine.home=@artifact
>
> in the eclipse.ini. Is there a way I can get the installed location of
> the artifact to a jvm arg in 3.4? How about 3.5?
>
>
> <artifacts size='1'>
> <artifact classifier='binary' id='engine.win32.x86' version='1.0.0' />
> </artifacts>
>
> <touchpoint
> id='org.eclipse.equinox.p2.osgi'
> version='1.0.0' />
> <touchpointData size='1'>
> <instructions size='3'>
> <instruction key='zipped'>
> true
> </instruction>
> <instruction key='configure'>
> addJvmArg(jvmArg:-Dengine.home=@artifact);
> </instruction>
> <instruction key='unconfigure'>
> removeJvmArg(jvmArg:-Dengine.home=@artifact);
> </instruction>
> </instructions>
> </touchpointData>
>
> Jon
>

Report message to a moderator