Hi Hugo, I think you ran into the same problem I saw a couple hours ago, but didn't have time to investigate yet. can you please open a JIRA issue with a simple test projects showcasing these bugs? It seems they're related to the order of project import . Can you try checking in projects in the correct dependency order? - first parent project (will complains for missing modules) - then utility project if you have any, - then ejb if you have any - then web project - finally ear.
thanks. Regards, Fred Bricon On Wed, Oct 29, 2008 at 2:54 PM, Visser, Hugo <[EMAIL PROTECTED]> wrote: > Hi, > > I'm testing the dev version of m2eclipse on RAD 7.5 and I'm seeing two > issues. > When I check out a project as multi module project using "check out as > maven project" my web projects (contained in an ear) are set up > incorrectly. The org.eclipse.wst.common.component file contains: > > <?xml version="1.0" encoding="UTF-8"?><project-modules id="moduleCoreId" > project-version="1.5.0"> > <wb-module deploy-name="MyProjectWeb"> > <wb-resource deploy-path="/WEB-INF/classes" source-path="/src"/> > <wb-resource deploy-path="/" source-path="/src/main/webapp"/> > <wb-resource deploy-path="/WEB-INF/classes" > source-path="/src/main/java"/> > <wb-resource deploy-path="/WEB-INF/classes" > source-path="/src/main/resources"/> > <property name="context-root" value="MyProjectWeb"/> > <property name="java-output-path" > value="/src/main/webapp/WEB-INF/classes"/> > </wb-module> > </project-modules> > > The first deploy-path entry is incorrect and is giving me "source path > is nested" errors in RAD. I can fix this by doing a "update project > configuration", which will give me an error about installing Dynamic web > module 2.4, but will update the file to: > > <?xml version="1.0" encoding="UTF-8"?><project-modules id="moduleCoreId" > project-version="1.5.0"> > <wb-module deploy-name="MyProjectWeb"> > <wb-resource deploy-path="/WEB-INF/classes" > source-path="/src/main/java"/> > <wb-resource deploy-path="/WEB-INF/classes" > source-path="/src/main/resources"/> > <wb-resource deploy-path="/" source-path="/src/main/webapp"/> > <wb-resource deploy-path="/" source-path="/src/main/webapp"/> > <property name="context-root" value="MyProjectWeb"/> > <property name="java-output-path" > value="/src/main/webapp/WEB-INF/classes"/> > </wb-module> > </project-modules> > > The second issue is that for a dependent module the java facet > (jst.java) is incorrectly configured. It is set to version 6.0 while the > compiler settings in the pom are set to 1.4. I can fix this by deleting > the entire .settings folder which will then be recreated containing the > correct settings. > > Is it possible to force the jst.java version as a work around? I guess I > could fix the settings files once and check those into svn but I'd > rather not. > > Other than that m2eclipse is working quite alright on RAD 7.5, wst > integration is is working great (not counting the above). > > Thanks, > > Hugo > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- GMail rox! --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
