Hi,
At the end of createIdeBackend() there is a line:
ideBackend = createBackend(info, options, null);
createBackend:
private ErlideBackend createBackend(final RuntimeInfo info,
final Set<BackendOptions> options, Map<String, String>
env)
throws BackendException {
ILaunchConfiguration launchConfig = getLaunchConfiguration(info,
options);
ILaunch launch;
try {
launch = launchConfig.launch(ILaunchManager.RUN_MODE,
new NullProgressMonitor(), false,
false);
} catch (CoreException e) {
e.printStackTrace();
return null;
}
ErlideBackend b = createBackend(info, options, launch, env);
return b;
}
so launchConfig.launch is called and then createBackend is called.
Or maybe I have an old version of code (I haven't merged with 'next' branch for
few days)?
Are you sure that that this line does the job:
launch = launchConfig.launch(ILaunchManager.RUN_MODE, new
NullProgressMonitor(), false, false);
In RuntimeInfo.getCmdLine I found this:
final boolean globalLongName = System.getProperty("erlide.longname",
"false").equals("true");
final String nameTag = useLongName || globalLongName ? "-name"
: "-sname";
What's that property? In my case it has null value (doesn't exist), useLongName
is set to false so last expression should give "-sname". Instead when I check
it in console (ps -ef | grep beam) I still see that node was started with
"-name".
regards,
Piotrek
----- "Vlad Dumitrescu" <vladd...@gmail.com> wrote:
> On Tue, Aug 24, 2010 at 13:13, Piotr Dorobisz
> <piotr.dorob...@erlang-solutions.com> wrote:
> > Hello,
> > I wrote method to create my own node (actually I did it very similar
> to BackendManager.getIdeBackend()). However, the problem is that this
> node is started with long name (-name parameter) instead of short one.
> It happens despite setting info.useLongName(false). What else can I
> do?
> > Btw, what's the way of saying that I want/don't want console? As I
> see you specify it in two places:
> > info.hasConsole(true), and using BackendOptions.NO_CONSOLE.
>
> Hi!
>
> Regarding the long vs short name, you're creating the backend the
> wrong way. When you call launchConfig.launch, this does all the work
> and then you try to create the backend again, manually, which calls
> launchConfig.launch again. In createIdeBackend, there's no
> launchConfig involved, you should do likewise.
>
> Regarding the console option, do it like in createIdeBackend and set
> only the options.
> The reason for these to be in two places are historical. It's good
> that you point out these issues, we're used to the way it is...
>
> regards,
> Vlad
------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users
worldwide. Take advantage of special opportunities to increase revenue and
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Erlide-devel mailing list
Erlide-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/erlide-devel
