eclipse build problems

[starksm64]

In looking at the mdb destination type not being defaulted, I pulled down a new ejb3 trunk and update my eclipse m2 integration, but I still have the following build error in ejb3-core:

Severity and Description Path Resource Location Creation Time Id
The project was not built due to "Resource already exists on disk: '/jboss-ejb3-core/eclipse-target/classes/security/tst.policy'.". Fix the problem, then try refreshing this project and building it since it may be inconsistent jboss-ejb3-core Unknown 1218050054674 3004

Tried building clean and yet another project is complaining about an existing resource:

The project was not built due to "Resource already exists on disk: '/jboss-ejb3-interceptors/eclipse-target/tests-classes/supermethod/jboss-aop.xml'.". Fix the problem, then try refreshing this project and building it since it may be inconsistent jboss-ejb3-interceptors Unknown 1218050869912 5164

Doing a refresh and clean changed this to another problem:

Severity and Description Path Resource Location Creation Time Id
Required library cannot denote external folder: '/Users/svn/JBossAS/projects/ejb3/metadata/target/classes' for project 'jboss-ejb3-interceptors' jboss-ejb3-interceptors Build path 1218051089374 9445

Anyone have the eclipse projects working?

[starksm64]

After removing the metadata/target/classes from the core libraries and instead using a project dependency, I'm down to one error due to core referencing M2_REPO/org/jboss/ejb3/jboss-ejb3-common/0.1.3/jboss-ejb3-common-0.1.3.jar instead of 0.1.5-SNAPSHOT as defined in its pom.xml. Trying to update dependencies/snapshots is not correcting the classpath version.

Is there another option to get the versions in sync?

[starksm64]

Using m2/Update project configuration has things building. It looks like the correct way to setup a new workspace is to run eclipse:m2eclipse first. If that's needed, why not checkin the .project/.classpath with this?

[alrubinger]

I'm not having these problems, either with mvn eclipse:eclipse or the m2eclipse plugin...

Maybe manually remove .classpath locally and import fresh?

This gets back to lots of debate about what form the Eclipse project files should take. Carlo's been committing plugin-specific stuff, though I wouldn't be surprised if they've fallen out of sync. My opinion is that all IDE-specific stuff is out of scope for version control due to these types of problems.

S,
ALR

[starksm64]

Running eclipse:m2eclipse before importing is what was needed.

[wolfc]

My commit 76526 was actually bad, it disabled m2eclipse. Recommitted the real thing again.