On 13/02/2010, at 6:59 PM, Kay Kay wrote: > +1 on the 'maven'ization. > > As far as I see - there is not any special cross goal dependencies coming up, > in the HBase lifecycle so this should not be a problem. >
Yep, I think HBase definitely is a standard project type that fits the intent that Maven was originally designed for. There's no question, if a project has a non-standard requirement, then going down a Maven path could be tricky. But HBase is nice and simple, and standard. > As I had suggested earlier - the best course of action, for a smooth > transition would be - > > * directory changes as necessary for mvn > * modify build scripts. > . > . > . > * working pom.xml in place and build scripts /ivy removed. sounds good, so keep the ivy part tracking the Maven changes (basically a side-by-side approach) until a final switch? It might be worth setting up a branch too for visibility prior to a commit/merge to trunk (I don't recommend a merge under SVN for sure, GIT probably handles that way better). Paul
