Hi all, interesting scenario here (and probably relevant as more sites transition to straight NaturalOne usage)
For the Hash Value in the
Natural Ant build cache_xxx.properties file
How is the hash value for the modules generated?
I say this, as there may be developers who are working in an ‘old’ style (Natural Studio / MF Editor), and rather then clobber their change with a redeploy (stow/cat) - I would rather ignore the rogue modules and leave it be - update the value in the cache properties file (to match the server version / updated from base library version) so it does not deploy.
I have been overcoming this problem in the past by running a Natural Ant Deploy without Stow or Upload on (to update the hash values).
For all those interested, It is easy to identify the modules intended for deployment (without performing the deploy) with the ‘checkts’ argument in the Natural Ant Deploy.
Unfortunately, unless everybody in a team is using modern ways of working (Git, NaturalOne, Jenkins) - there would be many sites with similar issues.