Maven local process artifacts

2007-07-30 Thread Dmitry
By default Maven attempts to locate a dependecies artifact using the 
follloing process: 1-st generate path to the artifact in local repositiory. 
etc
How we can change Maven configuration that instead having to add the Spring 
framework jar to every project  - change just from one common configuration?


Thanks,
DT,
www.ejinz.com
Search Engine News Shop 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Maven local process artifacts

2007-07-30 Thread Wayne Fay
First off, I think you probably should avoid doing this. I think you
will run into troubles down the line if/when changes in Spring cause
your older projects to break, so suddenly you can't use the latest
Spring in all your projects, etc.

Having said that, you could create a single Super Parent POM (with the
Spring framework as a dependency) and tell all your other projects and
modules to utilize that pom as their parent.

Wayne

On 7/30/07, Dmitry [EMAIL PROTECTED] wrote:
 By default Maven attempts to locate a dependecies artifact using the
 follloing process: 1-st generate path to the artifact in local repositiory.
 etc
 How we can change Maven configuration that instead having to add the Spring
 framework jar to every project  - change just from one common configuration?

 Thanks,
 DT,
 www.ejinz.com
 Search Engine News Shop


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]