I have a typical project structure that works perfectly fine for me: myproject |__myproject-app |__myproject-shared |__myproject-ejb |__myproject-web
Within the EJB project's pom (packaging=ejb), I have two build plugin: * org.codehaus.mojo:was6-maven-plugin:ejbdeploy * org.apache.maven.plugins:maven-ejb-plugin:2.0 (ejbVersion=2.0, generateClient=true) When we build with plain-old Maven, we get one extra artifact: myproject-ejb-client.jar. However, when I import the projects with m2eclispe, I'm gaining an extra eclipse project: myproject-ebjClient. Its also modifying the myproject-ejb's ejb-jar.xml to include this new project's name. This explicit ceration of the project and mismatch of the name is vexing me greatly. Where's my disconnect? -- View this message in context: http://www.nabble.com/How-to-live-with-m2eclipse%27s-WTP-support-projects--tp22740678p22740678.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
