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 r
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 th
ne-
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
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
al
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
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 cove
