You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would work fine in 3.10.2 but when using 4.4.3 it doesn't (we've had to add to the classpath property by the way, to ensure we could run absolute paths in the CLI). In 4.4.3 it says that it cannot find items/data.csv. We also updated the XSD schemaLocation to 4.4. I only got it to work when removing relativeToChangelogFile="true" and using a file path starting from the current working directory.
I've seen that in 4.4.3 there were some fixes related to SQL files and relativeToChangelogFile property, I'm not sure whether there is still some issue lying around in the loadUpdateData.
Additional note: we have logicalFilePath set in our changelogs.
Thank you
The text was updated successfully, but these errors were encountered:
Hi @DiogoParrinha Thanks for writing up this issue. We have changed quite a bit to fix file path issues between how 3.x works and 4.x works. We will add this to the list of issues that we are processing.
Our file structure is:
-- project/
--- subchangelog.xml (included by master.xml)
--- items/
---- data.csv
master.xml
includes the subchangelog.xmlExample changeset in
subchangelog.xml
:This would work fine in 3.10.2 but when using 4.4.3 it doesn't (we've had to add to the classpath property by the way, to ensure we could run absolute paths in the CLI). In 4.4.3 it says that it cannot find
items/data.csv
. We also updated the XSD schemaLocation to 4.4. I only got it to work when removingrelativeToChangelogFile="true"
and using a file path starting from the current working directory.I've seen that in 4.4.3 there were some fixes related to SQL files and relativeToChangelogFile property, I'm not sure whether there is still some issue lying around in the loadUpdateData.
Additional note: we have logicalFilePath set in our changelogs.
Thank you
The text was updated successfully, but these errors were encountered: