I've migrated the clone on GitHub to Maven.

You can see a proposed structure here:

https://github.com/mathieucarbou/Socket.IO-Java

What is gained by using Maven?

• transitive dependencies
• modules (not one big bloated jar with everything)
• easier to generate sources, javadoc, reports and so on
• no script to write: instead of writing copy, javac, ... just say compile, test, deploy
• easier deployment and release system: our project needs to depend on socket.io so we expect a serious tagging, snapshot and versionning scheme
• project descriptor
• deployable centrally in maven repo
• Maven becomes a real standard in project development since it 'standardize' the structure of a project
• A maven project is also directly understood by IDEs: no need to setup build path, libraries, ...
• The project does not need to contain jars (=> small git repo)
• Build path separation: test classpath and runtime classpath are isolated
• [...]
• Greater momentum: Ant is now legacy and not moving fast ahead. Maven is forging ahead fast and there's a potential of having lots of high-value tools around Maven (CI, Dashboard project, IDE integration, etc)
• scoping dependencies

See also: - http://radio-weblogs.com/0112098/stories/2002/12/06/whyIUseMaven.html - http://maven.apache.org/benefits-of-using-maven.html