Hi, 
     
    This is probably a really, really stupid question, but I can't
    figure it out. 
     
    We're working with a multi-module project.  It works fine when it's
    checked out clean.  It processes the pom, recurses and everything is
    fine.  The problem happens when someone adds a module to the
    project.  I can't find a way to convince Eclipse to refresh the
    configuration of the project and detect the new module. 
     
    I've tried Maven->Update Project, but that doesn't seem to do the
    job, and I can't find anything else that will do it.  How do people
    convince Eclipse that the module list in the base pom.xml is out of
    date and that it needs to be reprocessed? 
     
    We've also tried checking out the project on top of the existing
    tree, but that seems to create new projects with unique directory
    names for the overlap. 
     
    I have the same issue with people using subversion from the command
    line, so something that can be done independently of the update is
    best. 
     
    What am I missing?  I'm guessing it is really, really simple because
    I can't find it - that tells me everyone just knows how to do it. :) 
     
    Thank you, 
    Jason Pollock 
     
    Versions: 
     
    Eclipse Juno 
    m2e - Maven Integration for Eclipse    1.1.0.20120530-0009  
    Maven SCM handler for Subclipse    0.14.0.201204121509 Sonatype,
    Inc. 
    Subclipse (Required)    1.8.16  
    --  
      
        Oracle
      Jason Pollock | Principal Member of the Engineering
        Staff 
        Phone: +6449015856 | |  
        Oracle  
         
        ORACLE New Zealand | | Newlands
      
      
        Green
      
      Oracle is committed to developing practices and
        products that help protect the environment
      
      
     
  
 |