Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Reorganize the project to mostly-Maven conventions #16
I began looking at the existing POM files, and after pulling on the initial thread I ended up unravelling the entire garment and ended up replacing the entire build system with a modern Maven-based implementation. There are a few new test failures, the causes of which I've not yet tracked down but which are almost certainly caused by resource files no longer being where the test suite assumes they are. See the rather lengthy commit message for details!
I can deploy the packages to Central (see #1) with or without these changes, so it's entirely up to you whether or not you integrate them. By the time this pull request has been posted, you should have received my signed contributor agreement at your published address.
There were files moved for more than one reason:
Were there other file moves that you don't like that I've forgotten about?
I'd argue that one of the main benefits of Maven is uniformity: I can (and do) routinely work with Maven projects without any prior knowledge of the projects and can always find everything I need right away as they follow a set of well-understood conventions. Each time you tell Maven to do something against those conventions, you lose a small piece of those benefits. I could have pushed this even further with the XOM build (creating separate modules for the optional dependencies), but that would have required breaking historical compatibility, so I didn't.