Deleting Issues, C++

[Nadya]

I use EA Version 7.0.817 (Build: 817) on C++ source code base.

I'm trying to update my project from source code and remove redundant classes from it.

When I do Import Source Directory command with Always delete option on, I expect the classes which don't exist in Source Code anymore to be deleted. It doesn't happen. They are not removed.
If I set on Prompt for action, there is no any list with classes to be deleted shown after.
It seems that everything was working in EA 6.5. At least I do remember I got a list with classes when Prompt for action was on.

Is it a bug or I'm simply doing something wrong?

Is there any other way to automatically remove redundant classes from the project?

I tried to do Merge with Visual Studio on a package, but it doesn't remove anything.

Thanks

[«Midnight»]

I'm just guessing but...

Have you moved the parent package within the project? Or have you moved the source code to another directory path?

AFAIK EA keeps track of the names and paths of each element when you first build the tree. I think it uses these to determine which model entity matches a given source code fragment.

[Nadya]

Yes, I moved the source code to another directory.
Then I updated GenFile field in t_object table.

Do I need to update anything else?

No new classes have been created after import, so I assumed I made all needed changes.

Is there any other way to change the source code path except updating the field?

[Paolo F Cantoni]

Is there any other way to change the source code path except updating the field?

Yes Nadya, look into Local Path variables - they are a much safer route to solving this type of problem.

HTH,
Paolo

[Nadya]

Thanks, Paolo! It helped.

Frankly speaking, I don't like to use EA application. It is not very handy

[Paolo F Cantoni]

Thanks, Paolo! It helped.

Frankly speaking, I don't like to use EA application. It is not very handy

Unfortunately, from our point of view - it's the best of a bad lot...  Because of it's database centric appraoch, we have been able to work around (albeit with a lot of effort) many of it's serious limitations.  This, of course, means we have avoided its Unique Interface...

The REAL worry is that it's not (really) getting better...  The fundamental problems don't appear to be being addressed.

Anyway, we live in hope...

Paolo