Community
Participate
Working Groups
From talking to Jason, the dependency graph builder is probably better off as a resource change listener (POST_CHANGE). That still leaves the question of why there are two separate builders from the same plugin instead of one builder.
*** Bug 102155 has been marked as a duplicate of this bug. ***
*** Bug 101307 has been marked as a duplicate of this bug. ***
To reiterate, this bug is about having a single plugin registering 3 builders instead of using 1 builder and the performance implications of that.
The dependency graph builder issue is being tracked under bug 102173. I believe the builders will be addressed in M6.
The two builders related ot the .deployable will be removed via this defect as soon as the server tools have the publish tasks ready. There needs to be two currenlty of them as they must surround the java builder. As for the dependency graph build as john indicated it will be handled *** This bug has been marked as a duplicate of 97756 ***
Closing duplicate.