Hi, I've upgraded WST to 3.0.2 but still see the same effect in my projects. While all important projects are included in the Java EE Module Dependencies, only some can also be found in the build path - libraries -> maven dependencies. My first guess is that they inherit from a different parent, but I will evaluate if that is really the difference.
Andreas [EMAIL PROTECTED] mobile: +49 (175) 2664109; office: +49 (212) 2494 331; fax: +49 (212) 2494 334 Grünewalder Str. 29-31; 42657 Solingen Geschäftsführer: Peter Gierse, Mirko Novakovic und Rainer Vehns - Sitz der Gesellschaft: Solingen Registergericht: Amtsgericht Wuppertal, HRB 19214 > -----Ursprüngliche Nachricht----- > Von: Igor Fedorenko [mailto:[EMAIL PROTECTED] > Gesendet: Montag, 29. September 2008 16:09 > An: user@m2eclipse.codehaus.org > Betreff: Re: AW: AW: [m2eclipse-user] dependencies are not added to build > path for web projects > > Yes, Ganymede comes with WTP 3.0.0. There were several issues with > initial 3.0.0 release, so you probably want to update WTP to at least > 3.0.1 (3.0.2 is out but I have not tried it yet). > > It really should not matter how you create new web project. FYI, > maven-archetype-webapp archetype worked pretty well for WTP mini HOWTO [1]. > > I do not think there is a strong case whether to checking project > metadata into subversion or not. And Checkout As Maven project wizard > ignores project metadata coming from SVN, so it does not really matter. > > [1] http://docs.codehaus.org/display/M2ECLIPSE/WTP+mini+howto > > Andreas Ebbert-Karroum wrote: > > Hi Igor, > > > > I'm using Eclipse Ganymede and the WTP container that comes with it. The > Web Standard Tools Feature is in Version 3.0.0 ( so how does that map to > WTP?!) > > > > If I have some spare time I will try to reproduce it. What is the > recommended way to start a web project? Use the maven archetype? Create it > with eclipse and later enable the maven nature/dependency management? Is it > recommended to check in also .project, .classpath and .settings to > subversion, or do you add them to svn:ignore and let m2eclipse figure that > out on checkout? > > > > Thanks for your hints, > > Andreas > > > >> -----Ursprüngliche Nachricht----- > >> Von: Igor Fedorenko [mailto:[EMAIL PROTECTED] > >> Gesendet: Freitag, 26. September 2008 15:41 > >> An: user@m2eclipse.codehaus.org > >> Betreff: Re: AW: [m2eclipse-user] dependencies are not added to build > path > >> for web projects > >> > >> Andreas, > >> > >> WTP 2.0 or later maintains its own "Web App Libraries" classpath > container > >> and all Java EE Module Dependencies are automatically added to this > >> classpath container (see attached screenshot). > >> > >> What version of WTP are you using? If you can reproduce the problem > using a > >> sample project, please open new bugreport in JIRA [1] and provide the > >> sample project and steps to reproduce it. > >> > >> [1] http://jira.codehaus.org/browse/MNGECLIPSE > >> > >> Andreas Ebbert-Karroum wrote: > >>> Hi Igor, > >>> > >>> the problem is, that eclipse is complaining that it cannot resolve the > >>> classes. To the best of my knowledge, the j2ee module dependency is > >>> just to package the war and ear files and set the classpath entries in > >>> the manifest correctly, for correct compilation it still has to be on > >>> the build path. At least this is how it worked with RAD up to version > >>> 6.1 (haven't used the 7 yet) > >>> > >>> Andreas > >>> > >>>> -----Ursprüngliche Nachricht----- > >>>> Von: Igor Fedorenko [mailto:[EMAIL PROTECTED] > >>>> Gesendet: Freitag, 26. September 2008 01:43 > >>>> An: user@m2eclipse.codehaus.org > >>>> Betreff: Re: [m2eclipse-user] dependencies are not added to build > >>>> path for web projects > >>>> > >>>> Andreas, > >>>> > >>>> This is how it is supposed to work, i.e. utility jar projects should > >>>> not appear in Maven Dependencies classpath container, only in J2EE > >>>> Module dependencies. What is the problem exactly? > >>>> > >>>> Andreas Ebbert-Karroum wrote: > >>>>> Hi, > >>>>> > >>>>> > >>>>> > >>>>> is it a known bug (or is it even a bug), that if I have a > >>>>> multi-module project with a pom, some utility jars and a web project > >>>>> (so pretty standard), the utility projects are listed in the Java EE > >>>>> module dependencies, but not in the Maven Libraries in the Java > >>>>> Build Path. It works sometimes for some projects, but not everytime, > >>>>> but I could not figure out the pattern yet to fix it. Any ideas? > >>>>> > >>>>> > >>>>> > >>>>> Andreas [EMAIL PROTECTED] <mailto:ebbert- > >>>> [EMAIL PROTECTED]> > >>>>> * mobile:* +49 (175) 2664109; *office:* +49 (212) 2494 331; *fax:* > >>>>> +49 > >>>>> (212) 2494 334 > >>>>> > >>>>> Grünewalder Str. 29-31; 42657 Solingen > >>>>> > >>>>> > >>>>> > >>>>> Geschäftsführer: Peter Gierse, Mirko Novakovic und Rainer Vehns - > >>>>> Sitz der Gesellschaft: Solingen > >>>>> Registergericht: Amtsgericht Wuppertal, HRB 19214 > >>>>> > >>>>> > >>>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe from this list, please visit: > >>>> > >>>> http://xircles.codehaus.org/manage_email > >>>> > >>>> > >>>> > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe from this list, please visit: > >>> > >>> http://xircles.codehaus.org/manage_email > >>> > >>> > > > > > > --------------------------------------------------------------------- > > To unsubscribe from this list, please visit: > > > > http://xircles.codehaus.org/manage_email > > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
