[jbosstools-issues] [JBoss JIRA] (JBIDE-16351) FixClasspathConfigurator isn't obliged in a newer m2e

Can this explain why wildfly is so slow to build ?

What jira introduced this configurator ? I assume it was requested in context of WFK Seam 2 maven projects which still are part of wfk so just wondering if it is still relevant for them ?

Should also consider removing this in maintanence branch if no use for it.

FixClasspathConfigurator isn't obliged in a newer m2e ----------------------------------------------------- Key: JBIDE-16351 URL: https://issues.jboss.org/browse/JBIDE-16351 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: maven Affects Versions: 4.2.0.Alpha1 Reporter: Snjezana Peco Assignee: Fred Bricon Fix For: 4.2.0.Alpha2 The FixClasspathConfigurator configurator has been introduced to solve https://issues.sonatype.org/browse/MNGECLIPSE-2433. The issue happens with a mavenized seam 2 project that has a flat layout structure. This configurator refreshes the old maven facade causing m2e to solve dependencies twice when ever building a project. It is the configurator for maven-compiler-plugin so it is called for every Java project. Since solving dependencies can take a long, it can slow down building projects up to 15% (depends on the project's dependencies) The solution: - removing the configurator. The issue is only related to the mavenized Seam projects that aren't included into project examples anymore and a required classpath entry can be manually added(newer m2 versions won't remove the existing classpath entry).