Re: Externalize POM file
On Friday 16 December 2011 Anders Hammar wrote: Using dependencyManagement in the parent to specify the version of dependencies is also an option. IMHO that's the true Maven way, but Ron's approach could be an option in some cases. I don't like that approach though as it will create an incorrect dependency tree (dependencies will be on the wrong level and there will likely be too many dependencies). +1 for Anders' comments about Ron's approach. - martin signature.asc Description: This is a digitally signed message part.
Re: Externalize POM file
(MavenXpp3Reader.java:2094) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:3912) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1606) Regards Kumar -- View this message in context: http://maven.40175.n5.nabble.com/Externalize-POM-file-tp5079337p5079564.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Externalize POM file
On 16/12/2011 2:25 AM, Anders Hammar wrote: Using dependencyManagement in the parent to specify the version of dependencies is also an option. IMHO that's the true Maven way, but Ron's approach could be an option in some cases. I don't like that approach though as it will create an incorrect dependency tree (dependencies will be on the wrong level and there will likely be too many dependencies). It reduces the number of dependencies at the module level since there is a single provided dependency for all of Spring, Hibernate, MySQL and Tomcat. Another for all of the stuff that is required for Faces, another for web services, another for Apache commons and other third party libraries (Jasper Reports, another for all of the libraries that we have made, etc.. The only downside is that there are a number of jars (about 10) that we make that have to be added to the Tomcat shared lib at runtime to get the 70+ libraries that we use. It makes the module wars really small since they contain only the code that we wrote for the module. That speeds up the builds tremendously. It also makes it much easier for the developers to set up a module since they only have to depend on a few artifacts (usually about 5). We are sure that their module is using the correct version of all of the little libraries that they need. All of the exclusions to avoid version conflicts are done inside the shared jars so the developer does not have to worry about 2 versions of Spring getting called up. This reduces the dependency tree for the module and avoids run-time library conflicts which was one of the problems that prompted us to implement this. Ron /Anders On Fri, Dec 16, 2011 at 08:15, Ron Wheeler rwhee...@artifact-software.com wrote: http://blog.artifact-software.com/tech/?p=121 On 16/12/2011 12:17 AM, KumarR wrote: Hi I am new to maven. I want to maintain a separate POM file for version of the jar files. This will help in maintaining the versions of jar files. For eg: if we are using junit.jar, the version of the jar file should be maintain in the separate POM file. This will help us in changing in only one POM rather than all the POM files if any version changes is there. Please help me in this regard. Regard Kumar -- View this message in context: http://maven.40175.n5.nabble.com/Externalize-POM-file-tp5079337p5079337.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Externalize POM file
Hi I am new to maven. I want to maintain a separate POM file for version of the jar files. This will help in maintaining the versions of jar files. For eg: if we are using junit.jar, the version of the jar file should be maintain in the separate POM file. This will help us in changing in only one POM rather than all the POM files if any version changes is there. Please help me in this regard. Regard Kumar -- View this message in context: http://maven.40175.n5.nabble.com/Externalize-POM-file-tp5079337p5079337.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Externalize POM file
http://blog.artifact-software.com/tech/?p=121 On 16/12/2011 12:17 AM, KumarR wrote: Hi I am new to maven. I want to maintain a separate POM file for version of the jar files. This will help in maintaining the versions of jar files. For eg: if we are using junit.jar, the version of the jar file should be maintain in the separate POM file. This will help us in changing in only one POM rather than all the POM files if any version changes is there. Please help me in this regard. Regard Kumar -- View this message in context: http://maven.40175.n5.nabble.com/Externalize-POM-file-tp5079337p5079337.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Externalize POM file
Using dependencyManagement in the parent to specify the version of dependencies is also an option. IMHO that's the true Maven way, but Ron's approach could be an option in some cases. I don't like that approach though as it will create an incorrect dependency tree (dependencies will be on the wrong level and there will likely be too many dependencies). /Anders On Fri, Dec 16, 2011 at 08:15, Ron Wheeler rwhee...@artifact-software.com wrote: http://blog.artifact-software.com/tech/?p=121 On 16/12/2011 12:17 AM, KumarR wrote: Hi I am new to maven. I want to maintain a separate POM file for version of the jar files. This will help in maintaining the versions of jar files. For eg: if we are using junit.jar, the version of the jar file should be maintain in the separate POM file. This will help us in changing in only one POM rather than all the POM files if any version changes is there. Please help me in this regard. Regard Kumar -- View this message in context: http://maven.40175.n5.nabble.com/Externalize-POM-file-tp5079337p5079337.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Externalize POM file
in context: http://maven.40175.n5.nabble.com/Externalize-POM-file-tp5079337p5079564.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
