Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » --launcher.ini doesn't work in Run Configuration
--launcher.ini doesn't work in Run Configuration [message #61861] Fri, 15 May 2009 00:33 Go to next message
Eclipse UserFriend
Originally posted by: maggie.eclipse.gmail.com

Hi,

I want to specify a non default eclipse.ini file for the testing eclipse
launched by a Run config. And this is the eclipse.ini used by the target
platform as well.

However, specifying the --launcher.ini option in the "Program arguments"
on the Arguments tab of the run configuration's doesn't make the testing
eclipse pick up the configurations from the specified eclipse.ini file.

I can see the "--launcher.ini ...." line in the
Help->About->Configuration Details but not the contents from the .ini
files (such as the vmargs).

The "--launcher.ini" works if used in the CLI to launch eclipse from an
xterm.

How did others make the testing Eclipse pick up a specific eclipse.ini file?

Thanks
Maggie
Re: --launcher.ini doesn't work in Run Configuration [message #62748 is a reply to message #61861] Fri, 22 May 2009 19:50 Go to previous message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
The --launcher.ini argument is used by the eclipse executable to find
the eclipse.ini. When you running a launch config inside eclipse, it
does not use the eclipse executable, but is instead starting java directly.

The only way I know to get it to read the --launcher.ini would to
instead use something like the CDT to start the eclipse executable. You
would need to pass vm arguments to tell it to accept a java debugger,
you end up with 2 debuggers on the process, the CDT and the JDT. The
arguments for this would be "-vmargs -Xdebug -Xnoagent
-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=800 0 "
When the vm is started it will wait for you to attach a java debugger.

You would lose the self hosting of the java code from your workspace
when you do this. To get that back you would need to pass "-dev
/path/to/dev.properties". Start a normal self hosted workspace and look
at the configuration details to see what that looks like. You may also
need to set the vm system property "eclipse.pde.launch=true" for PDE to
be happy.


Maggie wrote:
> Hi,
>
> I want to specify a non default eclipse.ini file for the testing eclipse
> launched by a Run config. And this is the eclipse.ini used by the target
> platform as well.
>
> However, specifying the --launcher.ini option in the "Program arguments"
> on the Arguments tab of the run configuration's doesn't make the testing
> eclipse pick up the configurations from the specified eclipse.ini file.
>
> I can see the "--launcher.ini ...." line in the
> Help->About->Configuration Details but not the contents from the .ini
> files (such as the vmargs).
>
> The "--launcher.ini" works if used in the CLI to launch eclipse from an
> xterm.
>
> How did others make the testing Eclipse pick up a specific eclipse.ini
> file?
>
> Thanks
> Maggie
Re: --launcher.ini doesn't work in Run Configuration [message #597789 is a reply to message #61861] Fri, 22 May 2009 19:50 Go to previous message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
The --launcher.ini argument is used by the eclipse executable to find
the eclipse.ini. When you running a launch config inside eclipse, it
does not use the eclipse executable, but is instead starting java directly.

The only way I know to get it to read the --launcher.ini would to
instead use something like the CDT to start the eclipse executable. You
would need to pass vm arguments to tell it to accept a java debugger,
you end up with 2 debuggers on the process, the CDT and the JDT. The
arguments for this would be "-vmargs -Xdebug -Xnoagent
-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=800 0 "
When the vm is started it will wait for you to attach a java debugger.

You would lose the self hosting of the java code from your workspace
when you do this. To get that back you would need to pass "-dev
/path/to/dev.properties". Start a normal self hosted workspace and look
at the configuration details to see what that looks like. You may also
need to set the vm system property "eclipse.pde.launch=true" for PDE to
be happy.


Maggie wrote:
> Hi,
>
> I want to specify a non default eclipse.ini file for the testing eclipse
> launched by a Run config. And this is the eclipse.ini used by the target
> platform as well.
>
> However, specifying the --launcher.ini option in the "Program arguments"
> on the Arguments tab of the run configuration's doesn't make the testing
> eclipse pick up the configurations from the specified eclipse.ini file.
>
> I can see the "--launcher.ini ...." line in the
> Help->About->Configuration Details but not the contents from the .ini
> files (such as the vmargs).
>
> The "--launcher.ini" works if used in the CLI to launch eclipse from an
> xterm.
>
> How did others make the testing Eclipse pick up a specific eclipse.ini
> file?
>
> Thanks
> Maggie
Previous Topic:P2 generator - How to specify feature categories ?
Next Topic:View menuContribution always disabled
Goto Forum:
  


Current Time: Sun Jul 25 22:01:34 GMT 2021

Powered by FUDForum. Page generated in 0.02063 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top