| Thanks, Fred, for your quick answer, and sorry for the delay. Trying
    to strip down our Eclipse project is not an option. With all the
    Eclipse history and caches I doubt I'd be able to end up with an
    Eclipse project that I can share with you or anyone else. But: 
 I finally succeeded in getting our webapp to work under Eclipse
    Indigo with m2e - yuppieee!
 
 Rough howto (if anyone else is affected):
 1. Start with a fresh Eclipse Indigo install and an empty workspace.
    Install and configure the required plugins, incl. the latest m2e-wtp
    (v 0.13.1) *before* importing any of your projects.
 2. Delete .project, .classpath from your Eclipse project *before*
    importing it into your workspace
 3. Right-click your project in the SVN Repositories perspective and
    choose "Check out as Maven project...". Select the appropriate
    options and checkout/import your project
 4. Create/update the project configuration by right-clicking your
    project in the Package Explorer and selecting Maven > Update
    Project Configuration. This should generate the necessary Java Build
    Path entries, and also the necessary entries for "Deployment
    Assembly" in the project properties.
 5. In my case, the web content stuff (META-INF, WEB-INF) is located
    under <projectHome>/src/main/webapp instead of
    <projectHome>/WebContent where Eclipse is obviously expecting
    it. Thus I had to manually add /src/main/webapp to the "Deployment
    Assembly" paths.
 
 Following these steps (and compiling and maven-building your webapp
    in between of course), I succeeded in getting it up and running.
 
 The following problems I have observed earlier have not occurred
    anymore (touch wood!):
 * "Maven Dependencies" container is not added to the "Deployment
    Assembly" list.
 * All maven dependencies marked with
    <scope>provided</scope> are deployed to the webapp
    nontheless.
 Should they occur for you, I advise you to follow the steps above
    instead of trying to fix your existing workspace.
 
 HTH,
 stefan.
 
 
 On 2011-07-22 10:31, Fred Bricon wrote:
 Stefan, I suspect the provided dependencies are
      deployed because you manually added the Maven Libraries to the
      deployment assembly. But I'm not sure.
 If you guys can try to reproduce the issue using a sample project,
      that'd be helpful. You can try by trimming down your app (remove
      any code), remove references to any proprietary plugins /
      dependencies, obfuscate some names or whatever you don't wanna see
      publicized.
 
 I'd be happy to help but really, I need you guys.
 
 regards,
 
 Fred Bricon
 
 
 2011/7/22 Stefan Thurnherr <st.mailinglists@xxxxxxxxx> 
          Hi   I completely agree with you - I've also tried to move to
            Eclipse Indigo with m2e 1.0 and m2e-wtp 0.13.1 - but gave up
            after some time.   The problem you see can be solved by adding the Maven
            Dependencies to the Deployment Assembly: Right-click on your
            web project > Properties > Deployment Assembly >
            Add > Java Build Path Entries > Maven Dependencies.   The problem that then remains (at least for me) is this
            bug:   HTH,  stefan.
 
 
            
            
              
                _______________________________________________
                  I am having a real tough time trying to migrate
                    our existing app which consists of about 10 java
                    projects with 1 java webapp project. Installing
                    eclipse and just m2e is fine but as soon as I
                    install m2e-wtp I either get errors or things
                    generally aren't working. I'll start with my current
                    issue but I may have some follow-ups. 
 Before the migration I deleted all my existing
                    Eclipse project files (.classpath, .project,
                    .settings/) and then used the 'Import Existing Maven
                    Projects' option. After the import I had a number of
                    errors which I have all now fixed. I had to
                    restructure a number of things but ultimately I am
                    happy with all those modifications. 
 When I create a new (Tomcat) Server I select the
                    option 'Use Tomcat Installation'. When I look in the
                    <tomcat>/wtpwebapps/intouch-webapp/WEB-INF/lib
                    folder I only see my internal project dependencies
                    (i.e. the 10 jars from the 10 projects). I don't see
                    any of my external dependancies such as Spring,
                    commons*, ehcache, joda, etc...  In previous
                    versions of m2eclipse I always saw all the project
                    dependencies.
 
 Any ideas? Collin Peters
 
 m2e-users mailing list
 m2e-users@xxxxxxxxxxx
 https://dev.eclipse.org/mailman/listinfo/m2e-users
 
 
 
 _______________________________________________
 m2e-users mailing list
 m2e-users@xxxxxxxxxxx
 https://dev.eclipse.org/mailman/listinfo/m2e-users
 
 
 
 --
 "Have you tried turning it off and on again" - The IT Crowd
 
 
 
 _______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
 
 |