[jbosstools-issues] [JBoss JIRA] (JBIDE-15324) Add an option to regenerate project files

[Fred Bricon (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-15324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798770#comment-12798770 ] 

Fred Bricon commented on JBIDE-15324:
-------------------------------------

I'm not overly thrilled about that idea, rather the opposite.
- This would require changes in m2e core, where the import logic is defined, before calling any configurators; and m2e ui, to enable that option 
- we can't know in advance what files to delete. The most common ones being .project, .classpath, .settings/. But other config files can be generated by eclipse plugins at the root of the project that would be ignored. Also blindly wiping .settings/ out would delete some config files for stuff not necessarily integrated with m2e, forcing users to reconfigure some projects settings manually after each import. And since m2e core knows nothing about JDT for instance, we would need to have a pluggable approach (extension points and all) to let each individual plugin from the m2e ecosystem tell what files to delete on import. 

Not sure we'd have much to gain from all that. And that idea would still need to be vetted by the m2e project lead which is another story... 
                
> Add an option to regenerate project files
> -----------------------------------------
>
>                 Key: JBIDE-15324
>                 URL: https://issues.jboss.org/browse/JBIDE-15324
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: maven
>            Reporter: George Gastaldi
>
> 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 [~akazakov] and [~gastaldi] in the #jbosstools channel:
> {quote}
> <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
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira