Re: [M2] [M1] Multiproject dependencies question
That's not an exception to the inheritence rule described. On 11/21/05, Jörg Schaible [EMAIL PROTECTED] wrote: Arik Kfir wrote on Friday, November 18, 2005 7:20 PM: in m2 you can define the version once - in the parent POM via a dependencyManagement section. All child POMs just state the group artifact IDs, without the version (they inherit the version from the parent). Well, with exceptions: http://jira.codehaus.org/browse/MNG-1577 - Jörg - 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]
RE: [M2] [M1] Multiproject dependencies question
Arik Kfir wrote on Friday, November 18, 2005 7:20 PM: in m2 you can define the version once - in the parent POM via a dependencyManagement section. All child POMs just state the group artifact IDs, without the version (they inherit the version from the parent). Well, with exceptions: http://jira.codehaus.org/browse/MNG-1577 - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] [M1] Multiproject dependencies question
in m2 you can define the version once - in the parent POM via a dependencyManagement section. All child POMs just state the group artifact IDs, without the version (they inherit the version from the parent). as for m1, I think it can only be done via a property... On 11/18/05, Ballard, Ken [EMAIL PROTECTED] 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] [M1] Multiproject dependencies question
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]
