>> I will try the "Import Maven projects" option and hopefully that will work >> better. Thanks for your response
Thank you Igor, worked like the shiznitz. Bhaskar On Tue, Jun 17, 2008 at 11:35 AM, Bhaskar Maddala <[EMAIL PROTECTED]> wrote: > Thank you for your response, > >>>maven-eclipse-plugin is not related to m2eclipse and does not do all needed >>>configurations. > > Yes I realize that, I think my email from before might not have been very > clear > > I am guessing my using > > mvn eclipse:eclipse > > does not make sense, since I should have been importing projects as > maven projects instead of using the maven-eclipse-plugin > > I did import my project previously using "Existing Projects into > Workspace", right clicked the projects and set the manage maven > dependencies and removed the M2_REPO class path references, clearly a > lot of busy work by me. > > I will try the "Import Maven projects" option and hopefully that will > work better. Thanks for your response > > Thanks > Bhaskar > > > On Tue, Jun 17, 2008 at 11:10 AM, Igor Fedorenko <[EMAIL PROTECTED]> wrote: >> Bhaskar, >> >> The correct way to import maven projects into m2eclipse workspace is by >> using Import->General->MavenProjects import wizard (see >> http://docs.codehaus.org/display/M2ECLIPSE/Importing+Maven+projects). >> >> maven-eclipse-plugin is not related to m2eclipse and does not do all needed >> configurations. >> >> Bhaskar Maddala wrote: >>> >>> I have my projects set up for multiple modules, using a parent pom for >>> module aggregation, as such >>> >>> <modules> >>> <module>common</module> >>> <module>service</module> >>> <module>war</module> >>> </modules> >>> >>> Although we have this set up the modules in the order above currently >>> war has a dependencies only on common and not on service, this I have >>> captured this in pom.xml (in war) with a dependency >>> >>> <dependency> >>> <groupId>pr</groupId> >>> <artifactId>common</artifactId> >>> <version>${project.parent.version}</version> >>> </dependency> >>> >>> I then created eclipse .project and .classpath files using maven >>> >>> mvn eclipse:eclipse >>> >>> I import the projects into eclipse and the war project does not >>> compile, as the dependencies to common are not resolved. >>> >>> I do a mvn install on common, refresh the Maven Indexes and verify in >>> the view that common shows up in the list (local repository), I then >>> update dependencies on war and it still does not build. >>> >>> The only way I can get the war to build is by "Enable Nested Dependencies" >>> >>> Question : Why do I need to enable the nested dependencies, when I >>> have an explicit dependency in the pom to a jar which exists in my >>> local repository? What exactly am I doing incorrectly? What am I >>> missing? >>> >>> Thanks >>> Bhaskar >> >> >> --------------------------------------------------------------------- >> 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
