Well actually I'm rebuilding it each time but I did not expect its sha1/md5 to change each time. But it makes sense after some thought: some config properties, based on the timestamp, are included in the jar thus generating a new checksum each time. Now, I will base my verification on the git sha1.
Thank you a lot really. Le mardi 21 avril 2015 00:46:33 UTC+2, Brian Coca a écrit : > > so I'm guessing the problem is the jar and not the init script you > copy, are you sure you are not rebuilding the jar? some ways of > building them can change the file and it's md5/sha1 even when there is > no change in code. > > > > > -- > Brian Coca > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/0d49be89-2755-4582-bf5f-010413a69554%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
