Hi Alejandro, I'm no longer getting the error, but I'm also not getting the source pulled out into the different modules (common, war -- i.e. common/src/main/java/<packages> & war/src/main/java/<packages>) in the package explorer view. Is the issue with my expectations?
Dave Wolf H: 303-377-9537 M: 303-956-9106 "There is no passion to be found playing small - in settling for a life that is less than the one you are capable of living." --Nelson Mandela On Tue, Nov 27, 2012 at 1:41 PM, <[email protected]> wrote: > it looks like you are mixing maven eclipse plugin and m2e > My suggestion is go to the project in the command line, do mvn > eclipse:clean > Confirm that .project, .classpath, .settings were deleted. if not, delete > them by hand > > Once everything is clean, repeat the check out as maven project and it > should be fine > > There is something about eclipse metadata created with eclipse:eclipse > that generates the IClasspathEntry error > > good luck > > *Alejandro Endo* <%[email protected]> | Software > Designer/Concepteur de logiciels* > **Miranda Technologies* <http://www.miranda.com/contact.php> | Tel: (514) > 333-1772 Ext: 3789 > 3499 Douglas-B.-Floreani, Montréal, QC H4S 2C6 Canada > Miranda Technologies is a brand of Belden Inc. > > [image: Inactive hide details for Dave Wolf ---2012-11-27 03:22:56 > PM---Hi, I feel like I've been banging my head against the wall atte]Dave > Wolf ---2012-11-27 03:22:56 PM---Hi, I feel like I've been banging my head > against the wall attempting to get a > > From: Dave Wolf <[email protected]> > To: <[email protected]>, > Date: 2012-11-27 03:22 PM > Subject: [m2e-users] Checking out a multi-module project using Juno & m2e > Sent by: <[email protected]> > ------------------------------ > > > > 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 > > DISCLAIMER: Privileged and/or Confidential information may be contained in > this message. If you are not the addressee of this message, you may not > copy, use or deliver this message to anyone. In such event, you should > destroy the message and kindly notify the sender by reply e-mail. It is > understood that opinions or conclusions that do not relate to the official > business of the company are neither given nor endorsed by the company. > Thank You. > > > _______________________________________________ > m2e-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/m2e-users > >
<<graycol.gif>>
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
