On a project based on the old ERP model we face problems when working more developers on different changes simultaneously.
Each change is developed in a separate branch. Changes are typically made in a different packages and have scripts.
That causes problems when doing deployment later into production environment, where unmet dependency error raise.
A possibility to overcome this problem is to move all the deployment scripts to one dedicated package. However, architect is not prepared for it. When generating scripts from wizards (e.g. Create lookup field including entity) it always generates scripts to the current package. So it needs to be moved later manually. Unfortunately, the actual move is very cumbersome. It needs to be done one by one (firstly move into different package, then move to a different folder). It is not possible to see, in which package the deployment script is located and check whether it was a successfull operation. Therefore, it’s easier to move packages in the filesystem, which is not the proper way and can’t be done without a deep insight into model.
We would need to move it more quickly - e.g. add a possibility to multi-select items and move it together to another package. Also be able to move scripts between directories in a bulk manner . Other option is to modify wizards, so that a user can tell a target of creating the scripts. At least, we need to see in which package the script is currently located which is standard in all other model elements.