[jbosstools-issues] [JBoss JIRA] (JBIDE-18097) Update project configuration is not enough to update eclipse settings - need to delete .project/.classpath and reimport

[Jeff MAURY (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-18097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff MAURY updated JBIDE-18097:
-------------------------------
    Fix Version/s: 4.6.x
                       (was: 4.5.x)


> Update project configuration is not enough to update eclipse settings - need to delete .project/.classpath and reimport
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-18097
>                 URL: https://issues.jboss.org/browse/JBIDE-18097
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: maven
>            Reporter: Max Rydahl Andersen
>            Assignee: Fred Bricon
>             Fix For: 4.6.x
>
>
> I'm finding this more and more worrisome so wanted to record it.
> When trying to fix JBDS-2847 or rather fix javee7-samples to be able to import easily we easily end up with a set of projects where settings are wrong.
> I updated the parent pom to not have the groovy compiler enabled and ran update project configuration - and the changes regarding source paths did not take effect.
> Only way to fix was to nuke all files and reimport.
> can this be true ? no way to "force" an update ?



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)