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

propath option of PCTRun extends propath instead of replacing it #73

Closed
GoogleCodeExporter opened this issue Mar 28, 2015 · 2 comments
Closed

Comments

@GoogleCodeExporter
Copy link


What steps will reproduce the problem?
  1. define os environment variable propath
  2. create PCT run task to show propath (e.g. the attached showinfo.p)
  3. PROPATH is path set by task + os enviroment variable

What is the expected output? 
  Only the propath as set by the task

What do you see instead?
  The propath set by the task followed by the os-getenv("propath")


What version of the product are you using? 
  1.84

On what operating system?
  RHEL 5, OE 11.3

Please provide any additional information below.
I would expect the ouput of both commands to be the same

[CCE+cvb@cce-dev01 ant]$ PROPATH=/from_environment ant -f [CCE+cvb@cce-dev01 
ant]$ ant -f pct_issue_propath.xml

Original issue reported on code.google.com by cverbi...@gmail.com on 13 Oct 2014 at 11:30

Attachments:

@GoogleCodeExporter
Copy link
Author

Not needed, I can get the behaviour I expect  by adding a
 <env key="PROPATH" value="" /> 
to the run config.

Original comment by cverbi...@gmail.com on 13 Oct 2014 at 11:39

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Original comment by g.quer...@gmail.com on 10 Nov 2014 at 7:20

  • Changed state: Invalid
  • Added labels: ****
  • Removed labels: ****

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant