dsanderbi opened a new issue, #8187:
URL: https://github.com/apache/hop/issues/8187
### Apache Hop version?
2.19.0
### Java version?
21
### Operating system
macOS
### What happened?
When using Apache Hop project variables to shorten and centralize file
paths, the variables are correctly resolved when configuring Environment
Settings files through the UI. However, the same variables are not resolved
when the workflow or pipeline is executed.
For example, the project configuration defines variables such as:
```json
{
"metadataBaseFolder" : "${PROJECT_HOME}/metadata",
"unitTestsBasePath" : "${PROJECT_HOME}",
"dataSetsCsvFolder" : "${PROJECT_HOME}/datasets",
"enforcingExecutionInHome" : true,
"autoExportMetadataFilename" : "metadata.json",
"parentProjectName" : "default",
"config" : {
"variables" : [ {
"name" : "CONFIG_HOME",
"value" : "${PROJECT_HOME}/config"
} ]
}
}
```
When selecting a file through the Browse functionality in the Environment
Settings, Apache Hop uses the project variable name to reference the selected
file instead of `${PROJECT_HOME}/config`
<img width="512" height="166" alt="Image"
src="https://github.com/user-attachments/assets/0ba4b574-367a-45a5-b337-d27269a8a9fe";
/>
When the workflow or pipeline is started, Apache Hop fails to resolve
${CONFIG_HOME} and therefore cannot find the referenced file to load its
variables.
You need to use `${PROJECT_HOME}/config` to get the variables from json.
### Issue Priority
Priority: 2
### Issue Component
Component: Hop Gui
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
