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.

"dependencies of WAR-typed modules appear to be messed up" does not
provide enough information to be able to help you troubleshoot the problem.

* What are you trying to do ("start wtp tomcat server",
"run-as->maven-install", etc)?
* What is expected behaviour?
* What is the observed behaviour?


On 11-02-15 08:53 AM, 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?



m2e-users mailing list

Back to the top