[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
| Re: [m2e-users] WTP and Multi-module project woes. | 
Reverting back to 0.10 gives me issues with the SCM integration (*sigh* the cake 
is a lie). According to that issue, the problem should be fixed in a "released" version 14b. How do I get my hands on that? The old dev-build update site doesn't appear to work any longer. Is there a new one?
 - Guus
On 15 February 2011 14:56, Ronald Spierenburg 
<rspierenburg@xxxxxxxxxxxxx> wrote:
  
    
  
  
    According to 
https://issues.sonatype.org/browse/MNGECLIPSE-2676
    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.
    
    Ronald
    
    On 02/15/2011 02:53 PM, Guus der Kinderen wrote:
    
Hello,
      
      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)
          0.12.1.20110112-1712
- Maven Integration for WTP (Optional) 0.11.1.20101108-1810
User odin_ on irc.codehaus.org / #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?
Regards,
      
        Guus
    
    
   
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users