Re: Need to convince my manager to switch to maven
Most questions got already answered, just one more comment about finding third party dependencies. On Thursday 04 June 2009 scabbage wrote: - Your pom.xml only shows those dependencies your project is directed dependent upon. Fine. But what about all other dependencies that your dependencies depend upon? Know who they, get them and put in CVS!! Use the maven-dependency-plugin's [0] goal dependency:tree to get a list of all dependencies with their dependencies listed. hth, - martin [0] http://maven.apache.org/plugins/maven-dependency-plugin/ signature.asc Description: This is a digitally signed message part.
Need to convince my manager to switch to maven
Our group does release engineering and we have a Jave project that gets build every night. Our java source code and lib jars are checked into CVS. Every night we do a sync and build. As a Java developer, I have a hard time managing/upgrading my Java libs. In the process of switching to Maven, I have to convince my team that Maven is the right tool to use. But many concerns have been raised. For example: - What if the central repo goes down? We'll end up with broken builds and the QEs will go crazy at us! - Ok, so we can have proxies, but then we have to maintain them. Lots of work. - Not checked into CVS??? That's not good. Not comfortable without having a complete set of artifacts in a SAFE place. Not comfortable! - Your pom.xml only shows those dependencies your project is directed dependent upon. Fine. But what about all other dependencies that your dependencies depend upon? Know who they, get them and put in CVS!! Not sure if any of you have encountered these challenges. Please give me some suggestions. -- View this message in context: http://www.nabble.com/Need-to-convince-my-manager-to-switch-to-maven-tp23876576p23876576.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: Need to convince my manager to switch to maven
Answers inline. On Thu, Jun 4, 2009 at 3:50 PM, scabbageguans...@gmail.com wrote: - What if the central repo goes down? We'll end up with broken builds and the QEs will go crazy at us! There are a few things about this that bug me. Maven only downloads from central once for released artifacts. So, the build server and most likely all of the developers will have copies of all required jars in their ~/.m2/repository directory. So if central is down, and you aren't dependent on any SNAPSHOTs, as long as the build doesn't include a new dependency, then you probably won't even notice. Furthermore, I've been using maven for a couple of years now and I don't remember even so much as a planned outage of central. IIUC, central is mirrored all over the world, one server being down probably just means it gets taken out of rotation and no one notices. The what if style arguments are a PITA... What if the cold war starts back up and our colo facility gets nuked?!! Will the builds fail? Of course they will, but I prefer to worry about making my day-to-day easier than worrying about all of the things that *could* make it harder. - Ok, so we can have proxies, but then we have to maintain them. Lots of work. See my answer to question 1. Rather than a proxy, get nexus. I run a repository manager for myself and my team in my office, as well as one at home. It's not that much work at all. - Not checked into CVS??? That's not good. Not comfortable without having a complete set of artifacts in a SAFE place. Not comfortable! Who says things aren't checked into CVS? As I mentioned before, you will end up with all of the jars you need distributed on machines all over your network. In fact, that is one of the things I have had to deal with before. Since ~/.m2 translates to c:\Documents and Settings\Username on modern windows machines, a few developers ended up with roaming profiles exceeding a few gigabytes. Anyhow, I can't force you to be comfortable with something, but if you must, then just have the build server check-in it's ~/.m2 directory on a regular basis. - Your pom.xml only shows those dependencies your project is directed dependent upon. Fine. But what about all other dependencies that your dependencies depend upon? Know who they, get them and put in CVS!! You can check-in the ~/.m2 if it's a requirement. I think many people will agree that it's a waste of time, but YMMV. Not sure if any of you have encountered these challenges. Please give me some suggestions. -- Wes Wannemacher Author - Struts 2 In Practice Includes coverage of Struts 2.1, Spring, JPA, JQuery, Sitemesh and more http://www.manning.com/wannemacher - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Need to convince my manager to switch to maven
See below for my comments. -Dave On Thu, Jun 4, 2009 at 1:50 PM, scabbage guans...@gmail.com wrote: Our group does release engineering and we have a Jave project that gets build every night. Our java source code and lib jars are checked into CVS. Every night we do a sync and build. As a Java developer, I have a hard time managing/upgrading my Java libs. In the process of switching to Maven, I have to convince my team that Maven is the right tool to use. But many concerns have been raised. For example: - What if the central repo goes down? We'll end up with broken builds and the QEs will go crazy at us! [dh] Not likely. We use the open source Artifactory maven proxy so you will only ever download something once. Not much of a concern, now its your job to keep your server up. - Ok, so we can have proxies, but then we have to maintain them. Lots of work. [dh] No, very little work. Set it up and is very little maintenance. You can even configure it to create exports of all artifacts for backup. - Not checked into CVS??? That's not good. Not comfortable without having a complete set of artifacts in a SAFE place. Not comfortable! [dh] Artifactory can be just as safe as CVS. - Your pom.xml only shows those dependencies your project is directed dependent upon. Fine. But what about all other dependencies that your dependencies depend upon? Know who they, get them and put in CVS!! [dh] They are all in your proxy as well as developer repos, not to worry. Not sure if any of you have encountered these challenges. Please give me some suggestions. [dh] These are the easy problems. -- View this message in context: http://www.nabble.com/Need-to-convince-my-manager-to-switch-to-maven-tp23876576p23876576.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: Need to convince my manager to switch to maven
See my comments: [gj] -Guillaume From: David Hoffer [mailto:dhoff...@gmail.com] Sent: Thu 6/4/2009 4:33 PM To: Maven Users List Subject: Re: Need to convince my manager to switch to maven See below for my comments. -Dave On Thu, Jun 4, 2009 at 1:50 PM, scabbage guans...@gmail.com wrote: Our group does release engineering and we have a Jave project that gets build every night. Our java source code and lib jars are checked into CVS. Every night we do a sync and build. As a Java developer, I have a hard time managing/upgrading my Java libs. In the process of switching to Maven, I have to convince my team that Maven is the right tool to use. But many concerns have been raised. For example: - What if the central repo goes down? We'll end up with broken builds and the QEs will go crazy at us! [dh] Not likely. We use the open source Artifactory maven proxy so you will only ever download something once. Not much of a concern, now its your job to keep your server up. [gj] we use open source nexus maven repository manager, it is based on flat-file m2 repo making it all the much easier to maintain. - Ok, so we can have proxies, but then we have to maintain them. Lots of work. [dh] No, very little work. Set it up and is very little maintenance. You can even configure it to create exports of all artifacts for backup. [gj] with nexus just setup a tape backup for the underlying nexus repo file store. - Not checked into CVS??? That's not good. Not comfortable without having a complete set of artifacts in a SAFE place. Not comfortable! [dh] Artifactory can be just as safe as CVS. [gj] yep again, nexus is better at this than CVS. CVS is not meant to manage anything other than source code files. - Your pom.xml only shows those dependencies your project is directed dependent upon. Fine. But what about all other dependencies that your dependencies depend upon? Know who they, get them and put in CVS!! [dh] They are all in your proxy as well as developer repos, not to worry. Not sure if any of you have encountered these challenges. Please give me some suggestions. [dh] These are the easy problems. -- View this message in context: http://www.nabble.com/Need-to-convince-my-manager-to-switch-to-maven-tp23876576p23876576.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 This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
