Community

build path not set correctly after importing from svn for mavenized Seam project

reply from Max Andersen in JBoss Tools - View the full discussion

yes, the problem is that mvn eclipse:eclipse doesn't work reliably well. I don't even think it is capable of resolving projects with a different name than its module directory name (i.e moduleA should be named moduleA-<version> for your scenario to work)

 

Thus try use m2eclipse instead which supports importing with different styled names.

Reply to this message by going to Community

Start a new discussion in JBoss Tools at Community