JBIDE-15322 was caused due to a malformed .project file. It would be nice to have an option when updating (or importing) the Maven project to allow regeneration of these files (.project, .classpath, .settings/).

Here is a chat transcript from alexeykazakov and rhn-support-ggastald in the #jbosstools channel:

<akazakov> can you remove this project, pull it again and re-import?
<gastaldi> I deleted my .project, .classpath, .settings and .external-builders and it works now
<gastaldi> is it possible to add an option to regenerate these files on import ?
<gastaldi> this may be garbage from older m2 versions
<akazakov> when you import the project as a maven project then these files should be generated
<gastaldi> in my case these files already existed
<gastaldi> but they were screwed
<akazakov> yes the maven tooling just updates them if they exist.
<akazakov> it can't remove the old one since it can have some custom settings you don't want to loose
<gastaldi> I know, that's why I asked for an option to regenerate it
<gastaldi> I think that the majority of use-cases will not have any custom settings
<akazakov> ah. got it. I'm not sure.. Maybe Fred knows anything about it.
<gastaldi> is he on PTO ?
<akazakov> yes
<gastaldi> ok, perhaps it may be worth talking with him about this, since it may save some headaches in the future
<akazakov> yes. you are right
<gastaldi> thanks for your time akazakov
<akazakov> no problem )
<akazakov> can you create an issue about the option to regenerate .project .classpath etc when importing a maven project? Just not to forget it when Fred is back
<gastaldi> ok