gmitter-ef opened a new issue, #8800: URL: https://github.com/apache/hop/issues/8800
### Apache Hop version? 2.18, 2.19 ### Java version? OpenJDK 21 ### Operating system Windows ### What happened? In any sufficiently big project, execute workflow with a "Copy files" transform in this way: <img width="400" alt="Image" src="https://github.com/user-attachments/assets/8e4d41c7-f73e-42e2-bcaf-64de3d486a78"; /> and the settings <img width="360" height="273" alt="Image" src="https://github.com/user-attachments/assets/cc564356-d78c-4a09-8966-4b6b026a10fb"; /> In 2.16, the whole project gets copied into "copy", but *there is NO `${PROJECT_HOME}/copy/copy`* (and files/folders therein). This is the behaviour that was built upon in one of our projects (unfortunately). In 2.18/2.19 however, also the destination *`copy` folder gets copied into `${PROJECT_HOME}/copy`*, resulting in a doubly copied files/folders <img width="622" height="503" alt="Image" src="https://github.com/user-attachments/assets/4ed5c1e0-930f-4f20-942e-2033a29de515"; /> Note that the size of the projects might make a difference: in a very small project (e.g. `default`) I could not reproduce the difference, resulting in the situation that no `copy/copy` folder was greated in 2.18/2.19. Note also that in case of a big project in 2.18/2.19 _not all files/folders_ of `${PROJECT_HOME}` are copied to `${PROJECT_HOME}/copy/copy` (so the contents of `${PROJECT_HOME}/copy/copy` is not complete), whereas `${PROJECT_HOME}/copy` contains the complete list of files/folders that are also in `${PROJECT_HOME}`. I understand that having a destination that is a subfolder of the source is kind of problematic, but the behaviour should be consistent over the different versions (me personally preferring the behaviour 2.16 shows). ### Issue Priority Priority: 2 ### Issue Component Component: Actions -- 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]
