^M present in liquibase unix running file (from jar on maven repo)
Description
Environment
linux
Attachments
1
- 28 Jul 2013, 11:03 AM
Activity
Show:
Adrien SALES August 28, 2013 at 9:58 PM
That seems to be good news. i'll test that : if it does not the job, i'll try to find a trick to make it through maven, around resource plugin, but your approach looks much cleaner.
Nathan Voxland August 28, 2013 at 8:46 PM
Tried that but git complained since it is trying to "fix" line endings for me on windows.
However, I added a setting that seems to force that file to checkout with linux line endings for me now, so I think should be fixed now
Adrien SALES August 28, 2013 at 7:51 PM
Why not trying to dos2unix the source liquibase file and to commit it, it should do the trick.
Nathan Voxland August 28, 2013 at 4:03 PM
I'm not enough of a maven guy to know off hand how to fix it in the .jar. Anyone have an idea?
Adrien SALES July 28, 2013 at 11:12 AM
Same behavior on a locally built jar, on the 3.0.3.
Fixed
Details
Details
Reporter
Adrien SALES
Adrien SALESComponents
Fix versions
Priority
MajorCreated July 28, 2013 at 11:03 AM
Updated August 28, 2013 at 9:58 PM
Resolved August 28, 2013 at 8:46 PM
Here are the steps to reproduce :
mkdir /tmp/test
cd /tmp/test/
wget http://repo1.maven.org/maven2/org/liquibase/liquibase-core/3.0.2/liquibase-core-3.0.2.jar
ls
unzip liquibase-core-3.0.2.jar
ls
cd dist/
ls
chmod u+x liquibase
./liquibase
bash: ./liquibase: /bin/sh^M: bad interpreter: No such file or directory
The workaround is to pass a dos2unix commande, but it's not clean. This behavior is only available on the jar that comes from the maven repo : official build is perfectly fine.