RE: convincing Workplace to use Maven
Depending on which technology stack you are using you may have hard time to sell this migration, especially if you're building J2EE apps mixing EJBs and webapps deployed on a commercial platform. Make sure you don't propose only a tool (maven) but rather a full development environment with a repository manager hosted in your intranet, a continuous integration server on top of maven, project web sites, guidelines, etc... I have sold it to my management by proposing what I called a software factory to homogenize our dev environment and enable developers to switch more easily and faster between projects and re-use components. This argument is usually relevant for managers as they tend to think that developers as resources that can be switched between projects. Management may not be very sensible to dependency management or other technical arguments. Cheers, Gael - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: convincing Workplace to use Maven
Ok, then that of convincing colleagues, chiefs etc. to switch to maven seems a recurring challenge developers have to face here in Italy. I use maven since 2004 (or was 2003, anyway...) , I think that maven is a great step ahead in code building, integrating,testing, in developing a project life cycle that fulfills anybody needs... but from the other side we always find someone not available to see this great potential; not that they don't have some good reasons, since switching a (long lived) project to maven it's not easy nor recommendable or fast, in some realities. I would convince colleagues by simply saying they won't face dependency trouble anymore...and that the stack: Maven + Eclipse + CVS (or Subversion) is an INDUSTRY standard nowadays. Would they use Idea or Netbeans or whatever? No problem. Maven is much better from the command line (even if Maven integrations still exist), and doesn't care what is the IDE used. Sure the need to spend a little time and effort to understand maven basics, but this effort will pay back... If it isn't enough, let me know... greetings On 9/30/07, Marco Mistroni [EMAIL PROTECTED] wrote: hello all, i am a big fan of maven (i have been using it since approx 3 years..).. and i'd like to use it @ my work, where we are still using ant and coding most of the tasks manually.. but i'd need good arguments, as now many IDEs( especially IntelliJ) offer lot of capabilities such as code coverage, identifying code smells etc so, i'd need good arguments for pushing for Maven2 @work can anyone help me out? thanks and regards
Re: convincing Workplace to use Maven
This is not a comparison to other options, but from my perspective I would say standardization of code artifacts and structure, advanced dependency management, descriptive vs. programmatic builds, enforcement of enterprise conventions through super pom's, rich plugin ecosystem, project site that allows open visibility into build and build-related operations (testing results, code coverage, code quality, etc), integration into enterprise build and deployment tools. Tony On 9/30/07, Marco Mistroni [EMAIL PROTECTED] wrote: hello all, i am a big fan of maven (i have been using it since approx 3 years..).. and i'd like to use it @ my work, where we are still using ant and coding most of the tasks manually.. but i'd need good arguments, as now many IDEs( especially IntelliJ) offer lot of capabilities such as code coverage, identifying code smells etc so, i'd need good arguments for pushing for Maven2 @work can anyone help me out? thanks and regards
RE: convincing Workplace to use Maven
Hi, Does your IDE manage third-party dependencies ? Maven do it ! I worked on my project using Jdeveloper and Ant few years ago. All people think they used a particular version of commons-lang. But commons-lang was added twice in the project... with of course two different versions. Why ? Just because Struts package in Jdeveloper include commons-lang... and developers added their own version of common-lang in the project. A such mistake with Maven cannot occurs. In another project, I need to do theses tasks : - remove dependencies because they became obsolete : with Maven, you just have to change the pom file and all your project is cleaned. - change version of dependencies because of bugs in initially selected version : with Maven, just change the pom... There's a lot of reason the move to Maven. Good Luck ! Regards ! Eric Lewandowski -Message d'origine- De : Marco Mistroni [mailto:[EMAIL PROTECTED] Envoyé : dimanche 30 septembre 2007 05:56 À : Maven Users List Objet : convincing Workplace to use Maven hello all, i am a big fan of maven (i have been using it since approx 3 years..).. and i'd like to use it @ my work, where we are still using ant and coding most of the tasks manually.. but i'd need good arguments, as now many IDEs( especially IntelliJ) offer lot of capabilities such as code coverage, identifying code smells etc so, i'd need good arguments for pushing for Maven2 @work can anyone help me out? thanks and regards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: convincing Workplace to use Maven
Hi, well it really depends on to whom you want to sell it. Some ideas: - easy to generate IDE project files (or use native IDE import/sync with IDEA 7): estimate the time to setup the environment for a new developer in the current setup vs. mvn eclipse:eclipse - don't reinvent the wheel: count the hours you spend maintaining your ant scripts and tasks vs just using the plugins provided by Maven - governance: provide a company wide repo with the jars that are approved to be used - site: greatly improves inner and inter project communication, helps to leverage reuse across projects We've sold it together with subversion (the successor of cvs) as the successor of ant. An additional advantage was to greatly reduce build time: while previously everything had to be built from scratch, the build process is much more modular now. Building one module now uses prebuild (SNAPSHOT) jars of the dependant modules instead of compiling them. Of course that could also be achieved with ant, but it was easy to attribute that to Maven :-) =Stefan -- reuter network consulting Neusser Str. 110 50760 Koeln Germany Telefon: +49 221 1305699-0 Telefax: +49 221 1305699-90 E-Mail: [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] Steuernummern 215/5140/1791 USt-IdNr. DE220701760 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
