Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] WTP and Multi-module project woes.

According to the workspace resolution for 0.12 fails. This is a problem i encountered as well.

For me reverting to version 0.10 fixed this problem.


On 02/15/2011 02:53 PM, Guus der Kinderen wrote:

Using my combination of Eclipse, M2Eclipse and the WTP extra, a pretty annoying problem pops up. For all of our multi-module projects, the dependencies of WAR-typed modules appear to be messed up, while "workspace resolution" is enabled (removing the <type>war</type> declaration from their pom resolves the problem immediately). Compiling the code from the command line works fine, which leads me to believe that m2eclipse is a contributing factor in this problem.

I've found several JIRA issues that all appear to relate to similar issues:
in MWAR-192 Eugene Kuleshov appears to indicate that using a WTP integration should prevent this problem from occurring. I am using WTP integration, but I'm experiencing an issue. Where does this go wrong, and more importantly: is there a way to work around it?

Related version information:
  • Eclipse Helios SR1
  • Maven Integration for Eclipse (Required)
  • Maven Integration for WTP (Optional)
User odin_ on / #m2eclipse suggested that I first uninstall all Maven-related plugins from Eclipse, and then reinstall them. I did (which gave me the exact same versions of both plugins) but this did not resolve our issue.

What is going on here? Can this issue be prevented in such a way that:
  • our Eclipse projects appear as compliation-problem free, and;
  • does not require me to explain to all of my co-workers that they have to install all modules in their local repository for these projects to work?


Back to the top