After further tests it appears that lock/unlock works, but it's not very useful, since:
1) developer1 is locking some package
2) developer2 can easly change anything in that package
3) developer2 is making huge changes somewhere else
4) developer2 wants to commit, but he can't do that, cause one package is locked. After changes made in 3) he can't go back with changes made in 2)
5) only solution now for developer1 is to unlock the file and let developer2 send commit with package which will be conflicted with local changes made on developer1's computer
For me, it should work like:
2) somehow developer2 can download this information, so the package is really locked and untouchable
3) everyone's happy :)
Cheers
Jakub Tutaj
Neoprimus.com
To use the full functionality of this web site, JavaScript needs to be turned on.
For best results, use the Firefox browser..
Copyright © 2003-2017 - Tersus Software Ltd., All rights reserved. Terms of Use License Graphic design by EmaraDesign
