Comments on: Maven Tips http://blog.xebia.com/2008/10/25/maven-tips/ Tue, 09 Mar 2010 17:30:15 +0100 http://wordpress.org/?v=2.8.4 hourly 1 By: Thomas Ferris Nicolaisen http://blog.xebia.com/2008/10/25/maven-tips/comment-page-1/#comment-67019 Thomas Ferris Nicolaisen Sun, 07 Dec 2008 16:57:37 +0000 http://blog.xebia.com/?p=717#comment-67019 We've got a whole collection of advice on how to get a proper Maven infrastructure up and running: http://wiki.community.objectware.no/display/smidigtonull/Enterprise+Maven+Infrastructure And here's our pretty extensive Maven FAQ: http://wiki.community.objectware.no/display/smidigtonull/Maven+FAQ We’ve got a whole collection of advice on how to get a proper Maven infrastructure up and running:

http://wiki.community.objectware.no/display/smidigtonull/Enterprise+Maven+Infrastructure

And here’s our pretty extensive Maven FAQ:

http://wiki.community.objectware.no/display/smidigtonull/Maven+FAQ

]]> By: javabean http://blog.xebia.com/2008/10/25/maven-tips/comment-page-1/#comment-59300 javabean Tue, 28 Oct 2008 20:54:14 +0000 http://blog.xebia.com/?p=717#comment-59300 why dont you put the company repos in the parent pom ? migration is simple then, noone even notices. why dont you put the company repos in the parent pom ? migration is simple then, noone even notices.

]]> By: Jan Groot http://blog.xebia.com/2008/10/25/maven-tips/comment-page-1/#comment-59284 Jan Groot Tue, 28 Oct 2008 18:48:41 +0000 http://blog.xebia.com/?p=717#comment-59284 In my previous post the word dependencyManagement disappeared, as I put it in between A section of the maven introduction handles this issue: http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Management (I also seem to have some issues with your software) In my previous post the word dependencyManagement disappeared, as I put it in between

A section of the maven introduction handles this issue:

http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Management

(I also seem to have some issues with your software)

]]> By: Jan Groot http://blog.xebia.com/2008/10/25/maven-tips/comment-page-1/#comment-59281 Jan Groot Tue, 28 Oct 2008 18:35:50 +0000 http://blog.xebia.com/?p=717#comment-59281 As for using the properties for versioning, maybe you can use instead. This also regulates the versioning of transitive dependencies. As for using the properties for versioning, maybe you can use instead.
This also regulates the versioning of transitive dependencies.

]]> By: Brian Fox http://blog.xebia.com/2008/10/25/maven-tips/comment-page-1/#comment-59016 Brian Fox Mon, 27 Oct 2008 01:44:33 +0000 http://blog.xebia.com/?p=717#comment-59016 Good summary. Definately putting the repos in your settings is the way to go as you discovered. Having them in the pom makes it a tiny bit simpler to setup a new user, but it can be quite a pain to migrate later. Inserting the file based repo in your pom is also a bad idea, if you really must do it, put it in your settings. A better idea is a repository manager like Nexus (http://nexus.sonatype.org) even for personal use. It makes it easier to manager your repository connections, upload 3rd party resources etc. Plus you can trash your local repo and not have to redownload everything from the net. Good summary. Definately putting the repos in your settings is the way to go as you discovered. Having them in the pom makes it a tiny bit simpler to setup a new user, but it can be quite a pain to migrate later. Inserting the file based repo in your pom is also a bad idea, if you really must do it, put it in your settings.

A better idea is a repository manager like Nexus (http://nexus.sonatype.org) even for personal use. It makes it easier to manager your repository connections, upload 3rd party resources etc. Plus you can trash your local repo and not have to redownload everything from the net.

]]> By: Erik Pragt http://blog.xebia.com/2008/10/25/maven-tips/comment-page-1/#comment-58662 Erik Pragt Sat, 25 Oct 2008 19:50:54 +0000 http://blog.xebia.com/?p=717#comment-58662 Hi Lars, Thanks for the tips. One small remark: I'm using IntelliJ, and I never use the maven plugin to generate my project: I just open the pom.xml from within my IDE, which works great. I'm sure Eclipse (m2eclipe?) has similar tools. This way, you're project is always in sync with your pom, and you don't have to manually sync it when adding dependencies. Oh, and about point 2: I would advice to put in in the pom :). Actually, I would put all maven repositories there, internal or external. It happend to often that a build was failing on my machine, only to be notified (too much time later...) by an other developer that a new repo was added, but since it was in his/her settings, and not in a global place, my build was failing.... A workaround for your problem could be to 'standardize' on hostnames, and add them to your /etc/hosts file (or your windows host file). This way you can refer to them by name, and when the IP address changes, you only have to change your host table! Hi Lars,

Thanks for the tips. One small remark: I’m using IntelliJ, and I never use the maven plugin to generate my project: I just open the pom.xml from within my IDE, which works great.

I’m sure Eclipse (m2eclipe?) has similar tools. This way, you’re project is always in sync with your pom, and you don’t have to manually sync it when adding dependencies.

Oh, and about point 2: I would advice to put in in the pom :) . Actually, I would put all maven repositories there, internal or external. It happend to often that a build was failing on my machine, only to be notified (too much time later…) by an other developer that a new repo was added, but since it was in his/her settings, and not in a global place, my build was failing….

A workaround for your problem could be to ’standardize’ on hostnames, and add them to your /etc/hosts file (or your windows host file). This way you can refer to them by name, and when the IP address changes, you only have to change your host table!

]]>