Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TMP and TEMP, etc... returns "null" string #127

Closed
pchuong opened this issue Mar 5, 2014 · 1 comment
Closed

TMP and TEMP, etc... returns "null" string #127

pchuong opened this issue Mar 5, 2014 · 1 comment
Labels
Milestone

Comments

@pchuong
Copy link

pchuong commented Mar 5, 2014

Hi,

It looks like the latest nodeclipse broke the process.env (PATH, TEMP, TMP, and SystemDrive) while debugging a nodejs process. These environment variables return "null" string literal instead of null (or undefined).

From this file, line 275 - line 278, it should check whether these java environment variables is not equals to null before adding it into the array.

https://github.com/Nodeclipse/nodeclipse-1/blob/master/org.nodeclipse.debug/src/org/nodeclipse/debug/launch/LaunchConfigurationDelegate.java#L275-278

Regards,
Patrick

@paulvi paulvi added the bug label Mar 6, 2014
@paulvi paulvi closed this as completed in d910337 Mar 6, 2014
@paulvi
Copy link
Member

paulvi commented Mar 6, 2014

Yes, indeed. I had the same issue in Maven plugin, but overlooked to fix for Node.js.
It is fixed now. You can compile sources or wait 0.12 release in the end of March

@paulvi paulvi added this to the 0.12 milestone Mar 6, 2014
paulvi added a commit to Nodeclipse/www.nodeclipse.org that referenced this issue Mar 6, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants