if you're using the m2eclipse plugin, building project b will force a
build of project a... but all the jar files will be installed into and
resolved from your local maven repository (~/.m2/repository), not the
target directory.
Not sure why you would want the jar files in your target directory...
is there some sort of project specific reason for this?
---
Nayan Hajratwala
http://agileshrugged.com
http://twitter.com/nhajratw
734.658.6032
On Sep 25, 2009, at 6:41 PM, Piyush Gupta wrote:
I have configured Multiple project in my eclipse workspace and each
project
has its own POM.XML . I have worked with the dependencies with single
eclipse project with multiple modules in that single project and it
works
fine when build with Maven but when working with Different projects
is there
any possibility to build the all the project with one single parent
project?
I do not want to build all the dependent project and install the JAR
in
local repository and than build the parent project I know that will
work
fine. What I want to achieve is with out building the dependent
project I
will just build the Parent Project and it will build all the dependent
project plus all the Third party JAR's which every project is having
and put
it into the local repo and every project's respective target
directory.
The project structure in eclipse is like this
C:\eclipse\workspace
\ ProjectA
|
pom.xml
|
src.com.javasource
\ ProjectB (Child)
|
pom.xml
|
src.com.javasource
\ ProjectC
|
pom.xml
|
src.com.javasource
So when I will compile or run the command on ProjectA 's pom.xml it
should
build the ProjectB and ProjectC and create the projectb.jar and
projectc.jar
and put those jar's into the respective projects target directory.
