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:
  https://issues.sonatype.org/browse/MECLIPSEWTP-126

HTH,
 stefan.

On Fri, Jul 22, 2011 at 1:50 AM, Collin Peters <
[email protected]> wrote:

> 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
> [email protected]
> https://dev.eclipse.org/mailman/listinfo/m2e-users
>
>
_______________________________________________
m2e-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/m2e-users

Reply via email to