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
