Show Posts
1
General Board / Import from source file(s) generates orphans
« on: January 12, 2012, 04:11:57 am »
We've embarked on documentation maintenance project and are going through our code base and the project models updating everything.
Our standard procedure is to delete all the old classes in a particular package and then Import from source file(s) (Java). However, recently that action does not place the generated classes in the package selected. The classes are created but they're orphaned, without a parent package.
Why is this happening and how can we fix this? We do not want to roll back to our initial state as that will lose many hundreds of hours of work already done.
Note: We keep our project in SVN and have most of our packages locked. Procedure is to unlock the particular package we're working on (the bottom most level) and do the import.
Thanks for your help!
Our standard procedure is to delete all the old classes in a particular package and then Import from source file(s) (Java). However, recently that action does not place the generated classes in the package selected. The classes are created but they're orphaned, without a parent package.
Why is this happening and how can we fix this? We do not want to roll back to our initial state as that will lose many hundreds of hours of work already done.
Note: We keep our project in SVN and have most of our packages locked. Procedure is to unlock the particular package we're working on (the bottom most level) and do the import.
Thanks for your help!