Ballard, Ken wrote:
This is a question for Maven 1 & 2, although I know that the answers will be
different.
Let's say that I have a multiproject with subprojects. Some build jars, one
builds a war, a couple that build an ejb jar and an ejb client jar, and one
builds an ear. Now let's say that I need the Spring jar in a jar subproject
or two, the war subproject, an ejb subproject, and the ear subproject. When
I upgrade to Spring 1.2.6, I need to go upgrade all the project.xml (M1) or
pom.xml (M2) files. There's a good chance for missing something there. In
M1, I could define custom property in the project.properties file like
spring.jar.version. But would this be the best practice, or is there a
better way? And what about M2, which doesn't use a project.properties file?
Thanks,
Ken
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi Ken,
In M1, you have to go the property route. M2 handles it more gracefully.
List your dependencies under the dependencyManagement tag in your parent
pom and any child poms will inherit those versions automatically.
Regards,
Henry
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
