I believe they're caused by the maven-eclipse-plugin - https://bugs.eclipse.org/bugs/show_bug.cgi?id=394042
On 27 November 2012 15:22, Dave Wolf <[email protected]> wrote: > Hi, > > I feel like I've been banging my head against the wall attempting to get a > multi-module project checked out, its dependencies (from the sub-modules) > recognized, and src/main/java & src/test/java actually treated as Java > source. My project builds just great from the command-line, but is > blood-red with errors from missing dependencies in eclipse. > > I'm running Juno SR1 with m2e 1.2.0.20120903-1050 (latest), m2e-wtp > 0.16.0.20120914-0945 (latest), on Mac OS X 10.8.2. > > In eclipse, I go to SVN Repository Exploring, expand the desired project, > right-click on trunk selecting "Check out as Maven Project". A dialog is > displayed with the path to the project's trunk displayed, Checkout Head > Revision checked, and Checkout All Projects checked. Click Next, then > Finish and get an error dialog with the following error: > > An internal error occurred during: "Importing Maven projects". > Unsupported IClasspathEntry kind=4 > > Is there a work-around for this issue? I'm really hoping that this isn't > as broken as it appears. > > Dave Wolf > > > _______________________________________________ > m2e-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/m2e-users > >
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
