Unless I've missed something (or maybe I'm reading between the lines) there
seems to be an assumption that we're moving to Maven.

I've never used Maven, though I do from time to review whether or not it
will be useful to me.  So far I haven't seen a use-case where it actually
adds benefit (above and beyond anything I can put together in Ant), but
that's just in my little world.

My understanding is that once you go down the Maven route it is very hard to
get out of it if you decide it's not for your project.  It also seems like
quite a big dependency to have for building your project.  At the moment all
I need is ant and an SVN client.

I know there are a lot of Maven fans out there, so I'm open to giving it a
chance, but I think we should all be committed to it.

So before this project considers moving to Maven I would like to see:
- a volunteer to be Maven champion
- a list of benefits that it will add to the project
- a list of disadvantages
- a getting started overview for people working on pivot
- a getting started overview for people working with pivot
- an overview of how people working on pivot would work day to day
- an overview of how people working with pivot would work day to day

Then we should vote on it.

Thoughts?

Cheers,
Chris

Reply via email to