History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: CIB-1268
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: Unassigned
Reporter: James French
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Pulse

local resources only turned into environment variables if resource defined at project scope

Created: 01/Oct/07 10:54 AM   Updated: 17/Oct/07 09:11 AM
Component/s: Local build
Affects Version/s: 1.2.35
Fix Version/s: 1.2.38


 Description  « Hide
When using the local build engine resource properties are only turned into PULSE_* environment variables if the resource is defined at project level.

If I have the following local resource file:

<resources>
  <resource name="doxygen"
        <property name="doxygen.bin" value="C:\\Program Files\\doxygen\\bin\\doxygen.exe"/>
  </resource>
</resources>

then this doesn't define PULSE_DOXYGEN_BIN:

<project defaultRecipe="doxygen">
  <recipe name="doxygen">
    <resource name="doxygen"/> <---- If this is defined inside <recipe>, PULSE_DOXYGEN_BIN is not defined
    <executable name="Build doxygen" exe="${ruby.bin}">
      <arg>common/doxygen-internal/build.rb</arg>
    </executable>
  </recipe>
</project>

whereas this causes it to get defined.

<project defaultRecipe="doxygen">
    <resource name="doxygen"/> <---- If resource placed here, PULSE_DOXYGEN_BIN is defined
    <recipe name="doxygen">
      <executable name="Build doxygen" exe="${ruby.bin}">
        <arg>common/doxygen-internal/build.rb</arg>
      </executable>
  </recipe>
</project>

Also, as far as I can tell putting <resource> at <project> level is an undocumented feature.

 All   Comments   Change History      Sort Order:
jason - 03/Oct/07 02:46 PM
Hi James,

This is a very strange one. I will need to create a test case and get back to you.

Daniel Ostermeier - 17/Oct/07 09:11 AM
resolved in 3841 and 3842. The problem was a) the global scope was being used to look up resources, not the scope used by the command, and b) references were not working up the scope hieararchy