It looks like the forum software totally mangled the display of your post - for the record here is what the error looked like:
Errors during build. Errors running builder 'Java Builder' on project 'sree'. org.eclipse.core.internal.registry.ConfigurationElementHandle cannot be cast to org.eclipse.jdt.core.compiler.CompilationParticipant org.eclipse.core.internal.registry.ConfigurationElementHandle cannot be cast to org.eclipse.jdt.core.compiler.CompilationParticipant Errors running builder 'Maven2 Project Builder' on project 'sree'. C:\workspace\sree\pom.xml (The system cannot find the file specified) C:\workspace\sree\pom.xml (The system cannot find the file specified)
I didn't see a screenshot attached to the post.
Hmm. That's an interesting set of error messages It looks like there is something interesting going on with the Eclipse runtime configuration. I think it would be a good idea if you could attach your Eclipse configuration and a zipped version of your troublesome project to this thread so I can try it out. I'd suggest that you restart Eclipse and use the -clean flag when doing so, to clear out the OSGi caches.
To get a copy of the Eclipse configuration, choose About Eclipse SDK, then press Configuration Details. You can then copy the report.
I looked at the configuration you sent (very helpful) and it seems that what we have here is a clash on the m2eclipse version that is being used by the JBI tools (which are older) and the m2eclipse that is being used by the FID tools (which is bang up to date).
It looks like those tools can't live together right now
So, how do we proceed? We'll have to remove the JBI tools features and
plugins so you can make progress on using FID capabilities. Here's how to
Close Eclipse, then go into the features directory in the Eclipse home. Remove the following directories:
Next, go into the plugins directory in the Eclipse home. Remove the following plugins (which may be directories or jar files):
com.iona.jst.jbi com.iona.jst.jbi.descriptor com.iona.jst.jbi.ui com.iona.jst.server.fuse.core com.iona.fuse.help com.iona.fuse.intro com.iona.fuse.activemq
Then, restart Eclipse, giving it the -clean option, so that it can clear out its caches.
In addition to the plug-ins Oisin had mentioned above there are a few more that you need to remove.
This is what's causing the problem.
org.maven.ide.eclipse (1.4.2) "Maven 2.0 integration" Active
org.maven.ide.eclipse.wtp (1.4.2) "Apache Maven WTP Integration" Active
While the M2Eclipse that was shipped with the earlier JBI tools is older than the currently required version for this release of the FID tools. It is versioned 1.4.2 and that's what's causing the problem.
Eclipse will use those plug-ins because of the greater version string.
These are the plug-ins we want active
org.maven.ide.eclipse (0.9.6.20080905-0917) "Maven Integration for Eclipse" Installed
org.maven.ide.eclipse.wtp (0.9.6.20080905-0917) "Maven Integration for Eclipse WTP" Installed
So just to be clear these are the features and plug-ins that need to be removed
Features: Version com.iona.fuse 1.4.2 com.iona.fuse.lite 1.4.2 com.iona.fuse.onlinehelp 1.4.2 Plug-ins com.iona.fuse.activemq 1.4.2 com.iona.fuse.help 1.4.2 com.iona.fuse.intro 1.4.2 com.iona.jst.jbi 1.4.2 com.iona.jst.jbi.descriptor 1.4.2 com.iona.jst.jbi.ui 1.4.2 com.iona.jst.server.fuse.core 1.4.2 org.eclipse.wst.common.modulecore 1.1.104.v20080404_fuse org.maven.ide.eclipse 1.4.2 org.maven.ide.eclipse.wtp 1.4.2