On 18/02/2008, Nikolay Karasev <[EMAIL PROTECTED]> wrote: > > I had to add manually a couple of jar files from ~/.m2 that were not > added by this command. Also as far as this commend simply expands the > entire repository to individual files - I'd say it is only half way > helpful. It seems that eclipse team might want to have some sort of > auto-expand feature.
Not entirely sure what you mean by "expands entire repository to individual files" but I have used mvn eclipse:eclipse for a while now on both modular and basic projects and have never had to manually add any dependencies. Could you describe the process you followed? There was another strange thing with this command on modular appfuse: > it did not create .project and .classpath file in the root, only in > the core and webapp directories. I had to resort to using basic > appfuse instead of modular for the whole thing to finally pass through > the first JUnit test and have eclipse not complaining about > dependencies. I wonder if somebody with modular appfuse has actually > done this to eclipse. This is an unfortunate feature of the maven eclipse plugin - it does not include the root of multi-module projects as an eclipse project. This should not stop your tests working though - have you followed the instructions here http://www.appfuse.org/display/APF/Eclipse to get your project up and running? The worst effect this should have is that if you need to edit the root pom.xml you need to do it outside eclipse. Mike I will try to copy this .classes files over from basic to modular > project and see maybe this would help, but this is still half way from > auto. > > Thanks, > Nikolay > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
