yea you're right.  I totally forgot about <dependencyManagement>.  Thanks 
:)


_Mang Lau





"Wayne Fay" <[EMAIL PROTECTED]> 
04/04/2006 12:41 PM
Please respond to
"Maven Users List" <[email protected]>


To
"Maven Users List" <[email protected]>
cc

Subject
Re: Shared projects and Maven best practice






> release a version of the Utility project.  As a result of this release, 
we
> would have to manually update all the POMs dependent on the Utility
> project with the specific version number being released.  Then, we would
> have to manually update all the POMs from the other application that 
needs
> to depend on the new snapshot number since it is now incremented.  This

Can you not utilize <dependencyManagement> and then change the Utility
version in one parent POM for each project, rather than in "every pom
file" in the project?

This doesn't seem unreasonable to me...

Wayne

Reply via email to