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

[Snjezana Peco (JIRA)]

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

Snjezana Peco commented on JBIDE-16351:
---------------------------------------

> Can this explain why wildfly is so slow to build ?

FixClasspathContainer slows down building a Maven Java project (including wildfly), but not as much as it is Andre's issue (20 minutes).

> 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 ?

JBIDE-7011
I don't think that is relevant anymore, but will test WFK seam 2 maven projects. Do you mean wfk 2.4.0 seam demo?

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

I think we can remove this configurator in the maintenance branch too.

                
> 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).

--
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