On 3/18/07, Adam Hardy <[EMAIL PROTECTED]> wrote:
I want the software house where I work to go to the next level with maven from
where we are at the moment, which is a case of gross under-utilisation. We use
maven as a glorified ant script to run tests and build jars.
There are several other projects in-house which have not been mavenised but
could be, there is a great opportunity to implement maven's release cycle
management, and the need for configuration, filtering and profiles is huge.
No-one on the project management side though has much interest in all the
reports, the QA, test coverage, continuous integration or release management. I
have a meeting with a chief PM lined up and I have to present hard data in terms
of developer-days saved if we put maven into place.
What is the best way to nail down potential future gains from mavenization into
easily grasped cost savings? Are there any good stories out there on this sort
of stuff? Does anyone have some experiences they would like to share in this
area?
Some basic questions to ask:
All your non-maven projects are supported by whom?
Do they have to hand craft the scripts to support the build process?
Can you move people across projects without having to re-train them on
the build process?
If you chose Maven and enjoy the benefits of "convention over
configuration", does that free up someone to spend their time moving
to the next level?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
