Eclipse Plugin - Endevor Types on Add

[Darren Morris]

We are early stages of adopting an IDE.   Running latest Compuware Topaz on Eclipse Photon with Endevor plugin version 18.0.2 (though in process of updating back-end and with that the plugin to suit - likely to 18.1.5).

After adding an element to a local project (retrieve), there have been occasions that when adding/updating back up to Endevor the Endevor Type defaults to the first Endevor Type it finds for that file extension and does allow change of the Endevor Type.  That is, it is trying to add/update to a Type that was not the Type retrieved, and we are unable to change it.

We have mapped a number of our Endevor Types to the same local file extension as that made sense to the eclipse editor.  Is there an issue in doing that or should all Endevor Types have a unique local file extension?  Should the Endevor Type field really be locked?

Thanks for any advice offered....

Darren

[Darren Morris]

2nd para should read:

After adding an element to a local project (retrieve), there have been occasions that when adding/updating back up to Endevor the Endevor Type defaults to the first Endevor Type it finds for that file extension and does NOT allow change of the Endevor Type. 

[Vaughn Marshall]

Hi Darren - this should not be happening - the plugin should retain information about the type it was retrieved from to the local project.   We've made quite a number of changes in the plugin since 18.0.2; can you advise if the issue is still happening in v18.1.5 once you upgrade?  If it is, it will be considered a defect and we should open a case.